go.rwsc.au/fy27 now routes to the campaign and preserves print attribution. Search indexing remains disabled for pre-launch review.
Campaign progress · live source view
Built, visible and
finishable.
Every campaign asset in one place—what exists, what is live, what still needs a decision, and the suburb evidence behind the print system.
Produced assets
—
Colour cards are produced.
Grey cards still need action.
Use rwsfy27-sales-talk.pages.dev, never a hashed deployment alias.
Launch operations · Git source of truth
Fresh data, visible gates and repeatable campaigns.
This view is generated from versioned campaign configuration. It shows what can run now, what needs a secret or approval, and where launch would currently stop.
Automation pipelines
Campaign configuration
Open versioned campaign config ↗Master asset register
Everything produced—and everything still to do.
Click colour cards to open the real asset. Grey cards are the remaining production, approval or infrastructure work.
Client discussion · email
Start generic. Personalise where the evidence earns it.
The existing broadcast is a draft and its dates need refreshing. These are the sensible production levels to take to the client.
Launch one generic corridor email first. Follow with suburb-level variants using the verified matrix. Pilot address-and-recent-sales personalisation only for a smaller seller/landlord segment with licensed data and agent review.
View the 13 existing email source files
DL cards · live data matrix
Every suburb, stat, image, contact and QR target.
Each card now has a recommended positive lead chosen from verified growth and yield evidence. Full market figures remain available underneath for transparent review.
. Final Canva masters show , which is now the live campaign route and should be used for final print.
| Suburb | Recommended card lead | House | Unit | Investor lens | Office | QR |
|---|
Operations visibility
ClickUp is connected to the campaign.
The dashboard reads a sanitised snapshot only. The API token stays in a local or Cloudflare secret and never reaches the browser.
Final production gates
What must happen before go-live.
These are approvals and infrastructure actions—not missing campaign concepts.
Social queue · Instagram and Facebook
Manage here. Approve once. Publish securely.
The static dashboard should never hold Meta access tokens. It can manage status and approvals, then hand publishing to Meta Business Suite or a secure server-side connector.
Copy, format, image, alt text and target date.
ClickUp status becomes Approved to publish.
Meta Business Suite now; Graph API automation later.
Post URL and date return to ClickUp.
ClickUp + Meta Business Suite
Low setup risk. Use ClickUp for owner/approval/date and schedule the approved asset in Meta Business Suite.
ClickUp webhook + Cloudflare Worker
On approval, a server-side worker calls the Meta Graph API. Requires a Meta app, Page/IG permissions, long-lived tokens and token rotation.
Buffer or Metricool
Fastest multi-channel scheduler if the client prefers a supported publishing product over a custom connector.