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 ↑Shorten your first-inquiry form to what you need now
Ask only for what the first useful reply needs. The local form demo helps you test the questions and error handling.
Clean up duplicate CRM contacts without losing history
Separate duplicate contacts from another job or a namesake. Prepare a controlled merge and a record of what changed.
Move from a spreadsheet to a CRM and verify the import
Prepare field mapping, a small trial import, and checks for history and owners. A green importer message does not complete the move.
Where your CRM ends and project delivery begins
Separate sales agreements from delivery without duplicate records. A field map shows what to hand over.
Leave your CRM without losing history and relationships
A contact list is not the whole sales story. Before changing CRM, check whether projects, activities, and their relationships can move too.
One contact, two projects: what is actually a duplicate?
The same email address does not always mean the same inquiry. Separate the contact, requested work, and individual messages so you do not lose a new project.
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 ↑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.
Collect complete client materials with one clear request
Request usable materials and follow up only on missing items. Includes a register and request wording.
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.
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.
Client approvals without version confusion
Connect the client's answer to a particular deliverable version and decision. Includes an approval record.
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.
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.
Recurring client work: renewals with a clear owner
Track work periods, decision dates, and next actions with a reusable renewal register.
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.
Check next week's capacity before promising a project start
A project can be attractive and still not fit the team's next week.
Time tracking: what a project actually leaves you
Include delivery, rework, and administration. A calculator distinguishes contribution from net profit.
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.
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.
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 ↑Import CSV into Excel without losing leading zeros, codes, or accents
Import four sample rows as text, check exact values, and spot unwanted conversions. Includes a CSV sample and an optional local checker.
A successful import is not a correct report: checks before sending
A report can look current while missing part of its period. Check seven days, duplicates, totals, and recipient access in a simple Google Sheets example.
Prepare a client spreadsheet without internal columns
Select the right jobs and values, create a separate static file, and check its contents and recipient access. Includes fictional CSV examples.
Recover an overwritten spreadsheet without losing today's good entries
Restoring yesterday's spreadsheet can bring back a damaged value and remove today's valid work at the same time.
Build a shared work tracker people can update without breaking its formulas
Your team has a spreadsheet, but one person writes “waiting,” another writes “pending,” and a third overwrites the formula that totals the open work.
Report booked work, invoices, and cash as three different numbers
You accept a project this week, invoice part of it, and receive a smaller payment.
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 ↑Hand over shared files and automations before removing a colleague's account
A colleague leaves, someone removes the account, and the team discovers that a useful file or automated task belonged to that person.
Hand over client files and access so your team can start work
A link in an email does not mean your teammate can open the file. Set up separate Google Drive folders and check the handover using the recipient’s work account.
Give colleagues access to a client mailbox without sharing its password
Two people cover a client mailbox, but both sign in with the same password.
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 ↑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.
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.
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.
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.
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.
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.
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.
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.
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.
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 ↑When automation pays off: costs and released capacity
Count work before and after automation, including maintenance. The calculator separates released capacity value from changes in cash spending.
Google Workspace or Microsoft 365 for a small team
Compare proposal files, client access, booking, and handover. Includes licensing and migration effort.
Notion or a spreadsheet for your team knowledge hub
Choose around short lookups or developed procedures. Three retrieval checks compare the same information.
Self-hosted n8n: what costs more than the server
A low server bill is not the total operating cost. Include administration, recovery, updates, and the person who will respond when something fails.
Cancel unused software without breaking the work around it
An unused subscription can still own something useful: a glossary, a client file, an integration credential, or an export someone needs next month.
Check a browser extension before it touches client work
An extension promises to summarize a page or capture a screenshot.
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 ↑Choose an AI assistant for one repeatable office task
Compare one task against an expected answer and complete review effort. Includes a synthetic test set.
Check the citations in an AI-prepared client summary
Open the original sources, check the version and scope, and record which claims to keep, correct, remove, or leave unresolved. Includes a worked example and editable ledger.
Build an AI source packet when the whole project is too much input
Select the sources for one AI task, preserve their versions, and show what is missing. Includes an editable manifest and a complete fictional status-note example.
Try an AI task with a fictional case before adding client information
You want to see whether an AI tool can sort an inquiry, summarize a brief, or prepare a reply.