Skip to content

We would like to use Google Analytics cookies to count page visits and clicks, so we can see which pages are useful. Privacy notice

ROODTSQUARED

How we work

Five stops from the problem to a live, improving solution. Here is what happens at each, and what it looked like on one real project.

  1. 01

    Diagnose

    Find the commercial or operational problem.

  2. 02

    Design

    Shape the right solution.

  3. 03

    Build

    Create and connect the tools.

  4. 04

    Implement

    Fit the solution to the client's team and systems.

  5. 05

    Improve

    Measure performance and refine the solution.

The worked example on this page:PyroPlanner, live since 21 august 2026

01 Diagnose

Find the commercial or operational problem.

It starts with a discovery call: a conversation about what is getting in the way, not a pitch. Then we look at how the work actually runs today, with the people who run it, and at the systems and data already there. The point is to find the real problem and the cost of leaving it, before any technology is mentioned.

What you receive

  1. A plain-English statement of the problem and what it is costing.

  2. A view of the systems, hand-offs and workarounds involved.

  3. A clear yes or no on whether we can help, and which services it touches.

02 Design

Shape the right solution.

We shape the smallest solution that fixes the problem properly, decide what to connect, what to build and what to leave alone, and write it up as a scoped proposal. This is where scope and price are set, so you decide with the whole picture in front of you.

What you receive

  1. A scoped proposal for a first phase, with what it includes and what it depends on.

  2. The price for that phase, fixed before work starts.

  3. A design of the solution your team can read: what it does, where it sits, who uses it.

03 Build

Create and connect the tools.

We build it, connect it to your systems, and test it against real cases rather than tidy examples. You see it working early, and what you see shapes what comes next.

What you receive

  1. A working build you can use before it is finished.

  2. Integrations to your existing systems, documented.

  3. Testing against your real data and real edge cases.

04 Implement

Fit the solution to the client's team and systems.

Going live is a change for people, not just systems. We switch on with the team, train them on the real thing, keep a fallback for anything that fails, and stay close for the first weeks.

What you receive

  1. A go-live with the team, not a hand-over by email.

  2. Training and documentation your people will actually use.

  3. A fallback and a named owner on each side for anything that goes wrong.

05 Improve

Measure performance and refine the solution.

A live solution is the start of the useful part. We watch how it is used, where it is slow or avoided, and what the business needs next, and we extend it in phases that are each scoped and priced the same way as the first.

What you receive

  1. A review of what is working and what is not, from the run data.

  2. The next phase, proposed and priced before it starts.

  3. A partner who runs it with you, or a clean hand-over to your own team.

How scope and pricing are set

Prices live in proposals, not on this page, because the right first phase is different for every business. The way we get to a price is the same every time.

  1. The discovery call comes before any proposal.

    It is a conversation to find out whether we can help. If we cannot, we say so and, where we can, point you somewhere better.

  2. Diagnosis before design.

    We do not quote for a solution until we understand the problem. Where that takes real work, the diagnosis itself is scoped and priced as a small first phase.

  3. A first phase, scoped and priced before it starts.

    The proposal says what is included, what it depends on, and what it costs. You decide with the whole picture in front of you.

  4. Phases, not an open tab.

    Each extension is proposed and priced the same way, so the next step is always a decision rather than a surprise.

  5. Running it is a choice.

    We can host, monitor and improve what we build, or hand it over cleanly to your own team. Either way, you own the code and the data.

The first stop is a conversation.

Bring the problem that matters most. We will tell you straight whether we can help.

Book a Discovery CallSee the services

Talk it through with us. No obligation to go any further.