Resources
The method before the tool
Most of these guides are useful even if you never buy Magic. They describe the job, the records involved, and the questions worth answering before you choose software.
No email gate on any guide listed here.
Start from the job
Guides are organised by the decision you are trying to make.
Worked examples
One illustrative business, followed across every product.
No borrowed credibility
Examples are labelled as illustrations, never as customer results.
Guides
Start with the job
Each guide states the problem, the records involved and the decision it supports.
Keep a forecast tied to actuals
Why a forecast drifts, what an assumption actually is, and the three statements a change should touch.
Run a pipeline people read
The smallest set of fields that makes a pipeline useful, and why a next step needs an owner.
Consent before campaigns
What consent means in practice, what a suppression list is for, and why a stop condition is a feature.
Keep a reviewable call record
What to keep from a call, what to leave out, and where human approval belongs.
Support without starting again
How prior context changes a conversation, and which commercial facts are appropriate to show an agent.
A company record with an owner
Agreements, obligations and ownership, and the difference between record-keeping and payroll execution.
How these guides are written
The rules are deliberate, because a resource library that overstates the product is worse than no library.
No unsourced claims
If a number appears, it names its source and the date it was checked.
- No customer statistics without a dated source
- No comparative savings claims without a configuration
- No “most popular” language
Scope is stated
Every guide says which product and which edition a workflow needs.
- Starter and Professional jobs are labelled
- Cross-product workflows name the dependency
- Unreleased workflows are marked as such
Fit before enthusiasm
Guides name who should not switch, and which job belongs to a different tool.
- Statutory reporting belongs to an ERP or specialist
- Payroll execution belongs to payroll
- Documents with legal effect stay in the document store of record
Every claim on this site has an owner and a review date.
If the evidence is missing, the claim narrows. It is never replaced with more confident copy.
Resource questions
Pick the job, then look at the product
Start free, or see which edition a workflow actually needs.