01
Discovery
30–45 min call, 1–2 days to confirm scope in writing
Deliverable
A written scope summary and a fit check
What you do
Describe the problem, the deadline, and the budget range honestly
02
Proposal & agreement
2–3 business days
Deliverable
A fixed-price proposal: scope, includes, out-of-scope items, timeline, payment schedule
What you do
Review, ask questions, sign
03
Design & architecture
1–3 weeks, scaled to the package
Deliverable
Wireframes/UI or a technical architecture document, reviewed before production code starts
What you do
Review and approve before build begins — changes are cheapest here
04
Build & check-ins
The bulk of the project timeline
Deliverable
Weekly working builds you can log into
What you do
Test each check-in build, flag anything off-course early
05
Launch & handover
1–3 days
Deliverable
Deployment, admin credentials, full source code, 30-day warranty starts
What you do
Confirm launch, receive handover documents
03 What we need from you
What we need from you
A clear problem statement
Even a rough one. We'll help sharpen scope, but we can't invent the problem you're solving.
A realistic budget range
So we can point you at the right package instead of wasting a call.
One decision-maker
Feedback from a single point of contact keeps check-ins fast; a committee reviewing every build slows the timeline down.
Access to what already exists
Existing systems, brand assets, or accounts we need to build against or integrate with.
Timely feedback at check-ins
The build moves at the speed of the slower of the two of us — usually feedback, not code.
04 How we communicate
How we communicate
K1
Channel
Email and a shared project channel (your preference — Slack or similar) for day-to-day questions.
K2
Check-in cadence
Weekly, at a fixed time, with a working build to review — not a status meeting with nothing to look at.
K3
Response time
One business day for project questions during a live build; retainer clients get the SLA stated in their tier.
K4
Documentation
Scope, decisions, and change orders in writing, in the project channel — not only spoken on a call.
Ready to start the five steps?
Start a project