1. Channel–Market Fit: Choose the Channel That Fits the Economics
Channel–market fit exists when a channel's fixed properties match a product's economics and buying conditions. The most popular channel is not automatically the right one: a channel can be excellent in general yet unprofitable or irrelevant for a particular product, ICP, and stage.
Three failures illustrate the distinction:
- A B2B SaaS founder spent ₹3 lakh on TikTok creators. TikTok was popular, but a buyer looking for a meeting recorder was more likely to be on LinkedIn, Slack, or talking to peers during work.
- A B2B company with an average contract value of ₹1,000/month spent ₹2 lakh on LinkedIn ads and faced CAC around ₹8,000. The CAC–ACV maths could not work.
- A founder spent ₹5 lakh on Google Ads for a product nobody searched by name, against competitors with 10× the budget. The ads ranked low and produced near-zero conversion.
Exam tip: Product–market fit without channel–market fit cannot scale; channel–market fit without product–market fit also fails. Both are required.
Six channel properties
Evaluate every possible channel—LinkedIn, WhatsApp, SEO, creators, billboards, or otherwise—on these properties.
| Property | Decision question | Examples |
|---|---|---|
| Targeting | How precisely can it reach the exact ICP? | LinkedIn: company, role, industry; Instagram: interests/behaviour; billboard: anyone passing |
| Control | How much can spend, audience, creative, or keyword selection predictably affect output? | Paid ads are high-control; organic/word of mouth is lower-control |
| Input | What does it truly cost in money, time, skill, and talent? | Creator partnerships need content capacity; SEO needs technical/content skill; outbound needs a list, writer, and GTM capability |
| Output | What is the expected volume and quality shape? | Meta may create high-volume/low-quality B2B leads; search can create lower-volume/high-intent leads |
| Time to result | How long before success/failure is observable? | Paid ads: days; SEO/YouTube: often 6–12 months |
| Scalability | Can effort/spend increase 10× while retaining useful output? | Google Ads can expand; Product Hunt is mainly a one-launch event; founder-led sales cannot create 10 founders |
Input cost includes more than media spend: creative production, campaign management, analytics, and founder/team time must be included.
Four product characteristics to match
| Product characteristic | Why it changes the channel choice |
|---|---|
| Price point / ACV / AOV | A ₹999/month product cannot support a CAC that a ₹50,000 contract can support. Low ACV rules out many paid channels at first. |
| Purchase frequency | A ₹1,000 monthly customer retained 10 months yields ₹10,000; ₹3,200 CAC can work. For a ₹1,800 one-time event ticket acquired at ₹2,000 CAC, every sale loses ₹200. |
| Market size | Narrow B2B ICPs need precise targeting; broad B2C audiences can use broader channels. |
| Consideration time | An impulse cosmetic purchase needs immediate conversion; a 30–90-day B2B purchase needs lead nurture. |
The full choice is a 10-point match: six channel properties × four product characteristics. A fit matrix can classify each row/column intersection as green (strong), amber (marginal), or red (poor).
| Product type | Typical strong fits | Typical poor fits |
|---|---|---|
| B2B low ACV (≤ about ₹3,000/month) | LinkedIn organic, long-tail SEO | Many paid channels: CAC:LTV generally fails |
| B2B mid/high ACV | Precise outbound, paid LinkedIn/search where economics work | Broad, low-intent reach where targeting is weak |
| B2C impulse/considered | Instagram organic, micro-creator seeding, relevant SEO | Cold consumer email, LinkedIn |
| B2C subscription | Creator/social proof plus category/search demand | Channels whose CAC cannot be repaid by retention |
Clairo versus Zoko
| Brand | Economics and ICP | Strong channel choices | Poor channel choices |
|---|---|---|---|
| Clairo | B2B SaaS; ₹999 Pro and ₹2,499 Team; 10–100-person growth-stage B2B teams | Product Hunt + founder LinkedIn content; founder-led outbound; long-tail SEO such as “meeting recorder for sales team” or “auto follow-up email after calls” | LinkedIn paid at low ACV; TikTok; billboards/TV |
| Zoko | D2C skincare; broader women 24–34 audience | Instagram Reels + micro-creators; Amazon (stated 12% traffic and high purchase intent); branded/near-branded Google Shopping; limited high-intent SEO | LinkedIn; cold consumer email; large SEO investment whose cost/time does not fit the ACV |
For Clairo, outbound is high-control and economically sensible at roughly ₹12,000–₹30,000 annual value, though founder time limits scale. SEO has 6–9-month time to result but can become the lowest-CAC channel. For Zoko, Amazon has marketplace margin cost but lower acquisition friction; Instagram creates awareness and Google Shopping captures resulting branded/category intent.
Four-step channel-selection method
- List 10–15 theoretically plausible channels without filtering.
- Score each on the six channel properties using a 1–5 scale.
- Cross-check against price, frequency, market size, and consideration time; eliminate any channel with a direct fit failure.
- Test only two or three channels.
One channel creates concentration risk and no comparison. More than three disperses attention. With a quarterly growth budget below ₹2 lakh, start with two; with more budget, test three. Use comparative output to reallocate money, effort, and creative capacity.
Key takeaways
- Popularity is not fit; channel properties must match product economics.
- Assess targeting, control, input, output, time to result, and scalability.
- Match those six properties with price, frequency, market size, and consideration time.
- Low ACV usually rules out expensive paid acquisition early.
- Test two or three channels—not one and not many.
2. B2B Outbound: A Five-Component Acquisition Machine
B2B outbound is not “send cold emails and see.” It is a controllable system that turns a targeted stranger list into qualified meetings. The system fails if any component is missing.
| Component | Function | Diagnostic when it breaks |
|---|---|---|
| 1. List | Defines precisely who to reach | Reply rate below 2% can indicate poor list, trigger, or message |
| 2. Trigger | Establishes why outreach is relevant now | Untimed “interesting, maybe later” replies |
| 3. Message | States a relevant problem/value and earns reply | Long feature-led messages are ignored |
| 4. Sequence | Sets number, channel, and spacing of touches | Positive interest does not turn into meetings if follow-up is weak/too short |
| 5. Reply engine | Moves replies immediately to a scheduled sales process | Replies cool down before meeting is booked |
Common pseudo-outbound failures are: an unfiltered purchased list of 10,000 generic contacts; an ICP-filtered list with no timing trigger; and a good list/trigger that receives only one touch. In a proper sequence, 60–80% of replies arrive at touches 2–4.
1. Build the target list with four filters
| Filter | Meaning | Clairo application |
|---|---|---|
| Firmographic | Company size, revenue, geography, industry | SaaS companies with 10–100 employees in India/Southeast Asia/other defined markets; can remove 80% of a database |
| Technographic | Software/technology already used | HubSpot or Salesforce users, where Clairo integrates and has value |
| Role | Named buyer/influencer, not a department | Founder, head of sales, account executive leading a sales team—not SDRs who lack buying authority or IT teams that do not use it |
| Behaviour | Observable movement toward the problem | Sales hiring, funding, job posting, public pain statement |
The list is not a database. It is a database narrowed by filters into an actionable group. A 50,000-company database can become a roughly 600-company monthly target for one Clairo outbound operator.
2. Use triggers: “Why this prospect, why now?”
A trigger is an event in a prospect's world that makes the timing relevant. A right company may not need the product today; a trigger makes its likely need visible. Combining a trigger with a filtered list can improve reply rate 2–3×: roughly 1–2% without a trigger versus 4–6% with one.
Strong triggers include:
- Funding raised: budget and team expansion may follow.
- Hiring in the function the product serves: a new sales hire signals a growing sales workflow.
- A related job post: a pre-hire expansion signal.
- A founder/head-of-sales post explicitly describing the problem: reach out within 24 hours (at most 1–2 days).
Triggers decay. A relevant LinkedIn post approached weeks/months later is no longer a trigger. Sources include LinkedIn, job boards, Crunchbase, and prospecting tools such as Clay, Apollo, or Gojiberry; automation can surface signals in real time.
3. Write the 80–120-word four-part message
| Part | Requirement | Clairo-style example |
|---|---|---|
| Trigger reference | One sentence explaining why now | “Saw you hired two sales reps last week.” |
| Problem framing | Two lines in the prospect's language, not feature language | New SDRs can spend early months writing follow-ups instead of selling |
| Specific value | One concrete customer outcome, preferably evidence-backed | Three SaaS teams got reps to first close 40% faster |
| Single CTA | One specific, low-friction ask | “Do you have 15 minutes next Tuesday at 4 pm?” |
Avoid 300–600-word product explanations and generic “let me know if you are interested” requests. A concise, outcome-led message earns attention.
4. Run a multi-touch, multi-channel sequence
For lower-ticket B2B, use about five touch points over 18–27 days. Higher-ticket sales can extend 2–3 months (or longer-cycle relationship work), with greater spacing.
| Timing | Touch |
|---|---|
| Day 0 | First four-part email |
| Day 3 | LinkedIn connection request plus a brief relevant comment |
| Day 7 | Second email with a new proof point, angle, or useful resource |
| Day 10–12 | One- or two-line LinkedIn DM |
| Day 18–21 | Final email / breakup message |
The breakup email states that outreach will stop if timing is wrong. It often has the strongest single-touch reply rate because it removes pressure and lets prospects suggest a later time. Mix email, LinkedIn, and calls where appropriate; cap small-ticket sequences at 25–30 days. Do not compress five touches into five days. If the team cannot run the sequence consistently for 12 weeks, redesign it shorter.
5. Build the reply engine and judge the maths
On a positive reply, send a calendar link within two hours, log the meeting in CRM, and send an agenda confirmation 24 hours before it. A small-percentage funnel is normal:
For a Clairo scenario with 400 prospects and 5% replies:
Outbound works because CAC can remain low even after tools and founder time. The stated example of ₹1,44,000 LTV and ₹35,000 CAC gives about 4:1, above the accepted SaaS guide of 3:1.
Applications and rules
Clairo's message can use subject “Saw your sales rep hiring post,” reference the first-90-days follow-up problem, offer a 40%-faster-first-close proof point, and ask for a 12-minute Tuesday 4 pm discussion—about 110 words total. The reply engine then drives booking, CRM logging, and confirmation.
Zoko can use the same system for B2B partnership outreach to salons, wellness studios, and premium boutiques. Relevant triggers include a new salon opening, a competitor exiting a store, or clean-beauty content on a boutique's social account. Retail cycles may need only 3–4 touches.
Three guardrails:
- If filtering does not eliminate at least 80% of the initial database, the list remains too broad.
- “They are in our ICP” is not a trigger; use an observable event tied to the pain.
- Five light-personalisation touches beat one deeply personalised touch because most replies arrive later in the sequence.
Key takeaways
- Outbound requires list, trigger, message, sequence, and reply engine.
- A trigger is the highest-leverage element because timing creates relevance.
- Use firmographic, technographic, role, and behavioural filters.
- Keep messages to 80–120 words; use a specific CTA.
- Diagnose failure by component rather than declaring outbound ineffective.
3. B2C Organic Loops: Turn a Customer into the Next Acquisition Source
A campaign produces a temporary output while the brand pushes it. A funnel ends at acquisition and requires new spend/effort for the next customer. An organic loop makes a customer the beginning of the next acquisition: use produces visible output, output reaches a new audience, and the new buyer enters the same process.
Hashtag spikes, one-off influencer posts, and “tag and repost” often look like organic growth but are not loops:
| Pattern | Why it is not a compounding loop |
|---|---|
| Hashtag campaign | Posts stop when brand promotion stops |
| One-off influencer | Traffic spike dies when the post leaves the feed |
| Tag and repost | Repost mainly reaches the brand's existing followers; it amplifies a closed audience rather than expanding into customers' networks |
The four loop components
| Component | Question | Requirement |
|---|---|---|
| Trigger | What automatically prompts the current customer? | Timed/event-based, not a manually pushed campaign |
| Action | What does the customer do? | Should make the customer look good, not make them an unpaid salesperson |
| Output | Who sees it? | Must reach the customer's new network, not merely existing brand followers |
| Re-input | How does the viewer become the next customer? | Clear discovery, matching landing page, easy offer, and entry to same trigger |
Three loop types
| Type | Mechanic | Fit |
|---|---|---|
| Content loop | Customer/user creates useful or aspirational content that reaches new viewers | Common B2C / creator and social-proof settings |
| Usage-embedded loop | Normal use exposes the product to non-users, e.g., “Sent via…” badges | Public-adjacent usage; e.g., “Built with Mailchimp” |
| Network loop | Product becomes more valuable with more users, prompting invitations | WhatsApp, LinkedIn, multiplayer games, marketplaces; usually not pure D2C cosmetics or a meeting recorder |
K-factor and cycle time
The K-factor is the average number of new customers generated by each existing customer through the loop:
| K-factor | Interpretation |
|---|---|
| Viral/self-sustaining: each customer brings more than one new customer; rare outside network-effect products | |
| – | Strong: meaningful primary acquisition contributor |
| – | Healthy supplementary acquisition channel |
| Marginal: technically active but needs improvement |
K alone is insufficient. Cycle time determines compounding speed: a K of 0.1 every 21 days can contribute more over 90 days than K of 0.2 every 90 days.
Worked low-K example: 1,000 customers, 20% participation, average reach 300, 2% click-through, and 2.5% landing-page conversion illustrate a loop yielding three customers and a stated . Estimate participation, reach, and end conversion, then divide loop-generated customers by the initiating customer base. To move K above 0.1, improve at least two of participation, reach/content quality, and conversion/re-input.
Design the action for customer status
Customers post when the action makes them look good. They rarely post to promote a brand for free.
| Weak ask | Better customer-centred ask |
|---|---|
| “Tag us for a chance to win” | “Post your day-1 versus day-21 transformation” |
| “Use our hashtag to spread the word” | “Share what your morning ritual looks like” |
| “Share a promo code with friends” | “Show what 21 days did” |
Use this test: Would the customer post it if the brand did not exist? If yes, the brand supplied a useful template for a customer story. If no, the brand is asking for unpaid promotion and participation will stay low.
Re-input: five leak checks
Even high participation fails if the viewer cannot enter the loop.
- Brand identification: can the viewer identify the brand in under three seconds?
- Discovery path: is there a tappable link, searchable profile, or clear next action?
- Landing-page match: does the page match the content seen (e.g., transformation content → transformation page, not generic home page)?
- Conversion offer: is there a clear first action such as starter kit or trial?
- Loop entry: does that first action place the new customer on the same trigger path?
Zoko's 21-day challenge loop
| Component | Design |
|---|---|
| Trigger | Automated WhatsApp at day 21 after purchase: results should now be visible; purchase date fires it without manual action |
| Action | Before/after image using a ready Zoko template and easy Instagram share; reduces design effort to about 90 seconds–5 minutes |
| Output | Customer's 200–400 followers: a new audience, unlike tag-and-repost amplification |
| Re-input | Bio/link to a /21-day page, other transformations, ₹999 starter kit, single CTA “Start your own challenge” |
The template makes the brand recognisable, quick to use, and user-centred. The re-input passes all five checks and places a starter-kit buyer onto their own day-21 trigger.
With 20% participation, average reach 280, and 0.5% click-to-buy conversion:
At a 21-day cycle, this is a strong loop that can compound about four times per quarter. This is why Zoko should prioritise it over a simple referral mechanic.
Key takeaways
- A loop has trigger, action, output, and re-input; omission of any part turns it into a campaign/amplification.
- K-factor and cycle time jointly determine growth contribution.
- Make the customer the hero; brand benefit should be a side effect.
- Output must reach a new customer network, not only existing brand followers.
- Re-input must connect the viewer to the same next-customer trigger.
4. Aha Moments and First-Value Design
An aha moment is the specific, measurable event at which a new user first experiences the exact value the product promised. It is the move from “I will try this” to “this is what I was looking for.”
It is not an adjective (“users feel the magic”), a multi-event bundle (“complete setup, invite team, upload data”), or a vague stage (“fully onboarded”). Those definitions cannot be timestamped, measured, or compressed.
The three requirements
| Requirement | Meaning | Test |
|---|---|---|
| One specific event | A discrete occurrence: first follow-up arrives, first file syncs, first message sends | Can it be pinpointed? |
| Measurable | Logged in analytics with user and timestamp | Can time to aha and activation be calculated? |
| Promised value | Delivers the exact outcome that led the user to sign up | Does it match the landing-page/ad promise? |
Use the core test: Can you name the user, timestamp, and event? If not, it is speculation rather than an operational aha definition.
Data-discovered examples
| Company | Aha event | Evidence/design consequence |
|---|---|---|
| Add 7 friends within 10 days | Users doing this retained; friend suggestions and reminders pushed new users to it | |
| Slack | Team sends 2,000 messages within 14 days | Teams below threshold stopped using Slack; activation is team-level |
| Dropbox | First file successfully syncs within 24 hours | Onboarding was redesigned to guarantee a first sync |
| Follow at least 30 accounts | Below threshold, feeds felt empty; above it, product felt alive | |
| Airbnb | Guest: first booking; host: first 5-star review | Different user types require different aha moments |
These were found by retention data, not guessed. Each is a behaviour strongly associated with retention and close to the product's central promise.
Three-step aha diagnostic
- Segment by retention: cohort A retains at day 30/60/90; cohort B churns in the first week or two.
- Find differentiating event and threshold: identify one specific early behaviour retainers did and leavers did not—e.g., friend count, message count, first feature use. Do not use vague aggregate metrics such as time spent.
- Test causation, not only correlation: push a new-user sample toward the candidate event and compare retention with a control group. If retention rises, it is likely causal; if unchanged, it is merely correlated with users who would have retained anyway.
Use event-level analytics such as Mixpanel, Amplitude, or PostHog. Sign-up counts and broad traffic analytics cannot perform this user-behaviour analysis. When several events correlate, select the one closest to the promised value—not simply the one with the highest correlation.
Time to aha and activation
Use the median, not the mean, because outliers inflate averages. Industry benchmark bands presented are:
| Median time to aha | Typical activation rate | Interpretation |
|---|---|---|
| Under 10 minutes | 60%–80% | User is still in the sign-up-intent moment |
| 10 minutes–1 hour | 35%–55% | Users begin switching to other tasks |
| 1 hour–1 day | 15%–30% | Sign-up urgency is largely lost |
| More than 1 day | Below 15% | Most users have moved on |
Clairo: current median time to aha is 14 minutes and activation is 34%, placing it in the second band. Moving below five minutes is expected to yield roughly a 15–20 percentage-point lift.
Zoko: biology prevents compressing the visible-result moment below 21–30 days. For slow-result products (skincare, fitness, education), accelerate recognition of progress instead: photos, streak counters, milestone notifications, and explicit reveals make incremental value visible before/following the eventual outcome.
Five first-value design principles
- Hard-code the path: give every new user the fastest guided route to aha; exploration can follow value.
- Preload value: supply sample data, content, contacts, calendars, or recordings so users do not do all the setup before value.
- Make aha explicit: use a timely confirmation, notification, animation, or small celebration. A silent aha is functionally close to no aha.
- Strip non-essential steps: defer profile, preferences, and other steps not required for first value.
- Measure time to aha by cohort: what is measured becomes optimisable; apply the principles together rather than in isolation.
Clairo intervention
Clairo's promised value is “never miss a follow-up.” Its aha is receiving the first auto-generated follow-up email after a meeting. The existing path—sign-up → install bot → connect calendar → schedule/join meeting → record five minutes → wait for processing—leaks more than 60% before aha.
Provide a “Try with this sample meeting” button immediately after sign-up. A preloaded 30-second recording can generate a sample follow-up in 90 seconds, giving the user value before a real meeting. Then prompt the next real meeting. The target is time to aha under five minutes and activation from 34% toward 50%.
Zoko intervention
Zoko's aha is visible skin/hair change at day 21–30; 90-day repurchase activation is 38%, meaning 62% of starter-kit buyers never reach/recognise aha. Use a four-touch awareness sequence:
| Day | Intervention |
|---|---|
| 1 | Selfie/baseline capture |
| 7 | WhatsApp prompt with structured side-by-side comparison overlay |
| 14 | “More than halfway” routine reinforcement |
| 21 | Full reveal/transformation card to save/share |
The product does not change. Clairo shortens absolute time; Zoko makes a slow value journey visible and sustained.
Key takeaways
- Aha is one measurable event delivering the exact promised value.
- Find it through retention segmentation, differentiating behaviour, and causal testing.
- Measure median time to aha and compress it where possible.
- For inherently slow outcomes, create earlier recognition checkpoints.
- Do not confuse sign-up, checkout, or onboarding completion with first value.
5. Onboarding Friction: Remove What Does Not Earn a Place Before Aha
Onboarding friction is any step between sign-up/first touch and aha that costs time, attention, or effort without materially helping the user reach aha. It is not synonymous with an ugly interface: a beautiful but unnecessary step is still friction.
Common well-intentioned traps are explanation-first tours/videos, choice-rich personalisation (use case, goal, industry, team size), and profile-data gates. They can create 30–50% drop-off at a choice cluster and collectively move activation from about 60% to 25%.
Four friction types
| Type | Tax paid by user | Symptom | Example | Typical remedy |
|---|---|---|---|---|
| Cognitive | Attention | Abandons while reading/choosing | Choose team size from seven options | Smart default, defer, progressive disclosure |
| Behavioural | Effort | Abandons during clicks/actions | Install extension, fill form, upload file | Automate, defer, remove |
| Emotional | Confidence | Pauses before a possible action | “Send email to team” feels risky/unclear | Clear copy, preview, permission reassurance |
| Technical | Trust | Leaves after error/unexpected screen | OAuth/integration error | Engineering reliability and recovery |
Friction is relational: it can only be judged after aha is known. The audit question is not “is this well designed?” but “is it needed before this aha?”
Five-step friction audit
- Reset to a fresh identity: create a new email/account/device; power-user accounts hide new-user friction.
- Timestamp every step: record seconds, clicks, decisions, waits, and hidden steps.
- Classify friction: one step may contain multiple types.
- Score aha contribution 1–5: 1 = little/no contribution (welcome video, profile field); 5 = indispensable (e.g., Clairo real meeting/recording requirement).
- Prioritise the friction-to-contribution ratio:
High ratios are top reduction priorities.
Why small drop-offs compound
Drop-offs multiply through a journey rather than add. A technical tool example has drop-off rates: sign-up 8%, email verification 5%, welcome video 12%, use-case selection 15%, profile fields 11%, bot installation 20%, and first-meeting scheduling 35%.
Thus, individually reasonable steps leave roughly 30 of 100 users: about 70% loss. For B2C, the same multiplication occurs across days/weeks rather than UI clicks. If 8% stop using a product each week in month 1, only around 60% may still be active at day 21.
Five reduction techniques and the order of use
| Technique | What it does | Example |
|---|---|---|
| Removal | Delete a step that does not contribute to aha | Test removing a non-essential step one at a time |
| Deferred questions | Ask after aha, not before | Move Clairo profile fields to after first follow-up value |
| Automation | Replace user action with system action | Detect email domain and suggest five colleagues to invite |
| Smart defaults | Preselect likely choice; user confirms/changes | Detect/preselect industry from email domain |
| Progressive disclosure | Show only essential options; hide advanced complexity | Show 3 required settings; place 17 others under “Advanced” |
Apply in this order: remove → defer → automate → smart default → progressive disclosure. Each later option preserves more of the original step and generally reduces less friction. Test removals on small cohorts before permanent deletion.
Clairo audit and redesign
| Step | Friction / contribution | Intervention |
|---|---|---|
| Sign-up form, ~30 sec | Behavioural | Smart defaults |
| Email verification | Technical but needed | Retain; keep one-click |
| Select use case from 7, ~60 sec, contribution 1 | Cognitive | Defer post-aha |
| Four profile fields, ~60 sec, contribution 1 | Cognitive + behavioural | Defer post-aha |
| Bot installation/permissions, ~90 sec | Technical + emotional, essential | Keep but improve clarity/UX |
| Calendar connection | Technical, essential | Keep one-click auth |
| Schedule real meeting, hours/days | Behavioural, essential in original flow | Replace with preloaded sample meeting |
| Wait 2–3 minutes for AI | Emotional/behavioural | Keep but show processing progress |
Deferring steps 3–4 and preloading step 7 can reduce time to aha from 14 minutes to under 5 minutes and lift activation from roughly 34% toward 50%.
Zoko audit and redesign
Zoko's friction lies mainly in customer experience between steps, not an in-product setup flow.
| Current phase | Friction | Reduction |
|---|---|---|
| 3–4 shipment-tracking emails | Cognitive | Reduce to one or two useful updates |
| Eight-page brochure | Cognitive | Replace with one-page quick-start card |
| Days 1–20 with no support | Emotional + behavioural; dominant friction | Day 1, 7, and 14 prompts to sustain routine |
| Day 21–30 outcome may go unnoticed | Emotional | Explicit day-21 reveal |
Unlike Clairo, Zoko needs system support to fill silence, not merely fewer screens. The projected result is 90-day repurchase/activation from 38% to 50% without changing product or marketing.
Exam tip: Do not disguise added friction as “personalisation.” A 10-minute personalisation quiz is still friction if it delays aha.
Key takeaways
- Friction is relative to aha, not a judgement of interface beauty.
- Audit from a brand-new user identity and quantify each step.
- Cognitive, behavioural, emotional, and technical friction require different remedies.
- Several small drop-offs multiply into a large activation loss.
- First ask whether a step can be removed; do not optimise a step that should not exist.
6. Activation Metric Design: Put the Right Number on the Dashboard
An activation event is one user-level occurrence at a timestamp. An activation metric aggregates many such events into a cohort-level, time-bound rate. Both are necessary, but they are not the same.
| Concept | Example |
|---|---|
| Activation event | Akash receives his first auto-generated follow-up email at a specified time |
| Activation metric | 34% of free sign-ups receive first follow-up email within seven days |
Avoid three bad metrics:
- Vanity count: “5,000 active users” has no denominator; it can rise while activation rate falls.
- Vague rate: “activation is 75%” omits event, timing, cohort, and base.
- Biased proxy: social posting may correlate with activation but excludes many activated non-posters; optimising posts may not optimise product value.
Four components of a well-formed metric
| Component | Question |
|---|---|
| Event | What exact aha behaviour occurred, as verb + object at a timestamp? |
| Time window | By when must it occur? |
| Cohort | Which precisely named users are included? |
| Denominator | Out of all users who could plausibly have activated, how many did? |
Famous metrics decompose cleanly:
| Product | Event | Window | Cohort / denominator |
|---|---|---|---|
| Add at least 7 friends | 10 days | All new sign-ups / % of sign-ups | |
| Slack | Team sends 2,000 messages | 14 days | New paid teams / % of paid teams; team, not individual-user, unit matters |
| Dropbox | First file sync | 24 hours | Desktop app installs / % of installs |
| Connect with 5+ people | 7 days | New profile creators / % of new profiles |
Select the time window and denominator
Choose the window using:
- Time-to-aha distribution: capture about 70–90% of normally activating users; a 30-day window is noisy if 90% activate by day 5.
- Decision velocity: shorter windows enable weekly iteration; 90-day windows force a quarter of blind work.
- Business-cycle maths: software often uses 7/14/21 days; D2C needs 30/60/90 days because delivery and use take time. Never copy SaaS's seven-day window to customers who have not yet received delivery.
The denominator should be neither too broad (all website visitors: bots and accidental clicks dilute the number) nor too narrow (only users completing all onboarding steps: hides friction). It is usually verified sign-ups for SaaS and first-time buyers/deliveries for D2C—everyone who could have activated.
Clairo metric
Percentage of verified free sign-ups who receive their first auto-generated follow-up email within seven days of sign-up.
| Component | Clairo definition |
|---|---|
| Event | First auto-generated follow-up email received |
| Window | Seven days; median active-user aha is 14 minutes, while weekly feedback remains possible |
| Cohort | Free-tier sign-ups who complete email verification |
| Denominator | Total verified free sign-ups in that cohort week |
Current activation is 34%; target is 50%. A quality guardrail can require the email to originate from a meeting longer than five minutes, preventing trivial/test events from inflating activation. This requires event-level analytics infrastructure.
Zoko metric when aha is unobservable
Zoko cannot directly record “customer saw visible change.” Use the closest defensible downstream proxy. A good proxy is done by almost everyone who experiences aha and rarely by those who do not. Social posting fails because many satisfied users never post; repurchase passes more strongly.
Percentage of first-time starter-kit buyers who repurchase any Zoko product within 90 days of delivery.
| Component | Zoko definition |
|---|---|
| Event | Repurchase, proxy for visible-result aha |
| Window | 90 days from delivery: shipping + 21–30-day biological window + decision time |
| Cohort | First-time starter-kit buyers |
| Denominator | Total first-time starter-kit deliveries in the cohort month |
Current value is 38%; target is 50%+. Exclude repurchases driven by promotions of 30% or more as a guardrail, so the metric reflects value rather than discount response.
Key takeaways
- An event is one timestamped user occurrence; a metric is an aggregate cohort rate.
- A valid metric specifies event, window, cohort, and denominator.
- Window length must fit aha distribution, feedback speed, and natural business cycle.
- Count everyone who could plausibly activate, not visitors or pre-completed users.
- For unobservable aha, use a defensible proxy and explicit guardrail.
7. Corporate Operating Perspective: Alignment, AI, and Fast Iteration
Corporate operating experience reinforces the architecture above. Demand generation is a P&L-oriented discipline: a product and campaign cannot overcome a poorly understood ICP or channel where the audience does not exist. Precision in persona, buying committee, message, and channel is the first requirement.
B2B buying committee and activation
In B2B, buyer and user differ. The CFO cares about cost/bottom-line, a functional leader about visibility/control, and the end user about time saved, easier work, and automation. Licences purchased for users who never activate become retention losses later.
Marketing, sales, product, and customer success should therefore align to one shared value action:
| Function | Contribution to activation |
|---|---|
| Marketing | Attract the customer likely to take the right product action |
| Sales | Sell the same valuable action/outcome |
| Product | Make that action the easiest route to value |
| Customer success | Help customers repeat it and keep realising value |
This shared-goal alignment is the operating logic of RevOps: multiple functions moving toward a common goalpost rather than handing off disconnected metrics.
AI operating principles
AI can integrate spreadsheets, ad platforms, CRM, and other data sources to automate reporting, data retrieval, audience work, and transactional workflows. A well-integrated system can answer cross-source questions such as one-day, seven-day, 30-day ad performance or historical spend without manual reporting.
However:
- AI is a tool, not the source of strategic intelligence.
- Poor workflow design produces poor output, regardless of model.
- Use AI for transactional work; humans retain creative/strategic thinking and novel direction.
- Do not delegate all original thought/creative content to models trained on past material. Create the base insight, then use AI to expand or operationalise it.
90-day channel and learning discipline
Use one primary acquisition driver with most investment and one secondary driver to manage risk/ROI. Keep foundational channels (content, SEO, appropriate events/industry visibility) running within budget, because brand familiarity improves click-through and downstream performance.
Run small tests across additional channels to fail fast before sunk-cost dependence. Do not make a full reversal for every weak result; use rapid, measured iterations in the first weeks. The decision framework remains scale, kill, or iterate—with iteration as the usual third option.
Key takeaways
- ICP precision and buying-committee understanding prevent wasted acquisition spend.
- End-user activation determines B2B retention even when a different role bought the product.
- Align marketing, sales, product, and customer success on one value action.
- Use AI to automate transactional workflows, not to replace judgment or original direction.
- Use a primary channel, a secondary channel, continuous baseline presence, and fast evidence-led iteration.