How we work
Mostly, we listen. Then we build.
Most projects go wrong before anyone writes a line of code: the wrong problem, or the right one in the wrong order. This is how we keep that from happening.
01 / Listen
Listen.
We start with calls, not proposals. We talk to whoever runs the site day to day, not just whoever signs off on it: the editor, the person packing orders, the one answering support email. We look at your analytics and search data, and we ask what you've already tried and why it didn't stick.
A short summary of what we heard, in your words, so you can tell us what we got wrong.
02 / Absorb
Absorb.
Then we go through the site, the tools behind it and the data they share. We follow an order or an article from start to finish and note every manual step and workaround along the way. We also check how fast it loads and how it shows up in search, AI assistants included.
A list of what's actually costing you, ranked by how much it costs, not by how hard it is to fix.
03 / Suggest
Suggest.
We come back with a plan: what we'd do, in what order, what each piece costs and why it's worth it. We'll tell you what not to do, even when it's something we sell, and we'll show you a smaller version if the big one doesn't fit.
A written plan with an estimate for each piece. You decide what goes ahead.
04 / Build
Build.
We design, build and test on a staging copy before anything goes live, so you see it working first. After launch we stay, keeping it updated and working on the next round of improvements.
A site that works on day one, and a team that's still around next year.
Fair questions
Questions to ask any agency. And our answers.
How do you keep things from falling through the cracks?
Every project follows the same written steps. Every change is saved in version history, so we can see what changed and when, and undo it if we need to. Anything significant goes to a staging copy first, and you see it working before it goes live.
Is my site secure?
We only ask for the access a job needs, and we remove it when the job is done. Passwords live in a password manager, never in email. We keep plugins and apps to a minimum and update them on a schedule.
What happens if something breaks?
Every site is backed up automatically. We watch uptime in real time, so we hear about an outage right away, and we run regular health checks on top of that.
How does maintenance work?
It's a monthly retainer with a set number of hours. You know what you're paying for and what it covers.
Who owns my site?
You do. Your accounts and domains are in your name, and we work as users on them. The code we write for you is yours. Every site comes with documentation of how it's built and how it runs.
The next better thing
Tell us what's not pulling its weight. We'll start by listening.
Start a project