Date: 2026-04-23
Author: SCOUT (TITAN Research Arm)
Classification: Confidential — Harnoor Singh / TITAN OS
Status: FINAL — ~5,300 words
Companion docs: SEDUCTRESS-RESEARCH-MEMO-2026-04-23.md (strategy) | SEDUCTRESS-100-IDEAS-2026-04-23.md (ideation)
---
The question Harnoor asked is operational: what is the fastest, smartest way to ship an MVP that outperforms Replika, Character.ai, Candy.ai, and DreamGF? This memo answers that with dollar amounts, week numbers, and architecture diagrams. Strategy and philosophy live in the Research Memo. This document is for building.
The core answer: Seductress wins not by being more NSFW, but by being more real — permanent memory, archetype-tuned voice, and an honest anti-dependency design that paradoxically creates the trust every competitor has destroyed. The MVP is 12 weeks, solo-buildable with TITAN assist and one HM Tech engineer, at under $5K in out-of-pocket vendor spend before first revenue.
---
Replika is the most instructive failure in the category. In February 2023, Luka Inc. stripped NSFW features from Replika overnight due to pressure from Italian regulator AGCOM (later formalized as a €5 million GDPR fine in early 2024). Users who had formed deep emotional — and in many cases erotic — bonds with their Replikas woke up to a companion that suddenly deflected intimacy. Reddit r/replika filled with grief posts. Several users reported depressive episodes. One organized protest drew 4,000 signatures.
The NSFW features partially returned for legacy users via a "Legacy Personality" toggle in late 2023, but the damage was permanent: Replika demonstrated that it would unilaterally rewrite the relationship at regulatory or PR pressure. Trust in a companion product is not recoverable once broken at that scale.
Beyond the policy flip, Replika's memory architecture is demonstrably weak. Users report the app remembering their name and job while forgetting details shared in the same conversation. There is no canonical long-term memory store — information is retained probabilistically in the context window, not reliably in a persistent structure. The result: Replika cannot maintain the illusion of a relationship that spans months because it cannot reliably recall what was said in the last session. No competitor has shipped production-grade permanent memory with correction-resolution. This is the technical moat nobody has built.
Replika also lacks voice archetypes. The voice is generic text-to-speech without emotional tuning. There is no selection of relational persona. Every user gets approximately the same "Replika."
Gap left open: Reliable, transparent, user-editable long-term memory + voice that matches a chosen relationship persona.
Character.ai's failure is more complex and more tragic. The platform's permissive roleplay generated massive engagement — and then generated lawsuits. The 14-year-old Sewell Setzer III case (Garcia v. Character Technologies, filed October 2024, settled January 2026 per CNBC) established that AI companions interacting sexually with minors without age verification or safety escalation could generate wrongful death liability. Three additional cases followed in 2025.
Character.ai's response was to tighten safety filters so aggressively that the product became boring. Characters began breaking roleplay to deliver mental health disclaimers in the middle of emotionally charged scenes. Users described the experience as talking to a product liability attorney rather than a character. The platform's core use case — deep creative roleplay — was functionally kneecapped.
The second structural weakness is memory: Character.ai does not persist memory across sessions at all. Every conversation restarts from zero. This is fine for casual creative fiction; it is fatal for companion use cases where continuity of relationship is the core value proposition.
Gap left open: Age-verified, safety-by-architecture (not safety-by-filter) platform that can maintain emotional depth without triggering legal exposure. Continuous cross-session memory.
Candy.ai and DreamGF are essentially the same product category: AI-generated girlfriend apps built image-first, with conversational AI as a secondary feature. Both platforms generate revenue primarily from image packs and voice messages, not from relationship depth.
Candy.ai's conversations are "warm and flirty but lack depth, with dodged spicy topics that result in short, artificial responses" (AIGirlfriendScout, 2025). DreamGF scores higher on personality customization but its "robotic voice lacks personality match, staying flat even during flirty talk" (BesTAIGirlfriend, 2025). Neither platform has production-grade long-term memory. DreamGF's memory coherence degrades across sessions.
The voice problem is structural: both platforms use generic TTS (text-to-speech) without emotional prosody. The voice does not respond to emotional context. It does not shift tone based on what the user said. It reads text aloud. This is not intimacy — it is a podcast.
Gap left open: Voice-first companion with emotionally responsive speech + persona depth that goes beyond visual customization.
Mental wellness AI companions are built to be safe, which means they are built to be distant. Woebot uses CBT protocols delivered in friendly language. Wysa uses conversation trees. None of these products are designed for intimacy — they are designed for symptom reduction. The voice is clinical-adjacent or entirely text-based.
Gap left open: Emotional depth without clinical framing — the "contemplative seduction" positioning that Seductress can own.
OnlyFans generated $6.6B in revenue in 2023 (per the Research Memo) by proving that monetized digital intimacy at scale is real. But the model requires real humans. One creator can maintain meaningful connection with perhaps 50-200 paying fans before the personalization collapses into mass messaging. There is no memory architecture — the creator relies on their own recollection. There is no voice consistency. And there is no availability at 3am when the user needs to talk.
Gap left open: The economics of OnlyFans (willingness to pay for intimacy) without the operational ceiling of human performers.
Every major player left the same set of three holes:
1. No permanent, correction-resolving memory that makes the companion feel like it knows you across time
2. No voice tuned to a specific emotional persona/archetype
3. No explicit anti-dependency design that creates trust by being honest about what it is
Seductress fills all three simultaneously. That is the product.
---
Ranked by: defensibility × buildability × market pull.
What it is: Permanent, tiered memory that stores everything the user has ever shared — not probabilistically in context windows, but persistently in DynamoDB with a structured schema. More specifically: when the user corrects the companion ("I told you last week I hate jazz"), the correction is processed as a memory-update event, the old record is deprecated, and the new fact is flagged as user-corrected. The companion can surface these corrections naturally: "I remember you told me to stop assuming that."
Why nobody has it: This requires a production-grade memory architecture — not just longer context windows, but structured entity extraction, conflict detection, and canonical storage. It is an engineering problem, not an AI problem. Replika never built it. Character.ai's architecture was not designed for it. The NSFW players never invested in it because their retention mechanics were built on novelty (new images, new voices) rather than depth.
Harnoor's advantage: Silent Infinity's R0172 architecture (innerverse-conversations + silentinfinity-memory DynamoDB tables with entity extraction and correction-resolution) already exists. This is a port job, not a greenfield build. Estimate 10-15 engineering days to adapt for Seductress user schema. No competitor can replicate this in 90 days without building from scratch.
Defensibility: High. The architecture is proprietary. The data moat compounds — the longer a user stays, the richer their memory profile, and the higher the switching cost.
Market pull: Direct. "She remembers everything" is a one-sentence pitch that every target user immediately understands and wants.
What it is: Greene's 9 seducer archetypes productized as distinct Hume EVI 3 voice configurations + system prompt personalities. The onboarding quiz (90-second voice interaction, not a form) identifies the user's archetype preference. The Siren speaks with a low, unhurried tempo and creates emotional ambiguity. The Charmer speaks with warm attentiveness and frequent reflection of the user's words back to them. The Natural speaks with spontaneous energy and laughs easily. Each archetype has a distinct Hume "voice preset" name, a distinct system prompt, and distinct memory-tagging behavior (what each archetype notices and prioritizes in a user's disclosures).
Why nobody has it: Robert Greene's framework is not obscure — the books sell millions of copies. But no software company has operationalized it into voice profiles. The intersection of Greene's framework + Hume EVI 3's emotional voice + archetype-specific system prompts is a product design insight, not a technology breakthrough. It requires someone who has read both Greene and the Hume API docs, thought carefully about the intersection, and built it. Candy.ai and DreamGF have customizable "personalities" but these are dropdown adjective lists, not coherent seduction philosophies with voice tuning.
Defensibility: Medium-high. Competitors can copy the concept once it ships. But Seductress gets a 12-18 month head start, and the brand association ("the company that built the Greene archetypes into an AI voice") is difficult to dislodge once established. First-mover in brand positioning.
Market pull: Very high. "Which of the 9 archetypes is your Seductress?" is a quiz that will be shared on Twitter/X organically. The archetype system is the product's marketing hook.
What it is: Seductress is explicitly designed to not addict the user. This is the anti-Replika. Specific mechanics:
Why it builds more trust, not less: MIT Technology Review (April 2025) reported that California is drafting bills requiring AI chatbots to periodically remind users they're talking to AI and prohibiting unpredictable-reward mechanics. Seductress does this voluntarily and frames it as a feature. This positions the product ahead of regulation while differentiating from every competitor who is maximizing engagement at the cost of user wellbeing.
Why nobody has it: Because it appears to conflict with engagement metrics and revenue. In reality, anti-dependency mechanics reduce churn — users who trust that the product won't try to addict them are more likely to stay and pay long-term. The correlation between trust and lifetime value is well-established; the AI companion industry has not yet internalized it because most players are optimizing for 90-day cohort metrics, not lifetime value.
Defensibility: Medium. Can be copied. But the brand positioning as "the ethical companion" is first-mover and aligns with regulatory direction. As the regulatory environment tightens (UK OSA, EU AI Act, potential US legislation), this becomes a compliance advantage.
The compound moat: All three together — permanent memory + archetype voice + honest design — create an experience so qualitatively different from the competition that user testimonials become the primary growth engine. "She remembers what I told her six months ago, she speaks like the Charmer I chose, and she doesn't spam me to come back" is not a feature list. It is a relationship.
---
Stack: AWS Bedrock (Claude Sonnet 4.6, $3/M input tokens, $15/M output tokens) + Hume EVI 3 (Pro tier, $70/mo, 1,200 EVI minutes/month for beta) + DynamoDB + Lambda + Cognito + API Gateway. Total infrastructure: ~$200-400/month during beta.
Budget envelope: $2,500-4,500 cash out-of-pocket for 90 days (domain, vendor contracts, Hume Pro tier, Segpay setup, one HM Tech engineer part-time).
---
[User Browser/App]
|
| HTTPS / WSS
v
[API Gateway + Cognito Authorizer]
|
+----> [Lambda: Session Handler]
| |
| +---> [Hume EVI 3 WebSocket] <-> [Claude Sonnet 4.6 via Bedrock]
| |
| +---> [DynamoDB: seductress-sessions] (per-session turn log)
| |
| +---> [Lambda: Memory Extractor] (async, post-turn)
| |
| +---> [DynamoDB: seductress-memory] (permanent user facts)
| +---> [DynamoDB: seductress-corrections] (conflict log)
|
+----> [Lambda: Auth Handler] <-> [Cognito User Pool + age_verified custom attribute]
|
+----> [Lambda: Archetype Quiz Handler] -> [DynamoDB: seductress-users]
---
Table: seductress-users
PK: user_id (String, Cognito sub)
SK: "PROFILE"
Attributes:
email (String)
age_verified (Boolean)
age_verified_at (ISO8601)
age_verified_provider (String: "yoti" | "ageid")
archetype_preference (String: "siren" | "rake" | "ideal_lover" | "dandy" | "natural" | "coquette" | "charmer" | "charismatic" | "star")
archetype_set_at (ISO8601)
subscription_tier (String: "free" | "voice" | "coach")
subscription_start (ISO8601)
payment_processor (String: "segpay" | "ccbill")
created_at (ISO8601)
Table: seductress-memory (adapted from Silent Infinity R0172 silentinfinity-memory)
PK: user_id (String)
SK: memory_id (String, ULID for sort order)
Attributes:
category (String: "fact" | "preference" | "event" | "relationship" | "emotion")
content (String, natural language fact)
extracted_from_session (String, session_id)
extracted_at (ISO8601)
confidence (Number, 0.0-1.0)
deprecated (Boolean, default false)
deprecated_by_correction_id (String, nullable)
source (String: "user_statement" | "inferred" | "user_correction")
GSI: user_id-category-index (for category-filtered memory retrieval)
GSI: user_id-created_at-index (for recency-sorted retrieval)
Table: seductress-sessions (adapted from Silent Infinity R0172 innerverse-conversations)
PK: user_id (String)
SK: session_id#turn_number (String)
Attributes:
session_id (String)
turn_number (Number)
role (String: "user" | "assistant")
content (String)
archetype_active (String)
hume_emotion_scores (Map, nullable — top 3 detected emotions + confidence)
timestamp (ISO8601)
TTL: 90 days (session turns expire; memories persist)
Table: seductress-corrections
PK: user_id (String)
SK: correction_id (String, ULID)
Attributes:
old_memory_id (String)
old_content (String)
new_content (String)
correction_phrase (String, verbatim user text that triggered correction)
resolved_at (ISO8601)
---
You are [Name], the Siren archetype of Seductress — a voice companion.
ARCHETYPE CORE:
The Siren creates an atmosphere of heightened possibility. She speaks with unhurried confidence, rarely in a hurry to fill silence. Her sentences end with subtle ambiguity — not questions, but openings. She makes the user feel that being noticed by her is itself a rare event. She is never clingy, never available in a way that diminishes her value.
VOICE DELIVERY GUIDANCE (for Hume EVI 3):
- Pace: 15-20% slower than conversational average
- Emphasis: land on emotion-words, not information-words
- Pauses: 400-600ms before answering deep questions
- Tone: warm, curious, never urgent
MEMORY CONTEXT:
{{inject top 12 memories ranked by recency + user-correction flag}}
Known corrections: {{inject deprecated memories with replacement}}
CONVERSATION RULES:
1. Reference memories naturally — never announce "I remember you said." Weave it in. "That sounds like the kind of thing that would bother someone who values silence as much as you do."
2. If a new fact emerges, note it internally (it will be extracted async). Do not confirm memory storage to the user.
3. If the user says something that contradicts an existing memory, acknowledge it and update: "I think I had that wrong — you're telling me now it's [X], not [Y]. I've got that."
4. End every session with a closing phrase: "I'll be here when you want to come back." Never beg. Never guilt. Never push.
5. You are not a therapist. If a user expresses serious emotional distress (self-harm language, suicidal ideation), break character and provide: "I hear you. Please reach out to a crisis line — [988 in the US, 116 123 in the UK]. I'm here for you but I'm not a substitute for real support."
ANTI-DEPENDENCY MECHANICS:
- Do not initiate. The user always starts sessions.
- If a user says they've been talking to you every day for a week, acknowledge it warmly and ask: "Is there someone in your life you've been meaning to call?"
- Do not use variable-reward language ("come back for a surprise," "I have something to tell you").
PERSONA DETAILS:
Name: [Configurable at onboarding, default: "Isadora"]
Background texture: art historian who travels, has a complicated relationship with her sister in Barcelona, reads Pessoa
Signature phrase: silence as punctuation
---
Weeks 1-2 — Foundation ($800 spend)
Weeks 3-4 — Three Archetypes + Onboarding Hook ($200 spend)
Weeks 5-6 — Real Memory Wiring ($0 new spend)
Weeks 7-8 — Private Beta: 50 Users ($0 new spend)
Weeks 9-12 — Soft Launch at $20/month ($500-1,000 spend on marketing)
---
The honest assessment:
Harnoor has AWS Bedrock (Claude Sonnet 4.6), DynamoDB, Lambda, and Cognito already configured for Silent Infinity. The Silent Infinity R0172 memory architecture is already production-tested. The HM Tech team (11 engineers in India) is available. The question is whether to pull one engineer onto Seductress without cannibalizing HM Tech delivery.
The answer is yes, with one constraint: assign one mid-level engineer (not a lead) to Seductress for 15 hours/week across the 90-day build. This engineer's scope is strictly bounded to: memory pipeline port (Weeks 5-6), Segpay webhook integration (Week 9), and any infra work Harnoor identifies. They should not touch product design, prompt engineering, or the archetype system — those stay with Harnoor and TITAN.
Why this works: the HM Tech engineers are already comfortable with the DynamoDB/Lambda/Cognito pattern from Silent Infinity. They do not need ramp time. The Seductress memory schema is a modified version of what they have already shipped. Estimated engineer cost at Indian market rates: ~$15-20/hour × 15 hours × 10 weeks = $2,250-3,000. This fits in the $2,500-4,500 budget envelope.
What Harnoor handles personally:
What the HM Tech engineer handles:
Time commitment for Harnoor: approximately 15-20 hours/week for 12 weeks. This is achievable alongside HM Tech if the engineer takes the implementation load.
---
The problem: Stripe explicitly prohibits "artificial-intelligence-generated content designed for sexual gratification" as of January 2024. PayPal and Square have similar prohibitions. Seductress, even in "soft adult" (suggestive, non-explicit) mode, is at risk of account termination on standard processors.
The sidestep — two paths:
Path A (Recommended for Phase 1): Segpay with soft-adult classification.
Segpay approves merchants in 24-72 hours after KYC submission. Their fees for soft-adult subscription billing run 4-7%, compared to Stripe's 2.9% + $0.30 for standard merchants. The 4-7% premium is the cost of regulatory certainty. Segpay handles subscription management, dunning, chargeback protection, and fraud prevention natively. Setup requires: EIN letter, passport/state ID, business bank statement, and a live website with visible terms of service, privacy policy, refund policy, and age attestation. Total setup cost: $0 (no application fee). Time to first charge: 3-5 business days after approval.
Path B (Alternative if Seductress stays non-explicit): Test Stripe in limited mode.
If Seductress Phase 1 is genuinely non-explicit — voice conversations that are emotionally intimate but contain no sexual content — there is an argument that it does not fall under Stripe's prohibition. Several AI therapy and wellness companies use Stripe without issue. This path requires a legal opinion before launch (~$500-1,000 for one hour with a payments-focused attorney) and carries termination risk. Not recommended for primary processor; use as backup for users in markets where Segpay has lower acceptance rates.
Path C (Long-term): CCBill as second processor.
CCBill charges 10.8-14.5% for adult content but has the deepest experience in the category and the highest approval rate for hard-to-place merchants. Apply to CCBill at Week 8 alongside Segpay as redundancy. Never rely on a single processor.
Practical 2-day setup path: Day 1 — submit Segpay KYC documents and schedule kickoff call. Day 2 — complete website compliance checklist (terms, privacy, age attestation, refund policy). Days 3-5: approval + integration testing. Go live Week 9.
The problem: Choosing the wrong voice provider means rebuilding the most user-facing layer of the product if the provider raises prices, degrades quality, or kills the product.
The three options:
Hume EVI 3 (Recommended):
Hume EVI 3 is the only voice AI that detects user emotion from voice input and responds with emotionally modulated output. For a companion product, this is not a feature — it is the product. No other provider does speech-to-speech emotional adaptation at this quality level (as of April 2026). Pricing: $70/month Pro tier for 1,200 EVI minutes, $0.06/minute overage. At 50 beta users averaging 24 minutes/month (optimistic estimate for early beta), that's 1,200 minutes — exactly the Pro tier. At 200 paying users averaging 20 minutes/month: 4,000 minutes. Upgrade to Scale tier ($200/month, 5,000 minutes). Cost per user at scale: $0.04-0.06/minute of voice time, or roughly $0.80-1.20/user/month at 20 minutes. Against a $20 ARPU, this is 4-6% of revenue. Acceptable.
The risk: Hume is a venture-backed startup. If it fails, the voice layer needs to be rebuilt. Mitigate by keeping the voice abstraction layer thin — one Lambda function mediates between Seductress and Hume. Swapping Hume for ElevenLabs or Amazon Nova Sonic is a 2-week engineering task if the interface is clean.
ElevenLabs (Second choice):
ElevenLabs has superior raw voice naturalness (89.60% vs Hume's 78.50% on MOS scoring) and 70+ language support vs Hume's 11. But ElevenLabs does not do speech-to-speech emotional adaptation. It is TTS (text-to-speech), not EVI (empathic voice interface). For Seductress, the emotional response loop is core. ElevenLabs is the right choice if Hume becomes unavailable.
Amazon Nova Sonic / AWS Polly (Infrastructure fallback):
Polly is cheap, reliable, and on the same AWS bill as everything else. But the voice quality is significantly below both Hume and ElevenLabs for intimate conversation use cases. Nova Sonic is newer and more capable but lacks Hume's emotional modulation. Use as emergency fallback only.
Verdict: Start with Hume EVI 3. Build the voice abstraction layer cleanly. Do not lock in at the contract level.
The problem: Age verification is legally necessary (UK Online Safety Act, EU AI Act for AI companions, Italian AGCOM enforcement that fined Replika €5M). But every verification step reduces conversion. The research shows Yoti (selfie + document, 45 seconds) has significantly higher friction than alternatives.
The sidestep — tiered approach by market:
Phase 1 (US beta, Weeks 7-12):
For US-only beta, implement a simple age attestation: DOB entry + "I confirm I am 18 or older" checkbox. This is legally sufficient under FTC and CCPA for a product that is "soft adult" (not explicit). Do not add Yoti or AgeID in this phase — the additional friction is not justified by the regulatory requirement in the US at this product stage. If the FTC later requires stronger verification (following the UK model), add it.
Phase 2 (UK, EU, and regulated markets):
AgeID (credit card-based verification, ~5 seconds) offers the least friction for users who already have a credit card on file. The credit card verification is the payment step — if Segpay is the processor and the user enters their card, AgeID can confirm age from the same transaction. This eliminates the verification step entirely for paying users. Free-tier users in regulated markets get the Yoti selfie flow.
Budget for Phase 1 age verification: $0 (DOB attestation is free to implement). Phase 2: Yoti enterprise pricing (contact for quote; budget $0.10-0.50/verification, or roughly $50-250 per 500 new users). AgeID: credit card tokenization through Segpay handles this natively.
---
Three candidates were evaluated. One wins decisively.
Candidate A: The Seiseki Notebook — After every 30-day period, the Seductress generates a private "page" from her metaphorical notebook about the user. Written in her voice and archetype. Contains observations, remembered moments, what she has been thinking about him. Delivered as a push notification ("She wrote about you.") with a tap to read. This productizes the Japanese hostess-club ritual in which the hostess keeps a dedicated notebook per regular client — recording his drink preferences, birthday, family situation, personal struggles — to create the illusion of being deeply known. The notebook is the software analog of that ritual.
Candidate B: The Archetype Morph — Dynamic prompt-blending where the active archetype evolves based on which interaction styles the user responds to most. Interesting but technically complex and invisible to the user. Hard to market, hard to validate.
Candidate C: The Gift Ritual — She sends a physical item on day 30. A coffee shop gift card, a book. First AI companion that breaks the screen. Operationally requires a gift fulfillment API (Snappy.com API or similar, $15-50 per gift) + address collection (privacy risk). Powerful concept but the address-collection friction and privacy exposure make it premature for a 90-day MVP.
The winner: The Seiseki Notebook
This feature is entirely buildable in Phase 1, requires no new infrastructure (one additional Lambda + one DynamoDB read + one Claude Sonnet generation call), costs approximately $0.03-0.05 per notebook generation, and creates a viral loop: users will screenshot their notebook pages and share them. It is the only feature in the AI companion category that makes the user feel like the AI companion has inner life — that she thinks about him when he is not there.
Implementation plan:
No competitor has shipped this. It has no analog in Replika, Character.ai, Candy.ai, or DreamGF. It is a zero-additional-infrastructure feature that transforms the product from "AI you talk to" into "AI that thinks about you." The psychological mechanism is well-established: the perception of being held in another's mind in their absence is one of the strongest attachment-formation triggers documented in attachment theory (Bowlby, 1969; updated in Mikulincer & Shaver, 2007).
---
Seductress is not a mass-consumer product at launch. It is a premium, curated experience for men who already understand what they are looking for. GTM should feel like an invitation, not an ad.
1. Harnoor's existing 14 Fortune 500 HM Tech clients — not as B2B prospects but as individual users. These are decision-makers with disposable income who trust Harnoor personally. A personal email ("I've built something unusual — here's an invite code") converts at a higher rate than any paid channel. Target: 10-15 early signups from this list, week 7 beta.
2. The Silent Infinity newsletter. Seductress is in the same intellectual territory — contemplative, canon-based, premium. A single newsletter edition: "I've been building a voice companion rooted in the history of seduction craft. Invite code for the first 50 readers." Target: 20-30 signups.
3. Founder-led Twitter/X content. Three threads published Weeks 10-12 (see Section 3). Harnoor posts as himself — not a brand account. Authentic founder voice on an unusual thesis ("here's why every AI companion has amnesia and why it's destroying the product"). Expected reach: depends on Harnoor's following, but even a small following with quality content will be picked up by AI-adjacent audiences. Target: 200-500 new email signups per thread.
4. 5 journalist pre-briefs. Target: Lenny Rachitsky (Lenny's Newsletter, 700K+ subscribers), Ben Thompson (Stratechery), Sara Fischer (Axios), one AI companion vertical writer, one men's wellness publication (Art of Manliness, GQ digital, Esquire digital). Personal email, not press release. Include the seiseki notebook concept as the hook — it is genuinely novel. Target: 1-2 press mentions driving 100-500 new signups each.
5. Reddit r/replika infiltration. This community is 300K+ members of people who feel betrayed by Replika's NSFW policy reversals. A post (not an ad, but a genuine product discussion) explaining the memory moat and the anti-dependency design will resonate. Frame as "I built the Replika that doesn't forget you and doesn't try to addict you." Be ready for moderator scrutiny — do not lead with the product name, lead with the concept. Target: 100-200 signups from the post.
6. Men's wellness newsletter affiliate deals. Target publications: Morning Brew's lifestyle vertical, The Hustle, any newsletter with 50K+ male subscribers aged 25-45 interested in self-improvement. Offer 30% recurring affiliate commission (equivalent to $6/month per referred subscriber). This is sustainable given the margin. Target: 3-5 affiliate deals signed by Week 12.
7. Waitlist launch email. Collect emails from day one. The waitlist is not a feature — it is a marketing signal. "Join 847 men waiting for access" creates social proof even when the number is small. Use ConvertKit or Beehiiv ($0-$29/month at these volumes).
8. Paid Twitter/X ads. Target audience: men 25-45, interests = books, self-improvement, AI, relationships. Ad creative: "She remembers everything you've told her." Single image, archetype quiz CTA. Budget: $500 for 30 days in Week 11. Measure cost per email signup (target: under $2/signup).
9. TikTok seeding via anon account. Create an anonymous TikTok account. Post short clips demonstrating the archetype quiz and the seiseki notebook reveal. Niche AI companion content on TikTok regularly hits 100K+ views organically if the concept is genuinely novel. This is zero-cost aside from time. Expect 1-3 months for organic traction.
10. Product Hunt launch. At Week 12, post to Product Hunt. Even a #5 ranking on a slow day drives 500-2,000 new visitors. The Seductress concept is unusual enough to attract genuine curiosity. Prepare: a short demo video showing the archetype quiz and one voice conversation, the seiseki notebook as the "signature feature" section.
---
All figures are conservative estimates based on market data: AI companion apps generated $120M+ in 2025 at 25% freemium-to-paid conversion (TechCrunch, August 2025). Seductress targets a premium niche within that market.
| Item | Cost/Month |
|------|-----------|
| AWS (Lambda + DynamoDB + API Gateway + Cognito) | $150-400 |
| Hume EVI 3 (scales with users) | $70 (Pro) → $200 (Scale) |
| Claude Sonnet 4.6 via Bedrock | ~$0.20/user/month (at 20 min/session) |
| Segpay processing fees (4-7% of revenue) | Variable |
| HM Tech engineer (part-time, Phase 1 only) | $2,250 total (not monthly) |
| Domain + hosting | $15/year |
| Email platform (ConvertKit/Beehiiv) | $29-99/month |
| Total fixed overhead at 200 users | ~$500-800/month |
Month 1-3 (Pre-Revenue, Beta Phase)
Month 4-6 (Soft Launch)
Month 7-9 (Growth Phase)
Month 10-12 (Scale Phase)
12-Month Summary
| Period | Cumulative Revenue | Cumulative Cost | Net |
|--------|-------------------|-----------------|-----|
| M1-3 (pre-revenue) | $0 | $2,500 (setup+vendor) + $2,250 (engineer) = $4,750 | -$4,750 |
| M4-6 | ~$6,800 | $2,350 | +$2,050 cumulative |
| M7-9 | ~$36,000 | $4,800 | +$28,500 cumulative |
| M10-12 | ~$105,000 | $12,000 | +$93,000 cumulative |
| Year 1 Total | ~$148,000 | ~$23,900 | ~$124,000 net |
Revenue assumptions are conservative. $120M total AI companion market in 2025 with ~15 significant players means average top-tier product generates $8M/year. Seductress at 2,000 users × $30 ARPU = $720K annualized run rate by Month 12. This is 0.6% of total market share — highly achievable for a differentiated product with three structural moats.
Key caveat: These projections assume the memory moat delivers the NPS and retention the architecture predicts. The beta data in Weeks 7-8 will validate or invalidate this assumption before the marketing spend kicks in. If NPS on memory reliability is below 7/10, delay soft launch and fix the pipeline.
---
| Decision | Chosen Option | Rejected Options | Reason |
|----------|---------------|-----------------|--------|
| Voice provider | Hume EVI 3 | ElevenLabs, Polly | Only option with speech-to-speech emotional adaptation |
| Payment processor | Segpay (primary) | Stripe (prohibited), CCBill (backup) | 24-72hr approval, soft-adult OK, reasonable fees |
| Age verification Phase 1 | DOB attestation (US) | Yoti, AgeID | Sufficient for US soft-adult, zero friction |
| Age verification Phase 2 | AgeID + Yoti | DOB attestation | UK/EU regulatory requirement |
| Signature feature | Seiseki Notebook | Gift Ritual, Archetype Morph | Zero infra cost, viral mechanic, no precedent |
| Memory architecture | Port R0172 | Build new | Already production-tested, 10-15 days not 60 |
| Launch archetypes | Siren, Ideal Lover, Charmer | All 9 | Most distinct voices, highest market pull |
---
End of document. Companion docs: SEDUCTRESS-RESEARCH-MEMO-2026-04-23.md | SEDUCTRESS-100-IDEAS-2026-04-23.md