Software shaped around your business, not the other way round

The most common failure in custom software is scope: an organisation tries to replace everything at once, the project takes two years, requirements drift, and the thing that goes live no longer matches the business. We work in the opposite direction.

In discovery we map every process end to end and attach two numbers to each: how many person-hours a month it consumes, and how much money leaks through it in errors, delays or missed opportunity. That gives a ranked list. The first release addresses the top one or two items only, and it goes live within eight to fourteen weeks. It earns its budget before we build anything else.

This has a second benefit. By the time release two is specified, your team has used release one for two months and knows far more precisely what they actually need — which is almost never what they said in the first workshop, and that is not a criticism of them. Nobody specifies software well in the abstract.

For most business systems our default is a Node.js or Laravel API with PostgreSQL underneath and a React or Next.js front end. PostgreSQL is deliberate: business systems are relational, they need real constraints and transactions, and they need to answer reporting questions years later. Choosing a document database because it feels modern is one of the more expensive mistakes we get called in to unwind.

Where a client's team is PHP-strong we build in Laravel or CodeIgniter 4 and make it genuinely good — proper service layers, migrations, queues, tests. The framework matters far less than whether the people who will maintain it can read it.

Everything is designed around a few non-negotiables. Every table that matters has an audit trail: who changed what, when, and what the previous value was. Every workflow that involves money or approval has a state machine rather than a boolean flag, so you can always answer where something is and who is holding it. Every integration is idempotent and retry-safe. And every environment — development, staging, production — is created from the same infrastructure definition, so "it worked on staging" is a meaningful statement.

Nobody replaces everything, and they should not. Tally is an excellent accounting package and your CA knows it. Your plant historian works. Your bank has its own portal. Custom software succeeds by fitting between these, not by pretending to replace them.

We have built integrations with Tally Prime, SAP, Oracle, Zoho, Salesforce, Marg, Busy, and a long list of bespoke systems written by someone who left in 2011. The pattern is consistent: a thin adapter service that speaks the legacy system's language on one side and a clean, documented API on the other, with a reconciliation report so finance can verify what synced.

That reconciliation report is not optional. Every integration will fail sometimes — a network drop, a locked file, a schema change nobody announced. The difference between a robust system and a fragile one is whether failures are visible and recoverable or silent.

The graveyard of custom software is full of technically correct systems nobody uses. Staff continue with the spreadsheet because it is faster, and within four months the official system holds stale data and everyone stops trusting it.

The fix is mostly in design. Screens must be faster than the thing they replace, measured with a stopwatch, not asserted. Fields must be in the order people actually fill them, which we learn by watching. Data that the system already knows must never be asked for again. Bulk entry, keyboard navigation and sensible defaults matter more than aesthetics for a user doing this two hundred times a day.

We also run pilots with the most sceptical user we can find rather than the most enthusiastic. If the person who hates change can complete their day faster on the new system, adoption takes care of itself.

Order and dispatch management for distributors and manufacturers — capturing orders from every channel, applying the right price list, checking credit, allocating stock, planning dispatch and pushing invoices into accounting.

Production and quality systems for plants — shift logs, batch records, quality checks, downtime capture with reason codes, and the daily and monthly reports that currently take somebody four hours each morning.

Service and field operations — job allocation, engineer scheduling, spare parts, warranty validation, service history and a customer-facing status page that removes half the phone calls.

Project and contract management for construction, EPC and consulting firms — milestones, billing, retention, subcontractor bills, and the physical-versus-financial progress view that most spreadsheets do badly.

Compliance and document systems for regulated sectors — controlled documents, version history, sign-offs, expiry alerts and an audit trail that satisfies an inspector without a week of preparation.

You own the source code, the database and the infrastructure from day one. We work in your repository and your cloud account. There is no runtime licence, no encrypted module, and no dependency on a component only we can rebuild.

We document as we go: a data dictionary, an architecture overview, integration specifications, deployment and rollback runbooks, and a recorded walkthrough. The test we hold ourselves to is that a competent engineer who has never met us could take over the system in a fortnight. We have handed systems over on exactly those terms and it costs us nothing we are not comfortable with.