Fixed-scope project
A clearly defined product or feature set, delivered to an agreed scope, timeline and price.
- Best for new products and well-defined builds
- Fixed quote after discovery
- Milestone-based delivery and sign-off
OUR APPROACH
A clear process.
No surprises.
We follow a proven, transparent way of working: understand the problem first, agree the plan in writing, then build in two-week sprints so you see working software early and often. Here is exactly what that looks like, and what you can expect from us at every step.
Freediscovery call to explore your idea
2 weeksper sprint, each ending in a demo
Your IPfull source code and ownership are yours
Overlapping hourswith the US, Canada and Australia
THE PROCESS
Six steps from idea
to a product people use.
Every project is different, so timings are typical rather than fixed. What never changes is how visible the work is to you.
- 01Free · 1–2 calls
Discover
We start with a conversation about your goals, your users and the problem worth solving, not with technology.
What happens
- A free discovery call, under NDA if you need one
- We map users, goals, constraints and risks
- An honest view on what to build first, and what not to
What you get
- A short summary of what we heard
- A rough estimate range and recommended next step
Your part
- An hour or two of your time
- Any existing documents, designs or code
- 02About 1 week
Scope & plan
We turn the conversation into a clear, written plan, so everyone agrees on what will be built before work begins.
Example: a detailed statement of work behind our email platform buildWhat happens
- Features broken down into a prioritised backlog
- Architecture and technology choices explained
- Milestones aligned to your launch dates
What you get
- A statement of work with scope, milestones and deliverables
- A fixed quote, or a monthly team plan
Your part
- Review and sign off the scope
- Name a decision-maker on your side
- 032–4 weeks
Design
We make the idea tangible before it is expensive to change, so you can click through the product and test it with real users.
What happens
- User flows and wireframes
- Visual design in your brand
- A clickable prototype to test with users
What you get
- Design files and a prototype in Figma
- A reusable design system for future screens
Your part
- Feedback on each design round
- Access to users for quick tests, where possible
- 042-week sprints
Build in sprints
We build in focused two-week sprints. At the end of each one you see working software, not a status report.
Example: continuous releases over more than two years on a consumer appWhat happens
- Sprint planning against the prioritised backlog
- Code review on every change
- Automated deployment to a staging environment
What you get
- A live demo at the end of every sprint
- A staging link you can try anytime
- Sprint notes covering progress, risks and next steps
Your part
- About an hour per sprint for the demo and review
- Quick answers to open questions
- 051–2 weeks
Test & launch
We test properly, launch carefully and stay close while real users arrive.
Example: separate testing and production environments with automated releasesWhat happens
- A QA test plan covering every role and key journey
- Performance and security checks
- App-store submissions and production go-live checklist
What you get
- A production release with monitoring in place
- Release notes and admin guides
Your part
- User acceptance testing and final sign-off
- Store and domain accounts in your name
- 06Ongoing
Support & evolve
Launch is the beginning. We help you learn from real use and keep improving what matters most.
Example: a platform we continue to run, monitor and improveWhat happens
- A warranty period for fixes after launch
- Monitoring, updates and security patches
- A roadmap shaped by real usage
What you get
- Fast fixes and regular improvements
- Optional monthly support or a dedicated team
Your part
- Share feedback and priorities
- Decide what to build next with us
WAYS TO WORK WITH US
Choose the model
that fits your stage.
Start with one model and switch as your needs change. Many clients begin with a fixed-scope project and continue with support.
Team extension
Our engineers join your team, follow your processes and work alongside your people.
- Best for scaling an existing product
- Monthly plan per engineer or team
- Works in your tools, rituals and codebase
Ongoing support
A monthly retainer to keep your product healthy, secure and improving after launch.
- Best for live products
- Monitoring, fixes, updates and small features
- Predictable monthly cost
HOW WE WORK, WEEK TO WEEK
Close collaboration,
whatever your time zone.
Sprint rhythm
- Sprint planning every two weeks
- Short async updates during the sprint
- A live demo and review at the end of each sprint
Tools you already use
- Jira or ClickUp for planning and tracking
- Slack or Microsoft Teams for day-to-day communication
- Figma for design and prototypes
Time zones
- Overlapping working hours with the US, Canada and Australia
- Meetings scheduled in your working day
- Progress that continues while you sleep
ENGINEERING STANDARDS
Built to last
- Separate development, staging and production environments
- Code review on every change
- Automated build and deployment pipelines
- Automated tests for critical journeys
- Error and performance monitoring from day one
- API documentation for every service we build
WHAT YOU OWN
Everything, from day one
- Full source code in a repository you control
- Intellectual property assigned to you
- Technical documentation and deployment scripts
- Admin guides and a handover session
- All accounts and credentials transferred and rotated
- NDAs signed as standard before detailed discussions
QUESTIONS
Frequently asked
How much does a project cost?
It depends on scope. After a free discovery call we give you either a fixed quote for a defined scope, or a monthly cost for a dedicated team. You will always know the cost before work starts.
What if our requirements change?
They usually do, and two-week sprints are designed for that. We re-prioritise the backlog together at each sprint. On fixed-scope projects, changes are estimated and agreed in writing before we act on them.
Do you sign NDAs, and who owns the code?
Yes, we sign NDAs as standard before detailed discussions. The source code and intellectual property belong to you, and we hand over everything at the end of the engagement.
Can you take over an existing product?
Yes. We start with a review of the codebase, infrastructure and open issues, then agree a plan to stabilise, upgrade and extend it. Several of our case studies began this way.
How do we work across time zones?
We keep overlapping working hours with clients in the US, Canada and Australia, schedule meetings in your working day, and share written updates so nothing waits on a call.
What happens after launch?
Every project includes a warranty period for fixes after launch. After that, you can continue with a monthly support plan, a dedicated team, or take the product fully in-house with our handover.
YOUR NEXT CHAPTER STARTS HERE
Have an idea?
Let’s make it happen.
Tell us what you’re thinking. We’ll start from there.