★ Marketing
What we deliver — the external headline numbers.Total visibility delivered ⓘReach + email opens of content PUBLISHED THROUGH Glowtify for paying clients (not their organic content). IG/FB reach + LinkedIn impressions + email UNIQUE OPENS. A conservative FLOOR — broken/disconnected connectors only ever undercount.DIRECTIONAL
people reached + emails opened, cumulative for clients
2.5M reach + opens delivered · FY 2026 Q4
⚠ Survivorship-safe: connector history before this is omitted — the airbyte migration deleted ~half of churned clients' history (only 10–13 of 25 retained), so older quarters silently undercount and cannot be fixed. This is frozen each quarter while the cohort is fully active, so a clean trend builds forward from here. Within a quarter, ~55–65% of paying-cohort posts match a reach row (Instagram insights expire at the API), so this is a consistent floor; email dominates magnitude.
Total content published ⓘCount of pieces PUBLISHED THROUGH Glowtify for paying clients (a real published URL), excluding bulk product-SEO. Point-in-time paying, outlier-clamped. The zero-caveat hero number — a logged event, survivorship-immune.HIGH RELIABILITY
pieces published for clients · across blog · social · email · ads
2k cumulative · 900 in FY 2026 Q4
Published-only and paying-only by construction (organic dwarfs it and isn't our work). Deduplicated; outlier-clamped at the 95th percentile so one bulk-publisher can't distort the total.
Audience reached ⓘTotal ADDRESSABLE audience across managed accounts, per quarter: email subscribers (Klaviyo list size — DEEP history via first-seen date) + IG/FB/TikTok followers. Email subscribers are counted as-of each quarter end (real history); social followers are held at current value, gated to the clients paying that quarter. LinkedIn follower table has no store key in BQ.HIGH RELIABILITY
email subscribers + social followers · split premium / self-served · FY 2026 Q4
6.7M reachable · 6.0M email + 658k social · FY 2026 Q4
Premium
10k
Self-served
6.7M
premiumself-served
⚠ Survivorship-safe: connector history before this is omitted — the airbyte migration deleted ~half of churned clients' history (only 10–13 of 25 retained), so older quarters silently undercount and cannot be fixed. This is frozen each quarter while the cohort is fully active, so a clean trend builds forward from here. Email subscribers dominate (a list IS reachable audience), concentrated in a few large consumer lists → premium < self-served (premium = B2B, small lists). Social platforms (IG/FB/TikTok) only sync since Feb 2026; LinkedIn not mappable in BQ — so the other platforms start here too.
Website traffic driven ⓘOrganic website sessions (GA4) for managed brands — organic search (incl. the SEO Glowtify does) + organic social. This is the Glowtify-driven slice, per quarter (real GA history back to 2023). Excludes Direct/Paid (not ours) and the bot-inflated Unassigned.DIRECTIONAL
organic + SEO sessions Glowtify drives · per quarter
858k organic sessions · FY 2026 Q4
⚠ Survivorship-safe: connector history before this is omitted — the airbyte migration deleted ~half of churned clients' history (only 10–13 of 25 retained), so older quarters silently undercount and cannot be fixed. This is frozen each quarter while the cohort is fully active, so a clean trend builds forward from here. Organic = organic search (incl. the SEO Glowtify does) + organic social — the Glowtify-attributable slice; email/SMS referrals sit in GA "Other"; total GA is larger but bot-inflated.
Ad impressions delivered ⓘPaid ad impressions delivered for clients — Meta (mapped via meta_sessions.defaultAdAccountId, the recovered mapping) + Google (Glowtify-created ads). Combined.DIRECTIONAL
paid ad impressions · Meta + Google combined
1.23B impressions · FY 2026 Q4
⚠ Survivorship-safe: connector history before this is omitted — the airbyte migration deleted ~half of churned clients' history (only 10–13 of 25 retained), so older quarters silently undercount and cannot be fixed. This is frozen each quarter while the cohort is fully active, so a clean trend builds forward from here. Meta mapped via defaultAdAccountId (~5 paying advertisers, concentrated in one); Google = Glowtify-created only (83k impr). A few-client signal, not base-wide.
Client visibility growth (YoY) ⓘPer-client TOTAL reach vs the same quarter a year ago — uses ALL the client's account content (the only way to get a year-ago baseline), NOT just Glowtify-published. Clients ≥3 months tenured; broken-connector channels excluded; per-client deltas capped. Methodology-fragile by nature — an analyst drill-down, not an exec KPI.DIRECTIONAL
do clients gain visibility while with us · all-content baseline · avg client
+51% avg client YoY · FY2026 Q4 · n=23 clients (13↑ 10↓)
⚠ Measures whether clients GAIN visibility while with us (their organic included) — not what we delivered (that's the visibility card above). Small n; early quarters ride launch-ramps off near-zero baselines. Per-client detail and excluded channel-breaks: detailed board.
A · Business
Is the business growing and holding?Paying base ⓘPaying workspaces (billing whitelistSource = Shopify / QuickBooks), split by customerType. Trend is point-in-time per quarter — since-churned clients still count in the quarters they paid (no survivorship bias).HIGH RELIABILITY
premium vs self-served · the commercial size of the business
Premium
33
Self-served
23
Total paying
56
premiumself-served
Source of truth = the billing record. Premium is the MRR engine (pair with HubSpot MRR off-page); self-served is deliberately concentrated, not maximized — so workspace count, not MAU, is the honest scale unit.
Publishing retention ⓘOf paying workspaces that published in a quarter, the share that published again the next quarter — ENGAGEMENT retention (behavioral, leading). Split premium vs self-served. Excludes the in-progress quarter. True REVENUE retention lives in HubSpot, off this page.HIGH RELIABILITY
engagement retention · publish in Q → publish in Q+1
Premium
100%
Self-served
84%
latest
26-Q3→26-Q4
premiumself-served
Behavioral retention — catches a client going dark a quarter before it shows up as churn. It is the engagement guardrail under the throughput metric in Operations. (Revenue/logo retention = HubSpot.)
Customers at risk ⓘPaying customers who ACTIVATED (published at least once through Glowtify) but have NOT published in the last 30 days — going dormant, an early churn signal. Current paying only; brand-new customers (activated <30 days ago) excluded. Dated by the task start timestamp, matching the retention & MMPS cards; scheduled/future posts don't count as activity.HIGH RELIABILITY
activated but silent 30+ days · early churn signal · as of 2026-08-24
9 of 39 activated ≥30d ago · 23% at risk
Premium
1
Self-served
8
The separate gap: 12 paying workspaces have never published through Glowtify at all (never activated) — an onboarding problem, not dormancy. Named per-customer list on the detailed board.
Strategy delivery — sold vs published ⓘWhat each paying customer was SOLD (channels in their in-app marketing strategy) vs what Glowtify actually publishes for them. Delivering = at least one publish on that channel in the trailing 30 days; dated by the scheduled publish slot (endTimestamp — this card's own convention, distinct from the other cards). Score = % of sold channels delivering, averaged over customers WITH a documented strategy; the documentation gap is shown beside it. The in-app strategy feature shipped 2026-03-18 — customers onboarded before that were never documented.HIGH RELIABILITY
are we delivering what was sold · trailing 30 days
41% of sold channels delivering · avg over documented strategies
Documented
23
Empty doc
28
No doc
5
Leading churn signal — a sold-but-silent channel is a broken promise. Only 23 of 56 paying customers have a documented strategy, so the score covers those; closing the documentation gap is the prerequisite to steering by this number. Per-customer gaps on the detailed board.
B · Usage
Is the product used deeply and stickily? (premium and self-served behave very differently)Publishing per active store ⓘMedian pieces published through Glowtify per ACTIVE store per quarter (winsorized @ p95 so one bulk-publisher can't distort it). Excludes product SEO. Premium = operator output; self-served = product autonomy.HIGH RELIABILITY
winsorized mean per active workspace · FY 2026 Q4
Premium
13.0
Self-served
20.4
premium (operator output)self-served (autonomy)
Never blended — the per-store value gap makes a combined median meaningless.
Depth — multi-channel publishers (MMPS) ⓘShare of publishing workspaces that published to 2+ channel families (social / email / blog-SEO / ads) WITHIN A MONTH; quarterly bar = average of the monthly rates. Breadth = stickiness = vendor lock-in. Lead the self-served line: a self-served merchant on 2+ channels is genuinely embedded; premium breadth mostly reflects operator coverage.HIGH RELIABILITY
% multi-channel in a month · lead self-served for lock-in · FY 2026 Q4
Self-served
42%
Premium
19%
self-served (true lock-in)premium (operator coverage)
Self-served breadth is the merchant choosing to depend on Glowtify for more of their distribution — the truer stickiness signal. Penetration context: Glowtify drives 5% of a self-served client's total reach (median) vs 48% premium — premium's high share is near-tautological (we are their team), so it reads as dependence, not added value.
Active contributors per store ⓘDistinct CLIENT-SIDE people who created, commented on, or reviewed content that month (NOT logins; Glowtify operators excluded). The 'involve the team' (Bet 01) signal — are the client's own people participating in the motion, or is it a single champion. Avg per active workspace.HIGH RELIABILITY
client team members participating · FY 2026 Q4
Premium
1.94
Self-served
1.96
premiumself-served
Contributors, not viewers — measures participation in the motion (the bet), so it excludes pure lurkers and Glowtify operators. For premium it asks the sharp question: is the client's team engaging, or are we doing it all for them.
Iterations per shipped piece ⓘPublished tasks only — never unpublished drafts. AI chat turns = user messages per published task; % used chat = share of published tasks refined with the conversational AI chat (launched ~Mar 2026, so earlier quarters are genuinely 0). Reviews & comments are the human-collaboration secondary signal. Falling chat turns over time = generation improving.HIGH RELIABILITY
AI chat turns per published task + adoption · FY 2026 Q4
Chat turns / task
1.55
Used chat
45.4%
Bars = % of published tasks refined with AI chat (adoption). Human collaboration in FY 2026 Q4: 50.9% of published tasks reviewed · 1.31 comments/task. This is NOT "% AI-generated" — essentially all Glowtify content is AI-generated; it tracks refinement effort per shipped piece.
Channels connected / workspace ⓘPublishing & analytics integrations connected per paying workspace (Facebook, Instagram, LinkedIn, TikTok, GA, email) — how much of the client's stack is wired into Glowtify. Recomputed live each rebuild from the session docs / airbyte.HIGH RELIABILITY
integrations wired in · distribution across connected workspaces
3.5 avg per connected workspace · 45 connected · 11 not yet connected
Distribution of connected workspaces by number of connected channels — more channels wired in = more of the client's distribution depends on Glowtify. ⚠ Meta-ads connections understate true advertisers (the migration broke the store↔ad-account mapping — GLOW-8032).
C · Operations
Are we running the premium (managed) base efficiently?Managed output & operator leverage ⓘPremium MANAGED output = content published by Glowtify premium operators per quarter, shown with operator HEADCOUNT beside it — NOT a divided per-operator ratio, because the active-operator count swings 3-7/quarter on who clicked publish, so a ratio lurches on the denominator, not on efficiency. Output rising on flat headcount = leverage.THROUGHPUT
premium operator throughput · output with headcount as context, not a cost ratio
Managed output
333 / FY 2026 Q4
Active operators
4
≈ per operator
83.2
The investor headline is revenue per operator (MRR ÷ operations headcount — can revenue grow without headcount growing). It is computed off-board: MRR lives in HubSpot and revenue is never published on this page. This card is its product-side proxy — output grew while headcount stayed flat (3–7 operators/quarter) = operator leverage, the half of the roadmap aimed at reducing time spent operating clients. Quality guardrail: premium publishing retention 100% (latest) — output is only leverage if managed clients keep engaging. True hours-per-piece / $-per-operation are not instrumented (no timers/timesheets); a direct NPS/satisfaction signal is the missing piece (survey-based, not yet in the warehouse).
⚠ Don't read "≈ per operator" as a quarter-to-quarter efficiency ratio — the active-operator denominator is volatile (3–7 on who published). The defensible signal is the OUTPUT trend against roughly-flat headcount, guarded by retention. For revenue per operator, divide by payroll operations headcount (stable), not active publishers.