Software · 01
Custom software & business systems
Software designed around the way your organisation actually operates, from focused internal tools to customer-facing platforms.
From spreadsheet to system
The same process, with one version of the truth.
Most business systems start as a shared spreadsheet and an inbox. They work until a second site, a new approver or an audit arrives. We model the roles, states and rules first, then build the tool around them.
Scroll sideways to compare before and after →
Before
- 01Copies of the same sheet, and nobody sure which is current
- 02Approvals given in email, phone calls and cell comments
- 03Limits and rules held in people's heads
After
- 01One record per request, visible to the people who need it
- 02Approvals given in the system, by the right role
- 03Rules written down, enforced and logged
Typical deliverables
What a project can include.
The exact package is agreed from your context, risk, timeline and responsibilities. Not every project needs every item.
| Ref | Deliverable | What it contains | You receive |
|---|---|---|---|
| CS-01 | Workflow and requirements model | Process maps, roles and permissions, the data model and acceptance criteria, agreed before build starts. | Document · diagrams |
| CS-02 | Role-based web platform | The application itself: forms, queues, approvals, notifications and an audit trail, with access by role. | Deployed web app · source code |
| CS-03 | Back-office and customer portals | Admin views for your team, and where needed, self-service views for customers or suppliers. | Portal modules |
| CS-04 | Data import and connections | Moving existing records out of spreadsheets, and links to the tools you keep, where in scope. | Import scripts · connectors |
| CS-05 | Deployment and support documentation | Environment setup, an administrator guide and a runbook, so your team can operate what we hand over. | Docs · handover session |
Engagement flow
- BriefWhat the process is and who it serves
- ScopeRequirements and acceptance criteria
- DesignWorkflow, data and screens agreed
- DeliveryBuilt and reviewed in increments
- SupportHandover, training, agreed support
Fit
Is custom software the right answer?
Sometimes it is not. We would rather say so at the start than build something you do not need.
A good fit for
- Manual processes that need a coherent systemRequests, approvals or records spread across spreadsheets, forms and inboxes.
- Legacy workflows ready for modernisationAn older tool that still works, but is hard to change, host or hand over.
- Organisations that need a tailored productWhere generic software forces the team to work around it.
Worth a conversation first
- An existing product already fitsIf an off-the-shelf tool covers the process well, configuring it is usually the better route.
- Nobody owns the process yetSoftware encodes decisions. Someone on your side needs to be able to make them.
Start a conversation
Talk through your requirements. Bring the spreadsheet.
Tell us who uses the process today, where it breaks and what it connects to. We will come back with a proposed scope and the questions we need answered first.