What automation actually means inside Base

Most automation tools give you a canvas. You pick a trigger, pick an action, map the fields, test it, and then maintain it forever. That is fine when you have someone whose job is to do that. Most founders do not.

Automation inside Base works the other way round. There is one command bar. You write what you want in plain English, and Base works out which module it belongs to, which connected tool has to do the work, and what it needs to know first.

A worked example

You type: "send a contract to my first client for £2k a month".

Base routes that to contracts. It pulls the client record from your CRM so the name, company and email are already right. It generates the agreement in PandaDoc with the term and value you specified. Then it stops and puts the draft in front of you.

You read it. You change the payment terms if you want. You send.

That is the whole mechanic. What would have been a morning of choosing a contract tool, building a template and copying details between tabs is one sentence and one review.

Why it stops before sending

Nothing sends, signs or pays without you approving it. Automation that acts on your behalf without a review step is not a time saver, it is a liability. Base does the work up to the point where judgement is needed, then hands it back.

What it covers

The same pattern runs across invoicing, follow-up email, CRM updates, hiring and finance questions. Because every connected tool feeds one company brain, the command has context. It knows who your first client is. It knows what you charged the last one.

If you are still comparing options, we wrote up where the category stands in best automation tools right now.