How a project runs
- 4
- Steps, the same every project
- 1 week
- From agreement to first staging link
- Written
- Scope, price, and every change
- Yours
- Every account, from day one
Four steps, the same every time
Select a step to see what happens, what we need from you, and what you walk away with.
We spend 30 minutes on a call understanding the problem and the constraints. Then we write it down: what we will build, what we will not build, a milestone plan with calendar dates, the price, and the payment schedule. You decide with the document in your hands. No pressure to sign on the call.
What we need from you
- The decision-makers on the call, not just a gatekeeper
- Access to any existing systems we need to understand
- The date you need to go live by, if there is one
- Brand assets and content drafts if they already exist
What you get
- A written scope document you keep
- A milestone plan with calendar dates
- A fixed price and payment schedule
A sample build week
Every week follows the same shape. You always know what day something happens and what to expect at the end of it.
Plan
We agree in writing what this week will deliver and what success looks like.
Build
Building starts. Questions go to your named contact and come back the same day.
Build
Continued development. Any scope question gets a written estimate before we act on it.
Test
We test on real devices and browsers, not just a local machine, and fix what we find.
Demo
Staging link updated. Written note of what changed. Feedback window open until Monday.
Weeks repeat until launch. The scope document names exactly how many weeks.
How we work together
The practices that make a project feel predictable instead of stressful.
One channel, every week
One shared channel, one written update every Friday. No status meetings, no chasing for updates. You always know where things stand.
Full visibility
Code in a repository you own. Staging on a link you can open on any device. Tasks on a board you can see. Nothing is hidden behind 'we're working on it'.
Changes in writing
Anything outside the written scope gets a written estimate before we build it. You approve it, or we skip it. Your invoice matches what you agreed to, line by line.
You own everything
Domain, hosting, analytics, source code, and third-party accounts are all registered in your name from day one. We work in your accounts, not ours.
Predictable timelines
The scope document has calendar dates, not vague estimates. If something changes the timeline, we tell you in writing before it slips, not after.
A fix window in writing
Every project ships with a 30-day fix window. Anything we built that breaks after launch gets fixed at no extra charge. In writing, in the contract.
Everything that matters is in writing
Before any work starts you have a document with the scope, timeline, price, and payment schedule. Every change, every addition, every fix window is added to that document, not agreed verbally and forgotten.
What if requirements change mid-project?
We write up a change request with the impact on scope, timeline, and price. You approve it or we do not build it. The original scope and price do not change without your signature.
Who owns the code and accounts when we finish?
You do, from day one. Code goes into a repository in your name. Third-party accounts are opened or transferred to you before launch, not after.
What does the fix window cover?
Anything we built that does not work as the scope described. The 30-day window starts on launch day and is stated in the contract.
How do I know the project is on track?
Every Friday you get a staging link with the latest build and a written note of what changed. The project board is always visible to you. No update meeting needed.
Tell us what you need
Answer a few questions about your project and we reply within one business day with next steps and, where possible, a price range.