Our process
No black boxes. A demo every week.
Every project follows the same five stages, with a decision point at the end of each one – so you only commit to the next step when you've seen the last.
At a glance
Five stages, five decisions
- 01
1–2 weeks
Discover
- 02
1–3 weeks
Design
AI-assisted - 03
4–10 weeks
Build
A live demo every week.
AI-assisted - 04
1 week
Launch
- 05
Ongoing
Scale
Stage by stage
What happens, what you get, what we need
Each stage ends with a decision gate. You never pay for a stage before approving the one before it.
01 · 1–2 weeks
Discover
- What happens
- Workshops, user and competitor research, scope and a technical plan.
- What you get
- A product brief, a clickable prototype of the core flow and a fixed quote.
- Your role
- Two or three workshops, plus access to data and stakeholders.
- Decision gate
- Approve the scope and quote – or walk away owning the brief and prototype.
02 · 1–3 weeks
Design AI-assisted
- What happens
- UX flows, UI design, a design system and user tests.
- What you get
- Tested high-fidelity designs and a build plan.
- Your role
- Review sessions, with feedback within 2 working days.
- Decision gate
- Sign off the designs.
03 · 4–10 weeks
Build AI-assisted
- What happens
- 1-week sprints, AI-assisted coding with engineer review, and QA.
- What you get
- A live demo every Friday, a staging link and a task board you can see.
- Your role
- A 30-minute weekly demo and quick answers on priorities.
- Decision gate
- Feature-complete sign-off.
04 · 1 week
Launch
- What happens
- Security review, performance tests, and store submission or deployment.
- What you get
- Your live product, monitoring, handover docs and credentials.
- Your role
- Final acceptance and launch communications.
- Decision gate
- Go-live approval.
05 · Ongoing
Scale
- What happens
- Free post-launch fixes, then an optional retainer for analytics, new features, AI improvements and live ops.
- What you get
- A monthly report with metrics and a recommended roadmap.
- Your role
- Share business priorities so we focus on what moves your numbers.
Communication
You'll always know where things stand
Shared channel
Slack or WhatsApp, answered during working hours.
Live task board
Linear or Jira, open to you anytime.
Friday demo
30 minutes, recorded, every week of the build.
Monthly founder review
Progress, risks and budget with a ZARX founder.
Change and payment
Change is normal. Surprise invoices aren't.
- A fixed quote per stage, with payments tied to milestones.
- New ideas go into a change log with a cost and time estimate before any work starts.
- You can swap features of equal size at no extra cost.
Quality gates
Nothing ships without passing these
- Code review on every change
- Automated tests on core flows
- Accessibility check
- Security review (OWASP)
- Performance budget (Core Web Vitals)
- Client acceptance
Your side
What we need from you
- One decision-maker
- Brand assets and content
- Access to accounts and data
- Timely feedback – within 2 working days
FAQ
Questions, answered.
How long does a typical project take?
Most MVPs take 8–14 weeks end to end: 1–2 weeks of discovery, 1–3 weeks of design, 4–10 weeks of build and a launch week. AI pilots take 3–4 weeks; audits and design sprints one to three. After discovery you get a written plan with dates for each stage, and the weekly demo shows whether you're on track.
What do you need from us to get started?
One person who can make decisions, your brand assets and any existing content, access to the accounts and data the project needs, and feedback within two working days during design and build. That's it. If you don't have brand assets or research yet, we can help create them as part of discovery.
What if our requirements change mid-project?
Change is normal. New ideas go into a change log with a cost and time estimate before any work starts, so you decide with the numbers in front of you. You can also swap a planned feature for a new one of equal size at no extra cost. Nothing outside the agreed scope is billed without your written approval.
Do you offer support after launch?
Yes. Every build includes free post-launch fixes for bugs in what we delivered. After that you can choose an optional monthly retainer covering monitoring, analytics, new features, AI improvements or live ops, with a monthly metrics report – or take everything in-house with our handover documentation and recorded walkthrough.
What if we need to pause?
You can pause at the end of any sprint. We'll write down where things stand, merge and document the work so far, and agree a restart date. Because code lives in your repository and stages are paid by milestone, pausing doesn't strand your work or your money. Restarting may need a short ramp-up depending on how long the pause lasts.
Can we bring our own developers?
Yes. Your developers can join our sprints, review our pull requests and take over parts of the build. We agree who owns what at kickoff, use your repository and tools, and keep the weekly demo for everyone. Many clients use this to hand the product over gradually to an in-house team.
How do milestone payments work?
Each stage has a fixed quote, and payments are tied to milestones you can verify – usually an advance to start, a payment at a mid-build demo and the rest at launch acceptance. The exact split is agreed in your proposal. You never pay for a stage before you've approved the previous one.
What if the project runs late?
You'll know early, because the weekly demo and task board show progress against the plan. If we're slipping, we say so straight away with the reason and options: adjust scope, add capacity or move the date. Delays caused by our own estimates don't cost you extra; changes you request are handled through the change log.
Let's build
Start with a Discovery Sprint. Decide with a prototype in hand.
Tell us what you're making. A founder replies within one working day with next steps, a rough timeline and a budget range.
NDA on request. You own the code.
