Can you repair existing automations?

We can inspect the workflow, recent failures and connected accounts, then scope a repair or a replacement.

Do we need a new CRM?

Not necessarily. We first check the systems already in use and whether they expose the access the workflow needs. If the CRM itself is the problem, see HubSpot and CRM.

Will it run without supervision?

Some steps can run automatically; others should wait for approval. We define that boundary, and how the team will know when intervention is needed.

What does it cost to run?

Running costs depend on the automation platform, the connected services, usage and any model calls. We identify these separately from the implementation scope.

Which platform do you use — Make, n8n or Zapier?

Whichever fits the workflow. Make and n8n handle multi-step logic well, n8n can be self-hosted, and Zapier is often enough for a straightforward connection. Where connectors cannot express the requirement, we write the integration.

When is an AI step worth adding?

When the workflow has to interpret text or choose between a small set of actions. If the steps do not vary, ordinary rules are more predictable and cheaper. For work that needs judgment, see AI agents.

Workflow automation

Workflow automation for the work you repeat every day.

Stop moving the same information between forms, spreadsheets, inboxes and business systems. We design and build connected workflows around your process, including what should happen when information is missing or a tool fails.

Discuss your project Explore a reporting project

Start with a free 30-minute call and one real example of the process.

Workflow · New enquiry

illustrative example

Example

Form submitted — required fields checked

Company details looked up

Assigned to an owner

Sending the agreed follow-up

Illustrative example, built with Makefour steps

Where the time goes

The same information, moved by hand.

These are the four patterns we are most often asked to connect. Each one is a candidate for automation, and each one needs rules for the cases that go wrong.

Lead and request intake

A submission arrives and someone has to check it, decide who owns it, and copy it into the CRM before anything happens.

Follow-up and reminders

Messages and internal tasks depend on a person remembering the event that should have triggered them.

Reporting

Numbers are collected from several tools by hand, on a schedule someone has to keep, into a report that is out of date once it is finished.

Operational handoffs

Information is re-entered as it passes between the tools used by sales, support and operations, and nobody owns the gap.

Anatomy of an automation

A trigger fires, then the agreed steps run.

An illustrative intake workflow: an event arrives, the engine routes it through the connected tools, and the record ends up where the team expects it.

Triggers

New form

New ad lead

Webhook

Automation
engine

The steps we would agree

Check required information

Assign an owner

Send the agreed message

Create the CRM record

Workflows we can help connect

Common workflows, and the tools involved.

Illustrative examples of the shape these workflows take. The steps, tools and exception rules are agreed per project.

New form submission

Check required information

Create the CRM record

Notify the assigned owner

Meeting booked

Raise the invoice

Send the confirmation

Update the deal record

New prospect added

Verify the contact details

Send the agreed sequence

Record replies and opt-outs

On a schedule

Collect the source data

Check it before publishing

Update the report

New customer

Start the onboarding messages

Schedule the follow-up steps

Segment the record

No reply after an agreed period

Send the reminder, if permitted

Log the attempt

Flag it for a person

What we build