Internal Platforms & Operational Tooling

Custom Software

We build the internal systems that replace a team's spreadsheets, email threads and PDFs. Scope is written down before the build starts, including what the first release leaves out, and the code is handed over with it.

How We Run a Custom Software Project

  1. 1
    Map the workflow

    We walk through the handoffs, spreadsheets and reporting your team maintains by hand, and agree which of them the first release replaces.

  2. 2
    Specify and architect

    We write the specification: data model, access rules, integrations, and an explicit list of what the first release excludes.

  3. 3
    Build and hand over

    We build in reviewable increments, then transfer source, infrastructure configuration and documentation so your team can operate it.

  4. 4
    Support what ships

    We fix defects and extend the system under an agreed arrangement. Ongoing support is optional and priced separately from the build.

Spreadsheets vs. a System

The question is not whether the current process works. It is what happens when the person who maintains it is away.

AspectSpreadsheets and PDFsA Built System
Record of workSpreadsheets and email threadsOne system with an audit trail
AccessWhoever has the fileRoles and permissions, set deliberately
ReportingRebuilt by hand each timeGenerated from the same records
IntegrationsManual re-entry between toolsDocumented interfaces between systems
HandoverKnowledge held by one personDocumented, with source and config transferred

Frequently Asked Questions

Describe the Workflow

Bring the handoffs, access rules and recordkeeping your current tools struggle to meet. Build work is quoted to scope.