Why is there no feasibility score out of a hundred?

Because it would be invented. A score like that implies the page has assessed your systems, data and team; it has read ticked boxes. What it shows is how many of your ticks each job matched: a fact, not a claim.

Why is there no pound figure against each one?

Same reason. A saving depends on hours, headcount and cost, and none of those are on this page. The ROI calculator asks for exactly those: put the top job into it and you get a number with your own inputs behind it.

How is the list actually ordered?

What you ticked counts most, at twelve points a match. Naming a department nudges it by fifteen. Headcount only counts for jobs several people repeat. Then effort is subtracted: hard if you want something small this month, lightly if you said a real project.

Where do these jobs come from?

Every one is already named on the solutions pages, which is the list of work we actually do. Nothing in the catalogue is an aspiration or a category borrowed from somebody else's website, which is why it is twenty-two jobs rather than two hundred.

Why does every result carry a limit?

Because a list where everything sounds easy is a sales page. The limit usually decides whether a job is worth starting: document extraction needs an exceptions queue, a voice agent needs an escalation path, and connecting two systems that disagree spreads the disagreement faster.

The top result is far too big for us right now.

Then change the appetite answer to something small this month, which weights effort far more heavily, and the order will shift towards the ones that finish in days. If it still looks wrong, the ranking is a starting point and not a verdict.

Is anything saved or sent?

No. It runs entirely in your browser. No account, no email box, nothing recorded, nothing to delete afterwards.

Find your first automation

Tick what actually eats your week. It ranks twenty-two jobs we genuinely do, and tells you what each one touches, roughly what it takes to build, and the limit printed beside it.

FREE
NO EMAIL
THREE MINUTES
NO INVENTED SCORES

22 JOBS IN THE LIST. THE ORDER CHANGES AS YOU TICK.

Which department loses the most time? Leave it off if you are not sure.

Which of these actually happen in your week? Tick as many as are true.

How much change can you take right now?

How many people does this touch?

Only counts towards the jobs several people repeat. It does not move the ones one person does once a month.

What to hand over first

Six of 22, ranked by how many of your own ticks each one matched, with roughly what it takes to build and the limit printed beside it. The pound figure comes from a conversation about your job.

01
START HERE
A week or two
The CRM stops needing to be typed into
Records created and updated from the conversation that produced them: the email, the call, the meeting.
Where it stops: It will not invent context nobody captured. If a deal moved on a phone call nobody logged, it stays where it was.
TOUCHESEmailCalendarCRM
Matched 1 of the things you ticked, in sales.
02
A week or two
Two systems that were never designed to talk, connected
The copying job nobody owns, done once properly, so the same information stops being typed in twice.
Where it stops: If the two systems genuinely disagree about what a customer is, connecting them spreads the disagreement faster.
TOUCHESBoth systemsWhatever sits between them
Matched 1 of the things you ticked, in operations.
03
A week or two
The status update nobody has to sit in a meeting for
Assembled from the systems that already hold it and sent round, so the recurring meeting either shortens or stops needing everybody in it.
Where it stops: It replaces the information half of a meeting. It does not replace the arguing half, and some meetings are mostly that.
TOUCHESProject toolsCRMEmail or chat
Matched 1 of the things you ticked, in operations.
04
A few days
Duplicates merged and fields mapped, once
The clean-up that has to happen before anything else is worth automating, done properly rather than by hand.
Where it stops: A one-off, not a system. Without the job above it, the mess starts building again the same week.
TOUCHESCRM
Matched 1 of the things you ticked, in sales.
05
A week or two
Every enquiry scored before it reaches you
Fit and urgency worked out on arrival, with the reason written down, so the morning list is ranked rather than chronological.
Where it stops: It ranks. It cannot tell you the quiet one is the buyer, and occasionally the quiet one is.
TOUCHESWeb formCRMEmail
Matched none of your ticks. It is here on how much it usually returns for what it takes to build.
06
A few days
Invoice chasing that happens without you remembering
Reminders sent on a schedule, with the tone matched to the customer: gentle for the reliable ones, firmer for the repeat offenders.
Where it stops: It will not decide when to stop asking and start escalating. That call stays yours.
TOUCHESAccounting softwareEmail
Matched none of your ticks. It is here on how much it usually returns for what it takes to build.

WORKED EXAMPLE, NOT YOUR ANSWERS

A four-person practice ticks two things: the same details typed into two systems, and a report somebody assembles by hand. They want something small this month and have not named a department.

The CRM stops needing to be typed into

A week or two, with its limit printed beside it: it cannot invent context nobody captured, so a deal that moved on an unlogged call stays put. Switch the appetite to a real project and the heavier jobs climb, document extraction among them.

THREE THINGS IT NEVER INVENTS

A feasibility score out of a hundred
A pound figure it has no inputs for
A job nobody here has actually done

All three are standard in tools like this, and all three would be numbers nobody measured.

How the order is decided

Why is there no feasibility score out of a hundred?: Because it would be invented. A score like that implies the page has assessed your systems, data and team; it has read ticked boxes. What it shows is how many of your ticks each job matched: a fact, not a claim.
Why is there no pound figure against each one?: Same reason. A saving depends on hours, headcount and cost, and none of those are on this page. The ROI calculator asks for exactly those: put the top job into it and you get a number with your own inputs behind it.
How is the list actually ordered?: What you ticked counts most, at twelve points a match. Naming a department nudges it by fifteen. Headcount only counts for jobs several people repeat. Then effort is subtracted: hard if you want something small this month, lightly if you said a real project.
Where do these jobs come from?: Every one is already named on the solutions pages, which is the list of work we actually do. Nothing in the catalogue is an aspiration or a category borrowed from somebody else's website, which is why it is twenty-two jobs rather than two hundred.
Why does every result carry a limit?: Because a list where everything sounds easy is a sales page. The limit usually decides whether a job is worth starting: document extraction needs an exceptions queue, a voice agent needs an escalation path, and connecting two systems that disagree spreads the disagreement faster.
The top result is far too big for us right now.: Then change the appetite answer to something small this month, which weights effort far more heavily, and the order will shift towards the ones that finish in days. If it still looks wrong, the ranking is a starting point and not a verdict.
Is anything saved or sent?: No. It runs entirely in your browser. No account, no email box, nothing recorded, nothing to delete afterwards.

Carry on next door

Automation ROI calculator

Take the job at the top of your list and put a number on it, with your own hours, headcount and rates.

Open it

Which tool for the job

Once you know which job goes first, this says what it would actually be built with.

Open it

Your job is not in the list

Twenty-two covers the jobs that come up most. The list is short because everything on it has actually been built, and the one you are thinking of is worth twenty minutes with us rather than a lookup.

Book twenty minutes

A chat panel asking to give the renewals job to an agent, the reply that the agent is live with the route worked out and every step logged, a flow of nodes joined by teal threads, and a run log. — One use case, handed to an agent, as a run. The figures are an illustration of a run, not a client's results.

Ran your numbers? Send us the figures and we will come back with a fixed price, or book twenty minutes and talk them through.

Book twenty minutes →Send us the brief

Elsewhere on this site

Each service is its own page. Pricing, the FAQ, the Manchester company page, the free tools and the blog sit alongside them.

Find your first automation

What to hand over first

The CRM stops needing to be typed into

Two systems that were never designed to talk, connected

The status update nobody has to sit in a meeting for

Duplicates merged and fields mapped, once

Every enquiry scored before it reaches you

Invoice chasing that happens without you remembering