How do you estimate a project?
After a short discovery we break the scope into features, estimate each one and share the plan with its assumptions written down. Big unknowns get a small, paid discovery first, so the estimate rests on facts.
Process
Sketch to live in four moves.
A calm, predictable way to build software: small steps, working demos every week, and no surprises at the end.
How a project runs
Discover
We map the users, the risks and the one metric the product has to move.
- Scope & risk map
- Success metric
- Estimate & plan
Design
Clickable prototypes, tested with real users before production code.
- Clickable prototype
- User testing
- Design system
Build
Two-week sprints with a working demo on a live link every Friday.
- Two-week sprints
- Friday live demos
- Code review & QA
Launch & grow
Deploy, validate, monitor — and keep improving after go-live.
- Deploy & monitor
- Validation docs for GxP
- Continuous improvement
Inside a sprint
A week with us.
Every week follows the same rhythm, so you always know what’s happening and when you’ll see it.
- Mon
Plan
Agree the week’s goals from the backlog, together.
- Tue
Build
Design and code in small, reviewed changes.
- Wed
Review
Every change is code-reviewed and tested before it merges.
- Thu
Test
QA on a staging link; fixes go in the same day.
- Fri
Demo
A live demo on a real link, plus a short written update.
Every project
Always included.
No add-ons, no premium tier — this is simply how we work.
A live demo every Friday
Working software on a real link — not slides.
A weekly written update
What shipped, what’s next, and any risks, in plain words.
A board you can see
The same task board our engineers use, open to you.
Review and tests on every change
Nothing merges without a second pair of eyes and passing checks.
Documentation as we go
Decisions and set-up notes written down while they’re fresh.
One point of contact
A tech lead who knows your product and answers directly.
Before you ask
Common questions.
What if the scope changes?
It usually does. New ideas go into the backlog, and we show the impact on time and cost before anything changes. You decide what goes in.
Can you work with our in-house team?
Yes. We can own the whole build, or work alongside your developers with shared code review, standards and tooling.
What happens after launch?
We monitor, fix and keep improving under a support plan — or hand over cleanly to your team with the documentation to run it.