Six stages, from a free discovery to launch

The most expensive thing in software is not development. It is building the wrong thing carefully, for months, before anyone finds out. Everything below exists to make that less likely.

01

Discovery

Free, and it starts with a short form about your business. Then we sit with the people doing the work and map the process as it actually happens - including the workarounds, because that is where the real rules live. You get a written scope with a cost range.

A written, scoped plan
02

Design

How it works before how it looks. Screens, flows and the data model, reviewed with the people who will use it every day rather than only the person paying for it. Changing a diagram costs nothing; changing a built system costs a fortnight.

Agreed flows and data model
03

Build

Shipped in stages, each one a working thing rather than a milestone on a chart. You see progress as it is built. Nothing disappears into a three-month black box. Real usage tells you things no workshop will, so each slice is built on what actually happened rather than what we assumed in week one.

Working software, in stages
04

Migrate

Its own phase with its own budget, not an afterthought in the final week. We extract, clean and map your existing data, then rehearse the migration more than once before anything goes live.

Your data, in, correct
05

Launch

Gradual where possible. Real users on the new system while the old one stays readable, so nobody is cut off from history while they are still learning. Training for the people who use it, at the point they need it rather than a month before.

Live, with people using it
06

Run or hand over

Rent it and we keep running, supporting and developing it for you. Buy it and you choose: keep us on for support and ongoing development, or take it in-house, in which case we walk your team through the handover.

Your choice, either way
Principles

What you can count on

Buy it or rent it

Buy your software outright and the code and infrastructure are yours. Or rent it as a subscription and we host, run and maintain it for you. Renting is an option depending on the size of the project, and it suits software that needs bug fixes and improvements every month.

We have shipped the hard parts

Checkout and card payments, finance at the point of sale, dealer portals, trade pricing, registration lookups against live vehicle data, and the data migrations underneath them. Already built, already running.

Small releases, early

Something usable early, rather than one big launch at the end. Real usage tells you things no workshop will, and finding out early is the cheapest time to find out.

Written down, in plain English

Scope, decisions, architecture and the reasoning behind them. Documentation for the people who use it and for whoever maintains it after us - including if that is not us.

Pay up front or in stages

Discovery is free. Once it has mapped the work and you commit to the project, payment is taken up front or in stages as the work is delivered.

We run our own products

RampDesk and NearOps are ours, live and supported by us. We live with our design decisions instead of handing them over, which is why we're opinionated about the boring parts.

What we expect from you

Software projects fail from both sides, and it is worth being direct about the client half of it. None of what follows is unusual - most development contracts ask for the same things, usually in smaller print.

One person who can decide. Not a committee, and not someone who has to take every question upstairs. They don't need to be technical, and they don't need to be the person paying. They need to be able to say yes. Where several people have opinions, argue them out and send us one answer. Three that contradict each other, a week apart, is the expensive version.

Access to the people doing the work. Not just the person signing off. The most valuable hour in any build is the one spent watching someone do the job the software is meant to replace. That is where the workarounds surface, and the workarounds are usually the real requirements.

Decisions within a few days. A build stalls on open questions faster than on hard problems. We'll keep the list short and visible so it is never a surprise what we're waiting on. When an answer takes a fortnight, the stage moves out by about a fortnight. That is worth saying now rather than in a revised timeline later, where it would look like our slip.

Your data, and the way in. Exports, logins, the spreadsheet somebody keeps on their own machine, and someone who can tell us what the odd columns mean. Migration is its own stage for a reason, and it cannot start on goodwill.

Honesty about the mess. Every business has processes that are undocumented, data that is inconsistent, and workarounds nobody is proud of. We have never once been surprised by it. Telling us in week one is much cheaper than us finding out in week six.

FAQ

How it works in practice

How much does discovery cost?

Nothing. It starts with a short form about your business and the job that takes the most time, so the first conversation is a useful one. Then we map how the work actually happens and you get a written plan with a cost range, before you commit to anything.

How do we pay for a project?

Discovery is free. Once it has produced a scope and a price and you commit to the project, payment is taken up front or in stages as the work is delivered. Or, depending on the size of the project, you can rent the software as a subscription instead of buying it.

Do you work fixed price or time and materials?

A price for the scope that discovery produces, rather than an open-ended hourly bill. Because discovery maps the work before anything is quoted, the price is based on what the job actually involves instead of a guess with contingency added. And if you would rather not pay for a build at all, you can rent the software as a subscription instead.

Who will actually work on our project?

The people you meet. We're deliberately small, which means you're not handed to a junior team after the sale - a pattern common enough in this industry that it is worth asking every supplier you talk to.

What happens after launch?

Whatever suits you - stage six covers the choice itself. In practice a handover takes a day to a week, depending on how big the system is. We walk your team through the code, the infrastructure and the decisions behind both. And we keep answering questions after the last day.

How do you handle our data during the project?

We work with the minimum we need, use anonymised or sample data in development wherever it is possible, and keep production access limited and logged. Where a project involves personal data we'll agree the specifics in writing before starting rather than afterwards.

Tell us what is slowing you down

A short conversation is usually enough for us to tell you what it would take to fix it. Discovery after that is free.