How we work
No black box. You see working software every two weeks.
Here is exactly what happens after you send a brief, what you receive at each step, and how engagements are priced.
- Pay per working milestone
- You own the code and IP
- See it before you commit
- 30-day launch warranty
What you receive, and when
A typical project moves from a first workshop to a launched product in a predictable sequence. Every step ends with something you can review.
Week 1
Discovery
- Kick-off workshop with the people who will build it
- Written goals, users and constraints
Week 2
Scope & architecture
- Scope with assumptions and an estimate
- Architecture and integration plan
Weeks 3–4
Clickable design
- Clickable screens for the key journeys
- Your sign-off before build starts
Every 2 weeks
Build sprints
- A working release on a staging link
- Demo, progress notes and next priorities
Launch
Go live
- Production deployment, monitoring and backups
- Handover documentation and access
After launch
Support & improve
- Fixes, updates and new features on a retainer — or a clean handover
Ways to work with us
| Discovery sprint | Fixed-scope project | Dedicated team | |
|---|---|---|---|
| Best for | Early ideas, modernisation, uncertain scope | Defined products and platforms | Ongoing roadmaps and scale-ups |
| Pricing | Fixed fee, 2–3 weeks | Priced per milestone | Monthly, per team member |
| Team | Lead engineer + designer | Delivery lead, engineers, QA | Engineers who join your rituals |
| Flexibility | Output is yours to use with any vendor | Changes handled through a simple change request | Scale up or down with a month's notice |
Commercial terms, plainly
- How is billing structured?
- An initial deposit, then invoices tied to working milestones you have reviewed.
- Who owns the code?
- Code, designs and accounts transfer to you as each milestone is paid.
- What if requirements change?
- A one-page change request with impact on time and cost, approved before work starts.
- Is there a warranty?
- 30 days of free fixes for defects after launch.
Questions
Procurement questions
How quickly can you start?
Discovery can usually begin within one to two weeks of agreeing scope; we confirm availability when we reply to your brief.
Who will we talk to day to day?
A delivery lead who is also an engineer, plus direct access to the people building your system.
Which tools do you use for communication?
Whatever your team already uses — Slack, Teams, WhatsApp or email — plus a shared board for tasks and releases.
Can we start small?
Yes. A paid discovery sprint gives you architecture, clickable screens and an estimate you can take to any vendor.
Have a system that needs building — or rebuilding?
Send a short brief. A senior engineer will reply with questions or a time to talk.