Most custom software development is sold to companies starting something. This is written for the other kind — a business that already has customers, staff and revenue, and a process holding it together that was never designed. Usually it is a spreadsheet somebody maintains by hand, a shared inbox doing the work of a system, and one person who knows why the numbers reconcile. It works until that person is on leave.
The first job is not to build. It is to find where the money actually leaks. That is rarely where it feels like it leaks — the loud problem is usually a symptom of a quiet one two steps upstream, and building software against the loud one produces an expensive tool nobody opens. So the engagement opens by walking the real process with the people who run it, and the output of that is a written scope naming what gets built and, as importantly, what does not.
What we build is ordinary in the best sense: it does the thing every day, it survives the input somebody types wrong, and it keeps working when the person who commissioned it has moved on. Where AI genuinely helps — reading documents nobody has time to read, classifying the exceptions queue, drafting what a human then approves — it goes in. Where it does not, we say so, and you get plain software that works.
If the honest answer is that you do not need custom software, you will hear it on the call. A configured off-the-shelf product beats a bespoke build for most standard problems, and the difference is often a year and most of the budget. The work worth commissioning is the part that is genuinely specific to how your business makes money.
Scope
Sit with the people who actually do the work, not only the person who signs. The spreadsheet they really use is never the one in the presentation, and the workaround they invented three years ago is usually load-bearing. What comes out is a written map of the process as it runs today, including the parts nobody was proud enough to mention.
What is being built, what is explicitly out, which milestone each payment attaches to, and who signs off on each. Scope is agreed in writing before a number is quoted, and changes move through a written change order. A scope that can drift in a phone call is a budget that drifts with it.
It runs on a Tuesday afternoon when the warehouse is busy and somebody pastes a date in the wrong format. Real permissions, real audit trail, error messages that say what to do next, and the reconciliation that used to live in one person's head written down where it can be checked.
Document extraction, exception triage, classification, drafting that a person approves before it counts. Each of those is added because it removes a specific hour from a specific week, never because it is on the roadmap. Anything irreversible keeps a human gate, and that gate does not come out later because it slows the flow.
The repository is yours from the start and IP assignment is signed before work begins. Handover is the deploy pipeline, the runbook, and a rollback path that has been tested rather than described. The measure of the work is whether a developer you hire next year can pick it up without calling us.
Ask what they would refuse to build. A custom software development company that accepts your whole list without argument is pricing effort, and the larger your scope the larger their invoice — nothing in that model rewards telling you a module is unnecessary. The other checks worth running: is the scope written before the price, is billing attached to milestones you can verify, and do you own the repository from the first commit rather than at final payment.
The label covers work that is not comparable, so read the scope rather than the name. Custom software development services here run from walking the existing process, through a written scope, to a build that faces daily use, to a handover with the deploy pipeline, runbook and signed IP assignment. What is not included: an open-ended retainer, or a feature agreed in a call without a written change order.
Usually not, and that is the right question to ask first. A configured product beats a bespoke build for anything standard — accounting, payroll, CRM, ticketing — and choosing bespoke there costs you a year and most of the budget for a worse result. Custom earns its place where the process is genuinely specific to how your business makes money, or where the integration between three products you already pay for is the actual problem.
There is no rate card, because the price follows the scope and the scope follows the process walk. Once scope is written it is a fixed fee against that document, billed at milestones as verified work lands, never by the hour. The honest thing underneath: the largest cost lever is what gets cut, not the rate. Removing a module nobody will open saves more than any negotiation over price.
That is most of the work. A business that already runs has an ERP, an accounting package, a warehouse system and four spreadsheets, and the valuable software usually sits between them rather than replacing any of them. Where a system has a real API we integrate against it; where it does not, we say early what that constrains, because discovering an integration is impossible halfway through a build is the expensive way to learn it.
That is the intended outcome, and the handover is built for it from the start rather than assembled at the end. You hold the repository, the IP assignment, the deploy pipeline and a runbook written for somebody who was not in the room. No licence we control sits underneath your product, and there is no dependency that makes leaving expensive. A build you cannot walk away from was mispriced.
Often no, and you should be suspicious of anyone who answers otherwise before seeing the process. AI is worth adding where a human is currently reading documents to move them into a system, triaging an exceptions queue by eye, or drafting the same message with small variations. It is not worth adding to a workflow that already runs correctly, and putting it near anything irreversible without a human gate is how a working process becomes an incident.
Founder · he answers these himself
Fixed fee, scoped in writing before anything starts. No hourly billing, no verbal scope.
Related: AI consulting and implementation · AI workflow automation · Healthcare software development · Hire vs engage a firm: a cost model · Payment reconciliation software · How we work