How we work
From first messageto handover
Here’s what happens at each stage of a project, what we’ll need from you, and what you’ll have at the end.
Stages of a project
1EnquiryYou getA reply with our first questions
You getA reply with our first questions
You
Send us what you have: a brief, some designs, a link to the code or just a description.
Us
Read it properly and reply with questions, or tell you if it isn’t something we do.
2CallYou getA shared picture of the work
You getA shared picture of the work
You
Tell us the background: who the client or users are, what’s fixed, and who makes decisions.
Us
Ask about the things that change how we’d build it, like integrations, data, deadlines and who owns what.
3Scope and quoteYou getA written scope and quote
You getA written scope and quote
You
Read the scope and correct anything we’ve got wrong.
Us
Write down what’s included, what isn’t, what it depends on, and the price or estimate.
4SetupYou getEverything ready to start
You getEverything ready to start
You
Give us access to the code, hosting and services, and tell us who our contact is.
Us
Set up somewhere to build and test, and join your chat or email.
5BuildYou getWorking software, a piece at a time
You getWorking software, a piece at a time
You
Check progress, answer questions and make the decisions only you can make.
Us
Build in stages you can review, with short written updates. If something falls outside the scope, we say so before doing it.
6Review and launchYou getThe live site or application
You getThe live site or application
You
Test it against what we agreed, and give the go-ahead to launch.
Us
Fix anything that doesn’t match the scope, run our launch checks, then put it live and keep an eye on it.
7HandoverYou getNotes and access your team keeps
You getNotes and access your team keeps
You
Join a walkthrough if you’d like one, and confirm who owns each account.
Us
Write down how to set it up, deploy it and what it relies on, and hand over access.
8After launchYou getMaintenance, or nothing further
You getMaintenance, or nothing further
You
Decide whether you need ongoing help.
Us
Keep looking after it under a maintenance arrangement, or step away.
Everything in writing
Each stage leaves something written behind, so you can check what was agreed and pass it on.
- EstimateBefore you commit · See a template
- ScopeWith the quote · See a template
- Progress updatesWhile we’re building
- Change requestsWhen the scope changes · See a template
- Launch checklistBefore going live · See a template
- Handover notesAt the end · See a template
In your tools
- Code
- Your GitHub, GitLab or Bitbucket, with changes you can review before they’re merged.
- Tasks
- Your issue tracker if you have one. If not, we’ll set up a simple shared board.
- Conversation
- Your Slack, Teams or email. Decisions get written down there too.
- Review
- A test site where you can see changes in a browser, set up in a way that suits your hosting.
- Passwords and keys
- Shared through a password manager or your hosting’s secret settings, never in chat.
Questions
How soon can you start?
It depends on what else we’re working on at the time. We’d rather tell you honestly when we reply than promise it here. If you have a fixed date, mention it in your first message.
Do you work on-site?
We work remotely. If an in-person meeting would genuinely help, mention it when you get in touch.
Who owns the code?
You do. The code we write for you is yours, and we keep it in your accounts wherever we can.
What if the requirements change during the project?
They usually do. We let you know as soon as we spot a change, tell you what it means for cost and time, and wait for your decision.