Avelia

Appearance

Avelia: Go-To-Market Strategy ​

Date: 2026-03-23 Team context: 2–3 part-time founders, ~10–20 hrs/week combined GTM bandwidth Team location: Germany — EU-first launch, US expansion once EU wedge is validated Grounded in: Market Analysis (2026-03-23) and Competitor Analysis (2026-03-23)

Section 1: The Part-Time Constraint — Strategic Logic ​

The Bandwidth Reality ​

10–20 hours per week across 2–3 people is not enough to run a conventional SaaS GTM playbook. It is not enough to maintain a consistent social media presence, write weekly blog posts, attend conferences, run paid acquisition experiments, and manage a community simultaneously. Attempting all of these things part-time produces mediocre execution across every channel and authority in none.

The strategic response is not to do less of everything. It is to do one thing exceptionally well and let everything else be downstream of that.

For Avelia, that one thing is earned trust in the IVF community.

Why Constraints Can Be an Advantage ​

Part-time constraints force the discipline that well-funded startups routinely fail at: saying no. Avelia cannot afford to chase the Flo audience of 380 million. It also doesn't need to. The IVF/Assisted community is approximately 5–6 million annual cycles in the US+EU combined, concentrated in a handful of online spaces, deeply motivated by exactly the privacy story Avelia offers, and almost entirely underserved by existing apps.

A part-time team that goes deep in one community will outperform a full-time team spread thin across many. The constraint is the strategy.

Operating Principles ​

Every GTM decision should be tested against these four principles:

1. Earned over paid. Paid acquisition before product-market fit burns cash and produces churn. Every euro/dollar spent on ads before you know your retention numbers is wasted. In the IVF community, paid acquisition is also counterproductive — this audience is acutely sensitive to being marketed to, especially on health topics. Trust is earned by showing up authentically, not by appearing in their feed.

2. Systems over hustle. A part-time team that relies on motivated weekly execution will break down the first time life intervenes — a deadline at the day job, illness, family demands. Every GTM activity should either (a) create durable assets (content, relationships, documentation) that keep working after the effort stops, or (b) be automated enough that it runs without weekly intervention. GTM activities that require sustained manual attention are not appropriate for this stage.

3. Depth over breadth. One community, one channel, mastered — is worth more than five communities half-heartedly attended. One exceptional piece of content — the Sovereign Data Whitepaper — distributed once and referenced forever, is worth more than twenty forgettable posts. Part-time teams cannot afford shallow presence anywhere.

4. Founder voice, not brand voice. Avelia the brand has no credibility yet. The founders do — as people building something real, sharing honest progress, and engaging authentically with a community they respect. Every piece of GTM content should come from a person, not a logo. This is where a part-time constraint becomes a genuine advantage: authenticity cannot be faked at scale, but it can be maintained by two people who actually care.

Section 2: The IVF Wedge — First 1,000 Users ​

Why IVF First ​

The competitor analysis confirms that no existing app simultaneously offers IVF-depth tracking, E2EE privacy architecture, and a bilateral couple model. The IVF community is the most privacy-sensitive, the most community-dense, the most willing to pay, and the most likely to move through subsequent Avelia stages (IVF → Pregnant → First Year). Acquiring one IVF user who successfully conceives is acquiring a multi-year customer.

The first 1,000 users are not a growth milestone — they are a research and validation cohort. The goal of the wedge phase is not scale, it is signal: do IVF users find Avelia valuable enough to log daily, to invite their partner, and to pay?

Why EU-First Is a Structural Advantage ​

Being based in Germany is not a constraint — it is a credibility asset. The EU user is already GDPR-literate, already suspicious of US-based health data companies, and already asking the question Avelia answers: "Who actually has my data?" A German-founded, GDPR-native app can make that claim authentically. Flo (Irish-registered but US-operated) and Clue (German-headquartered but with US analytics SDKs) cannot.

The EU IVF market is also substantial: approximately 1 million IVF cycles per year in Europe, with Germany, France, Spain, and the UK as the largest markets. German IVF patients in particular operate in a publicly visible healthcare system with well-established patient communities — easier to reach authentically than the more dispersed US market.

Where the Community Lives (EU-First) ​

Primary — German-language:

  • Kinderwunsch forums: kinderwunsch-forum.de and similar German-language patient forums are the highest-trust IVF community spaces in the DACH region. Long-form, anonymous, deeply substantive. Treat these with the same respect as r/IVF — show up to help, not to market.
  • Facebook groups: "Kinderwunsch & IVF Deutschland" and related groups have 20k–80k members. Older demographic but very active for IVF specifically; emotional support is the primary mode of engagement.
  • Instagram: German IVF nurses, fertility coaches (@fertilitycoach.de type accounts), and Kinderwunsch advocates are active and trusted. These accounts have 5k–50k followers and are reachable via DM for expert partnerships.

Primary — English-language EU:

  • Reddit: r/IVF and r/infertility have significant EU participation — English is the working language for many DACH, Scandinavian, and Dutch users. Acceptable secondary channel, but not the primary community for the German launch.
  • Specialised Discord servers for IVF (English-language, international)

Secondary:

  • Podcasts: "Wunschkind" (German), "Die Kinderwunsch-Reise" (German), and English EU-focused fertility podcasts — guest appearances build authority without ongoing time commitment
  • LinkedIn: for clinic and expert partner outreach (professional network, not consumer community)

The "Build in Public" Approach ​

The IVF community does not respond well to product launches. It responds to honesty. The most effective acquisition strategy is treating the community as collaborators in building the product, not as a market to be captured.

What this looks like in practice:

Posts that work:

  • "Wir bauen eine IVF-App, die eure Daten technisch nicht weitergeben kann — hier ist der Grund, und hier ist, woran wir gerade arbeiten" (authentic problem-sharing with technical depth — post in German for German forums)
  • "We analysed Clue's SDK stack and found that EU user data flows to US servers via Braze and Mixpanel. Here's what that means under GDPR, and here's how Avelia is architected differently" (GDPR-framed technical authority — highly resonant with EU users)
  • "We've been logging a mock IVF cycle to test our medication vault UI. Here's what we got wrong the first time and how we changed it" (genuine iteration story — works in any language)
  • "Was hätte dir eine App während der Zwei-Wochen-Warte geben können, die du nirgendwo gefunden hast?" (community as product advisor — German-language forums)

Note on language: Post in German in German-language communities. Post in English in international spaces. Do not use AI translation directly — have a German-fluent founder (or native speaker contact) review every German-language post before it goes live. Machine-translated German in a Kinderwunsch forum is immediately identifiable and damaging.

Posts that don't work:

  • "Introducing Avelia — the privacy-first IVF app!" (launch announcement without trust context)
  • Anything that sounds like a sales pitch
  • Anything that uses AI-generated empathy ("We understand how hard this journey is...") — this community recognises it immediately and it destroys credibility

Cadence: 1–2 substantive posts per week, maximum. Quality over frequency. A single post that genuinely helps or informs the community is worth ten forgettable updates.

Response discipline: Respond to every comment, personally, within 24 hours during the first 6 months. This is the highest-ROI GTM activity Avelia has. A founder replying thoughtfully to an IVF community question builds more trust than any content asset.

AI Tools for Community Engagement ​

What AI does well here:

  • Drafting initial responses to community questions for founder review and personalisation
  • Summarising long Reddit threads to identify the most common IVF app frustrations (feed these directly into product decisions)
  • Researching specific IVF medication protocols to make technical posts accurate
  • Generating multiple versions of a post for the founder to select and personalise from

What AI must not do:

  • Post autonomously in health communities. Ever. The liability and trust risk of an AI-generated health claim appearing in a community where people are making medical decisions is not acceptable.
  • Generate empathy language without heavy human editing. IVF community members are exquisitely sensitive to performative empathy. AI empathy reads as AI empathy.
  • Write the founder voice. AI can draft; the founder must rewrite in their own language before posting. The voice must be recognisably human and consistent over time.

Specific tools:

  • Claude / ChatGPT: Draft posts, summarise threads, research protocols
  • Perplexity: Real-time research on competitor incidents, regulatory news, medical references
  • Notion AI / Obsidian: Maintain a personal knowledge base of community insights, user feedback, and product decisions — searchable and connectable over time

Section 3: Proof of Privacy — Content as Trust Infrastructure ​

The Two Primary Assets ​

These are not blog posts. They are durable trust infrastructure — documents that will be referenced, shared, and linked to for years. Investing 10–15 hours to produce each one correctly is the highest-leverage content work the team will do.

Asset 1: The Sovereign Data Whitepaper

A 1–2 page technical explainer of Avelia's E2EE architecture written for a non-technical but motivated audience — in the EU this is someone who has Googled "Clue DSGVO sicher" or "Flo Datenschutz" (GDPR-aware users questioning whether their app is actually compliant). It should:

  • Explain in plain language what end-to-end encryption means for health data
  • Explain specifically why Avelia cannot comply with a data subpoena for health content (and why this is different from apps that "promise" not to share)
  • Acknowledge what Avelia does hold (account metadata) with honest precision
  • Be technically verifiable — cite the cryptographic primitives used, link to the open-source components where applicable

Distribution: post once to Hacker News (Show HN), r/privacy, r/IVF, German IVF forums, and LinkedIn. Publish a German-language version for DACH communities. Pin it in-app as the "About Privacy" page. Let it circulate organically.

Asset 2: The Competitor Privacy Audit

A factual, sourced comparison of competitor privacy architectures — citing FTC settlements, TOS analysis, known incidents, and SDK audits. Not an opinion piece. A documented record.

This document positions Avelia as the honest actor in a category of actors who sound honest. Its power is in specificity. For EU audiences, lead with GDPR: "Clue embeds Braze and Mixpanel — both US-based — meaning your health data flows to US servers subject to US jurisdiction, despite Clue's German headquarters and GDPR registration (cite)." For international audiences, the FTC framing ("Flo settled with the FTC in 2021 for sharing pregnancy status with Facebook and Google") carries more weight. Produce both versions.

Distribution: same channels as the whitepaper. For EU press, pitch to privacy-focused journalists at netzpolitik.org, Heise, Der Spiegel Digital, and The Markup. A single citation by netzpolitik.org reaches exactly the GDPR-literate German tech audience that Avelia's privacy story is built for. That audience then amplifies into the broader EU privacy-conscious health user base.

AI Tools for Content Production ​

What AI does well here:

  • First-draft synthesis of source material (FTC filings, GDPR enforcement decisions, TOS documents) into readable prose
  • Structuring arguments and checking logical flow
  • Identifying gaps or unsupported claims in a draft
  • Formatting and editing for clarity

What AI must not do:

  • Make legal or technical claims without founder verification. Every factual claim in these documents must be checked against a primary source by a human. An AI hallucination in the Competitor Privacy Audit — a wrong date, a misattributed incident — would destroy the document's credibility and potentially create legal liability.
  • Write the final voice. The whitepaper will be read by technically sophisticated people (Hacker News, privacy researchers, potential investors). It must sound like a founder, not a content tool.

Challenge — factual accuracy at speed: AI tools dramatically accelerate the research and drafting process for these documents. The risk is that the speed creates pressure to skip the verification step. The team should treat every AI-generated factual claim as "unverified until checked" and maintain a source log alongside each document. This is not optional for health-adjacent legal claims.

Responsibility framework: Before publishing either document, the team should have a qualified privacy lawyer review the legal claims (a 1-hour review, not a full engagement). The cost is low; the protection against a defamation or misrepresentation claim from a competitor is high.

Section 4: Partner Inclusion as a Growth Loop ​

The Mechanic ​

Every user who links a partner doubles the user count with zero acquisition cost. At a >50% partner linking rate (the target), Avelia's organic growth compounds: each acquired user generates 0.5 additional users, automatically.

This is not a referral programme. It is a product design decision — the invite is built into the onboarding flow, not added as a growth hack. The partner invite is the emotional heart of the "Together" value proposition: "[Name] wants to share this journey with you in a private space."

The Invite Moment ​

The partner invite has more emotional weight than any marketing copy Avelia will produce. The person receiving it is being invited into a private record of one of the most significant experiences of their life. The copy, the timing, and the friction level of this moment deserve more design attention than any other single GTM element.

What the invite must do:

  • Communicate the emotional significance of the invitation (this is a private space, not a shared app)
  • Require minimal friction to accept (one tap to download, one step to create account, immediately connected)
  • Make the privacy architecture legible without being technical ("your partner can only see what you choose to share — nothing else, ever")

What the invite must not do:

  • Sound like a referral ("earn a free month by inviting your partner")
  • Feel like being recruited into a product
  • Require the receiving partner to understand Avelia's features before accepting

AI Tools for Invite Optimisation ​

What AI does well:

  • Generating 10–20 variants of the invite message for founder review and selection
  • A/B testing copy variants across a small cohort with minimal manual analysis
  • Translating the invite for EU language markets (DE, FR, SE) with sensitivity review

Challenge — emotional authenticity: AI-generated emotional copy is detectable and counterproductive in this context. The invite message will be the first thing a partner sees. It should be written by a human founder who has thought carefully about what it would feel like to receive it, then tested with real people (friends, community members) before shipping. AI can generate variants; humans must select and refine.

Section 5: Expert Partner Network — Early Clinics & Doulas ​

Why Partners First, Not Marketplace ​

Building the expert marketplace (in-app session booking, consent-based data access) is a product investment for Year 2. The GTM work for expert partners in Year 1 is relationship-building and distribution — getting the first 5–10 experts to recommend Avelia to their clients, and getting the first 2–3 to contribute content to the Guide section.

This does not require a marketplace platform. It requires personal outreach, trust-building, and a clear value proposition for the expert.

The Expert Value Proposition ​

The pitch to an IVF nurse, doula, or fertility nutritionist is not "promote our app." It is:

"Your clients are already tracking their data in apps that have leaked it, sold it, or could be compelled to disclose it. You can recommend Avelia as the only tracker where you — and only you, with their explicit consent — can see their actual logs before a session. Everyone else is advising blind."

This is a meaningful clinical and trust differentiator. It makes the expert's advice better (they have real data) and makes their recommendation trustworthy (they're recommending a privacy-safe tool).

How to Find the First Partners ​

IVF nurses and embryologists: Active on Instagram and LinkedIn, often sharing patient education content. Search "#IVFnurse", "#embryologist", "#fertilitynutrition". Look for practitioners with 2k–20k followers — large enough to have an audience, small enough to respond to a direct message.

Doulas: Highly active in birth worker networks (DONA International, CAPPA). Many have their own client recommendation lists and are actively looking for tools to recommend. The privacy story resonates strongly — doulas are confidentiality-oriented by training.

Fertility counsellors / perinatal mental health: Less visible on social media but reachable through fertility clinic referral networks and organisations like the British Infertility Counselling Association (BICA) in the EU.

Outreach Process ​

  1. Research first (AI-assisted): For each target expert, use AI to summarise their public content (what they care about, what they post, what their clients ask them). Personalise the outreach to their specific focus.
  2. First contact: A short, direct DM or email — not a pitch deck. Three sentences: who you are, what you're building, why you thought of them specifically. No attachments.
  3. The ask: A 20-minute conversation. Not a partnership agreement. Not a content commitment. Just a conversation about what their clients need that no app currently provides.
  4. Follow through: After the conversation, send the Sovereign Data Whitepaper. If there's interest, offer to put their name on a Guide article in exchange for a review and endorsement.

Bandwidth reality: Expert outreach is time-intensive end-to-end — identifying, researching, personalising, scheduling, and conducting each conversation realistically costs 4–6 hours. At 10–20 combined hours per week, running expert outreach in parallel with active community engagement is not sustainable. Sequence these phases: establish community traction (Signal 1) first, then shift a portion of the freed bandwidth to expert outreach. Once community presence is established, 1 expert conversation per week is the sustainable cadence — delivering 12–15 relationships over the first three months of the outreach phase.

AI Tools for Expert Outreach ​

What AI does well:

  • Researching an expert's public profile and summarising their focus before outreach
  • Drafting the initial DM or email for founder personalisation
  • Generating a list of potential experts from a seed list of hashtags or organisations
  • Drafting interview questions for the 20-minute conversation

Challenge — personalisation at scale: AI-drafted outreach that has not been personalised is detectable and damages the trust relationship you are trying to build before it starts. Every outreach message must contain at least one specific, human-researched reference to the expert's own work. AI assists; the founder verifies and personalises.

Section 6: AI Tools — Opportunities, Challenges, and Responsibilities ​

The Opportunity ​

For a part-time team, AI is not a nice-to-have. It is a force multiplier that makes the difference between a sustainable GTM operation and an unsustainable one. Used well, AI allows 2–3 people with 10–20 hours/week to produce the research depth, content quality, and outreach volume that would otherwise require a full-time marketing hire.

The specific GTM functions where AI provides the highest leverage for Avelia:

FunctionAI ToolTime SavedHuman Oversight Required
Community thread researchClaude, PerplexityHighLow — summarisation, not claims
Post drafting (founder edits)ClaudeHighHigh — voice and accuracy
Expert outreach researchPerplexity, ClaudeHighMedium — personalisation check
Whitepaper/audit draftingClaudeHighVery high — legal/factual claims
Invite copy variantsClaudeMediumHigh — emotional authenticity
Competitor monitoringPerplexity alertsMediumLow — flag for human review
EU translation (DE, FR, SE)Claude + native speaker reviewHighHigh — cultural/medical nuance
User feedback synthesisClaudeHighMedium — pattern validation
Guide content draftingClaudeHighHigh — medical accuracy
Analytics interpretationClaude + PlausibleMediumMedium — strategic judgement

The Challenges ​

Challenge 1: Voice erosion The most dangerous GTM failure mode for AI-assisted content is gradual voice erosion — over time, all the content starts to sound the same, and that sameness sounds like AI. In a community as trust-sensitive as the IVF space, this is fatal. The mitigation is discipline: every piece of external content must pass through a founder's rewrite before publishing, not just a review. Reading it aloud and asking "would I actually say this?" is a reliable test.

Challenge 2: Factual drift in health content AI models hallucinate with confidence. In general content, this is annoying. In a document claiming competitor X had a specific data breach in a specific year, it is legally and reputationally dangerous. In Guide content advising on IVF medication timing, it is a patient safety issue. The team must maintain a strict policy: any factual claim that affects health decisions or makes a specific assertion about a named company or product must be verified against a primary source before publication.

Challenge 3: The appearance of scale masking the absence of depth AI makes it easy to produce a lot of content quickly. For a part-time team, this creates a specific trap: the illusion of being busy without doing the deep, trust-building work that actually acquires users. Posting 10 AI-assisted tweets per week while having zero real conversations with IVF community members is the worst possible use of GTM time. AI should compress the time spent on production tasks so that more time is available for the irreplaceable human work — community conversations, expert relationships, user interviews.

Challenge 4: Regulatory risk in health content Avelia is not a medical device and must not make medical claims. As Guide content scales, the risk of AI-generated health information crossing into medical advice territory increases. The team needs a simple content review checklist: does this content recommend a specific course of action? Does it diagnose or predict? Does it cite a medical source that needs verification? Any "yes" triggers human expert review before publication.

The Responsibility Framework ​

Operating at the intersection of reproductive health, couples' data, and AI-assisted content creation creates responsibilities that go beyond standard startup GTM ethics:

Users in crisis. Some Avelia users will be logging failed IVF cycles, pregnancy losses, and postpartum crises. Any AI-assisted communication that reaches these users — push notifications, email sequences, in-app messages — must be reviewed by a human for tone before deployment. An automated "celebrate your journey" message sent after a user logs a negative beta result is a product failure with human consequences. For email onboarding sequences specifically: every automated email in the sequence must be audited against the "Do Not Automate the Crisis Moments" principle in Section 7 — if the trigger condition could coincide with a negative outcome (e.g., a "check in on your TWW" email), it needs a human-reviewed response path for the negative case, not just the positive one.

Medical accuracy. The Guide section carries implicit medical authority. "Avelia says" will be quoted by users to their care providers. Every piece of Guide content must be reviewed by a qualified practitioner before publication. AI can draft efficiently; expert review is the non-negotiable gate.

Privacy claims must be technically accurate. Avelia's entire competitive position rests on privacy architecture. Any public claim about what Avelia can or cannot do technically — in community posts, in the whitepaper, in investor materials — must be verified by the technical founder before publication. The moment a privacy claim is found to be inaccurate, the entire trust foundation collapses.

Transparency about AI use. The IVF community and Avelia's privacy-focused target user are likely to ask whether Avelia uses AI. The honest answer — "yes, for drafting and research, with human review for everything we publish" — is the right answer and should be stated proactively. Discovering AI use after the fact creates more distrust than disclosing it upfront.

Section 7: What Not to Do ​

This section is as important as the rest of the strategy. Part-time teams fail not from doing too little, but from doing the wrong things with the bandwidth they have.

Do Not Chase Social Media Volume ​

Instagram, TikTok, and X (Twitter) require consistent, high-frequency content to build audiences. For a part-time team, maintaining these channels means producing content that is superficial enough to produce quickly — which is exactly the wrong tone for Avelia's audience. The IVF and privacy communities are not on TikTok waiting for fertility tips. They are on Reddit and Discord having real conversations. One authentic Reddit contribution per week > ten Instagram posts per week, for this product and this audience.

Exception: A LinkedIn presence for the founders is valuable specifically for investor and partner outreach. Keep it to 1–2 substantive posts per month on the privacy-in-health-tech topic.

Do Not Launch in EU and US Simultaneously ​

The EU and US markets require different regulatory framings (GDPR vs. post-Roe), different community spaces, different expert networks, and different content language. A part-time team attempting both will do both badly. The team is based in Germany — start EU-first. The EU IVF community is reachable from the home market, GDPR compliance is structurally built in, and the privacy story ("GDPR-native by architecture, not by policy") resonates most strongly here. Build the US playbook when the EU wedge is validated. The US market is larger in absolute terms but requires a pivot in framing (post-Roe legal risk replaces GDPR as the primary privacy narrative) and a different set of communities, press contacts, and expert networks — a full second GTM track that demands more bandwidth than a part-time team has in the early phase.

Do Not Build a Large Expert Network Before the App Is Ready ​

It is tempting to build relationships with expert partners before launch — they validate the concept and feel like progress. The risk: if you have built commitments with 20 doulas before the app is stable and the expert features are built, you will either disappoint them with a product that isn't ready, or you will ship under pressure with features that aren't right. Keep the pre-launch expert network to 2–3 advisors who understand they are advising on an unfinished product. Broader partner outreach begins when the core IVF tracking experience is stable.

Do Not Use AI to Fake Community Presence ​

Posting AI-generated content in the IVF community — even "personalised" AI content — without heavy founder editing constitutes fake presence. This community has seen it before and calls it out publicly. A single "this sounds AI-generated" comment on a community post from an Avelia founder undoes months of trust-building. The rule is absolute: if it appears in public with a founder's name on it, a founder wrote it. AI is the drafting tool, not the author.

Do Not Run Paid Acquisition Before You Have Retention Data ​

Paid ads before knowing your Day 30 retention rate means paying to acquire users who leave. In a privacy-sensitive health product, paid ads also create an association with the ad-funded competitors Avelia is trying to differentiate from. The earliest paid acquisition should begin only after (a) you have 500+ active users with measurable retention, (b) you know your partner linking rate, and (c) you have a clear LTV estimate. Until then, all acquisition is earned.

Do Not Automate the Crisis Moments ​

Push notifications for milestones, email sequences for onboarding, in-app messages for stage transitions — all of these can and should be automated for efficiency. The exception: any moment in the app that a user has logged as emotionally significant and potentially negative (a failed cycle, a negative beta, a pregnancy loss marker). These moments require human-designed responses with expert review, and they should never be triggered automatically without a thoughtful, tested human-written response attached.

Section 8: Milestones and Signals ​

These are not a timeline. A part-time team cannot commit to a calendar with confidence. These are the signals that tell you whether the strategy is working and when to shift.

Signal 1: Community Traction ​

What to watch: Post engagement quality in r/IVF and r/infertility — are your posts getting substantive responses (questions, personal experiences shared), or just upvotes? Are community members directly messaging the founders with product feedback?

What it means: Substantive engagement means you are being seen as a genuine participant, not a marketer. This is the precondition for any user acquisition from these communities.

Threshold to proceed: 3+ posts that generate >20 substantive comments each, and >5 direct messages from users requesting beta access or giving unsolicited product feedback.

Signal 2: Whitepaper Resonance ​

What to watch: Inbound links, citations, and direct messages after the Sovereign Data Whitepaper is published. Does it get shared by privacy researchers, journalists, or community moderators?

What it means: If the whitepaper circulates organically beyond the initial post, it is functioning as trust infrastructure. If it doesn't, the framing or technical depth needs revision.

Threshold to proceed: At least one citation or reference in a non-Avelia context (another Reddit post, a journalist's article, a privacy researcher's recommendation) within 30 days of publication, from a source with no affiliation to the founding team or their direct personal network.

Signal 3: Partner Linking Rate ​

What to watch: Of users who complete onboarding, what percentage link a partner account within 7 days?

What it means: This is the single most important product-GTM validation signal. Three threshold labels:

  • Target (>50%): The "Together" value proposition is strongly validated. Sustain acquisition and iterate on the invite flow to push higher.
  • Acceptable (35–50%): The proposition is landing but the invite mechanic or onboarding has friction. Investigate and improve, but do not pause acquisition.
  • Investigate (<35%): The couple-first positioning may not be understood, the invite mechanic is broken, or a significant portion of users are solo (single parents by choice, partners unwilling to engage). Identify which — the responses are different.
  • Stop and fix (<20%): Pause acquisition. The product is not communicating its core value proposition. Redesign onboarding and the invite flow before continuing.

Note: The 50% target is consistent with the marketing strategy and market analysis references to this metric. The investigate and stop thresholds are action triggers, not targets.

Signal 4: Expert Conversation Quality ​

What to watch: Of the 20-minute expert conversations, how many result in the expert asking to see the product again, or making an unsolicited referral to a colleague?

What it means: An expert who wants to see more is a potential distribution partner. An expert who refers a colleague without being asked has validated the value proposition.

Threshold to proceed to formal partnership: 3+ experts who have seen the product and expressed interest in recommending it to clients, unprompted.

Signal 5: Retention ​

What to watch: Day 7, Day 14, and Day 30 retention of the first 100 users. How many are still logging weekly at each interval?

What it means: Retention is the only metric that matters before paid acquisition. An app with 60%+ Day 30 retention has product-market fit. An app with 20% Day 30 retention has a product problem, not a GTM problem — and more acquisition will only make it more expensive.

Threshold to activate paid acquisition: Day 30 retention >40% across the first 100 users. Not before.

Signal 6: AI Tool Audit ​

What to watch: Every 6 weeks, review all published content and community posts. Does it still sound like the founders wrote it? Has the voice drifted toward generic AI tone?

What it means: Voice drift is gradual and hard to notice from inside. A periodic external read — a trusted friend, a community member who knows the founders — is the most reliable way to catch it before it damages trust.

Threshold to address: If a reader who knows the founders says "this doesn't sound like you" on more than one piece in a review cycle, pause all AI-assisted content production and reset the voice guidelines.

Signal 7: US Expansion Readiness ​

What to watch: EU market signals — partner linking rate, Day 30 retention, and active community presence in German-language and EU English IVF communities — sustained over at least 4 consecutive weeks.

What it means: US expansion requires a different regulatory framing (post-Roe legal risk replaces GDPR as the primary privacy narrative), different community spaces (r/IVF, r/infertility, US Discord servers), a different set of expert networks, and US-English content. It is a full second GTM track. Beginning US work before the EU wedge is validated splits bandwidth at precisely the moment EU community relationships are compounding.

Threshold to begin US planning: EU Day 30 retention >40% across 200+ users AND EU partner linking rate >40% sustained over 4 consecutive weeks. Until both conditions are met, all GTM bandwidth stays EU-focused.

Appendix: AI Tool Stack for GTM ​

ToolPrimary UseCostNotes
Claude (Sonnet/Opus)Long-form drafting, research synthesis, outreach personalisation~$20/moBest for nuanced health/privacy content
Perplexity ProReal-time research, competitor monitoring, source verification~$20/moUse for factual research; always check primary sources
Plausible AnalyticsWebsite analytics (privacy-preserving)~$9/moConsistent with Avelia's privacy positioning; GDPR-native
Notion AIKnowledge base, community insight capture, meeting notes~$10/moMaintain a running IVF community insight database
Beehiiv or ConvertKitEmail automation for onboarding sequences~$0–30/moChoose privacy-respecting options; avoid Mailchimp's data practices
Buffer or TypefullyLinkedIn scheduling (1–2 posts/mo)~$0–15/moKeep volume intentionally low
DeepL ProEU language translation (DE, FR, SE) with context~$10/moBetter medical/emotional nuance than Google Translate

Total AI tool spend: ~$70–100/mo — a fractional cost of a single marketing hire, delivering research, drafting, and automation support across all GTM functions.

Grounded in: Avelia Market Analysis (2026-03-23), Avelia Competitor Analysis (2026-03-23), Avelia Marketing Strategy (avelia-marketing-strategy.md), Avelia Product Spec (avelia-product-spec.md).

Private by design.