Project Scope & Pricing

How Projects Are Scoped and Priced

No two operations are the same. A property company handling maintenance requests has a different problem to a dental practice missing patient calls. A restaurant losing booking enquiries on a Friday evening has a different urgency to a trades business whose quotes go cold. The pricing reflects that. This page explains how we approach the work, what projects typically look like, and what they tend to cost.

Start with the free review →

How a project runs

01
Operations review
02
Workflow mapped
03
Pressure points identified
04
Build proposal created
05
Human review & approval

Nothing moves forward without sign off.

06
System deployed
How Pricing Works

What determines the scope

The main thing that drives the cost is how many moving parts are involved. A simple follow up workflow is a short project. A system that handles maintenance requests across multiple channels, notifies contractors, and tracks everything through to completion takes considerably longer.

How many manual steps exist, whether anything needs to connect to existing tools, and how busy the process is every day. All of these affect how long a project takes and what it costs.

The cost of a project almost always reflects how much time it frees up, not how long it takes to build.

Typical scope factors

Number of manual steps

How many handoffs, checks or decisions currently happen by hand

Communication volume

How many calls, messages or requests come in each day

System connections

Whether anything needs to connect to existing tools or platforms

Staff time absorbed

How much of someone's day the current process takes up

Operational urgency

How much the problem costs when it goes wrong

Worked Examples

The kind of project we build

These are representative examples, not fixed packages. Similar situations produce similar costs.

Focused Operational Workflows

A small professional services firm was handling appointment reminders, new enquiry acknowledgements, and routine follow ups by hand. Nothing was complex individually, but the daily admin was absorbing time that should have gone elsewhere.

A workflow that handles appointment reminders, enquiry acknowledgements, and routine follow ups automatically cutting the daily admin that was absorbing hours of the team's time each week.

Starting from

£1,500

Typical Timeframe

2 – 5 days

Trades & Service Businesses

A plumbing and heating company was sending out quotes and then losing track of them. No one was following up unless a customer called back first.

A quote follow up workflow that sends timed reminders automatically, so leads stop going cold and no one has to remember to chase.

Starting from

£2,500

Typical Timeframe

1 – 2 weeks

Healthcare & Clinics

A dental practice was missing patient calls during treatment sessions. By the time someone called back, half the appointments had already been booked elsewhere.

A missed call system that automatically messages the patient, notifies staff, and logs every call. Missed calls during treatment sessions no longer mean lost appointments.

Starting from

£4,000

Typical Timeframe

2 – 4 weeks

Restaurants & Hospitality

A busy restaurant was getting booking and private hire enquiries over the phone during service. Some were being handled. Most were not.

An enquiry handling workflow for busy service periods. Customers get a confirmation automatically, and the bookings team gets a clear handoff so no enquiry gets lost while the kitchen is running.

Starting from

£4,000

Typical Timeframe

2 – 4 weeks

Property & Facilities

A property manager was receiving maintenance requests across phone, text and email. Jobs were getting missed. Tenants were following up before anything had been actioned.

A single intake point for maintenance requests. Tenants get an automatic confirmation, contractors are notified, and jobs are tracked from first report to resolution without anyone having to chase.

Starting from

£6,000

Typical Timeframe

2 – 4 weeks

More complex projects involving multiple workflows or integrations are scoped individually after the review. See what can typically be automated →

Worth Saying

What it usually looks like

Most projects are smaller and more operational than people expect. The goal is usually to fix friction around a specific process, not redesign the business. We look at where work is getting delayed, repeated, or missed, and build around that. You stay involved at every stage before anything goes live.

  • Not a six month transformation programme
  • Not a large software rollout
  • Not a replacement for your existing staff
  • Not a complicated technical rebuild
  • Not designed without your involvement
Operational Value

What you get back

The question is not what this costs. It is what the current situation is costing.

One hour a day is twenty hours a month.

If a staff member spends an hour a day on a process a structured workflow could handle, that's roughly twenty hours a month. Most projects cost less than that time is worth at any reasonable hourly rate.

Missed enquiries have a real cost, not a projected one.

A week's worth of missed bookings at a busy practice, restaurant, or service operation will usually cover the cost of the system that prevents them. The maths does not require much optimism.

Small things cost more when they happen every day.

A five minute manual task that runs twenty times a week is not a five minute problem. Over a month, it is several hours. Over a year, it is days of someone's working time, from a single repetitive task alone.

After The Build

Ongoing support

Some clients want the system implemented and handed over. Others find it useful to have someone available as the operation evolves. Either works.

If things change, or you want to add more later, that option is always there.

There is no requirement to take it, and no pressure to if the system runs well without it.

System checks

Reviewing how the workflow is performing and whether anything needs adjusting.

Process adjustments

Updating the system as your operation changes, whether due to new staff, new processes, or seasonal variation.

New workflows

Adding further improvements once the first phase has bedded in.

Staff onboarding

Helping new team members understand how the system works and what to do with its output.

Before The Build

Map the workflow before committing to a build

Not sure which process to prioritise, or what a project would look like in practice? The Working Session is the structured step before a full build.

90 minutes. One operational workflow. Mapped properly, with friction identified and a clear picture of what implementation would involve and cost.

What the session covers

Map how the workflow currently runs, step by step
Identify where the friction is building and why
See what a working version of the process would look like
Understand what implementation would involve and cost

Fee

£150

Duration

90 minutes

One bottleneck. That is usually where to start.

It is free, and gives you a clear picture of what is actually worth fixing and roughly what it would cost. No preparation needed.

Read more about what the review includes →

Book the free review →