SIGNAL & SYLLABLE / CAMPAIGN DESK Studio example · 25 October 2026 Proposed Recallant launch plan — not an executed campaign OBJECTIVE Help a suitable B2B buyer understand the bounded pilot, inspect an original specimen and submit a useful enquiry. No traffic or conversion target is asserted without a baseline. CORE PROPOSITION One buyer question. One useful improvement. A defined website review, priority-page draft and enquiry recommendation. CALENDAR Offer alignment | Confirm offer and evidence | Owner and reviewer | Pilot scope, price, input requirements and exclusions agree across all assets. Landing-page preparation | Prepare the landing route | Web and editorial roles | Recallant page links to relevant evidence, package and preselected enquiry. Launch-kit review | Review the launch kit | Content reviewer | Announcement, article and follow-up copy use the same facts and one next action. Launch day | Publish approved assets | Designated publisher | Use only approved channels and assets; verify the destination after publishing. After launch / first review | Inspect the journey | Owner and technical reviewer | Check broken links, form errors and questions that reveal unclear scope. After enough relevant activity | Assess buyer response | Owner and analyst | Use a stated observation window and distinct event counts; do not infer uplift from a few visits. ASSET ROLES Landing page: scope and decision. Research specimen: inspectable method and evidence boundaries. Offer one-pager: a forwardable summary. Launch note: introduce the offer and one clear next step. Editorial article: explain a useful buyer decision. Enquiry: collect context and obtain explicit send action. PROPOSED EVENTS offer_open | Recallant page available | The offer destination is actually loaded. | An abandoned or broken click. proof_open | Research specimen available | The selected specimen is available to inspect. | Proof that the prospect understood or trusted it. enquiry_review | Complete review shown | The visitor reaches a usable review of their brief. | A received enquiry. enquiry_accepted | Server receipt returned | The sending service accepts the submission and returns a traceable reference. | Inbox receipt, a qualified lead or a sale. inbox_received | Owner confirms receipt | A matching message is independently observed in the receiving mailbox. | A customer engagement. MEASUREMENT RULE Record event name, content ID, source component, result state and build version. Keep names, email addresses, free-text challenges and message content out of analytics. Deduplicate success by event ID. The site has no separate analytics service; this is a specification, not active tracking. APPROVAL GATES Confirm truthful offer facts and asset ownership. Assign real review and publication owners. Agree any paid media or outreach separately. Test the destination before approved publication. Stop on a broken enquiry path or materially wrong claim.