
How we work
No account managers, no mystery timelines. Here’s exactly what happens on a project, start to finish. Including long after it’s handed over.
Before we start
A conversation and a written scope. Nothing gets designed until we both know exactly what we’re making.
The first conversation
We start with a conversation about your goals, your audience, and what success actually looks like. Not a questionnaire but a call, where we ask what the work has to do and who it’s for. You leave knowing whether we’re a fit. We leave knowing what we’d be making.
Clear scope, clear expectations
Before anything gets made, you get it in writing: what we’re delivering, what it costs, when it’s due, and what we need from you. One price, agreed up front. If something changes mid-project, we talk about it before it moves the number.
While the work is underway
Set calls you can rely on, visible progress, and tools chosen to fit your project.
Regular check-ins
We book calls at a set cadence and we keep them. You see the work in progress rather than a reveal at the end, and if something is drifting you hear it from us early, while it’s still cheap to change. That’s the entire point of talking every week rather than every month.
The right tools for the job
We pick the platform and the tools that fit your project, and we tell you why. Often that means WordPress, because you can actually run it yourself afterwards. Sometimes it means something else entirely.
Reviewed before it ships
We check the work the way the people using it will: on real devices, with real content, by someone other than whoever made it. Then we walk you through it before anything goes live.
After it ships
Handover is a milestone, not an exit. The same two people stay reachable.
Handed over properly
Files, accounts, domains and licenses all end up in your name, not ours. You get a short walkthrough of anything you’ll be running yourself, written down as well as said out loud. The work is yours to take anywhere.
Kept running after launch
If the project needs keeping, we keep it: hosting, security, backups, measurement. You get the price before you agree to anything. Same two people picking up, not a ticket queue.
Caleb and Stacey bring deep expertise in system administration, which means they don’t just build things. They make sure they run smoothly, scale smartly, and stay secure. They are the kind of developers who improve every layer of the project and every stage of the process.
Senior Software Developer
What we need from you
A project works when both sides do their part. Here’s ours, and here’s yours.
Someone who can decide
One point of contact who can approve work. When one person can say yes, the schedule holds.
Your material, or a plan for it
Words, photographs, logos, product information. Material sets the pace, so we’ll tell you exactly what’s needed and when.
Replies within a week
We move at the speed of the slowest answer. A week’s turnaround on feedback keeps the dates we agreed honest.
Questions we get asked
If yours isn’t here, ask us directly. We answer questions whether or not they turn into a project.
A full website is usually six to ten weeks from kickoff, and most of that variation comes from how long content takes to arrive. Smaller pieces, such as a landing page, a campaign or a single feature, run from a few days to a few weeks. You get real dates in the scope before we start, not a range.
One agreed price for the scope we write down, not an hourly meter. What it lands at depends on how much we’re making and how much of it is custom. Tell us what you have in mind and we’ll give you a number before you commit to anything.
One person who can make decisions, your material or a plan to get it, and replies inside about a week. That’s genuinely the whole list, and it’s set out in full just above this.
You do. Files, accounts, domains and licenses are in your name and handed over at the end. We don’t hold anything back as leverage, and you can take the work to someone else whenever you like.
You email us and one of us looks at it. If it’s ours, we fix it. If it sits with a host, a plugin or a service you pay for elsewhere, we’ll say so plainly. Then we either sort it out or point you to whoever can.
Your site sits on a server we set up and look after ourselves. Updates go on every month and the site is checked after, backups run daily and off-site, certificates renew on time, and we scan for anything that shouldn’t be there. Every site gets a development copy as well, so new work is tried there before it reaches the live one. One price a month, and you email us direct.
We work that out together on the first call, before anyone spends money. If it’s a fit, you’ll hear what we’d do and what it takes. If someone else suits it better, we’ll say who.
Yes, and a good share of our work is exactly that: one bug, one new feature, an afternoon of changes. Small jobs skip the phases above and get a straight estimate instead.
Happily. We take finished designs and build them, and before we start we’ll flag anything in the file that won’t survive a real browser or a real content editor.
Often. We’ll look at what’s there first and tell you plainly whether it’s worth keeping, improving, or replacing, including when the honest answer is that it’s fine as it is.
Not every project is a full build
The phases above describe a full build from scratch. A lot of what we do is smaller than that: a bug on a site we didn’t make, one new feature, a design handed off to someone else’s developer, an email campaign that needs setting up, a logo that needs a proper set of files.
Those don’t need phases and we won’t pretend they do. Tell us what you need and we’ll tell you what it actually takes.
Sound like a fit?
Tell us what you’re working on. We’ll give you an honest answer about whether we’re the right team for it. No commitment either way.