Book a callFree plan

Services

Three ways to engage. A clear starting point.

Find the cause. Build the fix. Keep the agreed work running. We set the scope, price and meaning of done before work starts.

Compare the three ways to work with us

Which one fits.

You don't need the assessment first if the problem and what you need are already clear. Its terms set how long each one takes.

Operations Assessment

Find the cause and choose a fix.

When it fits
Right when you see the same problems come back, but not why.
You receive
A map of the current work, ranked fixes and a priced build plan.
Discuss an Operations Assessment
What is in the assessment
What we do
We follow an agreed process through its people and systems. We check what evidence there is. Then we rank the fixes.
Deliverables
  • Workflow map
  • Ranked fixes
  • Cost estimates where the facts back them up, with what we assumed
  • Priced build plan
Finished when
You have the workflow map and the ranked fixes, with what we assumed. You also have a priced build plan.
Timing
10 to 15 working days, once scope and system access are set.
What we need from you
Agree the scope with us. Give us the system access we need. Do both before the assessment starts.

The assessment stands on its own, and the plan is yours to act on, with us or without us.

Build

Put the agreed fix in your tools.

When it fits
Right when the problem is clear and you’re ready to change how the work runs.
You receive
Tested steps in your own tools, with written guides and training.
Discuss a defined Build
What a Build includes
What we do
With your team, we set the details needed, the steps, the owners and the rules for choices. Then we build the agreed links and repeat actions. We test them against the checks you approved. Last, we hand over the written steps and training.
Deliverables
  • Approved needs
  • Steps that work
  • Test results
  • Guides and training
Finished when
The steps pass the checks you approved, and your team has the guides and training.
Timing
30 to 60 days, based on scope, system access and how fast you sign off.
What we need from you
Give us the agreed access, and sign off on needs and choices. Bring in the team that will take the handover.

While we set the scope, we confirm that your tools and each link will work. If a change needs a tool you don’t already have, you hear what it is and what it costs before we build. Scope changes are priced and approved before work goes on. Your tools and what we build in them stay yours.

Managed Operations

Keep the agreed work running.

When it fits
Right when the work matters too much to leave one person to watch it.
You receive
We watch the work your agreement covers. We fix issues and send a report each month.
Discuss Managed Operations
What Managed Operations covers
What we do
Monthly, under a service agreement. We watch the covered work and sort issues by how urgent they are. We work through problems with the people who own them. We report on what ran and what needs attention. When a change is worth making, one approved fix at a time can be in progress. It stays inside the written change limit. Each month we review the key numbers, what changed and what comes next. We set in writing what we cover, how fast we respond, who does what and the change limit. One named person answers for it. When the work is steady and your team can run it, we talk about a smaller scope or a written handover. Your tools stay yours.
Deliverables
  • Watching and fixing
  • Problem log
  • Changes you agree to
  • Report each month
Each month
A report on what ran and what needs a fix. It stays within the cover set in writing.
Timing
It runs each month. A service agreement sets the terms.
What we need from you
The agreement sets what we cover. It sets how fast we respond. It also sets how many changes we make each month.

This is defined coverage for the covered workflows, not general IT support or unlimited changes.

Not sure where to start?

Get a free plan first. You can use it with us or on your own.

Build my free plan

What each one leaves you with.

  • Illustrative example

    Operations Assessment: A ranked problem list

    1. 1. New leads get missed after hours. Owner: front desk. Fix: one shared inbox with a daily check.
    2. 2. Quotes have no next date. Owner: sales lead. Fix: a next step on every quote.
    3. 3. Finished jobs wait for billing. Owner: office. Fix: a weekly billing check.
  • Illustrative example

    Build: A tested handoff

    1. A test lead is sent through the form.
    2. It lands in the shared list.
    3. The named owner gets it.
    4. A next step and a date are set.
    5. Your team runs the same test before handover.
  • Illustrative example

    Managed Operations: What we cover and report on

    1. Covered: new leads, and getting work ready to start.
    2. Each month: what ran, what was held, and what changed.
    3. Issues: who looked at each one, and what happens next.

Made-up examples of the format. Not client work.

What we bring to the work.

Revenue operations is the way leads, customers and work move through a firm. We work on the steps and the people who own them. We work on the tools they use, too.

Three skills run through all of our work.

  • Clear steps

    Set steps, who owns each one, who signs off, and how work gets done.

  • Linked tools

    Links between your tools, so details move on their own. No one types them in twice.

  • Steps that run on their own

    Tasks go to the right person. Reminders, file requests and status notes go out on their own. Alerts go out when something goes wrong.

Work we often do

We often help set up new staff and new customers. We also help with sign-offs to buy and supplier files. And we help keep projects on track, book work, and report on how work runs.

Questions we get.

Do we have to make a free plan first?

No. If you know what needs changing, bring that problem to a call.

Can you help with more leads?

The free plan can help you choose a lead test. We can also discuss how new leads reach your team and get a next step. Any paid work has a scope and price agreed first.

Do we have to replace our software?

No. We start in the tools you already use. If a fix needs another tool, a new plan, or a service that links tools, you hear what it needs and what it costs before we build.

Do we have to start with an assessment?

Not always. It depends on how clear the problem and the needs already are. On the first call we work out which one fits.

How is the work priced?

A fixed price for a written scope, agreed before work starts. How hard the work is, what your tools rely on, and how much support you want move the number. Anything outside the scope is priced and approved on its own before we build it. We don't bill by the hour, and we don't rent out staff.

What happens after the build?

The work comes with tests, written steps and a handover. That way, your team can run it without us. If you want, we can watch it and support it after that. That is a separate agreement.

How do you deal with access to our systems and data?

We agree access, how data is handled and any outside tool with you before work starts. We use only the access each task needs. All we build stays in your accounts.

Who does the work?

One named person runs the work, from the first call to the handover. You always know who answers for it.

What happens when the work is stable?

We check if you still need the ongoing cover. The scope can shrink, or end with a written handover.

See what this looks like in the work itself.

Four examples show what we build and who acts. They show what happens when something is missing.

See the examplesFind your business