100 Daily Signups Growth Plan

# 100 Daily Signups Growth Plan ## BLUF Mode will run every viable acquisition, conversion, activation, proof, and launch motion in parallel from August 2026. No channel waits for a later phase. Each channel starts now, establishes a baseline, and ramps weekly when it produces ICP-qualified signups and first useful product changes. Planning target: ```text Current: 3-6 completed signups/day November 1: 100/day on a rolling 7-day average November 30: 100/day on a rolling 30-day average ``` The required growth model is: ```text ~120 → ~2,000 qualified visitors/day 2.5% → 5% visitor-to-signup conversion 20%+ ICP-qualified share maintained 14.4% → 30% signup-to-first-useful-change Low/noisy → 20%+ Day-7 return ``` This produces an expected November run rate of: - 3,000 completed signups; - at least 600 ICP-qualified signups if the current 20% quality rate holds (expected dropoff with scale); and - approximately 900 users reaching a first useful change at a 30% activation rate. This is a proposed execution plan. It links to, but does not replace, the canonical [330 qualified users growth cycle](../company/GTM/330-qualified-users-growth-cycle.md). “ICP-qualified signup” in this plan is not the canonical qualified-user metric of three distinct PRs within one month. Source baseline: [Next Quarter Marketing Plan — Working Baseline](../../04%20GTM/Next%20Quarter%20Marketing%20Plan%20-%20Working%20Baseline.md). --- ## 1. Current position ### Core 30-day acquisition metrics | Metric | Current | Prior period | Movement | |---|---:|---:|---:| | Unique website visitors | 3,596 | 2,676 | +34% | | Average visitors/day | ~120 | ~89 | — | | Completed signups | 90 | 10 | +800% | | Average completed signups/day | 3.0 | 0.33 | — | | ICP-qualified signups | 18 | 1 | +1,700% | | ICP-qualified share | 20% | 10% | — | | Visitor → completed signup | 2.50% | 0.37% | ~6.7× | | Visitor → ICP-qualified signup | 0.50% | 0.04% | ~13.4× | Peak days have already reached six to eight signups, but weekends and some weekdays still fall to zero. The immediate challenge is turning isolated strong days into a growing, stable run rate. ### Current source evidence | Source | Current evidence | Planning interpretation | | ----------------------- | ---------------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------ | | Branded Google search | ~326 visitors and 10–13 signups | Demand capture after another touch; do not call this non-branded SEO acquisition. | | Cold email | Majority of ~7 email/newsletter signups by UTM | Validated but incompletely attributed. | | There’s An AI For That | ~7 attributed signups | Evidence that its sponsored placement produces traffic/signups; not evidence that more ordinary directory listings will do the same. | | thesaasdir.com | 1 attributed signup | Early referral evidence. | | Organic LinkedIn | 1 attributed signup | Separate from LinkedIn outbound. | | Organic X | 1 attributed signup | Early evidence only. | | Direct/unknown/assisted | Majority of signups unresolved | Requires persisted and self-reported attribution. | Working search rule: ```text Current Google traffic = branded demand capture Current non-branded SEO acquisition = 0 (but we have started ranking) ``` ### Current activation and retention | Product stage | Current 30-day total | Share of 90 signups, directional | | ----------------------------------------------- | -------------------: | -------------------------------: | | Codebase imports | 23 | 25.6% | | Canvas opened | 32 | 35.6% | | First design edit | 10 | 11.1% | | First GitHub PR export created | 3 | 3.3% | | First useful change, supplied combined estimate | ~13 | 14.4% | - Most Day-7 cohorts show 0% return; two recent cohorts showed approximately 14–17%, but samples remain small. - Build Start / Build Succeed must not be used as the guided-demo funnel because completions exceed starts and activity is heavily concentrated. ### Cold-email baseline ```text 1,500 unique leads 5,000 total sequence sends 4-step sequence 79% open rate — directional only 2.9% platform reply metric — denominator/count unresolved 17 positive replies 1.13% lead → positive reply ``` Capacity: ```text 1,400 total sends/day ≈350 new leads/day at full four-step steady state Unlimited cold lead inventory for current planning ``` Current modeled output at capacity: - approximately four positive replies/day; - approximately 0.9–1.6 directly attributed signups/day using the unresolved four-to-seven cold-signup range; and - additional assisted/branded-search signups possible but unquantified. ### LinkedIn-outbound baseline LinkedIn started during the current week: ```text 162 connection requests 87 accepted — 53.7% 64 message replies — 73.6% of messages 22 interested leads — 34.4% of replies 13.6% request → interested ``` Capacity and current planning model: ```text 40 requests/day → ~21.5 accepts → ~15.8 replies → ~5.4 interested leads → ~1.6 expected signups at the 30% planning assumption ``` Interested does not equal signup. The 30% interested-to-signup rate is a forecast assumption until the cohort matures. ### Existing audience - Approximately 186 registered users. - 90, or approximately 48%, joined during the latest 30 days. - Total warm list: 260 people, including registered users. - Do not add the 186 users to the 260-person warm list. Audience segments: ```text Registered + activated Registered + inactive Warm + not registered ``` --- ## 2. Goal and funnel model ### Primary goal **100 completed signups/day on a rolling seven-day average by November 1, 2026.** ### Sustain goal **100 completed signups/day on a rolling 30-day average by November 30, 2026.** ### Quality guardrails The acquisition target is not successful if signup quality and product use collapse. Maintain or reach: | Guardrail | Current | November target | | ----------------------------- | ---------: | ---------------------------------: | | ICP-qualified share | 20% | 10% | | Visitor → signup | 2.5% | 5% | | Signup → first useful change | 14.4% | ≥30% | | Day-7 return | Low/noisy | ≥20% | | Production source attribution | Incomplete | ≥80% attributable or self-reported | ### Required traffic | Visitor → signup | Visitors needed for 100 signups/day | |---:|---:| | Current 2.5% | ~4,000/day | | Target 5% | 2,000/day | | Stretch 6% | ~1,667/day | The plan is built around reaching approximately 2,000 qualified visitors/day while improving conversion to 5%. ### Metric boundary - **Completed signup:** the primary acquisition target. - **ICP-qualified signup:** the quality guardrail used in this plan. - **First useful change:** the activation guardrail; exact ordered-event definition must be finalized. - **Canonical qualified user:** three distinct PRs within one month, subject to unresolved canonical measurement details. At 3,000 November signups, approximately 11% would need to become canonical qualified users for the November signup cohort alone to produce 330. This is directional until the canonical metric window is resolved. --- ## 3. Growth model by medium Every medium starts now and ramps concurrently. The figures below are required contribution targets, not causal forecasts. ### Daily signup contribution ramp | Medium | Aug 31 | Sep 15 | Sep 30 | Oct 15 | Nov 1 | |---|---:|---:|---:|---:|---:| | Branded/direct/word of mouth | 3.0 | 4.0 | 5.0 | 6.0 | 8.0 | | Cold email | 1.5 | 2.5 | 3.0 | 4.0 | 5.0 | | LinkedIn outbound | 1.5 | 1.5 | 2.0 | 2.0 | 2.0 | | Founder content and organic social | 1.0 | 4.0 | 7.0 | 12.0 | 19.0 | | Creators, partners, and communities | 0.5 | 2.0 | 6.0 | 12.0 | 24.0 | | Sponsored directories, newsletters, and media placements | 1.5 | 2.0 | 4.0 | 8.0 | 12.0 | | Non-branded SEO | 0.0 | 1.0 | 3.0 | 7.0 | 15.0 | | Paid acquisition | 1.0 | 3.0 | 5.0 | 9.0 | 15.0 | | **Expected total run rate** | **10/day** | **20/day** | **35/day** | **60/day** | **100/day** | Paid acquisition is included in the base model. Founder content, creators/communities, SEO, and sponsored media placements must absorb the missing 15 signups/day if paid is unavailable. That materially increases execution risk. ### Expected overall metric timeline | Checkpoint | Visitors/day | Signups/day | Visitor → signup | ICP-qualified/day at 20% | Signup → useful change | Useful changes/day | Day-7 return | |---|---:|---:|---:|---:|---:|---:|---:| | Current | ~120 | 3 | 2.5% | 0.6 | 14.4% | ~0.4 | Low/noisy | | Aug 31 | ~200 | 10 | 5% | 2 | 20% | 2 | Baseline established; ≥10% target | | Sep 15 | ~400 | 20 | 5% | 4 | 25% | 5 | ≥15% | | Sep 30 | ~700 | 35 | 5% | 7 | 27% | ~9 | ≥18% | | Oct 15 | ~1,200 | 60 | 5% | 12 | 30% | 18 | ≥20% | | Nov 1 | ~2,000 | 100 | 5% | 20 | 30% | 30 | ≥20% | | Nov 30 | ~2,000+ | 100, 30-day average | ≥5% | ≥20/day | ≥30% | ≥30/day | ≥20% | These are operating expectations. Weekly evidence should move individual channel contributions up or down while preserving the total trajectory. --- ## 4. Parallel workstreams and deliverables ### Week-by-week deliverables Each week has its own execution note with expected metrics, channel contribution targets, concrete deliverables, recurring work, and end-of-week evidence requirements. | Week | Dates | Signup run-rate target | Focus | |---|---|---:|---| | [Week 01](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2001%20-%20Aug%2011-17.md) | Aug 11–17 | 4/day | Launch every medium and establish source of truth | | [Week 02](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2002%20-%20Aug%2018-24.md) | Aug 18–24 | 6/day | Ship first experiments and collect proof | | [Week 03](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2003%20-%20Aug%2025-31.md) | Aug 25–31 | 10/day | Reach a reliable 10 signups/day | | [Week 04](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2004%20-%20Sep%2001-07.md) | Sep 1–7 | 13/day | Repeat the first winners across every medium | | [Week 05](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2005%20-%20Sep%2008-14.md) | Sep 8–14 | 17/day | Build the repeatable proof and distribution system | | [Week 06](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2006%20-%20Sep%2015-21.md) | Sep 15–21 | 20/day | Reach 20/day and select repeatable winners | | [Week 07](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2007%20-%20Sep%2022-28.md) | Sep 22–28 | 27/day | Scale distribution toward 35/day | | [Week 08](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2008%20-%20Sep%2029-Oct%2005.md) | Sep 29–Oct 5 | 35/day | Reach 35/day and remove weak treatments | | [Week 09](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2009%20-%20Oct%2006-12.md) | Oct 6–12 | 47/day | Compound the portfolio toward 60/day | | [Week 10](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2010%20-%20Oct%2013-19.md) | Oct 13–19 | 60/day | Reach 60/day with a balanced channel portfolio | | [Week 11](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2011%20-%20Oct%2020-26.md) | Oct 20–26 | 80/day | Close the final gap toward 100/day | | [Week 12](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2012%20-%20Oct%2027-Nov%2001.md) | Oct 27–Nov 1 | 100/day | Reach 100/day on a rolling seven-day average | | [Week 13](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2013%20-%20Nov%2002-08.md) | Nov 2–8 | 100/day | Stabilize the run rate after the milestone | | [Week 14](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2014%20-%20Nov%2009-15.md) | Nov 9–15 | 100/day | Improve quality and economics while sustaining volume | | [Week 15](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2015%20-%20Nov%2016-22.md) | Nov 16–22 | 100/day | Protect retention and operational capacity | | [Week 16](100%20Daily%20Signups%20-%20Weekly%20Deliverables/Week%2016%20-%20Nov%2023-30.md) | Nov 23–30 | 100/day | Close November and set the next growth cycle | ## 4.1 Measurement and attribution ### Start now - Define and verify production events for the ordered funnel. - Persist first-touch and latest-touch UTMs through signup. - Add optional self-reported attribution at signup. - Separate branded search from non-branded search. - Separate cold LinkedIn, organic LinkedIn, cold email, sponsored directories/media, newsletters, communities, creators, paid, direct, and referral. - Exclude internal, test, local, preview, and staging traffic. ### Deliverables By August 31: - one canonical acquisition-to-activation dashboard; - daily signup source table; - self-reported source field; - dedicated Guided Demo Started and Guided Demo Completed definitions; - ordered signup → demo → import → canvas → first useful change funnel; and - weekly cohort report for Day-1 and Day-7 return. By September 15: - first-touch, latest-touch, and self-reported source reconciliation; - channel-level ICP-qualified and activation reporting; and - documented discrepancies between analytics, CRM, and outbound tools. ## 4.2 Landing-page conversion ### Start now - Keep the lead promise simple: design directly in the real product. - Align the page, signup, demo, and project-import narrative. - Create dedicated landing pages for distinct offers/use cases without fragmenting the core persona. - Match every outbound, creator, sponsored placement, SEO, and paid campaign to a specific destination and UTM. - Show real product proof above or near the primary signup action. ### Deliverables By August 31: - primary homepage message/CTA live (post split testing); - cold-email landing destination (the split test completed); - LinkedIn-outbound landing destination; - at least three real-product proof modules; and - visitor → signup conversion at or trending toward 5%. By September 30: - winning message applied across major acquisition surfaces; - channel-specific conversion report; and - lower-performing landing treatments removed rather than retained as competing truths. ## 4.3 Activation and lifecycle ### Start now - Replace Build events as demo proxies. - Make connecting a real codebase the obvious post-demo action. - Give every imported project one clear first useful task. - Trigger lifecycle messages based on the user’s actual stage. - Follow up manually with high-intent users who stall. ### Deliverables By August 31: - verified guided-demo funnel; - explicit demo → real-project transition; - first-useful-task prompt/checklist; - stage-based onboarding messages; and - signup → first useful change at or trending toward 20%. By September 30: - signup → first useful change at or trending toward 27%; - import and setup failure reasons ranked; - median time to import and first useful change reported; and - Day-7 return at or trending toward 18%. By November 1: - ≥30% signup → first useful change; and - ≥20% Day-7 return. ## 4.4 Cold email ### Start now - Ramp toward the 1,400-send daily capacity while protecting deliverability. - Run distinct offer tests by ICP segment, not minor CTA wording tests. - Use a unique UTM and destination for every offer/segment. - Track positive replies through signup, ICP qualification, import, useful change, and Day-7 return. Offer directions: 1. Solve one real UI issue in Mode. 2. Personalized workflow using the recipient’s existing product. 3. Design-system-aware UI change demonstration. 4. Founder-assisted onboarding for strong-fit designers. ### Deliverables Weekly: - unique leads added; - sends and delivery health; - positive replies; - directly attributed signups; - ICP-qualified signups; - imports and first useful changes; and - winner/loser decision for each offer. By September 15: - one winning audience × offer combination; - lead → signup at or trending toward 1%; and - positive-reply follow-up process that moves interested prospects directly into product use. By November 1: - approximately five completed signups/day from cold email, direct plus defensibly attributed assisted contribution. ## 4.5 LinkedIn outbound ### Start now - Maintain 40 connection requests/day. - Follow the existing 22 interested leads through actual product outcomes. - Preserve the message that produced the current acceptance, reply, and interest rates until enough downstream evidence exists. - Capture objections, user language, examples, and referral opportunities. ### Deliverables Weekly: - requests, accepts, replies, interested leads; - interested → signup; - signup → import; - signup → first useful change; and - qualitative objections and repeated language. By August 31: - observed interested → signup rate replacing the current 30% assumption; - at least one usable user story or testimonial candidate; and - approximately 1.5 signups/day if early rates persist. By November 1: - approximately two signups/day, with strong ICP quality and activation. ## 4.6 Founder content and organic social ### Start now Produce three anchor product demonstrations per week. Repurpose each across LinkedIn, X, short video, outbound follow-up, creator outreach, landing-page proof, and SEO. Every anchor demonstration should show: 1. a recognizable product UI problem; 2. the existing real interface/codebase; 3. the change made visually in Mode; 4. components/design-system context being preserved; 5. the working result; and 6. a specific signup action. ### Deliverables Weekly: - three anchor product demonstrations; - channel-native LinkedIn and X versions; - short video/GIF assets; - campaign-specific link and UTM; and - visits, signups, ICP-qualified signups, and useful changes by asset. By September 15: - repeatable demonstration format; - at least twelve anchor demonstrations published or ready; - winning product-story themes identified; and - approximately four signups/day from founder content. By November 1: - approximately nineteen signups/day from founder content and organic social. ## 4.7 Creators, partners, and communities ### Start now - Build a focused list of product-design, design-engineering, AI-design, and design-system creators. - Begin outreach immediately. - Run collaborations as soon as each partner is ready; do not hold them for Product Hunt. - Participate in relevant communities continuously rather than appearing only to promote a launch. Collaboration formats: - creator uses Mode on a real product interface; - before/after workflow; - live product teardown; - “fix this UI” session; - existing-codebase challenge; and - creator-specific onboarding link. ### Deliverables Weekly: - new creator/partner conversations; - confirmed collaborations; - published demonstrations; - community contributions; - attributed visits, signups, ICP-qualified signups, and useful changes. By September 15: - first live creator collaborations; - reusable partner brief and asset kit; and - approximately two signups/day. By October 15: - recurring creator/community calendar; and - approximately twelve signups/day. By November 1: - approximately twenty-four signups/day. ## 4.8 Sponsored directories, newsletters, and media placements ### Start now - Treat the sponsored placement on There’s An AI For That as the proof point, not directory presence by itself. - Continue sponsoring existing placements that produce qualified traffic, signups, and activation at acceptable cost. - Find new directories, newsletters, resource collections, and media properties with similar audience fit and traffic, then buy/test comparable sponsorship inventory. - Refresh sponsored creative and landing destinations when product proof or launch assets improve. - Do not use a higher count of ordinary directory submissions as the growth strategy. ### Deliverables Weekly: - sponsorship renewals, prospects, and pitches; - live sponsored placements and spend; - visits, signups, ICP-qualified signups, and activation by placement; and - ranking of placements by activated-user yield and cost, not listing count. By September 30: - repeatable sponsorship sourcing and renewal pipeline; - clear top-performing properties, audience patterns, and sponsorship formats; and - approximately four signups/day. By November 1: - approximately twelve signups/day. ## 4.9 Non-branded SEO ### Start now Current non-branded SEO acquisition is treated as zero. Build pages around high-intent product jobs and real proof: - AI tools for product designers; - design directly in an existing codebase; - visual code editing for designers; - design-engineer workflows; - design-system-aware AI; - Figma-to-real-product workflows; - UI polish without engineering handoff; - Mode comparisons and alternatives; and - concrete product-design use cases. ### Deliverables Weekly: - three high-intent pages or material page updates; - internal links and appropriate structured metadata; - product demonstration/proof embedded where relevant; - non-branded query impressions, clicks, visits, signups, and useful changes. By September 15: - first non-branded pages indexed and receiving impressions; - branded/non-branded reporting separated; and - approximately one signup/day. By October 15: - approximately seven signups/day. By November 1: - approximately 300–400 non-branded visitors/day; - 4–5% visitor → signup; and - approximately fifteen signups/day. ## 4.10 Paid acquisition ### Start now if budget is available Small paid learning tests can run immediately. Aggressive scaling depends on evidence, not a calendar date. Initial motions: - high-intent search; - retargeting; - paid amplification of product demonstrations; and - narrowly targeted designer audiences. ### Scale conditions Increase spend when: - visitor → signup is at or trending toward 5%; - ICP-qualified share remains at least 20%; - signup → first useful change is at least 25% or improving toward it; - source attribution is reliable; and - cost per activated user is approved. ### Deliverables Immediately: - monthly test budget decision; - maximum cost per signup and activated user; - channel-specific landing pages and UTMs. By September 15: - initial paid conversion and quality baseline; and - approximately three signups/day if economics are acceptable. By November 1: - approximately fifteen signups/day within agreed cost and quality guardrails. ## 4.11 Product Hunt and coordinated launch ### Start preparation now Product Hunt is an amplifier, not the sustained engine. Launch as soon as product, proof, assets, support, and follow-up are ready; do not wait until November by default. Deliverables: - final tagline and concise positioning; - product gallery/screenshots; - short product video; - maker story/comment; - at least five real-product examples; - at least three credible testimonials; - launch email and social assets; - creator/community distribution plan; - stable self-serve onboarding; - support coverage; - analytics and lifecycle follow-up. Readiness gate: ```text Product can reliably onboard launch traffic + proof is credible + assets are complete + source and activation measurement work + follow-up is ready ``` Product Hunt launch-day signups are not included as a permanent daily channel in the November run-rate table. Launch traffic should accelerate branded/direct, creator, sponsored-media, and search demand after the event. --- ## 5. Expected timeline and deliverables All workstreams run throughout. The timeline describes expected maturity and output, not delayed start dates. ### Now through August 31 — establish the parallel system Expected run rate: **10 signups/day**. Deliverables: - 5% visitor → signup target in active testing; - canonical ordered funnel and source dashboard; - self-reported attribution; - cold email near operating capacity with distinct offer tests; - LinkedIn at 40 requests/day with observed interested → signup starting to replace assumptions; - three founder type product demonstrations/week (Martin + Alex + Influencer) - creator/community outreach active; - sponsored-placement renewal and prospecting pipeline active; - first non-branded SEO pages published; - warm list segmented and reactivation underway; - Product Hunt assets in production; - small paid tests active if budget is approved. ### September 1–15 — identify repeatable winners Expected run rate: **20 signups/day**. Deliverables: - winning cold audience × offer combination; - observed LinkedIn interested → signup rate; - at least twelve anchor product demonstrations published or ready; - first creator collaborations live; - non-branded pages indexed and receiving impressions; - first paid quality/CAC baseline if enabled; - signup → first useful change at or trending toward 25%; and - Day-7 return at or trending toward 15%. ### September 16–30 — scale proven distribution Expected run rate: **35 signups/day**. Deliverables: - weak outbound offers stopped or replaced; - winning founder-content themes repeated; - recurring creator/community calendar; - repeatable sponsored media sourcing and renewal pipeline; - channel-level ICP and activation reporting; - approximately 700 visitors/day; and - approximately nine useful changes/day. ### October 1–15 — compound the portfolio Expected run rate: **60 signups/day**. Deliverables: - approximately 1,200 qualified visitors/day; - creator/community contribution approaching twelve signups/day; - founder content approaching twelve/day; - non-branded SEO approaching seven/day; - paid approaching nine/day if economics pass; - first-useful-change rate at or above 30%; - Day-7 return at or above 20%; and - Product Hunt/coordinated launch ready or already completed if readiness was reached earlier. ### October 16–November 1 — close the run-rate gap Expected run rate: **100 signups/day on a rolling seven-day average**. Deliverables: - approximately 2,000 qualified visitors/day; - 5% visitor → signup; - 20 ICP-qualified signups/day; - 30 first useful changes/day; - sustained parallel distribution across every medium; - coordinated launch used if ready and useful, not as a substitute for the portfolio; and - no single channel responsible for more than approximately 25% of the target. ### November — sustain and improve quality Expected result: **100 signups/day on a rolling 30-day average**. Deliverables: - approximately 3,000 monthly signups; - at least 300 ICP-qualified signups at a 10% quality rate; - channel contribution model refreshed from observed results; - weak channels reduced and winners expanded; - product/support capacity monitored; and - canonical three-PR qualified-user reporting reconciled separately. --- ## 6. Weekly operating cadence ### Daily - Review visitors, completed signups, source, ICP qualification, and first useful changes. - Follow up with high-intent cold and LinkedIn leads. - Publish/distribute scheduled proof assets. - Watch product/setup failures affecting new cohorts. ### Weekly growth review For each medium: ```text Activity → qualified visitors → completed signups → ICP-qualified signups → codebase imports → first useful changes → Day-7 return ``` Decisions: - **Scale:** channel produces ICP-qualified signups and useful changes at acceptable cost. - **Improve:** channel produces interest/traffic but weak signup or activation. - **Stop:** channel produces only impressions, opens, or low-intent signups after a sufficient test. - **Protect:** channel performs but quality or deliverability is degrading under volume. ### Reporting rule Do not report opens, impressions, replies, followers, sponsored-placement count, or page count as growth outcomes by themselves. Tie activity to completed signups, ICP quality, activation, retention, and placement cost. --- ## 7. Decision requirements The plan can begin immediately, but these decisions affect the contribution model: 1. Confirm 100/day means completed signups and approve the November 1 seven-day-average target. 2. Set paid-learning budget and maximum acceptable cost per activated user. 3. Finalize the activation event used for signup → first useful change. 4. Confirm Product Hunt account readiness and whether launch should happen at the earliest readiness date. 5. Confirm product/support capacity for 100 daily signups. 6. Reconcile the canonical three-PR qualified-user metric with the new acquisition target without conflating the definitions. --- ## 8. Guardrails - Start every viable medium now; do not use the timeline as a waterfall. - Scale from evidence, not calendar dates. - Do not call branded Mode searches non-branded SEO acquisition. - Do not use Build Start / Build Succeed as the guided-demo funnel. - Do not infer cold-email totals from an ambiguous platform rate. - Use unique leads, not sequence sends, as the primary cold denominator. - Do not equate LinkedIn interest with signup. - Do not double-count registered users and the warm list. - Do not treat more ordinary directory listings as scale; renew proven sponsorships and test comparable paid placements. - Product sharing is currently primarily a support capability, not an acquisition medium; do not assign growth contribution to it. - Keep completed signups, ICP-qualified signups, activated users, and canonical qualified users distinct. - Do not let a Product Hunt spike hide weak activation or retention. - Delete or replace superseded campaign treatments rather than retaining multiple active truths.