How do I ship a viral feature?
Real K-factor measurement, not vibes. Iterate until it actually goes viral.
You'd think 'viral' is luck — Astra runs the K-factor math, ships the right surface area, and iterates until the coefficient actually proves out.
The short answer
Astra ships a viral feature in 14 days using the proven Loom/Calendly/Notion playbook. Day 1-3: she audits your product for viral surface area — moments where users naturally share output (results, schedules, designs, calculations) — and picks the highest-leverage one. Then she designs the share unit: typically a beautiful OG image with your branding, a public viewable URL, and a 'made with [you]' attribution. Day 4-10: she ships it on Vercel with proper Twitter Card and OG metadata, viewable-without-signup links, embed support, and PostHog event tracking on every share + click + signup conversion. Day 11-14: launch with 4 power-user customers, measure baseline K-factor (shares per user × signups per share). After: weekly Lark report on K-factor trend with iteration recommendations. Target K=0.5+ within 60 days; >1.0 means true exponential growth.
How Astra actually does it
- 1Audit viral surface area
Map every user-generated output: reports, dashboards, schedules, designs, calc results. Score each by share frequency × recipient relevance × signup conversion potential.
- 2Design the share unit
Beautiful OG image (1200×630, branded), public viewable URL with no auth required, embed support (oEmbed + iframe), prominent 'Try [your product] free' CTA on the public view.
- 3Ship on Vercel
Next.js dynamic routes, OG image API route, Twitter Cards, full PostHog instrumentation: share_initiated, share_completed, share_link_clicked, share_signup_converted.
VercelPostHog - 4Seed with power users
Identify top 10 NPS promoters via Intercom + product usage. Personally onboard them to the new feature. Their first 50 shares are your baseline K-factor data.
IntercomPostHog - 5Measure and iterate
Weekly Lark report: K-factor (shares/user × signups/share), share completion rate, viral cycle time. A/B test OG image, CTA copy, share trigger. Goal: K>0.5 in 60 days.
LarkPostHog
What it looks like in chat
Live viral feature on Vercel with public share URLs, OG images, embeds, full instrumentation, and a weekly Lark K-factor report driving iteration.
14-day build + ship; weekly K-factor reports; 60-day target to K>0.5.
Ask Astra this right now
We'll spin up your workspace, hand the prompt to Astra, and you see the answer in 60 seconds. Free.
Try this with AstraFrequently asked questions
What if my product doesn't have anything inherently shareable?
Then the viral feature has to be created — most often a result/output/insight that didn't exist before. Astra will look for what users brag about in support tickets and reviews; that's the signal for what to make shareable. If truly nothing exists, she'll recommend not forcing virality and pursuing other growth channels first.
What's a realistic K-factor for B2B SaaS?
K=0.3-0.5 is solid for most B2B (cuts CAC by 30-50%). K>1 is exceptional — Loom, Calendly, Notion all hit it. K<0.2 means the feature isn't actually viral; iterate or kill. Astra benchmarks against your category and tells you if your numbers are good, average, or broken.
How is viral different from referral?
Viral = the product itself drives signups via natural use (sharing a Calendly link). Referral = explicit incentive to invite friends (give $20, get $20). Viral has no incentive but requires shareable artifacts. Referral works for anything but requires explicit user motivation. Most strong companies do both.
What if power users don't share the feature?
She investigates: are they getting friction? Is the share format embarrassing/branded badly? Does the recipient experience suck? She'll do 5-7 user interviews via Intercom to find the actual blocker, then ship a fix in 5 days. If after 2 iteration cycles K is still <0.1, she'll recommend pivoting away from viral.
Run your one-person company.
Hire your AI team in 30 seconds. Start for free.
Free to start · No credit card required · Set up in 30 seconds