Offer
Your worst spreadsheet, rebuilt as software in 30 days
Pick the one workflow that costs you the most time. We scope it properly, then ship a real application your team logs into, at a fixed price against a written scope.
Start with the workflow that costs you the most
Tell us what the process is and what it currently runs on. A senior engineer reads it and replies with either questions or a straight answer that we are not the right fit.
- Discovery
- £500–£1,500
- credited against the build if you proceed
- Build
- £8,000–£25,000
- fixed price against a written scope
- Care plan
- £200–£600
- per month, optional, cancel any time
What this is
Almost every business runs on one process that has outgrown the tools holding it together. A spreadsheet that four people edit and two of them have their own copy. A WhatsApp group where jobs are assigned and then lost. An inbox that is functioning as a database. Everyone knows it is costing hours a week, everyone has a workaround, and nobody has time to fix it because fixing it sounds like a six-month project with a consultant attached.
This offer exists because it is not a six-month project. One workflow, built properly, with your team logging into it, is roughly thirty days of work when the scope is genuinely fixed and the foundations are already built. We are not starting from an empty repository each time: authentication, roles, permissions, audit logging, exports and file handling are a spine we reuse, and that is where the timeline comes from.
The commercial shape is deliberately unfashionable. No subscription, no per-seat licence, no platform you rent from us forever. You pay a fixed price for a defined outcome, you own the code and the data, and if you want us to keep hosting and maintaining it there is an optional monthly plan for that. If you do not, you can take it to any competent developer.
What this is not: a SaaS product you are being sold a seat in, and not an AI project. It is ordinary, well-built custom software that does one job properly, which is the thing most businesses actually need and almost nobody is selling them.
You will recognise some of these
- A spreadsheet that has become critical, and someone maintains a second copy because the first one keeps breaking
- Jobs, approvals or requests assigned in a WhatsApp group, with no record of who agreed to what
- The same information keyed in twice because two systems do not talk to each other
- A weekly report that takes someone half a day to assemble by hand
- No reliable answer to "what is the current status of that", without asking three people
- Off-the-shelf software you pay for and use ten per cent of, because it was built for a different business
- A process that only works because one long-serving person holds it together in their head
What is included
- A paid discovery session where we map the workflow as it actually runs, not as the process document claims
- A written scope: every screen, every role, every rule, agreed and signed before development starts
- The application itself, built on a reusable, well-tested foundation
- Import of your current live data from the spreadsheet or system it lives in now
- Training for your team, and documentation written for them rather than for developers
- Deployment to hosting you own, with backups and monitoring configured
- The source code, in your repository, from the first commit
- A defined support window after launch for the things that only surface in real use
What is not included
Stated as plainly as the inclusions. A fixed price only means something if the boundary around it does.
- Native iOS or Android apps. This is a web application, which works in a phone browser without an app store review, an annual developer account or a release cycle between you and a bug fix.
- Migrating years of archived records. Importing the live data you work from is included; a decade of historical files is a separate piece of work with its own price.
- A second workflow. The thirty days buys one, and the discipline of that is most of why the date holds. The next one is quoted separately and runs faster.
- Rebuilding logic that a system you already pay for owns. Accounting, payroll and statutory filing stay where they are, and we integrate with them.
- Anything found after the scope is signed. It becomes a change order with its own price and its own effect on the date, agreed before it is built rather than absorbed quietly.
How the 30 days run
- 01
The scoping call
Paid, and the most important hour of the engagement. We walk the workflow end to end with the people who actually do it, find the exceptions everyone forgot to mention, and establish what would genuinely change if this were software. You leave with a written scope and a fixed price whether or not you proceed.
- 02
Week one
Data model and core screens. The foundation is already built, so the first week goes into the shape of your records and the rules around them rather than into plumbing. You see something you can click by the end of it.
- 03
Weeks two and three
The workflow itself: the statuses, the permissions, the notifications, the awkward cases. You get a working environment throughout and we expect you to use it, because feedback while something is half-built is worth ten times more than feedback at handover.
- 04
Week four
Your real data imported, your team trained, hosting and backups configured, and the application handed over running. Then a support window for the things that only appear when twelve people use it on a Monday morning.
Tell us which workflow it is
A short description of the process and what it runs on now is enough to get a straight answer on whether this fits.
Why the discovery call is paid
A free scoping call is a sales call, and both sides know it. It is short, it stays shallow, and it produces an estimate wide enough to protect the supplier, which is a number nobody can plan against. Charging for it changes what the hour is for.
A paid session is long enough to walk the process properly, ask the awkward questions and find the exceptions, which is where fixed-price projects actually go wrong. You leave with a written scope and a real price that we will honour, and that document is yours whether you build with us, build with someone else, or decide not to build at all.
It is credited in full against the build if you proceed. So for the client who goes ahead it costs nothing, and for the client who does not it buys a specification they can take anywhere. The only person it is bad for is a supplier hoping to win work on a vague estimate.
What "fixed price" has to mean to be worth anything
A fixed price is only meaningful if the scope is fixed with the same precision, otherwise it is a number with an argument attached to it. So the scope names the screens, the roles, the rules and the integrations, and anything not on that list is not in the price.
When something new comes up mid-build, and it usually does, it becomes a change order: a described piece of work with its own price and its own effect on the date, agreed before anyone builds it. That is less comfortable than absorbing it quietly and it is the only version that stays honest, because absorbed changes are paid for somewhere, normally by the parts of the build that quietly get less attention.
The other half of the bargain is ours. If we misjudged the effort on something inside the agreed scope, that is our cost, not a variation. That risk is what you are paying a fixed price to transfer.
You own it, including the parts suppliers usually keep
The code lives in your repository from the first commit. The hosting account is yours. The database is yours, and the data in it can be exported without asking us. There is no licence, no per-seat fee and no proprietary layer that stops another developer taking over.
This matters more than it sounds. The most expensive position a small business can be in is depending on software it does not own, from a supplier it has outgrown, with data it cannot easily extract. Everything about that arrangement is good for the supplier.
If the optional care plan is what you want, it covers hosting, monitoring, backups, security updates and small changes. If it is not, we hand over and you are genuinely free to leave.
Common questions
Is 30 days realistic, or is that a marketing number?
It is realistic for one workflow with a genuinely fixed scope, and that qualifier is doing real work. It is possible because we are not starting from nothing: authentication, roles, permissions, audit logging, exports, file handling and the deployment setup already exist and are reused. What gets built for you is your data model, your screens and your rules. Where a workflow turns out to be larger than that, we will say so at scoping and quote it as a bigger project rather than promise thirty days and miss.
What does it cost?
Discovery is £500 to £1,500 depending on how complex the workflow is, and it is credited in full against the build if you go ahead. The build is £8,000 to £25,000, fixed against the written scope, with the position inside that band set by how many screens, roles and integrations are involved. The care plan is £200 to £600 a month and is entirely optional.
Why do you charge for the scoping call?
Because a free one is a sales call and produces an estimate too vague to plan against. A paid session is long enough to walk the process properly and find the exceptions that break fixed-price projects, and you leave with a written scope and a real price. It is credited against the build if you proceed, so it costs nothing if you go ahead, and if you do not you keep a specification you can take to any developer.
What happens if we want changes halfway through?
It becomes a change order: written down, priced, and its effect on the date agreed before anyone builds it. We will not absorb it silently, because absorbed changes get paid for out of the quality of everything else in the build. Small clarifications where we misread the scope are ours to fix at our cost, and that distinction is set out in the scope document rather than argued about later.
Do we own the code?
Yes, completely. It is in your repository from the first commit, the hosting account is in your name, and the data is yours to export at any time. There is no licence fee, no per-seat charge and nothing proprietary that would stop another developer picking it up. If you leave, you leave with everything.
Is this an AI product?
No. It is a conventional web application: forms, records, permissions, notifications and reports, built properly. Most operational problems are not machine-learning problems, they are the absence of a system, and dressing that up as AI would add cost and risk to solve something that ordinary software solves reliably. If a genuine use for automation appears later, it can be added to an application that already exists.
What if we need more than one workflow?
Start with one, and pick the one that hurts most. A single workflow shipped in a month builds trust on both sides and gives you something real to judge us on, which a large multi-workflow programme does not do until it is far too late to change your mind. The second one is faster than the first because the foundations, the hosting and the working relationship are already in place.
What happens after the 30 days?
There is a support window included for the issues that only surface once the whole team is using it, because the first fortnight of real use always finds something. After that you can take the optional care plan for hosting, monitoring, backups and small changes, bring it in-house, or hand it to another developer. All three are genuinely available, which is the point of you owning it.
Related
The capability pages behind this work, and the other offers in this set.
Which spreadsheet would you kill first?
Describe the workflow and what it runs on today. If it is not a fit for a fixed-scope build, we will tell you that rather than sell you one.
- 01A senior engineer reads it. Not a form queue, and not an account manager.
- 02We reply either with questions or with a straight answer that we are not the right fit.
- 03If it looks like a fit, a technical call with the person who would actually run the delivery.
- 04Then scope, effort and risk in writing, before anyone signs anything.