Our process

How we work with you, and what you receive at each stage.

The build is the quick part. What decides whether a system works is getting the brief right at the start and supporting it afterwards. We start with how your work moves, agree what the software will do, show you the proposed flow, and support it once it is live.

  1. Free operational review

    What happens

    A free 20 to 30 minute review. We look across the whole business, not just one process, to understand where time and money are being lost or put at risk. We identify the main operational bottlenecks and recommend a practical solution. You decide whether to proceed.

    What you receive

    • A view of the whole company: everywhere time and money are threatened
    • A clearer way to manage the things that matter
    • A practical recommendation on what would help, including when an off-the-shelf product would suit you better
    • No obligation to continue
  2. Understand the process

    What happens

    We follow a real job from enquiry to invoice and look at how the work is actually done, not only how it is described, including the workarounds, the re-typing and the spreadsheets that only one person understands.

    What you receive

    • A map of your current process
    • The exceptions and problem points the system has to deal with
    • A clear view of what is in scope
  3. Agree the specification

    What happens

    We agree in plain English what the software must do and what it will not do, and agree which parts come from the configurable foundation and which are built to your requirements. Anything outside the agreed specification is scoped and agreed separately.

    What you receive

    • An agreed specification: what is included, what is built to your requirements and what is not
    • A view of the likely cost, talked through with you
    • Hosting and support arrangements agreed up front
  4. Show the proposed solution

    What happens

    Before anything is built, we show you the proposed flow on example screens built around your own scenario, so you can challenge it and ask for changes.

    What you receive

    • The proposed flow, on example screens built around your own scenario
    • A chance to change the design before building starts
  5. Build and test

    What happens

    We build to the agreed specification. Delivery is one week from the specification being completed, for the scope it describes. Any change agreed when we show you the proposed flow becomes part of the specification, and the week runs from when the specification is complete. You try working stages as they are built, and what we learn feeds the next stage.

    What you receive

    • Delivery one week from the completed specification, for the scope it describes
    • Working stages to try with real examples of your work
    • Your feedback built into each following stage
  6. Roll out and support

    What happens

    People move onto the system in an order that suits the business. Existing records are brought across where that has been scoped. We host and support the system afterwards, and add to it one process at a time.

    What you receive

    • People moved onto the system in an order that suits the business
    • Existing records brought in, where that has been scoped
    • Hosting and support as agreed in the specification

Deliverables are agreed per project. This is the shape of the work, not a fixed package, and the free review comes first with no obligation to continue.

Next step

Start with a conversation about how your business runs today.

The free review is the first stage. You decide whether to go further.