GTM Execution Portfolio
Support HQ
The operating system for bringing Support HQ to market — governing how content is created, how campaigns run, how channels are activated, and how performance is measured and acted on.
GTM Intelligence Layer
The research and context foundation. Who we sell to, what markets we are in, and how to reach each segment. Select any territory tile for full market intelligence. Select any persona card for its breakdown across all five markets. Referenced by every other module.
Five territories covered. Select a tile to open the full market intelligence deep-dive: competitive landscape, business culture, entry tactics, digital infrastructure, and campaign calendar anchors. Guyana added as Priority 2 emerging market — oil economy boom creates first-mover opportunity.
★ Each tile opens a full market intelligence deep-dive: Overview · Business Culture · Entry Tactics · Digital Infrastructure · Competitive Landscape · Calendar Anchors. Full research document: support-hq-market-intelligence-regions.html →
Five canonical buyer personas confirmed. DEC-006 resolved 2026-03-26 (Sam, Grace, Edwin, Garvin). Persona E — Maya (Merchant Maya) added 2026-03-31 to resolve the EMP Coverage Gap. Visual renders pending DEC-013 (now covers all 5 personas). Select "View by Market →" on any card to see how messaging, channel, trigger, and brand voice shift across TT · BB · JA · GY · EC.
💡 The personas are universal archetypes — but what you say, where you say it, and what triggers action changes materially by territory. Use the Persona × Market matrix to calibrate every campaign brief.
Sam built or commissioned a website years ago and hasn't touched it since. His digital presence is a liability he knows about but keeps pushing down the to-do list. He doesn't want to learn WordPress — he wants the whole thing handled, quietly and professionally, without his involvement.
- Site outdated, unmonitored, no backups
- Fear of public-facing failure — downtime or hack
- No in-house digital capability, no desire to hire
- Peace of mind — it's handled
- Peer validation before committing
- Frictionless, low-effort onboarding
- Google Search (problem-aware query)
- WhatsApp groups, Facebook
- Peer referral (primary trust signal)
Grace owns the digital channels for a growing brand. She knows what good strategy looks like — her problem is execution capacity and operational infrastructure. She is doing a 10-person department's work with a team of three. She needs a partner who brings both strategy and execution.
- Outgrowing freelancer — no SEO, no strategy
- Site not generating leads, paid media ROI unclear
- Senior management demands results, won't fund headcount
- Results she can report upward
- Reduced cognitive load
- Access to expertise without hiring
- LinkedIn (primary discovery)
- Industry newsletters, professional networks
- Long-form content & case studies
Edwin has built something that works. His business is past the founding chaos — systems, clients, recurring revenue. Now he's thinking about scale and professional digital infrastructure. He is digitally sophisticated, has strong opinions about tools, and wants the standard he sees internationally applied to his own business.
- Need compliance, reporting, board visibility
- Digital infrastructure doesn't match business maturity
- No clear digital growth roadmap
- Infrastructure that matches business ambition
- A real strategic partner, not contractors
- Clear roadmap with measurable milestones
- LinkedIn, industry events
- Caribbean entrepreneurship communities
- Direct referral from trusted peers
Garvin manages technology procurement for a public sector organisation. He is not responding to advertising — he responds to direct outreach, tenders, and peer referrals from trusted vendors. His priorities are vendor reliability, compliance documentation, data sovereignty, and board-level reporting. He needs a provider he can defend to a procurement committee.
- Accessibility compliance (WCAG) requirements
- Data sovereignty & vendor reliability concerns
- Procurement process demands documentation
- Defensible vendor selection
- Published SLAs, compliance certs
- Board-level reporting capability
- Direct outreach only
- Government tenders / RFP process
- Referral from trusted vendors
Maya runs an independent retail or food business that has moved sales online — a fashion boutique, a bakery with an order page, a local F&B brand selling direct. She has a WooCommerce or Shopify store that underperforms: slow load times, abandoned carts, payment friction, no automated email sequences. She's running a real business and the online store is a revenue channel she can't afford to let fail. She needs someone to own the store's technical health so she can focus on buying, merchandising, and fulfilment.
- Store slow, abandoned carts, payment friction
- No automated sequences (cart, post-purchase)
- Mobile experience broken on some devices
- Store performance = sales performance
- Clean, fast, secure store before next campaign
- Email automation running without her managing it
- Instagram / TikTok (primary discovery)
- Facebook groups, WhatsApp communities
- Google search (ecommerce problem queries)
📷 Visual renders pending DEC-013 — image brief needed (now covers all 5 personas: Sam, Grace, Edwin, Garvin, Maya). AI prompts are documented in the Market Intelligence & Target Personas doc (WG-21 Document 3 of 10).
A world-class GTM intelligence layer needs more than competitive maps and persona profiles. This assessment shows what exists, what is partially built, and what is missing. Items marked CMIF are sourced from or cross-referenced with the Caribbean Market Intelligence Framework. Gaps should be prioritised for resolution before scaling GTM investment beyond Phase 1.
🔑 Priority gaps for Phase 1 (do not stall on these): ICP Scoring Criteria · Objection Library (needed by CON Guide) · DEC-014 Early Adopter Offer (needed before TT launch). Block watch (these will stall specific tracks if unresolved): DEC-002 Checkout (blocks self-serve funnel) · DEC-003 DX Blueprint classification (blocks C-DX) · DEC-015 partner commissions (blocks referral programme). Phase 2 prerequisites: Regulatory & Compliance Map · Win/Loss Framework · EMP Persona gap resolution.
These decisions are unresolved and have a direct impact on the accuracy or completeness of this module. Resolving them does not block all other work — but they must be flagged here so downstream modules can handle them correctly.
| Decision | What It Is | What It Blocks in M1 | Status |
|---|---|---|---|
| DEC-002 | Stripe / checkout integration decision — how SMP/EMP self-serve onboarding is processed | M5 asset card pricing links · C1/C2 self-serve funnel · Payment Infrastructure Map | Open |
| DEC-003 | DX Blueprint product classification — which project tier it maps to | Edwin persona acquisition path · C-DX campaign activation · Campaign Architecture (M2) | Open |
| DEC-013 | Visual renders / AI image brief for the 4 canonical personas | Persona cards cannot be used in public-facing assets without confirmed renders. M5 asset cards for persona-driven content. | Open |
| DEC-014 | Early adopter programme offer design — TT-first launch incentive for inaugural SMP/EMP clients | C1 Health Check Push pricing/offer · M5 offer-activation asset cards · TT launch sequencing | Open |
| DEC-015 | Referral Partner Programme commission structure and mechanics · Programme paused pending resolution | Channel Architecture (WG-21.3) · Referral programme asset brief · Partner recruitment copy — all blocked while paused | Open ⏸ Paused |
These open decisions do not stall all GTM work. Campaigns C1–C5, brand authority content, persona development, and framework delivery continue without them. They must be resolved before M5 (Asset Portfolio) is fully activated.
Campaign Architecture
The structural skeleton of all GTM activity. Every campaign maps to waypoints. Every waypoint maps to a persona journey. This module is the connective tissue between intelligence and execution.
Standardised journey stops governing how a prospect moves through the GTM system. All campaigns reference waypoint entry and exit points.
How each canonical persona moves through the W1–W11 waypoint sequence. Active waypoints are filled; skipped waypoints are greyed. Campaign codes shown at the waypoints they activate. Read left to right.
Three-phase activation schedule from product launch through the first 90 days of GTM operation. Sourced from the Warfare Playbook content calendar and GTM Framework phasing model.
Creation Framework
The operating logic for how content moves from brief to published. Defines content types, the brief standard, the 8-step workflow, and the HITL gate map. This module governs all content across every campaign and channel.
Five content types, each with a distinct brief template, workflow path, and gate configuration.
Every Campaign, Reactive, and Evergreen content piece must have a complete brief before any draft is produced. Seven required fields. The brief lives in Airtable as a content request record with a type field distinguishing internal GTM from client-facing (CON-013) requests.
brand-decision-framework.jsx React tool or answer manually below.L1 copy (TOFU): Brand positioning — who Webgold is, the problem we solve, the standard we hold. Do not push product or price at L1.
L2 copy (MOFU): Capability messaging — the 4D Framework, how we work, why our approach wins vs competitors. Evidence and methodology front and centre.
L3 copy (BOFU): Offer activation — specific plan, CTA, Health Check, pricing. One clear next action. Friction-free.
Social: Lead with insight · Brand rides quietly as co-sign · One key idea only
Email: Results-first subject line · Max 600px · DM Sans throughout
Web/Landing: CTA above fold · No contract framing · Orange CTA button only
PDF/Report: Outcome-led intro · Sandstone callout boxes
Avoid always: "Cheap" · "Affordable" · "Basic" · "Just" · "Simply" · "Revolutionary" · "Game-changing" · "Quality service" · Generic agency speak
Applies to Campaign Content (Type 1) and Evergreen Content (Type 3) in full. Reactive (Type 2) uses Steps 1, 3, 4, 7. Social (Type 5) uses Steps 3, 6 (light), 7. Operational (Type 4) uses Steps 3, 4, 7.
Brief Intake
A complete 7-field brief is submitted via the Brief Intake Form above. Airtable content record created. Campaign code, persona, funnel stage, channel, objective, key message, and constraints are all confirmed before any draft work begins. AI-suggested fields reviewed by the initiating Guide.
Initiated by: STRAT Guide or Campaign ManagerIntelligence Pull
Before drafting, the CON Guide pulls the full intelligence context from Module 1 and the CMIF. Four mandatory checks:
2. Messaging Architecture Level — Confirm the L1 / L2 / L3 level from the brief. L1: brand positioning only — who Webgold is, the problem we solve, do not push product. L2: capability and methodology — the 4D Framework (Diagnose → Design → Deliver → Sustain), Caribbean context, why our approach wins. L3: offer activation — specific plan, pricing, CTA, Health Check next step.
3. Competitive context — If the content is Reactive (Type 2) or addresses objections, identify the competitor archetype from CMIF Tab 2: Commodity Agency / Freelancer / International Agency / DIY Platform / Consultant-Only. The counter-positioning angle is different for each archetype.
4. Territory context — Pull the territory profile from Module 1 (TT / BB / JA / GY / EC). Check calendar anchors, channel priorities, and any messaging shifts specific to this market.
Draft Generation
AI-assisted via Claude API (OP-06) or direct CON Guide authorship. Draft is written against the brief, intelligence context, and all five Brand Voice Attributes (Direct · Expert · Grounded · Confident · Human). The Messaging Architecture Level (L1/L2/L3) governs copy hierarchy — do not mix levels within a single asset. For L2 content, the 4D Framework (Diagnose → Design → Deliver → Sustain) is the primary structural and positioning asset — use it. Output is recorded in the Airtable content record. The asset card in Module 5 updates from PLACEHOLDER to DRAFT at this step.
Executed by: CON Guide or Claude API (OP-06) · Voice: Direct · Expert · Grounded · Confident · Human⛊ HITL Gate 1 — Content Validation (Type 1 GATE · T2 Soft)
Quality and fitness review. Does the draft meet brand voice standards? Is it accurate? Does it serve the stated objective? Is the CTA correct? Rejection returns the draft to Step 3 with annotated feedback recorded in Airtable. The asset card in Module 5 shows REVIEW status while gate is open.
Gate Owner: QA Guide (quality) + STRAT Guide (strategic accuracy)Channel Adaptation
Approved canonical draft is adapted for each channel it will run on. An email sequence becomes a social caption becomes a WhatsApp message. This step is primarily AI-assisted — the canonical draft clears the gate once, and channel variants are generated from it. No new brief required for variants of an approved canonical draft.
Executed by: CON Guide or Claude API (OP-06)⛊ HITL Gate 2 — Adaptation Review (Type 1 REVIEW · T1/T2 by channel)
Lighter review of channel variants. Email and WhatsApp: T2 Soft-Gate — a blocking review because the consequence of error is direct and irreversible. Organic social: T1 Informational — 4-hour default-approve window. If no flag is raised within 4 hours, the post is scheduled. Landing pages: T2 Soft-Gate.
Gate Owner: QA Guide (email/WhatsApp) · CON Guide (social, default approve)Schedule & Publish
n8n (OP-03) orchestrates the scheduled send via the appropriate channel block: Klaviyo (OP-07) for email, ManyChat (OP-08) for WhatsApp, CON-006 Social Scheduling block for organic posts, HubSpot (OP-01) sequences for prospect outreach. Asset card in Module 5 updates to FINAL on confirmed send.
Executed by: n8n automation (OP-03) · confirmed by OPS GuidePerformance Capture
7 days post-publish (48 hours for social), the analytics pull runs. Open rate, CTR, and conversion against the campaign waypoint target are recorded in Airtable and surfaced in Module 7. If performance is below a defined threshold flag, Module 6 (Reactive Playbooks) is triggered and a review task is created in PCC.
Executed by: n8n + Airtable · reviewed by STRAT GuideEvery gate in the production workflow has a Type (what is being validated), a Severity (what happens if not cleared), a Gate Owner (functional role), and a Rejection Action. The three-layer framework: Type (1–4) × Severity (T1/T2/T3) × Context label.
| Gate | Step | Type | Severity | Gate Owner | Rejection Action |
|---|---|---|---|---|---|
| Content Validation | 4 | Type 1 — GATE | T2 Soft | QA Guide / STRAT Guide | Return to Step 3 with annotated feedback in Airtable |
| Adaptation Review — Email / WhatsApp | 6 | Type 1 — REVIEW | T2 Soft | QA Guide | Hold send; return to Step 5 for revision |
| Adaptation Review — Social | 6 | Type 1 — REVIEW | T1 Info | CON Guide (default approve 4hr) | Flag within 4 hours to hold; auto-approved if no flag |
| Client Fit Assessment Client-facing content via CON-013 |
4 equiv. | Type 2 — REVIEW | T2 Soft | Account Lead Guide | Return to brief with client feedback recorded |
| Exception Flag Competitor named, guarantee claim, paid channel |
Any | Type 3 — STRATEGIC | T2 → T3 | STRAT Guide → Senior Guide | T2: Hold pending STRAT Guide review. T3: Escalate to Senior Guide / Programme Manager. Triggers if: competitor named by name, financial claim, legal-risk language, paid channel with wrong claim. |
| Escalation / Brand Risk | Any | Type 4 — EXCEPTION | T3 Hard | Senior Guide / Programme Manager | Immediate hold. Senior Guide + Programme Manager notified. Content cannot be published until resolved. Incident logged in Airtable. |
Channel Playbooks
How approved content reaches the audience. A playbook per channel with setup, cadence, and territory nuance. MKT Nucleus blocks execute delivery once content clears Module 3 gates.
| Channel | Primary Level | Copy Direction | Primary Personas |
|---|---|---|---|
| CH-03 Organic Social | L1 | Brand positioning. Who Webgold is, the problem we name, the standard we hold. The brand rides quietly — insight and value lead. Do not push plans or pricing at L1. The 4D Framework as thought leadership (not as a sales pitch) is appropriate here. | Sam · Grace · Edwin (LinkedIn) |
| CH-01 Email — Nurture (C3) | L1→L2→L3 | Sequence progresses through all three levels. D0 (L1 — you're in the right place) · D2 (L1/L2 — score explanation + capability) · D5 (L2 — social proof, the 4D methodology, case study) · D10 (L2/L3 — plan recommendation, specific fit) · D21 (L3 — last touch, friction-free CTA). | Sam · Grace |
| CH-04 Health Check Funnel | L3 | Pure offer activation. Landing page, results PDF, and follow-up CTA are L3 throughout. The person arrived from L1/L2 content — they are ready to act. Do not re-introduce brand positioning here. One clear next step. | Sam · Grace · Garvin (post-qualification) |
| CH-02 WhatsApp | L3 | Qualification and conversion channel only. Copy is conversational but direct. Qualification questions, booking confirmations, onboarding nudges. Never use WhatsApp for L1 brand positioning — it violates the channel's personal nature and damages trust. | Sam · Grace (EC/TT/JA primary) |
| CH-01 Email — Retention (C5) | L2→L3 | Existing clients — capability deepening and upsell. L2 value reinforcement (what's working, what the plan is doing) moving to L3 upsell prompts (next tier, EMP if store added, DX Assessment). Not acquisition copy. | All active clients |
| DX Authority / C-DX | L2 | Capability and thought leadership exclusively. The 4D Framework, DX Assessment framing ("where are you really in your digital maturity?"), Caribbean digital transformation narrative. Edwin persona. ⛔ C-DX blocked pending DEC-003. | Edwin |
Asset Portfolio
Every GTM asset in one place with live status. Assets from the Warfare Playbook WIP enter at DRAFT — they exist but haven't cleared Module 3's Gate 1 yet. Blocked assets link to the decision that is holding them.
Every production asset requires an approved template before it can be produced to brand standard. Templates are governed by the Brand System (Notion) — Sections 5, 7, and 9. Status below reflects current availability. Assets with a Blocked or Pending template cannot advance to FINAL status until the template exists. Wire these into the corresponding asset cards once templates are built in Sections 5 and 7.
Subhead: Free, no-obligation website health check. We scan your site for security vulnerabilities, performance issues, SEO gaps, AI readiness, and accessibility problems.
Body: Most Caribbean businesses don't know what's happening under the hood of their website. Our automated scan covers 5 critical areas and delivers a branded PDF report with scores and recommendations.
CTA: Enter your website URL below to get started.
Trust copy: No spam. No sales calls unless you ask.
Post-submit: Automated audit runs → branded PDF generated → PDF delivered via Klaviyo email → HubSpot contact created with scores → C3 nurture sequence triggered on Day 2
Conversion target: 15–20% of Health Check recipients convert to paid plan within 30 days
#FFF0D9 page background · Template: T-01 Website Landing Page — ⛔ Blocked (WG-25)| Timing | Subject Line | Purpose | |
|---|---|---|---|
| E-01 | Immediate | Your website scored [SCORE]/100 — here's what it means | Deliver results PDF. Surface top 3 findings. Invite reply for walkthrough. |
| E-02 | Day 2 | What a [GRADE] score means for your business | Contextualise scores in business impact terms (security, SEO, performance). Personalised by worst-scoring category. |
| E-03 | Day 5 | How a [territory] business went from a D to an A | Case study relevant to their worst-scoring category. Links to plan comparison page. Social proof via territory-specific example. |
| E-04 | Day 10 | Your site doesn't have to stay at [SCORE]/100 | Plan recommendation mapped to their scores. Friction-free CTA: subscribe online in 5 min or book a 15-min call. No contract messaging. |
| E-05 | Day 21 | One last thing about [domain] | Soft final touch. One free actionable tip from their worst-scoring category. Low-pressure — "we'll be here when you're ready." |
| Timing | Subject Line | Purpose | |
|---|---|---|---|
| OB-01 | D0 — Immediate on sign-up | You're in — here's what happens next | Confirm subscription. Deliver plan details, login/portal access, team contact. Set expectation for Month 1 activation. Eliminate post-purchase anxiety. |
| OB-02 | D1–7 — Welcome kit | Your Support HQ welcome kit — everything you need for Month 1 | Full welcome kit: what's included in their plan, how the 4D cycle works in practice, how to reach their Guide, what the first monthly report will look like. Builds confidence and reduces early churn risk. |
| Tier | Primary Persona | Content Focus | Upgrade Prompt |
|---|---|---|---|
| Essential Starter / Business | Sam | What we handled this month. One highlight metric (uptime / security scan / updates applied). Simple, plain-text-first format. | Soft — "Your site is protected. Here's what's included in the next tier when you're ready to grow." |
| Professional Starter / Business / Enterprise | Grace | Monthly performance summary (uptime, security, SEO movement). One strategic insight relevant to their business stage. Links to self-serve resources. | Contextual — feature or capability they're not yet using. Framed as "did you know your plan includes…" |
| Complete (Starter / Business / Enterprise) | Grace + Garvin | Full monthly report summary. Strategic recommendations for next 30 days. Territory digital landscape note. Guide signature. | None — Complete tier is the flagship. Cross-sell DX Assessment if applicable (blocked DEC-003). |
Cold/warm introduction email for procurement contacts. Short (under 200 words). Links to credentials brief. Request: a 20-minute introduction call. Variants: Ministry/Government Dept · State-Owned Enterprise · Statutory Body.
GOV-02 · SLA Capability Summary (1-page)
One-page document: uptime SLA commitments, security certifications/standards, disaster recovery, update cadence, dedicated Guide model. Formal document format — leaves behind after intro meeting.
GOV-03 · Compliance Credentials Brief (1–2 pages)
Webgold's security and compliance posture. Data residency, backup policies, access controls, vulnerability disclosure. Relevant to procurement officer sign-off.
GOV-04 · Formal Proposal Template Reference
Points to T-11 Proposal Template (.docx) — customised for government procurement language. Outcome-led 8-section format adapted for public sector context (scope, SLA, pricing, references, T&Cs).
Step 2 — Reach: GOV-01 outreach email to procurement/MIS contact. No bulk send — personalised per ministry/entity.
Step 3 — Meet: 20-min intro call. Leave GOV-02 SLA summary after call.
Step 4 — Qualify: Is there a live website management need? Budget holder identified? Procurement route confirmed?
Step 5 — Propose: GOV-03 compliance brief if required by procurement officer. GOV-04 proposal generated using T-11.
Step 6 — Close: SMP Professional Enterprise or Complete subscription. Multi-site variants priced separately on SOW.
Hero angle: Caribbean business context first, global trend second
Structure: Hook (local stat or question) → Problem framing → Insight/solution → Caribbean-specific application → Webgold perspective close
SEO target: One primary keyword per post (assigned in content calendar)
CTA: Soft — relevant lead magnet download or Health Check link. Never hard-sell from a TOFU blog post.
Repurpose path: Blog → Social carousel (A-015 template) → Webinar clip embed where applicable → Email teaser in A-019 Quarterly Pulse
Pillar B — Security: WordPress vulnerabilities, SSL, backup practices for SMBs
Pillar C — AI & Search: AI readiness, SGE impact on Caribbean businesses, voice search
Pillar D — Digital Business: E-commerce readiness, digital payments, Caribbean market data
Pillar E — DX Authority: 4D Framework application, managed infrastructure strategy, Edwin/enterprise-adjacent topics
Pillar F — Digital Commerce Education: Market Education · Content Audiences C1–C4 Safe online shopping in the Caribbean · Trust signals for buyers · Social selling vs. structured ecommerce · Diaspora buying guides · Pre-store entrepreneur education · Written for the Caribbean digital consumer, not the Webgold buyer. Indirectly warms EMP pipeline and supports client store conversion rates. See CMIF Tab 1 — Content Audience Profiles for full brief context.
Cadence: 1 per month, topic assigned in 90-day content calendar · First post due Week 3 (D15) · Pillar F posts approximately quarterly (1 in 4 months)
Reactive Playbooks
If/then response protocols for events that aren't on the campaign calendar. Four scenario types: competitor moves, crisis and complaints, regional opportunity moments, and reputational attack. Territory nuance is embedded in each.
Do not react to the price — respond with value. The instinct to match a discount creates a race to the bottom and signals insecurity.
- Within 24 hours: STRAT Guide documents the competitor move in the Airtable Competitive Intelligence log (Module 1 input).
- Assessment: Is the competitor's offer credible? Is it eroding existing pipeline? STRAT Guide + Senior Guide assess within 48 hours.
- If pipeline threat is confirmed: Activate a BOFU campaign (C2 variant) that leads with a value anchor — not a price counter. Emphasise what is included in the current plans that the competitor cannot match.
- Content brief: Type 2 Reactive. Campaign code C2-REACTIVE. Fast-track through Module 3 (Steps 1, 3, 4, 7). STRAT Guide owns Gate 1.
- If pipeline threat is not confirmed: No public response. Log the intel. Observe for 2 weeks before reassessing.
Territory note: EC and JA markets are more price-sensitive. In those territories, the value anchor message must be more specific about ROI and risk reduction, not brand prestige.
- Log: STRAT Guide documents in Competitive Intelligence log within 24 hours.
- Assess gaps: Does the new product fill a gap in the Webgold catalogue? Note but do not react publicly.
- If it directly overlaps with a Webgold product: Update the relevant Module 1 competitive card. Schedule an evergreen content refresh (Type 3) to sharpen differentiation messaging.
- No public response required unless the competitor's launch creates direct confusion in the market about Webgold's offering.
- Within 2 hours: OPS Guide acknowledges publicly — one sentence, professional, empathetic. Does not escalate or defend publicly. Example: "We've seen your post and a member of our team will be in touch directly within the hour."
- Within 1 hour of acknowledgement: Account Lead Guide contacts the client directly (WhatsApp or phone, not email).
- Root cause: Is this an isolated incident or a systemic issue? HITL Type 4 gate triggered if it involves a service failure, billing dispute, or SLA breach.
- Resolution: Resolved privately. No public defence. Once resolved and client confirms satisfaction, the public post context is noted in Airtable Incident Log.
- Content freeze: If the complaint is gaining public traction, pause all scheduled social posts in that territory until resolved.
Territory note: In TT, social complaints can escalate quickly via Facebook and WhatsApp broadcast lists. The 2-hour acknowledgement window is non-negotiable in TT.
(false claim, coordinated negative review, bad-faith content)
- Do not engage the attacker directly on public channels.
- Assess: Is the claim false and verifiable? Is it gaining reach? Senior Guide + Programme Manager notified immediately (T3 Hard Gate).
- Legal threshold: If the content is defamatory or commercially damaging, document everything and assess legal options. Do not delete evidence.
- Positive counter-signal: If the attack is gaining reach, activate a content piece (Type 2 Reactive) that demonstrates credibility through client outcomes or social proof — without referencing the attack directly.
- Client communication: If existing clients may have seen the content, the Account Lead Guide proactively reaches out with a calm, factual update.
e.g. A major Caribbean business is hacked or suffers a data breach
These are high-value moments where audience anxiety meets Webgold's solution. Speed and tone matter more than polish.
- STRAT Guide identifies the moment within 4 hours of the news breaking. Confirms it is relevant to the Webgold audience (SME digital security, website management, ecommerce risk).
- Brief initiated immediately: Type 2 Reactive. Fast-track Module 3 (Steps 1, 3, 4, 7). 4-hour production target from brief to publish.
- Tone: Empathetic and informative — not opportunistic. Do not name the affected company. Focus on the risk category and the protective action. Example angle: "Why Caribbean businesses are more exposed than they think — and what you can do today."
- Channel: Social (Instagram + Facebook) first for reach. WhatsApp broadcast for existing warm contacts. Email sequence variant if the moment has a longer tail (e.g., an ongoing security incident).
- Health Check CTA: Every TOFU moment piece should connect to the Health Check as the conversion action — the moment of anxiety is the best time to offer a diagnostic.
Territory note: In TT, news travels extremely fast via WhatsApp. Being first and credible on WhatsApp in TT is more valuable than any platform ad spend in the first 24 hours of a news cycle.
e.g. National budget, new business regulation, major employer hiring freeze
- Assess relevance: Does this affect SME spending on digital? Does it create urgency or anxiety that Webgold can address?
- If relevant: Brief a Type 2 Reactive piece within 24 hours. Tone: practical guidance, not political commentary.
- If uncertain: STRAT Guide + Senior Guide decide within 6 hours. Default is "observe and log" rather than react.
Analytics & Measurement Flags
The intelligence layer that tells the team when to change course. Defines KPIs per campaign and waypoint, establishes threshold flags, and links each flag to a specific action protocol.
| Metric | Baseline / Target | Flag Threshold | Level | Response Protocol |
|---|---|---|---|---|
| Health Check Completion Rate W2→W3 conversion |
PLACEHOLDER — set at launch | Drop below target for 2 consecutive weeks | RED | STRAT Guide initiates a C2 campaign review. Check: landing page copy (A-001 review), channel distribution, territory performance split. If TT is underperforming specifically, check against Carnival/post-budget calendar. |
| Health Check → Conversation Rate W3→W5 conversion |
PLACEHOLDER — set at launch | Drop below target for 2 consecutive weeks | RED | Review the W4 results delivery experience. Is the Health Check output compelling enough to drive a conversation request? Brief a Type 3 Evergreen refresh of the results page. HITL Type 3 Strategic gate — STRAT Guide decision. |
| Email Open Rate — Nurture Sequence (C3) 5-email sequence |
PLACEHOLDER — set after first 200 sends | Below 20% on Email 1 or below 10% on Email 3+ | AMBER | CON Guide reviews subject lines against A/B test data (MKT-008). Brief a variant brief for lowest-performing email. Fast-track through Module 3 (Steps 1, 3, 4, 7). |
| Monthly Client Churn Rate Support HQ active clients |
Target: <3% monthly | Exceeds 3% in any calendar month | RED | Account Lead Guide conducts exit review with churned clients (within 5 business days). Root cause logged in Airtable. If pattern identified across 2+ churns: Senior Guide + Programme Manager strategic review. Retention content (C5) brief initiated if messaging gap is identified. |
| Plan Upgrade Rate W10→W11 expansion |
PLACEHOLDER — set at Month 3 | Below target for 2 consecutive months | AMBER | Review C5 (Retention & Upsell) campaign performance. Are upsell touchpoints reaching clients at the right time? Check MGT-002 hours consumption data — clients consistently at <50% hours are candidates for upgrade conversation, not upsell email. |
| Referral Programme Activations C6 · ⏸ PAUSED |
— | — | PAUSED | Partner-based marketing is on hold. This trigger row is inactive until the programme resumes. Do not act on. |
| WhatsApp Qualification Completion ManyChat flow — W1→W2 |
PLACEHOLDER — set after first 100 flows | Drop-off above 50% at any single step | AMBER | CON Guide reviews the drop-off step. Brief a revised message variant for that step. Test with 50 contacts before full rollout. All WhatsApp message changes require T2 Soft Gate before deployment. |
| HITL Gate Rejection Rate Module 3 Gate 1 |
Target: <20% first-pass rejection | Above 30% in any 4-week period | WATCH | If Gate 1 is rejecting more than 30% of content first-pass, the problem is upstream — the brief standard or intelligence pull (Steps 1–2). QA Guide and CON Guide review the brief quality in the Airtable record. Likely cause: briefs are insufficiently detailed or intelligence pull is being skipped. |
HITL Governance
Full gate specifications for the GTM system. Three-layer framework: Type (what is validated) × Severity (operational consequence) × Context (application-specific label). This module feeds the overarching Webgold HITL policy.
Type 2 REVIEW: Output quality review. Can proceed with annotation if flagged.
Type 3 STRATEGIC: Direction-setting decision. A Guide with strategic authority must weigh in.
Type 4 EXCEPTION: Error handling, escalation, brand/legal risk. Immediate halt.
T2 Soft-Gate: Blocking. Work cannot proceed until a Guide confirms. Standard SLA: 4 business hours.
T3 Hard-Gate: Blocking + escalation. Senior Guide or Programme Manager notified immediately. Work suspended until resolved.
Site Map
Full structure of the GTM Execution Portfolio HTML. Each module is a page. Behaviours and content status noted per section.
/m1 — Intelligence Layer · Competitive landscape cards (4 territories) · Persona cards (blocked DEC-006) · Tech stack reference links
/m2 — Campaign Architecture · Waypoint Library W1–W11 · Campaign Index C1–C7 + C-DX
/m3 — Creation Framework · Content taxonomy (5 types) · Brief standard (7 fields) · Brief intake form (interactive) · 8-step workflow · HITL gate map
/m4 — Channel Playbooks · 5 channels · Territory nuance (TT, BB, JA, EC)
/m5 — Asset Portfolio · Asset cards with live status (PLACEHOLDER/DRAFT/REVIEW/BLOCKED/FINAL) · Decision block links
/m6 — Reactive Playbooks · Competitor response (2 scenarios) · Crisis management (2 scenarios) · Regional opportunity/TOFU (2 scenarios)
/m7 — Analytics & Flags · 8 trigger conditions with thresholds and response protocols · 3-tier review cadence
/m8 — HITL Governance · 3-layer framework · Role definitions (6 roles) · Notion policy link placeholder
/sitemap — This page
/decisions — Open decisions tracker (5 open decisions with DEC references)
When a GTM package is finalised and live, its URL is added to the Webgold GTM Index in Notion — a personal space for Gem that will surface for the team. The Notion GTM Index lists one entry per product GTM package with: product name, link to HTML file, status (Live / In Build / Draft), and date published. Governance documents (HITL policy, content standards, role definitions) will also be linked from that space. [Notion GTM Index link — add when live]
Open Decisions
Decisions from the Master Decision Log that are currently blocking or affecting GTM assets in this portfolio. Resolve these to unlock blocked assets.
Full Decision Log: Webgold 2026 — Decision Log.md · WG-21 specific: WG-21 — Decision Log.md