7
Joined
The day-7 operator scorecard
Every Monday at 8am local, Foothold sends one email to the operator. Four numbers, three names, one change line. Readable in under sixty seconds. Pastable into your monthly metrics doc, your investor update, your standing one-on-one with a co-founder. Below is the actual rendered email — example data from a 460-member paid community of product managers.
FromFoothold <hello@foothold.community>
ToMaria — PaidPM operator
DateMonday, April 21 · 8:01 AM
PaidPM, week of Apr 13–19 → 7 joined, 4 activated (57%)
Maria — your week-13 cohort closed yesterday. Here is the scorecard.
57%week-one activation
last 4 weeks 52% · 48% · 61% · 55% → 57%
4
Activated
2
Stalled
1
Ghosted
Three names worth a personal DM this week
Stalled members, ranked by ICP fit. Plain-text DM templates pre-filled when you click through.
-
Sarah Kim — Senior PM, Stripe (joined Apr 14)Replied to your day-0 DM with “intro coming this week,” never came back. Picked goal-track find a co-founder. Has read 3 channels but posted in 0. ICP fit: 9/10 — exactly the persona PaidPM was built for. Open DM →
-
James Mowat — PM Lead, Atlas (Series-B fintech, joined Apr 15)Picked goal-track level up to head-of-product, never posted. The day-3 nudge fired Apr 18 with the recommended #principles channel; opened twice, no reply. ICP fit: 8/10. Try a one-line ask about his recent move into a leadership role. Open DM →
-
Aditya Rao — Sr PM, Onfleet (joined Apr 13)Replied to day-0 DM asking how #principles differs from #frameworks. You answered. He never came back. ICP fit: 7/10 — your reply may have read as transactional; soften with a question of your own. Open DM →
What changed in onboarding last week: shortened goal-track options from 5 to 3 (dropped “explore PM as a career” and “build community,” kept “find a co-founder,” “level up,” “ship my first product”). Hypothesis: shorter list raises pick-rate. Next Monday's scorecard will tell us.
↑ Mockup — example data, no real customers (Foothold is pre-launch). Email renders the same in Gmail, Apple Mail, Outlook desktop and Outlook Web. Plain-text fallback ships in every send.
Why this email looks like this
The scorecard exists for one job: get the operator to take an action this week that they would not have taken without it. Every design choice is a defence of that job. Below is the per-section reasoning so you can argue with it before we ship it to your community.
One subject line that delivers the headline before the email opens
The subject line carries the cohort label, the joined count, the activated count, and the activation rate. If the operator is on a treadmill or in a meeting, the subject line alone is the report. The body is the supporting detail for the subset of weeks the operator wants to act.
Four numbers, in this order, every week
Joined → Activated → Stalled → Ghosted is the funnel left-to-right. Same order every week so the operator's eye learns where to land. Activation is coloured moss-green; stalled is amber; ghosted is rust. Colour is decoration, not data — every number is also stated in the headline and in a plain-text fallback for screen readers and Outlook 2007.
What we deliberately do not show: a sparkline. A pie chart. A breakdown of which channels members read. A heatmap of what time of day people open Slack. A confidence interval. None of those produce a Monday-morning action. They produce a 9am dashboard refresh and a 9:02am tab-close.
The compare line — last four weeks beside this week
One line of monospace digits, last four weeks then this week in clay. No graph. The operator does not need to see the trend visually; they need to know whether 57% is up, down, or flat against recent history. Five numbers in a row answer that in three seconds. If the operator wants the longer view, the “open the rolling 4-week archive” link in the footer goes to a real page with a real chart — but the chart never lives in the email.
Three names, with a why-line, ranked by ICP fit
This is the part the operator will actually act on. The criteria are deliberately tight:
- Three names. Not five, not ten. The point is "before you make coffee on Monday, send three DMs." A list of ten is a list of zero.
- Stalled, not ghosted. A stalled member reached for the rope and let go. They read; they replied to the bot; they almost posted. A ghosted member never engaged at all and the right intervention is not a personal DM, it's a different day-0 DM next cohort. We rank stalled because the operator's hour spent on stalled members converts; the same hour on ghosted members does not.
- Ranked by ICP fit, not by recency. ICP fit is a 1–10 score from the data you gave us at install (job-title patterns, company-size band, goal-tracks the operator cares most about). Recency would surface whoever joined last; ICP fit surfaces whoever the community most needs to keep.
- Why-line is one sentence and one ask. Not a profile. The why-line tells the operator what the member did and what tone the DM should take, not who they are. The operator already knows who Sarah is — they let her in.
One “what changed” line — so the trend connects to actions
Step 4 of the playbook works only if step 5 (the weekly cadence review) runs. The “what changed last week” line bridges them. It is whatever single change the operator deployed Monday morning of the prior week — a new goal-track option, a different day-3 nudge text, a different recommended channel for a goal. Three months in, the rolling archive shows a column of changes against a column of activation movements, and that column is the operator's playbook for their specific community.
What the email does not do
- It does not embed a 30-day churn forecast. We do not have enough signal to compute one honestly, and a fake one would erode trust in the four numbers that are honest.
- It does not nag the operator if they don't open it. The cadence-review meeting is the operator's job. We deliver the artifact; the meeting is theirs to keep.
- It does not have a "schedule a call with our success team" button. There is no success team. There is a $49–199/mo product, an honest email every Monday, and a public roadmap.
How the numbers are computed
All four numbers come from the Slack Web API on a 7-day rolling cohort window. Joined = team-join events in the cohort. Activated = a non-bot, non-DM message in #introductions (or whatever channel the operator marks as the intro channel) within seven days of join. Stalled = at least one DM reply to Foothold's day-0 message but zero qualifying public posts. Ghosted = no reply to the day-0 DM and no public post. The cohort closes Sunday at 23:59 in the operator's timezone; the email lands at 8am Monday.
ICP fit is computed at install from a one-page form (target job titles, company-size band, goal-tracks you weight most heavily). If you do not fill in the form, every member is scored 5/10 and ranking falls back to recency. Filling it in takes about three minutes and is the single highest-leverage thing you do in onboarding the bot itself.
Why an email and not a dashboard
A dashboard requires the operator to remember to open it. An email arrives in the place the operator already opens twenty times a day. Three months from now, when the operator forwards a screenshot of the scorecard to a co-founder with the message "this is the number we are moving," the screenshot is of an email — because the email is what they actually see every Monday. A dashboard would have produced a habit decay curve that bottoms out in week six.
If you want the dashboard view as well, the rolling 4-week archive linked from every email's footer is your dashboard. We are happy to build one. We are unhappy to make it the primary surface.
If something in the mockup feels wrong: tell us before we build it. The whole point of shipping the preview before the product is to argue about the design while the cost of changing it is one HTML edit. Email hello@foothold.community with the line you'd cut, replace, or add. The first ten operators who send substantive feedback get Pro free for the first year.
Want this email to land in your inbox every Monday?
Foothold is opening a small early-access cohort. Join the waitlist and we'll get you a real PaidPM-style scorecard on real data from your community within fourteen days of install.
Join the waitlist Or read the full 6-step onboarding playbook the scorecard plugs into.