Phantom Cloud / personas
Ryan, your GTM engineer.
Ships landing pages. Wires integrations. Catches signup drops in real time.
Day one
Ryan's first hour.
Pulls merged PRs in your landing-page or marketing-site repos from the last 7 days.
Knows what shipped to GTM this week.
Reads #gtm or #marketing channel for signup or funnel anomalies.
Catches drops before the daily funnel report does.
Pulls Linear issues labelled gtm or marketing-site in active sprint.
Knows what is in-flight and what is blocked.
Drafts one #gtm summary post plus an experiment writeup.
Approve the post; edit the writeup before sharing.
Asks before sharing the writeup with engineering.
Engineering hates reading raw ticket copy; Ryan rewrites for the audience.
Connected to
Ryan's toolbelt.
GitHub
ConnectedSlack
ConnectedLinear
Optional, for sprint awarenessRyan needs GitHub for marketing-site PRs. Slack for #gtm. Linear for sprint context.
In Slack
What Ryan's first DM looks like.
Slack DM
Ryan
Ryan here.
Ryan
I read marketing-site PRs merged in the last 7 days, plus #gtm signal from the same period. 3 landing pages shipped. 1 signup-funnel drop got flagged in #gtm 2 days ago that does not have a writeup yet. 1 Linear issue ("Pricing page A/B finished") is in done state but the experiment writeup never landed.
Ryan
I drafted a #gtm summary plus the experiment writeup. Approve the #gtm post; edit the writeup before I share with engineering.
Draft
Weekly #gtm summary post
- In
- #gtm
This week in GTM: Shipped: pricing v3 (PR #412, +12% conversion in A/B), enterprise contact form (PR #415), changelog redesign (PR #418). Signup funnel: 2-day drop on May 3 between landing-page-view and start-signup; 18% drop, recovered by May 5 noon. Cause: the pricing-v3 deploy briefly changed the pricing-page CTA from "Start free trial" to "Get started", which underperformed. Reverted in PR #420. Next week: enterprise contact form A/B starting Monday; Linear FRONT-2102 (changelog SEO).
Draft
Pricing A/B experiment writeup
- In
- internal #engineering
Pricing page A/B, results Variant A (control): "Start free trial" CTA, 7-day-free-trial copy, $99/$199/$499 ladder. Variant B (treatment): "Get started" CTA, 14-day-free-trial copy, $79/$179/$449 ladder. 5,200 sessions total over 12 days. Variant B converted 4.1% to start-signup, Variant A converted 3.6%. p < 0.05. Decision: ship Variant B's CTA + 14-day-free-trial copy; keep Variant A's price points (the lower price did not measurably help). Confidence: medium. Sample is small for the price-point arm. Recommend a follow-up A/B on the price points alone, isolated from the CTA change.
Draft
Funnel-anomaly nudge
- In
- #gtm reply
The May 3 funnel drop was the pricing-v3 CTA change. Reverted in PR #420 May 5. Funnel back to baseline by 6pm Pacific. Adding a "gate marketing-site PR if landing-page CTA changes" check to the deploy workflow. Filed FRONT-2107.
What slips past you that Ryan catches.
The receipts.
- The signup-funnel drop that lasted 2 days and would have shown up in the weekly report (3 days late).
- The experiment that finished 6 days ago that nobody has written up.
- The marketing-site PR that shipped without a Linear ticket update.
- The integration breakage in #gtm that engineering does not see because they live in #engineering.
- The summary post you would have written while half-listening to a Friday standup.
Hire Ryan in 30 seconds.
Bring your provider key. Connect Slack. Pick Ryan. He is in your DMs by the time you finish naming him.
Ryan needs GitHub for marketing-site PRs. Slack for #gtm. Linear for sprint context.