How we work with you.
We agree a useful first version, show you the work as it develops, and check the launch and handover. Scope, responsibilities and significant decisions stay in writing.
Start a conversation
Clear scope, visible progress, honest limits.
Every project is different. Simple websites can move quickly. Web apps, Android apps, automation, hosting, and integrations need more planning. We explain what is realistic before work starts.
- No vague promises
We do not promise results, timelines, or outcomes we cannot control.
- Scope first
We define what is included, optional, excluded, and what changes cost.
- Staged work
You see progress before the end, so feedback can happen while it still helps.
- Launch when ready
We go live when the core work has been checked and the handoff is clear.
The seven steps.
A clear route from first chat to launch, with checkpoints instead of surprises.
First conversation
We talk about your business, the people using the work, and the problem you want to solve.
CheckpointThe goal is understood.
Scope & priorities
We agree the essential features, what can wait, the budget and the information needed to plan delivery.
CheckpointPriorities and dependencies are clear.
Written proposal
The proposal records scope, price, timing and responsibilities. You can review it and ask questions before agreeing to the work.
CheckpointThe written proposal is agreed.
Build in stages
You review working versions as we build, so feedback can shape the next stage.
CheckpointWorking versions are reviewed.
Review & feedback
We review the agreed work together and address defects. Refinements and revision rounds follow the written scope.
CheckpointThe agreed version is ready for launch.
Launch
We check the agreed launch routes and publish the reviewed build. We verify the live pages and record any remaining limitations.
CheckpointThe live release is verified.
Support & handoff
We hand over access and maintenance notes. Ongoing support, response expectations and update work are agreed separately.
CheckpointOwnership and the support path are clear.
Client responsibilities
To keep projects moving smoothly, we rely on you for a few key things.
- Content & assets
Providing text, images, and business information.
- Timely feedback
Reviewing work and giving prompt feedback during staged builds.
- Account ownership
Accessing and owning your domain, hosting, email, and business accounts where possible.
- Final decisions
Making final decisions on wording, legal content, and business claims.
Explicit exclusions
For clarity, here are a few things we do not cover by default.
- Content creation
Legal advice or copywriting, unless agreed upfront.
- Open-ended changes
Unlimited revisions after the agreed scope.
- Marketing
Guaranteed Google rankings or paid ads management.
- Unsafe access
Handling passwords through unsafe channels (e.g. plain email).
Why written agreements matter
A handshake is friendly. A written proposal is professional and protects everyone.
- No surprises
- Everyone knows what to expect: scope, timeline, price, and what is included.
- Change clarity
- If scope changes, we discuss cost and timeline impact before doing the extra work.
- Reference point
- If either of us needs to remember what was agreed, it is written down.
Why discovery matters
For simple websites, we can move fast. For custom systems, discovery prevents expensive mistakes.
- Workflow
- How does your business actually work, and where does it hurt?
- Tools and data
- What systems do you use, what data matters, and what needs to connect?
- Users and risk
- Who will use it, what happens if it breaks, and how will success be measured?
Building the wrong thing is slower than building the right thing carefully.
Let’s find a useful first step.
Tell us what you’re building or what needs to work better.
Start a conversation