These five principles guide every decision across product, growth, and operations. When in doubt, return to the doctrine.
Women First. Always.
Every product decision, every growth channel, every event format must prioritise the female experience. Female supply determines platform health. Every decision that affects gender ratio must prioritise women. If women love SPARK, men will follow.
Density Beats Scale.
100 active users in Thonglor is worth more than 1,000 users spread across Bangkok. Do not expand until density is achieved in core zones. Concentrate before expanding.
Meetings Beat Matches.
A match that never becomes a meeting is a failure. One great first-date story shared on Instagram is worth 50 paid ads. Optimise every product mechanic for real-world meetings, not digital engagement.
Stories Drive Growth.
Every meeting generates a story. Every story generates referrals. Build content capture into every event and every match. Stories are the primary acquisition channel. Engineer stories at every event.
Community Beats Advertising.
Paid ads can acquire users. Community retains them. Connectors, ambassadors, and yoga studios will outperform Meta ads in the first 6 months. Build the community first. Advertising amplifies what already works — it does not create it.
The Founder Is the Network.
Until strong network effects exist, you must personally engineer activity. You are the product.
| # | Rule | Category |
|---|---|---|
| 1 | Never launch a new district until the previous one has hit density | Growth |
| 2 | Every new user gets 3 curated matches within 24 hours | Liquidity |
| 3 | Female ratio must never drop below 50% | Supply |
| 4 | Attend every event for the first 90 days | Operations |
| 5 | Respond to every safety report within 1 hour | Safety |
| 6 | Never position Sparks as pay-to-date | Brand |
| 7 | Recruit 10 female users per day in person | Growth |
| 8 | Every event must generate minimum 20 social posts | Content |
| 9 | Check dashboard metrics every morning before 9am | Operations |
| 10 | Never scale paid ads before WOM rate is ≥20% | Growth |
| 11 | Conduct 5 user interviews per week | Product |
| 12 | Never hire before PMF is confirmed | Operations |
| 13 | Every meeting must generate content or referral | Growth |
| 14 | Male users who behave badly are removed immediately, no exceptions | Safety |
| 15 | NPS below 40 is a product emergency | Product |
| 16 | Never expand to a new city until Bangkok has passed the PMF gate | Growth |
| 17 | The founder must be the most active user on the platform for the first 90 days | Operations |
| 18 | Every event must have a female host present | Safety |
| 19 | No event runs with less than 45% female attendance | Operations |
| 20 | Manually curate matches in Weeks 1–4, no exceptions | Liquidity |
| 21 | Review all metrics every Monday before any other task | Operations |
| 22 | Any metric in red for 7 days triggers the Pivot Decision Tree | Growth |
| 23 | Do not raise funding or expand to a new city during a crisis | Operations |
| 24 | Publish monthly safety transparency report | Safety |
| 25 | The goal of every phase is density, not scale | Growth |
The 25 rules are not suggestions. They are operating constraints. Each rule exists because a specific failure mode has been observed in comparable marketplace launches. The rule prevents that failure.
| # | Rule | Why It Exists | Failure It Prevents |
|---|---|---|---|
| 1 | Never launch a new district until the previous one has hit density | Premature expansion dilutes density and kills liquidity | Ghost-town dynamics in multiple districts simultaneously |
| 2 | Every new user gets 3 curated matches within 24 hours | First experience determines D7 retention | Users churn after seeing no matches on Day 1 |
| 3 | Female ratio must never drop below 50% | Female supply determines platform health | Male-heavy platform → women disengage → men leave → collapse |
| 4 | Attend every event for the first 90 days | Founder presence creates energy and trust | Events feel corporate and lifeless without founder |
| 5 | Respond to every safety report within 1 hour | Safety incidents destroy female trust permanently | One mishandled incident → viral negative press → female exodus |
| 6 | Never position Sparks as pay-to-date | Brand perception determines female willingness to join | "Pay-to-date" positioning kills female acquisition |
| 7 | Recruit 10 female users per day in person | Female supply must be actively manufactured | Organic female acquisition is too slow in Phase 1 |
| 8 | Every event must generate minimum 20 social posts | Events are content engines, not just social events | Events with no content generate no organic acquisition |
| 9 | Check dashboard metrics every morning before 9am | Early detection prevents small problems becoming crises | Metrics left unchecked for 3 days = 3 days of compounding damage |
| 10 | Never scale paid ads before WOM rate is ≥20% | Paid ads before WOM = paying full price for every user | Burning budget on acquisition that organic growth would provide for free |
| 11 | Conduct 5 user interviews per week | Qualitative data reveals what metrics cannot | Building features users don't want; missing obvious friction |
| 12 | Never hire before PMF is confirmed | Premature hiring creates overhead that kills runway | Running out of money before product works |
| 13 | Every meeting must generate content or referral | Meetings are growth events, not just product outcomes | Meetings happen but don't compound into growth |
| 14 | Male users who behave badly are removed immediately | Male behaviour determines female retention | One bad actor → multiple female churns |
| 15 | NPS below 40 is a product emergency | NPS is the leading indicator of retention and referral | Ignoring low NPS until retention collapses |
| 16 | Never expand to a new city until Bangkok has passed the PMF gate | Multi-city operations before PMF = diluted focus | Failing in two cities instead of succeeding in one |
| 17 | The founder must be the most active user on the platform for the first 90 days | Founder activity manufactures early network effects | Platform feels empty without founder-driven activity |
| 18 | Every event must have a female host present | Female host signals safety and comfort | Women feel unsafe at male-hosted events |
| 19 | No event runs with less than 45% female attendance | Gender ratio is the product at events | Male-heavy events → women don't return → event programme collapses |
| 20 | Manually curate matches in Weeks 1–4, no exceptions | Algorithm cannot work without sufficient density | Users receive zero or poor matches → Day 1 churn |
| 21 | Review all metrics every Monday before any other task | Weekly rhythm prevents drift | Metrics drift unnoticed for weeks → crisis |
| 22 | Any metric in red for 7 days triggers the Pivot Decision Tree | 7 days of red = structural problem, not noise | Hoping a structural problem resolves itself |
| 23 | Do not raise funding or expand to a new city during a crisis | Crisis requires full founder attention | Fundraising during crisis = distracted founder + worse crisis |
| 24 | Publish monthly safety transparency report | Transparency builds female trust | Silent moderation = female users assume nothing is being done |
| 25 | The goal of every phase is density, not scale | Density produces quality; scale produces noise | Chasing user count while liquidity collapses |
This is the founder's daily operating manual. Every day has a structure. Deviation from this structure is permitted only when a red flag requires immediate attention — and in that case, the red flag becomes the entire day's priority.
DAILY RULE: The founder's time is the most valuable resource in the company. Every hour must be allocated to the highest-leverage activity. This schedule is designed to maximise leverage across acquisition, community, product, and operations.
| Time Block | Focus | Specific Actions | Time |
|---|---|---|---|
| Morning (7–9am) | Metrics & Intelligence | Check all 11 dashboard metrics. Flag any red flags. Review overnight installs and gender ratio. Read 5 new user profiles. Curate 3 matches manually. Reply to all user messages. | 2 hours |
| Mid-Morning (9am–12pm) | Acquisition & Outreach | Connector DMs: 3–5 personalised messages. Influencer conversations: 1–2 per day. Community partnership follow-ups. Respond to all partnership enquiries. Review paid social performance. | 3 hours |
| Afternoon (12–3pm) | Product & Operations | Review app feedback and support tickets. Conduct 1 user interview (5 per week). Review event bookings and attendance. Plan next event. Review content pipeline. | 3 hours |
| Late Afternoon (3–6pm) | Strategic Work | Weekly: review cohort data, update war plan, plan next week. Daily: prepare for evening community activity. Review influencer content. Respond to media enquiries. | 3 hours |
| Evening (6–10pm) | Community Building | Attend 1 social venue in Thonglor/Ekkamai. Recruit 2–3 connectors in person. Observe user behaviour. Introduce SPARK to 3–5 people. Capture 1 piece of social content. | 4 hours |
| Night (10–11pm) | Growth Analysis | Review day's metrics vs. targets. Update war plan if needed. Plan tomorrow's priorities. Identify any emerging red flags. | 1 hour |
| Day | Primary Focus | Non-Negotiable Actions |
|---|---|---|
| Monday | Marketplace Health | Review all metrics. Set 3 weekly priorities. Activate any protocols triggered by red flags. |
| Tuesday | Influencer & Partnerships | Review content pipeline. Brief 2 creators. Identify new nano-influencer candidates. |
| Wednesday | Product & User Research | 2 user interviews. Review onboarding funnel. Prioritise top 3 product improvements. |
| Thursday | Community & Connectors | Meet 2–3 super-connectors. Attend community event. Identify new female acquisition channels. |
| Friday | Partnerships & PR | Venue relationship management. Media outreach. Review weekly metrics vs. targets. |
| Saturday | Events & Observation | Attend SPARK event. Observe user interactions. Collect qualitative feedback. |
| Sunday | Strategy & Planning | Weekly retrospective. Update war plan. Plan next week. Review cohort data. |
| Month | Primary Objective | Key Milestone |
|---|---|---|
| April | Build the foundation | 1,000 users, ≥50% female, NPS ≥35 |
| May | Activate the referral engine | 3,000 users, referral rate ≥20%, PMF gate ready |
| June | Launch offline events | First 3 events, NPS ≥45, event fill rate ≥80% |
| July | Build event momentum | 8 events/month, repeat attendance ≥25%, WOM ≥30% |
| August | PMF gate evaluation | All 8 PMF metrics green. Scale or pivot decision. |
| September | Scale or pivot | 20,000 users or pivot executed. Series A preparation. |
One page. Six months. Everything the founder needs to know about what to do and when.
This is the single-page summary version of the War Calendar. Print it. Put it on your desk. Review it every Monday morning.
| Month | Date | User Target | Meetings/Week | Primary Focus | Non-Negotiable | Success Gate |
|---|---|---|---|---|---|---|
| Month 1 | Apr 2026 | 500 users | 10/week | Manual curation + connector recruitment | NPS ≥35, female ratio ≥50% | 500 users, 20 connectors live |
| Month 2 | May 2026 | 1,500 users | 30/week | Referral engine + influencer content | Referral rate ≥20%, D30 retention ≥22% | PMF app gate: all 4 metrics green |
| Month 3 | Jun 2026 | 3,000 users | 50/week | First 3 offline events | Event NPS ≥45, event fill rate ≥80% | 3 events run, female referral rate ≥30% |
| Month 4 | Jul 2026 | 5,000 users | 100/week | Event momentum + WOM engine | 8+ events/month, WOM ≥30% of installs | Tipping point reached |
| Month 5 | Aug 2026 | 8,000–12,000 | 200/week | PMF gate evaluation | All 8 PMF metrics green | Scale or pivot decision made |
| Month 6 | Sep 2026 | Scale or pivot | — | Series A or pivot execution | Honest PMF evaluation | Series A deck ready |
The founder's primary activity shifts dramatically across the six months. Understanding this shift is critical — doing Month 1 activities in Month 3 is as damaging as doing Month 3 activities in Month 1.
| Month | The Founder Is... | The Founder Is NOT... |
|---|---|---|
| Month 1 | Chief Matchmaker — personally curating every match | Running paid ads or scaling acquisition |
| Month 2 | Referral Engineer — building the WOM loop | Worrying about revenue or monetisation |
| Month 3 | Event Producer — making every event exceptional | Expanding to new districts or cities |
| Month 4 | Growth Architect — scaling what is working | Manually curating matches (the algorithm does it now) |
| Month 5 | Data Analyst — evaluating PMF with brutal honesty | Ignoring bad metrics or rationalising poor data |
| Month 6 | Fundraiser or Pivot Executor — moving fast | Staying in operational mode |
Phase A: Manufacture (Months 1–2). The founder is the product. Every match is personal. Every user is known by name. Growth is manufactured through sheer founder effort. This phase ends when referral rate exceeds 20%.
Phase B: Accelerate (Months 3–4). The founder is the event producer and growth engineer. Events replace manual curation as the primary meeting mechanism. WOM begins to compound. This phase ends when the tipping point (5,000 users) is reached.
Phase C: Evaluate (Months 5–6). The founder is the strategist. The product runs itself. The founder's job is to evaluate PMF honestly and either scale aggressively or pivot decisively. This phase ends with a fundraise or a pivot.
WAR CALENDAR RULE: The most common founder mistake is staying in Phase A mode during Phase B. If you are still manually curating matches in Month 3, something is wrong — either the referral engine is not working, or you are not trusting the system. Fix the engine. Trust the system.
The Founder War Calendar translates the 90-day launch plan into a month-by-month operating guide. Each month has a single primary objective, a user target, a meeting target, a key focus area, and a set of non-negotiable actions. The founder should review this calendar at the start of every month and use it to set weekly priorities.
Primary Objective: Reach 500 high-quality active users with ≥50% female ratio.
| Dimension | Target | Actions |
|---|---|---|
| User Target | 500 active users | Recruit 300 female connectors. Release male waitlist in batches. Maintain 55/45 gender ratio. |
| Meeting Target | 10 real-world meetings/week | Founder manually curates every match. Personal introductions. 3 matches per new user within 24 hours. |
| Primary Focus | Manual curation + connector recruitment | Identify and recruit 20 super-connectors. Attend 5 social venues per week. DM 50 potential female users per week. |
| Non-Negotiable | NPS ≥35 | Conduct 5 user interviews per week. Fix every friction point immediately. Do not scale until NPS ≥35. |
| Red Flag | Female ratio < 50% | Pause male onboarding immediately. Activate female acquisition channels. |
Month 1 Weekly Milestones:
Primary Objective: Reach 1,500 active users with referral rate ≥20%.
| Dimension | Target | Actions |
|---|---|---|
| User Target | 1,500 active users | Referral programme live. Double-sided incentives. Connector network fully activated. |
| Meeting Target | 30 real-world meetings/week | Algorithm assists matching. Connector-facilitated introductions. First event planning begins. |
| Primary Focus | Referral engine + influencer content | 15 nano-influencers posting authentic content. Referral rate target: 20%. Female referral rate target: 25%. |
| Non-Negotiable | PMF app gate check (31 May) | All 4 app PMF metrics must be green: NPS ≥40, D30 retention ≥22%, Match→Meeting ≥12%, referral rate ≥20%. |
| Red Flag | Referral rate < 10% by Week 6 | WOM engine not working. Conduct 10 user interviews. Identify friction. Fix before scaling. |
Month 2 Weekly Milestones:
Primary Objective: Run first 3 offline events with NPS ≥45 and event fill rate ≥80%.
| Dimension | Target | Actions |
|---|---|---|
| User Target | 3,000 active users | Event-driven acquisition. Each event generates 50–100 new installs through content and WOM. |
| Meeting Target | 50 real-world meetings/week | Events become primary meeting engine. Target: 40% of meetings happen at or through SPARK events. |
| Primary Focus | Event operations + content capture | 3 events in June. Venue partnerships signed. Event content team briefed. Post-event NPS tracking live. |
| Non-Negotiable | Event NPS ≥45 | Every event must be reviewed within 24 hours. Change 3 things before the next event. |
| Red Flag | Event fill rate < 70% | Events not generating demand. Review targeting. Increase event waitlist mechanics. |
Month 3 Weekly Milestones:
Primary Objective: Run 8+ events per month with repeat attendance ≥25% and WOM ≥30%.
| Dimension | Target | Actions |
|---|---|---|
| User Target | 5,000 active users — tipping point | Density loops activating. WOM becomes primary acquisition channel. |
| Meeting Target | 100+ real-world meetings/week | Events + app matching + connector introductions all contributing. |
| Primary Focus | WOM engine + event scaling | 8–12 events per month. Event formats diversifying (speed dating, activity events, dinner events). |
| Non-Negotiable | Reach 5,000 active users | This is the tipping point. Growth loop becomes self-reinforcing. |
| Red Flag | WOM < 20% of installs | Referral engine not working at scale. Review referral mechanics. Increase post-event content capture. |
Primary Objective: Pass all 8 full PMF gate metrics. Scale or pivot decision.
| Dimension | Target | Actions |
|---|---|---|
| User Target | 8,000–12,000 active users | Scale acquisition if PMF gate passed. Pause and pivot if not. |
| Meeting Target | 200+ real-world meetings/week | Events at full capacity. WOM loop self-sustaining. |
| Primary Focus | PMF evaluation + Series A preparation | All 8 PMF metrics reviewed. Investor deck updated. Series A conversations begin if PMF passed. |
| Non-Negotiable | Honest PMF evaluation | Do not scale a broken product. If PMF gate fails, execute the pivot playbook. |
Primary Objective: Either begin Series A fundraising or execute the pivot playbook.
| Scenario | Actions |
|---|---|
| PMF Passed | Begin Series A fundraising. Hire first growth team. Plan second city launch (Singapore or Kuala Lumpur). |
| PMF Not Passed | Execute pivot playbook. Identify which metrics failed. Redesign the failing component. Re-run 90-day cycle. |
WAR CALENDAR RULE: The calendar is a guide, not a contract. If a month's targets are reached in 3 weeks, advance to the next month's objectives immediately. If a month's targets are not reached by the end of the month, do not advance — diagnose, fix, and re-run the month's playbook before moving forward.
When a red flag appears, the founder's daily schedule is suspended. The red flag becomes the only priority.
| Red Flag | Immediate Response | Time to Resolution |
|---|---|---|
| Female ratio < 45% | Pause male onboarding. Activate Level 2 Liquidity War Plan. | 48–72 hours |
| NPS < 35 | Stop all acquisition. Conduct 10 user interviews in 48 hours. | 1–2 weeks |
| Daily installs < 15 for 3 days | Review paid social creative. Activate connectors. Double outreach. | 5–7 days |
| Event NPS < 40 | Debrief within 24 hours. Change 3 things. Do not run next event until fixed. | 1 event cycle |
| Safety incident reported | Respond to affected user within 1 hour. Remove reported user. Document fully. | Immediate |