Custom Software
You need it built. We build it, starting with what the system actually has to do.
We build the system and hand it over. Every milestone is agreed in writing before it starts, and you pay one milestone at a time.
We reply within one business day.
Sounds familiar?
- You know what you need built: a system, an integration, an internal tool.
- You have a specification, or a diagnosis, ours or anyone's.
- You want one team accountable from scope to running system.
- Off-the-shelf tools got you this far, and now the workarounds cost more than they save.
- A previous build ran late, and nobody could say what was in scope.
If that's where you are, Custom Software was built for exactly this: taking a defined need to a running system, one approved milestone at a time.
What you get
Whatever the scope, every build delivers three things. The exact deliverables are named in the proposal, so there's never a question about what's included.
A working system
Built to the agreed scope, running in your business, not a demo.
Its documentation
How it works and how to run it, written for the people who will own it, technical or not.
A handover your team can run
Training and monitoring in place, with us on call while it settles.
How the work runs
Scope.
The first milestone locks the specification: what the system has to do, agreed in writing before any code is written. Bring a Blueprint or another diagnosis and it goes faster; we never skip it, because everything after it is built on what it confirms.
Build, milestone by milestone.
The build runs as a sequence of milestones, as many as the scope calls for. Each one is agreed in writing before it starts, delivered as working software you can see and test, and paid when it lands.
Hand over.
The system goes to your team with the training, documentation and monitoring to run it, and we stay on call while it settles in.
We take a small number of engagements at a time.
That means only a few start dates are open at any time, and they go in the order conversations begin. The sooner you reach out, the earlier the date you can hold.
Start the conversationHow pricing works
No two systems are the same size, so the fee depends on what has to be built:
- 01How many workflows the system has to cover
- 02What it has to connect to: existing tools, data and providers
- 03How much existing data has to move, and the state it's in
- 04How many people use it, and from where
One proposal prices the whole build, milestone by milestone. The first milestone locks the specification; each milestone is paid as it lands.
How the engagement is governed
The same four rules on every build, agreed before work starts, so nothing surprises you mid-build:
- 01Scope
- Priced in one proposal before work starts, and locked in detail by the first milestone.
- 02Delivery and payment
- By milestone.
- 03Changes
- Mid-engagement changes are agreed in writing, with their cost stated before they're built.
- 04The carried credit
- If a Blueprint came first and you hired us to build within 30 days of its final presentation, the Blueprint fee counts toward this work.
Common questions
Can you start from the specification we already have?
Yes, and it makes the first milestone shorter. We still run it, because prior work lowers the effort of confirming the specification, never the need for it.
Do we need a Blueprint first?
No. You can hire Custom Software directly. A Blueprint of either kind makes the first milestone shorter; it's never a requirement.
Who owns what you build?
Ownership is defined in the service agreement, and we walk you through that clause before you sign.
Tell us what's slowing you down.
We reply within one business day, and if we're not the right fit, we'll say so.