A process nobody has built software for
You’ve looked for software that does this. It doesn’t exist.
You know exactly what good looks like. You live with a painful, manual process, or you watch your clients lose time and money to it. You looked for a product and found nothing that fits, or only tools built for companies ten times your size. You know how it should work and how you’d judge it. What you don’t have is someone to put it into software. That’s what we do.
You’ll recognise this.
We see this in construction, real estate, legal, health operations, research, events, finance operations, professional services and sport. The sector matters less than this: someone on your side knows the domain and can say what “correct” looks like.
- The process runs on email chains, paper forms or a spreadsheet.
Someone fills it in on Friday.
- The judgement behind it lives in one or two people’s heads.
- Things get missed between one step and the next.
Finding out what happened takes half a day.
- You’ve explained it to software vendors.
And watched them try to fit it into something it isn’t.
Software nobody has built yet, built around how you work.
You don’t have to describe it in software terms. Tell us about the process: who does what, where it goes wrong, and what good looks like. We turn that into the scope of a first version, in plain English, and the first version is running in one to four weeks.
Then a new version every week. You put it in front of the people who do the work, they tell you what’s wrong, and next week’s work changes to match. Change direction any week, no change fees. Nobody understands a new process from a document alone, so the plan is agreed but never locked.
Research platform · Client, Israel
The proof: 15 PhDs, no engineers.
A research company in Israel had a process no product served. Their scientists had built a pipeline that worked, but it only ran on laptops. Each run took a day or two, and only one person could see the results. Four of them had each built the same tool to browse the results, without knowing about each other.
We didn’t rewrite it. The pipeline was sound; where it ran was the problem. It now runs in the cloud, starting up for each run and switching off afterwards. The results sit in one secured place the whole team can use, with every finding traced back to the paper it came from. And the scientists have somewhere to put the tools they build themselves.
- A day or two per run, on one laptop
Now one shared place for the whole team.
- Four copies of the same tool
Now one, used by all fifteen.
What you get back after scoping.
Free scoping gives you the scope of the first version and how many weeks it takes. You approve the scope before paying anything. The rest follows once you start.
See a sample plan for a fictional construction firm whose site inspections lived on paper.
What gets built is yours, not ours.
The whole product, built to hold up: the screens, the data, the AI where it helps, the servers, sign-in, tests and deployment. In your own GitHub and your own cloud account, in your company’s name from day one. So the process you built is yours, not ours.
What it costs.
- Free scoping: free
You approve the scope before paying anything.
- A version: $5,600CAD $7,900£4,200€4,900
One week of building, ending with something running your people can use. Stop after any week.
- The CTO Hour: $575CAD $800£425€500
Still working out whether to build at all? If you build with us within 30 days, the hour’s price comes off your first week.
- After the version
30 days of bug fixes at no charge, then maintenance in tiers by what is kept running.
Questions.
Can you build custom software for a process in your sector?
Yes, if someone on your side knows the process well and can decide what correct looks like. That person matters more than the sector.
There’s no software for what we do. Is that a bad sign?
Usually not. It often means the process is specialised and the people who know it have never had an engineer to build it with. That’s the kind of product we build best.
Can you automate a manual process we run on spreadsheets and email?
Yes. We start from how the work happens today, keep what works, and build the first version around the step that costs you most.
Do we need engineers on our side?
No. A data, AI or infrastructure person is welcome, but you don’t need software engineers. What you need is someone who knows the process and can join a weekly call.
Tell us about the process.
Share what you have: a description, the forms you use, a sample report, or just a call. We scope the first version, for free. Not sure yet? The CTO Hour is $575CAD $800£425€500, and it comes off your first week if you build with us within 30 days.
Or write: [email protected]