What do you need to solve?

Choose a specific task. Each area offers a suggested starting point, followed by articles, decision guides and workflows with resources you can use.

Not sure where to start? Explore common problems →

Enquiries and contacts

Keep one contact record and make responsibility for new enquiries clear. Start with the form; define CRM rules as your records grow.

Suggested starting point: Shorten your first-inquiry form to what you need now →

Back to task selection ↑

Client work and communication

Turn an agreement into work your team can deliver. Establish ownership and inputs first, then manage changes, approvals and handover.

Suggested starting point: Hand a client to a new colleague without losing the next step →

Back to task selection ↑
Practical workflow

Hand a client to a new colleague without losing the next step

Transfer a client with the latest commitment, next action, and the new owner's acknowledgment. Includes a handover record and introduction.

Practical workflow

Collect complete client materials with one clear request

Request usable materials and follow up only on missing items. Includes a register and request wording.

Practical workflow

Client meeting agenda: questions, inputs, and decisions

Turn a vague agenda item into a decision question. Add the inputs, the person authorized to decide, and a plan for missing information.

Practical workflow

Tell a client about a delay without making unverified promises

Explain a delay promptly, separate facts from estimates, and commit to the next update. Includes messages for known and unresolved delivery dates.

Practical workflow

Client approvals without version confusion

Connect the client's answer to a particular deliverable version and decision. Includes an approval record.

Practical workflow

Handle a mid-project scope change before work continues

Preserve the original agreement and separate the requested change, cost and timing impact, and decision. Includes a change record and client reply.

Practical workflow

Hand over completed work and define the support route

Give the client a usable deliverable, instructions, and a clear support route. The handover record separates completed work from open items.

Practical workflow

Recurring client work: renewals with a clear owner

Track work periods, decision dates, and next actions with a reusable renewal register.

Practical workflow

Automations while you are away: what runs and who steps in

Before you leave, decide what can continue, what must wait, and who takes over checks. Prepare coverage and a safe return to normal operation.

Practical workflow

Check next week's capacity before promising a project start

A project can be attractive and still not fit the team's next week.

Article

Time tracking: what a project actually leaves you

Include delivery, rework, and administration. A calculator distinguishes contribution from net profit.

Practical workflow

Appointment scheduling without double bookings

Set up one booking page, meaningful availability checks, and a clear route for date changes. Includes eight checks before you share the link with clients.

Practical workflow

How to mark one exact PDF correction on a Mac

Use Preview to mark the location, specify the original and replacement text, and check the saved copy. Includes a fictional example and request template.

Practical workflow

Check a templated email against the right recipient and attachment

Compare a fictional service-email draft with an independent reference, then check actual attachment contents. Resolve mismatches before a manual decision.

Spreadsheets, data and reporting

Check input data and spreadsheet access before automating. When something goes wrong, recover the right version before changing reports.

Suggested starting point: Import CSV into Excel without losing leading zeros, codes, or accents →

Back to task selection ↑

Access and ownership

Files, mailboxes and automations need a named owner. Choose a workflow for the resource you need to hand over or share.

Suggested starting point: Hand over shared files and automations before removing a colleague's account →

Back to task selection ↑

Automations you can control

Prepare tests, monitoring and a manual fallback before launch. After a failure, establish what actually happened before running anything again.

Suggested starting point: Ten checks before relying on an automation →

Back to task selection ↑
Practical workflow

Ten checks before relying on an automation

A successful first transfer covers only one situation. Check repeated input, missing data, and revoked access before the team relies on the connection.

Practical workflow

Detect a scheduled automation that did not deliver its result

An automation that never starts may send no error. Set up a separate expected-job check in Google Sheets with an alert to your own email address.

Practical workflow

An automation failed: retry it without creating a duplicate

A write error does not prove that no record was created. Inspect one incomplete Make execution and decide whether to retry from the actual destination result.

Practical workflow

Build a manual exception queue into your automation

Ambiguous cases need a place, an owner, and a decision. Build a review queue that retains the source and prevents blind repetition.

Practical workflow

Change an automation with a saved baseline and a clear stop decision

You need to change one step in a workflow that already handles real work.

Practical workflow

SaaS outage: track manual work and resume without blind retries

Retain original requests, record actual manual actions, and reconcile the source, manual register, and restored destination. Includes a blank CSV and five fictional cases.

Practical workflow

Review your automations and retire what you no longer need

Track each automation's purpose, owner, and dependencies. Retire unnecessary workflows in stages with checks and a recovery route.

Article

Webhook or polling: how triggers change automation cost

Two workflows can transfer the same inquiries while using very different numbers of runs. The difference starts with how they discover new work.

Article

Do you need Make or n8n? Check the apps you already use first

Connecting work does not always require another tool. Choose based on the missing step, usable access, and what happens when the process fails.

Practical workflow

Internal reminders that stop when the task is done

Use current task state and suppress same-day repeats. The included script starts in dry-run mode.

Choosing tools and checking costs

Start with the task and ongoing administration before choosing a tool. Compare operating costs and the work involved in leaving it.

Suggested starting point: When automation pays off: costs and released capacity →

Back to task selection ↑

AI: instructions, inputs and checks

Define one task, prepare appropriate inputs and check the result against sources. Try synthetic examples before sharing work data.

Suggested starting point: Choose an AI assistant for one repeatable office task →

Back to task selection ↑