process
How a project actually runs.
Sprint-based development with a written scope, a live staging link and a fixed review rhythm. You always know which step the build is on.
plan phase
Plan
- 01
Discovery
A call to understand the business, the users and what success actually looks like — before anyone writes code.
- Goals & context notes
- Success criteria
- 02
Planning
Scope, feature list, timeline and budget agreed in writing so there are no surprises in week six.
- Requirements document
- Scope definition
- Written estimate
- 03
UI / UX
Wireframes then visual design, approved before development starts.
- Wireframes
- Design approval
build phase
Build
- 04
Development
Sprint-based build with a live staging link you can open any day of the week.
- Development sprints
- Staging environment
- 05
Testing
Structured QA against the agreed requirements — functionality, responsiveness, performance and security.
- QA report
- Bug fixes
- 06
Client review
A dedicated feedback round where you use the real product and we adjust.
- Feedback round
- Revision pass
launch phase
Launch
- 07
Deployment
Production deploy, domain and SSL setup, analytics wired up, and a handover walkthrough.
- Go live
- Documentation handover
- 08
Support
A support window after launch, then an optional monthly plan for updates and improvements.
- Support window
- Optional retainer
payment structure
Payments follow the work.
50% advance
Secures the slot and starts the build
30% milestone
At the agreed midpoint
20% on delivery
After handover and final review
Exact percentages and milestones vary with project size, duration and client type — and all of it is written into the contract before work begins.
questions
Answers before you ask.
If something here is missing, send the question, and it usually becomes the next entry.
next step
Tell us what you want to build.
Send the idea in a few lines. You get a reply within one working day, a discovery call, and a written proposal with scope, timeline and price, before you commit to anything.