Process
How we work
A short, repeatable path so you always know what happens next. No big reveal at the end, and no invoice for something you did not agree to.
The path
- Discovery call: goals, constraints, and timeline
- Written proposal: scope, milestones, and investment
- Build with iterative reviews at each milestone
- Launch, handoff, and a clear path for future changes
1. Discovery call
About thirty minutes. You describe the problem, the constraints, and what success looks like. We ask what the site or system has to accomplish and what has already been tried.
This is not a free exhaustive audit and it is not a pressure pitch. Sometimes the honest outcome is that you do not need what you thought you needed, or that we are not the right fit. Both are better discovered now than three weeks in.
2. Written proposal
Everything agreed goes in writing: what is included, what is explicitly not, the milestones, and the investment. If something is uncertain we name it as uncertain rather than burying it.
A written scope protects both sides. It gives you something concrete to approve, and it gives us a clear line for when a new request is genuinely new work rather than something that was always assumed.
3. Build with checkpoints
Work happens in milestones, and you see it at each one. Feedback at the halfway point is straightforward to act on. The same feedback after launch is a rebuild.
You get a link to review real work in progress rather than a slide deck. Between checkpoints you can reach us directly with questions.
4. Launch and handoff
Before launch: redirects mapped, forms tested end to end, analytics confirmed recording, and the site checked on real mobile widths.
After launch: admin access, documentation for routine edits, and a documented way to request changes. Ongoing maintenance is available but never assumed, and you keep full ownership of everything either way.
When scope changes
Projects evolve and good ideas surface mid-build. When a request falls outside the written scope we say so, price it, and let you decide. What we do not do is absorb it quietly and resent it, or add it to a final invoice you never approved.
Common questions
- What happens on the discovery call?
- About thirty minutes describing the problem and constraints. We outline fit, rough shape, and whether a paid proposal makes sense. No obligation and no pressure.
- How do you handle changes mid-project?
- Anything outside the written scope gets named, priced, and decided by you before it is built. No silent additions to the final invoice.
- Do we own the work when it is finished?
- Yes. You get admin access, source files, and full ownership, whether or not you continue with ongoing maintenance.