Magic Reach · Pilot release
Marketing your whole business can follow.
Magic Reach builds campaigns from the same customer record Sales and Support use. You can see the brief, the draft, the audience preview, the approval and the stop condition before anything is sent.
Starter A$29/month Ex GST.
Starter from A$29/month. Contact, send and AI allowances are shown before you subscribe.
Build a campaign, preview the audience
Build
Write the campaign, with the list it will reach shown beside it.
Magic Reach
Preview the audience
Who matches, who is suppressed, and why — before anything is sent.
Permissions and consent
Origin recorded
The campaign a response came from is kept, so Sales can see it.
Magic Reach → Magic Sales
You can see the list
Preview who matches, and who is suppressed, before you send.
Stops are visible
Exits and suppression drawn on the journey, not buried in a setting.
Sales sees the origin
The campaign a response came from stays attached to it.
The handoff problem
Your marketing stops where another tool begins
A customer tells Sales one thing and receives a campaign that assumes another. A response arrives in a marketing list nobody in the pipeline can see. Consent is recorded somewhere, but not next to the person who is about to be emailed.
Reach puts the campaign beside the customer record it draws on. The audience comes from the records the business already keeps, the consent behind each contact is visible, and a response can fall straight into a next step that somebody owns.
This is a pilot release
Sending is released to a controlled cohort while the sending path, authentication, consent and suppression rules and usage definitions are verified. The walkthrough shows the same product, with the current limits stated plainly.
Build it, follow it up, understand it
The demo is open — it does not ask for an account and it does not send anything. Illustrative data only.
Start from the customer record
A campaign begins with an audience drawn from records the business holds, and a brief that names the offer, the sender and the outcome being asked for.
- 01Choose the audience from customer records and saved views
- 02Read the consent basis and the suppression list for that audience
- 03Write the brief: what is being offered, and what a response looks like
This demo is open — it does not ask for an account, a card or a connected system.
Who is in the audience, and on what basis
A campaign is only as defensible as the list behind it. Reach keeps the basis for contact visible before the send, not after it.
1 · Eligibility
Who is allowed to receive this campaign at all.
- The customer records the audience is drawn from
- The saved view or rule that selected them
- The products and records each contact is linked to
2 · Consent
Why each contact is allowed to be contacted.
- The consent status recorded against the contact
- The source and date the consent was captured
- A clear mark on any contact whose basis needs review
3 · Suppression
Who is removed regardless of the rule.
- Unsubscribes and do-not-contact records
- Open complaints and recent service escalations
- A recent purchase that makes the offer irrelevant
Approved send
From brief to approved send
Nothing is sent because a draft exists. The send is a reviewed step with a named approver.
Brief
The offer, the audience and the outcome are written down first, so a reviewer has something to approve against.
Draft
A draft is produced from the brief and the customer record, and it is marked as machine-assisted until a person edits it.
Brand edit
Tone, claims and legal wording are edited by a person. Brand rules are applied and any exception is shown.
Audience preview
The exact recipients are previewed with consent and suppression reasons before the send is requested.
Approval
A named approver reviews the audience, the content and the stop conditions, and either approves or returns it.
Send
The approved version is sent, and the record of what was sent to whom is kept against the campaign.
Orchestration with visible stop conditions
A lifecycle journey is a Professional workflow. It is previewed here so the difference from a single campaign is clear before any quote is discussed.
What starts the journey
Entry is an event the customer caused or a state the business can see, not a manual upload with no trigger.
- 01Name the event or condition that enters a customer
- 02Read which customers are already in another journey
- 03Confirm the entry cannot fire twice for the same event
This demo is open — it does not ask for an account, a card or a connected system.
When a campaign becomes a customer
A response becomes an opportunity, with the campaign and the consent behind it.
The response itself is never held behind a new product paywall. If your workspace holds Reach, you can see and act on the response even if you do not hold Sales. Adding Sales deepens the pipeline view; it does not unlock the reply.
Magic Reach → Magic Sales
How this is measured
These are definitions, not claims. A response is counted once, and the words used in a report mean exactly this.
Attributed response
A response credited to this campaign because it is the most recent send to that contact inside the stated window, and no other campaign or channel was in between.
- Most recent eligible send to the contact
- Inside the response window stated on the campaign
- No competing send or channel recorded in between
Influenced
The contact received the campaign inside the window but the eventual response is credited elsewhere. It is reported separately and never counted as attributed.
- Received the campaign inside the window
- Responded through another channel or campaign
- Shown as influenced, not as attributed
Unattributed
The response cannot be tied to a send with confidence, so it is left unattributed rather than assigned to whatever campaign is convenient.
- No eligible send inside the window
- Consent or suppression blocks the link
- Kept visible as unknown rather than guessed
What the campaign cost, and what it changed
A campaign has a cost on day one and an effect that may arrive later. Reach keeps the two apart and names where each number came from.
Campaign record
Acme Services — autumn campaign, cost and send record
The send volume, the contacts reached and the campaign cost are recorded against the campaign, so the cost is a fact rather than an estimate.
Model assumption
Cost and pipeline effect, not booked revenue
In this illustration the campaign cost is entered as an assumption in Magic Model and the responses are shown as open pipeline. Weighted pipeline is never presented as revenue or cash.
Illustrative — Acme Services. Requires Magic Model for the financial view.
Campaign types
Three campaigns you can run
Start narrow. The type of campaign should match the job, and the allowances should match the type.
One-off campaign
A single send to a defined audience, with a brief, an approval and a response window. The usual first campaign.
Triggered follow-up
A short sequence that starts from something the customer did, such as an enquiry or an abandoned quote, with a stated exit.
Lifecycle journey
A rules-based journey with branches and exits, for a recurring process rather than a single send. A Professional workflow.
When Magic Reach is the right choice — and when it is not
This is a fit guide, not a knockout table, so that someone who should not switch can tell quickly.
Do not move to Reach if you need deep, whole-of-market marketing automation as the centre of your business, or a very large pre-existing list with complex segmentation that only a specialist suite maintains, or agency-managed campaigns that will not run from your own workspace. Reach is for businesses whose campaigns should follow the customer records they already keep. Competitor pricing is quote required here; we do not publish figures we have not verified.
| Task | Magic | Marketing suites and standalone lifecycle tools | Source | Checked |
|---|---|---|---|---|
| Start an audience from customer records | Audiences are drawn from the customer record and saved views already held. | Vendor-described: usually a separate contact list with its own sync. | Product behaviour, this release | 2026-09-19 |
| See consent before sending | Consent status, source and date are shown per contact, with suppression reasons. | Vendor-described: consent fields, sometimes an add-on. | Vendor-described where untested | 2026-09-19 |
| Follow up a response in the pipeline | A response becomes a next step on the customer record, with the campaign attached. | Vendor-described: requires a CRM integration to be configured. | Vendor-described where untested | 2026-09-19 |
| Lifecycle branches with exits | Professional: rules-based journeys with entry rules, branches and visible exits. | Typically the core strength of specialist lifecycle tools. | Vendor-described | 2026-09-19 |
| Very large lists and complex segmentation | Bounded by the stated contact and send allowance on your edition. | Vendor-described: built for high volume, priced accordingly. Quote required. | Vendor-described | 2026-09-19 |
| Replace an agency-run program | Not the job. Reach assumes the business runs its own campaigns. | A managed service, not a product comparison. | Product scope | 2026-09-19 |
Facts are vendor-described unless marked tested. Prices that are not published are shown as “quote required” rather than estimated.
Move one campaign, not your whole list
A sending migration fails when it starts with the whole list. Reach starts with one campaign and a small, reviewed audience.
Campaign content and the customer records behind it.
- The campaign copy and its brand assets
- The customer records the audience is drawn from
- Consent status and source where it is recorded
Anything where consent or identity is uncertain.
- Contacts with no recorded consent basis
- Duplicate contacts across two lists
- Historic unsubscribe and complaint records
Lists and systems Reach reads rather than replaces.
- Your accounting system, read for customer records
- A specialist list tool you still need for another channel
- Archived campaigns you do not need to resend
Nothing is deleted from your current system by connecting Magic. A transfer is only marked complete when it has been verified, and anything uncertain is listed for review.
How sending is controlled
Reach pricing
Free is a campaign preview. Starter runs live campaigns inside a stated contact and send allowance. Professional adds lifecycle journeys. Business is scoped by volume.
Magic Reach
- FreeFree
- StarterA$29/month/mo
- ProfessionalA$199/company/mo
- BusinessQuote
A$29/month
Ex GST · A$290/year, billed annually (10 × monthly)
Live campaigns within the stated send and contact allowance.
A$199/company/month
Ex GST · A$1,990/year, billed annually (10 × monthly)
Campaigns and lifecycle marketing, without the HubSpot bill.
AUD ex GST. Contact, send and AI allowances are stated on each edition before you subscribe, and any usage beyond them has its own rate. Annual billing is charged as 10 × monthly.
The contact-and-send selector shows the allowance for the edition you choose and the rate beyond it. AI usage is shown as its own line, separate from the software price.
Talk to sales
Magic Group and multi-entity groups are scoped by sales. Bring your entity count, user bands and any consolidation requirements, and they will quote the configuration — monthly, with the annual invoice stated as 10 × monthly.
Reach questions
See a campaign become a customer
Book a walkthrough of the pilot, or look through the open demo and the pricing before you talk to anyone.