Custom WordPress
Development.
WordPress is still the right answer for a lot of businesses. It stops being the right answer when it's twenty plugins deep and nobody will touch it. We build the version that a team can actually run.
How we actually work on this
Applications, not just brochures
For Seubert & Associates — one of the larger surety brokerages in the US — we built a bid-bond portal on top of WordPress: forms, a reviewer view, and a pipeline that replaced an email thread. WordPress will carry real workflow if it is built like software rather than assembled like a page.
Sites large enough to have an architecture problem
A thousand-page site that barely links to itself is a common and expensive failure, and it is invisible until you measure it. We audit the internal link graph, not just the pages, because on a large site that graph is what decides which pages Google bothers with.
Security and hosting that are actually configured
WAF rules at the edge, sensible caching, and a deploy pipeline instead of a person editing files in production. Most WordPress security incidents are configuration, not zero-days.
Headless, when it earns its keep
Keeping WordPress as the editor and rendering the front end separately is a real option and sometimes the right one. It also doubles the surface area you maintain, so we recommend it when the content model justifies it and not as a default.
The work behind the claim
Not a list of capabilities. The actual builds, the writing that shows the thinking, and the sectors we have done this in before.
Case study
Seubert
An eBonds pipeline for a leading surety brokerage
Case study
Maurice Law
Brand and web for an Indigenous-owned national law firm
The thinking, written up
Sectors we have shipped this in
Insurance & Surety
Law Firms
ManufacturingScoped so you can say no to half of it
Audit what exists
Plugin inventory, theme quality, host configuration and the internal link graph. This is where we find out whether a rebuild is warranted.
Fix the foundations first
Hosting, deploys and security come before features. Building on a broken base is how a site ends up here twice.
Ship in slices
A staging site you can look at from week one, deployed by a pipeline you own, rather than one reveal at the end.
We work from Vancouver, British Columbia. The WordPress work in our portfolio runs from a national law firm in Canada to a surety brokerage in Pittsburgh, so distance has not been the constraint — overlap in working hours has.
Straight answers
Will we be locked into you?
No. It is standard WordPress in a git repository, deployed by a workflow you own. Any competent developer can pick it up, which is the point.
Can you take over a site somebody else built?
Yes, and it is a good chunk of what we do. The first deliverable is an honest read of what you have — including when the answer is that it is fine and you should spend the money elsewhere.
Do you use page builders?
Only where a client's team already relies on one and moving them would cost more than it returns. Left unchecked, builders are how a site ends up slow and unmaintainable.
Start with the teardown,
not the invoice.
Send us your URL and we'll send back what's slow, what search can't see, and what we'd change first. Two business days, free, no call required.