A software team that builds what it scopes
Intuites is a full-stack web and mobile development company. The engineers who estimate your project are the ones who build it, and every promise below is written into the scope.
Four numbers we put in every scope
Six reasons, in plain terms
You own the code, the repo and every account
Source lives in your GitHub or GitLab from day one. Cloud, domain and app-store accounts are opened in your name, not ours.
No lock-in
A written scope with a number before any work
You see what will be built, by when and at what cost, with the assumptions written down beside the figure.
Fixed scope, fixed price
A demo every two weeks, a written update every week
Working software on a staging URL at the end of each sprint, not a slide deck at the end of the project.
Weekly update
Tests, CI and a runbook ship with the code
Every build has automated tests, a deployment pipeline and a plain-language document on how to run and change it.
We say when custom software is not the answer
If an off-the-shelf product or a no-code tool would serve you better, we say so and point you to it.
The engineers who scope the work build it
No hand-off from a sales team to a delivery team you have never met. The person on the first call is on the last one.
Four stages from first call to live product
Each stage ends in something you can open and judge. If the scope is wrong at stage one, you find out at stage one.
01Discover and scope
1–2 weeksA kickoff workshop, user and role mapping, a review of any existing code or data, and a written scope with a fixed price, a dated plan and the assumptions stated.
You receive
- Written scope and fixed quote
- User flows and role map
- Technical approach and stack
- Risks and open questions
02Design and prototype
2–3 weeksWireframes become a clickable Figma prototype that we test with five real users. The design system that falls out of it is what the build follows exactly.
You receive
- Clickable prototype
- Usability test findings
- Component library
- Accessibility checklist (WCAG 2.2 AA)
03Build in two-week sprints
6–16 weeksWorking software on a staging URL at the end of every sprint, a written update every Friday, and automated tests and a deployment pipeline from sprint one.
You receive
- Staging demo every 2 weeks
- Weekly written update
- Code in your repository
- Test suite and CI pipeline
04Launch and support
30 days includedRelease to production or the app stores, monitoring and alerting switched on, a runbook handed over, and 30 days of support. Most clients then move to a monthly retainer.
You receive
- Production release
- Monitoring and backups
- Plain-language runbook
- Retainer proposal, if wanted
What 6 clients say about working with us
In their own words.
“The written scope matched what was delivered, line for line. We had a staging link to test every two weeks, and the final invoice was the number on the scope.”
“They rebuilt our dispatch portal without a day of downtime. The hand-over runbook meant our own developer could make changes the week after launch.”
“One Flutter codebase, both app stores, and the reviews went through first time. The weekly written update was the part our board liked most.”
“We came with a spreadsheet and left with a booking system our clients use every day. Everything lives in our own GitHub and AWS accounts.”
“The QuickBooks and Stripe integration we had been quoted six months for elsewhere shipped in seven weeks, documented and load-tested.”
“Two years on a monthly retainer. Security patches land before we ask, and small features are turned around inside the agreed response time.”
Start with a 15-minute call
Tell us what you need to build. You get a written scope with a number on it, or an honest answer that we are not the right fit.