Stop entering the same information twice.

Start with one process

Show me one recurring job, from the trigger to the finished result. We map what information is needed, which software holds it and who can approve an action. Then we choose the smallest useful improvement.

For example, an enquiry can become a CRM record, an assigned task and a draft response. A confirmed appointment can trigger a reminder. A paid order can move into fulfilment. Those are different events, so a click or a submitted form should never be treated as a sale.

Where automation can help

• Enquiry handling: collect the right details, route the request and show who needs to reply.
• Quote follow-up: track open quotes and use an agreed reminder schedule that stops when the customer replies or declines.
• Bookings: connect available times, requests and confirmations, using your booking system as the authority.
• Reporting: bring agreed figures into one view and show missing or stale data.
• CRM and internal tools: make responsibilities and next steps visible to the people doing the work.

Will it work with your existing software?

I check the actual product, plan and account permissions before promising an integration. Some tools offer an API or an approved connector; others only support an export or a manual step. We confirm the supported route and any supplier fees in the scope.

You keep the steps that need judgement. An unusual request, a conflicting booking, an uncertain price or a payment problem should have a clear route back to a person. A system also needs a way to show failures and retry safely without sending the same message or creating the same record twice.

What I need from you

Bring the current process, the tools involved, a few anonymised examples and the rules staff use today. We also need an owner for each decision: who can change a price, accept a booking or approve a message. Start with test information before using real customer records.

We test the ordinary path and the awkward cases together: a missing detail, duplicate request, unavailable provider and somebody changing their mind. Your team reviews the result before it goes live.

Cost and ongoing support

Momentum is a published starting point at £3,000 to £5,000 setup plus £500 a month. Broader automation may fit Catalyst at £5,000 to £8,000+ plus £750+ a month, or need a bespoke quote. An existing system may only need a smaller, scoped addition.

Project payments are 50% up front and 50% on completion. The monthly service has a six-month minimum, then rolls with 30 days' notice. There is a 30-day warranty from go-live. Once paid for, the agreed build is supplied under a perpetual licence; your own materials remain yours. Hosting, support, supplier subscriptions and reusable underlying tools have separate terms.

Read the package guide. The build date and monitoring responsibilities are agreed in writing.

When to keep it simple

If the process happens rarely, changes every week or has no agreed owner, automating it may create more work. An improved form, checklist or existing software feature can be enough. Read how to choose the first process to automate.

Fixed rules usually need ordinary software. AI systems are useful where the job involves interpreting language or finding answers in approved information. Your website can be the entry point for either.

Questions worth asking