Software built around how your business runs.
When no off-the-shelf tool fits, we design and build the one that does: internal tools, portals, dashboards and the integrations between your systems. You own the code, the data and the accounts.
We start with a short scoping sprint that ends in a written scope, screens and a fixed price for the build. You review each stage before the next one begins.
- Starts with
- A scoping sprint, from $3,500, about two weeks
- Build
- From $15,000, fixed after the sprint
- Support
- Optional, from $900 a month
- You own
- The code, the data and every account
- Credit
- The sprint fee counts toward a build started within 30 days
- Led by
- A senior software engineer and technical lead
The case for building your own tool
Most of the time you should buy software. When your process is what makes you different, or no product fits, a tool built around how you work removes the workarounds and keeps the advantage. It only pays if it is scoped first and you own what is built.
Your process stays your advantage
Off-the-shelf tools push everyone toward the same way of working. A tool built around yours keeps what makes you different.
One system instead of five workarounds
Spreadsheets, forms and email chains give way to one tool built for your steps, with the right people seeing the right screens.
You own it
The code, the data and the accounts are yours, not a rented seat whose price can rise. You can change supplier without starting again.
Built in stages you review
A short scoping sprint ends in a written scope, screens and a fixed price. Then you see working versions as they are built, and can stop.
Is this you?
- You run the business on spreadsheets and email chains.
- A product does most of what you need and the missing part costs hours.
- Customers or partners need a portal you cannot buy.
- Your pricing, booking or approval rules do not fit any tool.
- You want to test a product idea with a first version.
Compared with the other ways
Buying is usually right. Here is when it is not.
- Buy a product
- Fastest and cheapest to start. Best when it fits. You adapt your process to it.
- Connect the tools you have
- Often enough when two tools only need to share data. Limited when the process itself is the problem.
- Hire a developer or agency
- Works when you can define the job well. Without a written scope the price is a guess and ownership may be unclear.
- Our Custom Software Development
- A scoping sprint first, then a fixed-price build in stages, with the code, data and accounts yours. It costs more than buying and is only worth it when no product fits.
From the first sketch to a tool your team uses.
Software projects usually fail in the gaps: unclear scope, tools nobody uses, systems that do not connect. We close each gap in turn.
A scope you can sign
We talk to the people who will use the tool, study how the work happens today and write down what it must do.
- Interviews with the people who use it
- A map of the current process and where it hurts
- A ranked feature list, with what can wait
- A written scope and a fixed price for the build
Screens before code
You see and click through every screen before we build it, so changes are cheap and surprises are rare.
- Clickable screens for each key task
- Plain-language descriptions of each flow
- Review rounds with your team
- Your sign-off before development starts
Built in short stages
We build in stages you can try, not one reveal at the end.
- A working version at the end of each stage
- Automated tests on the parts that matter most
- Your feedback built into the next stage
- Code kept in your own repository
Connected to what you already use
The tool reads from and writes to your other systems, so nobody types the same thing twice.
- Links to your CRM, accounting, email and booking tools
- Imports from spreadsheets and older systems
- Clear rules for which system holds the master record
- Logs that show every transfer
Launch without a scramble
We move real data, train your team and keep the old way available until the new one works.
- Data migration with checks at each step
- Hands-on training and a short written guide
- A staged switch-over, not a single cut
- Fixes during the first weeks, included
Yours to keep
The code, the data and the accounts are yours from day one. We do not hold your tool hostage.
- Source code in your own repository
- Documentation another developer can follow
- Hosting and licences in your name
- Optional support, never required
Examples of what teams ask us to build.
These are examples of the shape of the work. They are not client projects and they are not results.
Quote and job tracker
A service business keeps quotes in a spreadsheet and jobs in email.
- Before: quotes retyped into invoices
- Built: one tool from quote to job to invoice
- Check: time from enquiry to sent quote
Customer portal
A firm sends documents and updates by email.
- Before: clients chase for status
- Built: a login where clients see status and files
- Check: status requests per week
Reporting dashboard
A manager builds the weekly report by hand from three systems.
- Before: hours of copying every Monday
- Built: a dashboard that pulls the numbers
- Check: time to produce the weekly report
First version of a product
A founder wants to test an idea with real users.
- Before: an idea and a slide deck
- Built: a small first version with the core flow
- Check: whether real users finish that flow
How a software project runs.
Each stage needs your approval before the next one starts.
Scoping sprint
About two weeks to produce the scope, the screens and a fixed price for the build.
Design and approve
You click through the screens and sign off before any code is written.
Build in stages
We deliver working stages and you review each one before the next starts.
Launch and support
We move your data, train your team and offer optional support.
Every engagement ends with a Delivery Record.
It is the proof that comes with the work: what we agreed, what we delivered, how it was checked, what you own and what we recommend next. You sign it off, or tell us what is missing.
You get one at launch, and an update after the first weeks.
In this service it covers
- Each stage you approved, and the automated tests that passed.
- The source code and documentation, in your own repository.
- The issues found in the first weeks after launch, and how each was fixed.
What a typical engagement costs.
These are the prices and terms from this page, set out as one sheet. Your own scope is agreed in a written proposal before any work starts.
Custom Software Development
- Scoping sprint
- From $3,500, about two weeks
- Build
- From $15,000, fixed after the sprint
- Credit
- The sprint fee counts toward a build started within 30 days
- Support
- Optional, from $900 a month
- Hosting and licences
- Paid by you, in your name
- Ownership
- You own the code, the data and the accounts
- Approval
- Scope waits for your approvalNothing is built until you sign the scope.
Example summary. Prices are in US dollars plus any taxes that apply. Your written proposal fixes the final price.
What is and is not included.
Here is where the service starts and where it stops.
What is covered
- A scoping sprint with a written scope, screens and a fixed build price
- Web applications, portals, dashboards and integrations
- Design, build, testing and launch in stages you approve
- Data migration and training for your team
- Source code and documentation in your own repository
- Fixes for issues found in the first weeks after launch
- Optional support from $900 a month
What is not included
- Any promise of a launch date before the scope is signed
- Hosting, licences and third-party fees, which you pay
- Native mobile apps, unless they are written into the scope
- Work outside the scope, which gets its own quote first
- Marketing the finished software to its users
Common questions
What kind of software do you build?
Internal tools, customer and partner portals, dashboards, integrations between systems and first versions of products. If an off-the-shelf tool does the job, we will say so.
How is the price fixed?
After the scoping sprint you get a written scope and a fixed price for the build. Changes you ask for later are quoted before any work starts.
Who owns the code?
You do, along with the data and every account. It lives in your repository, with documentation another developer can follow.
How long does it take?
The sprint takes about two weeks. The build depends on the scope, and its timeline is part of your written proposal. We do not promise a date before the scope is signed.
Do you build mobile apps?
Web applications that work well on phones are the default. Native mobile apps are possible when the scope needs them and are quoted separately.
What happens after launch?
Fixes for issues found in the first weeks are included. After that, support is optional, from $900 a month, and you are never required to take it.
Tell us what you need.
Tell us what you want built and which systems it needs to work with. A website address helps but is optional. We reply from a person and agree the scope in a written proposal before any work starts.
Services that work with this one.
Each service can be bought on its own. These connect to it, so the work fits together.
Have a tool that does not exist yet?
Tell us what the work involves, who will use it and what it must connect to. We will reply with a scoped proposal.