A custom web application replacing the disconnected spreadsheets a US professional services firm ran on: customers, tasks, workflows, permissions and reporting in one place.
A US professional services firm was running on spreadsheets that had outgrown themselves: customer data in one, tasks in another, reporting rebuilt by hand each month, and a growing amount of work whose only record was that somebody knew about it.
We replaced the set with a single custom web application. Customer records, tasks, internal workflows and reporting live in one place, and the processes the firm actually follows are encoded as workflows rather than as conventions people are expected to remember. Work is assigned automatically where the rule is clear, and triggers send the email or WhatsApp notification that used to be a manual chase.
User and role management decides who sees what, which matters more in professional services than in most sectors: client confidentiality is often contractual, and a spreadsheet shared with the team is a spreadsheet shared with everyone on it. The reporting dashboard reads live data, so the monthly report is a page rather than an afternoon.
The sales side sits in the same application rather than bolted alongside it: enquiries enter a pipeline, each stage has an owner, and the system shows what is stuck and where. Third-party integrations connect the tools the firm already pays for, so the platform joined the existing stack instead of replacing all of it.
Spreadsheet replacements fail when the new system is slower to use than the sheet it replaced, so the test we held this to was whether the people who lived in those spreadsheets preferred the application. The code, the data and the accounts are the client's.
What this project actually used. We pick a stack to suit the problem and the people who will maintain it, so this is not the same list on every project.
Each page below covers the process, the stack and the questions buyers usually ask about that kind of work.
A storefront and the operations behind it built as one system: orders processed, stock synchronised and customers updated on WhatsApp without anyone re-entering anything.
Read the case studyUnited Arab EmiratesA custom ERP for a UAE trading and distribution business: sales, purchasing, stock, invoicing and customer records in one system, with the repetitive work between them automated.
Read the case studyUnited KingdomWhatsApp enquiries, follow-ups and status updates handled automatically for a UK services business, with every conversation attached to a CRM record instead of living on someone's handset.
Read the case studyTell us where your situation differs and we will tell you which parts of this would carry over and which would not — including where we think you need less than this.
Talk to us