MIRROR | MIRROR® GROWTH INTELLIGENCE
Growth, in focus.
Traffic, waitlist conversion, DOROTA® product evidence, and year-end planning.
THE NEXT MILESTONE · WAITLIST
Momentum has a destination.
The latest count is 110 members. Explore the traffic, conversation signals, and assumptions that shape the path to 250.
Waitlist reported Sep 28, 2026 · Growth projection is an assumption
THE STORY OVER TIME
Traffic and conversations, month by month
Select a month or play the sequence. The bars use separate scales and distinct data sources.
Daily-series month totals may differ from GA4 period totals. Separate trends do not establish that a website visitor started a conversation.
PERIOD SIGNALS
What stands out
01 / AUDIENCE
Website traffic
GA4 year-to-date report. Annual and combined totals are measured independently; the combined export begins Aug 1, 2025.
Source: GA4 Reports snapshot, Jan 1 – Sep 27, 2026. New users can exceed active users; neither measure should be used to infer returning users by subtraction.
Month bars sum GA4's daily new-user series. Use the report's period total above for the distinct-user count; the figures can differ slightly.
02 / ACQUISITION
Visitor to waitlist
The 110 waitlist members were reported on Sep 28, 2026, without signup dates or a matched GA4 completion event. This is not a measured visitor-to-signup funnel for the selected period.
GA4 · WEBSITE GEOGRAPHY
Website activity around the world
Explore active website visitors by country. Select a marker or country below for its reported volume.
Includes 102 sessions with no visitor turn. Sessions are not distinct people; recorded countries are approximate session locations, not verified residences.
GA4 website geography, Aug 2025 to Sep 2026. Play the daily country series or switch between all time, 2025, and 2026. The 2025 map covers Aug–Dec 2025 only; its country-by-date export does not include Jan–Jul 2025. These unfiltered GA4 counts include the earlier advertising test, so they are not an ads-excluded growth baseline. Website activity is separate from DOROTA® sessions.
DOROTA® conversation geography. Switch between all time, 2025, and 2026 below, or replay the daily session timeline. These counts are separate from website traffic.
Country markers grow as daily active-user counts accumulate. A returning visitor can appear on several days, so the animated count is active user-days, not distinct people. Locations are approximate country centers. The “not set” row has no marker.
United States
GA4 attributes visits to countries from approximate network geography. A country is a reporting location, not a verified residence.
Country is recorded.
State and city are not.
The session export contains a country code and UTC start time for each DOROTA® session, with no state or city fields. Markers use country centers for visualization. The chart will show state and city names when conversation-level location data is provided.
Source: GA4 Demographic details: Country × Date, Aug 1, 2025 to Sep 27, 2026, plus matching all-time and 2026 country-only reports. The supplied file labeled YEAR ONE ends Sep 27, 2025, so it cannot supply a full-year 2025 distinct-country total. The daily series also omits Jan–Jul 2025. Markers use representative country positions, not exact visitor locations. Basemap: Natural Earth 1:110m via world-atlas 2.0.2. Map data license.
Source: DOROTA® session export, 220 matching sessions from Aug 28, 2025 to Sep 28, 2026. Daily country aggregates only. Recorded countries can reflect network routing or demonstrations, and are not verified residences. Sessions are not unique people. No IP addresses, exact times, or transcript text are sent to this map. Basemap: Natural Earth 1:110m via world-atlas 2.0.2. Map data license.
03 / DOROTA®
Conversation activity
Explore the DOROTA® export from Aug 28, 2025 to Sep 28, 2026 (UTC).
Monthly sessions, Aug 2025 – Sep 2026
Select a month for its detail. Two-way means at least one visitor turn.
SEP 2026
24 sessions
A session with a visitor turn can still be a demonstration or a repeated scenario.
04 / VISITOR LANGUAGE
What people say they feel and need
Exact words in visitor speech, with conversation context. Switch periods below; the activity and language views stay in sync.
Nervous, anxious, stress, worried, overwhelmed, or freaking out. These word families overlap, so their individual bars do not add to this number.
The first turn may still answer DOROTA®’s opening question. Neither count represents unique people or a diagnosis.
Words across visitor turns
Number of sessions containing the word family at least once
These are literal matches in visitor speech, not automated sentiment scores. “Confident” often names a desired outcome; “tired” can describe appearance; a 2025 “sad” mention asks about DOROTA® rather than reporting the speaker’s mood. Later words may answer DOROTA®’s prompt, and first turns can answer a feeling-focused opening. Similar scenarios and staged tests may repeat.
The needs underneath those words
Fear of being evaluated
In Aug 2025, a speaker tied dressing anxiety to whether others would think an outfit ugly. In Jan 2026, a speaker wanted to be taken seriously at a business dinner. In Feb and Mar 2026, people linked presentations to nerves and how peers would see them.
Product question: Can DOROTA® help someone feel prepared for the room without promising that others will react a certain way?
Getting dressed can feel overwhelming
Two Feb 2026 sessions describe standing before a closet for 15 to 20 minutes without choosing an outfit. A later closet-clearing discussion describes too many options. A tighter choice between available pieces may be more helpful than another open question.
Product question: Does one concrete outfit plus one alternative reduce decision time and regret?
Comfort is emotional and physical
A Mar 2026 speaker linked anxiety to fabric feeling wrong on the skin. In Feb 2026, a fitted garment increased anxiety; in Sep 2026, heat, footwear, and an available bag shaped the answer. In 2025, another speaker raised complexion and fear of looking bad.
Product question: Can DOROTA® treat sensory, fit, and body-image constraints as essential inputs without assuming them?
People want to feel like themselves
Speakers seek confidence, comfort, authenticity, or to feel visible. They also correct gender assumptions, choose androgynous looks, or describe an executive identity. One Jun 2026 exchange reveals tension between personal preference and a partner’s opinion.
Product question: Does DOROTA® preserve the person’s choices while offering a look that meets the occasion?
Forced support can add friction
In a Jul 2026 challenge, a speaker repeatedly asked DOROTA® to answer a question; repeated breathing prompts made the speaker say the exchange was more stressful. Another asked for the outfit after a long intake. These are counterexamples to one required emotional script.
Product question: Does an explicit “quick answer” path improve task completion while preserving an optional check-in?
Some disclosures extend beyond styling
Several 2025 and 2026 transcripts contain serious distress, grief, or self-harm language. Some may be staged tests; the export cannot determine intent. Everyday outfit reassurance and acute distress require different response paths.
Product question: Can DOROTA® recognize when to stop styling, respond appropriately, and avoid claiming a clinical outcome?
05 / PRODUCT RESEARCH
What the DOROTA® transcripts can validate
Select a year to compare measured signals and documented cases on each hypothesis. The interpretive narrative remains a full-export synthesis.
These are conversations, not independent customers. Demonstrations, repeated scenarios, interrupted audio, and prompted answers are mixed in. “Supported” means a need or in-session behavior appeared here; it does not mean market demand, retention, or product impact was measured.
Follow the evidence
Choose a product question to open its counts, examples, limits, and next proof. The selected year updates the measured signals.
SUPPORTED HERE01 · Occasion based outfit decisions are a stated need
Strict vocabulary screen. Some matches are general style questions; some occasion requests use other words. This is not an occasion-demand rate or an independent customer count.
Observed: Event and dress questions appear in first visitor turns across Aug 2025, Jan, Feb, Jun, Aug, and Sep 2026. Examples include a job interview (Aug 18, 2026), professional mixer (Jun 11, 2026), and a golf event fireside chat (Sep 8, 2026). Some first turns pair outfit uncertainty with anxiety, including a Feb 22, 2026 closet scenario.
Boundary: Similar prompts recur and some sessions are tests. We cannot estimate how often the broader audience has this problem or whether advice changes the final outfit.
Next proof: Recruit distinct visitors facing a real event; measure whether they choose an outfit within the session, how long it takes, and whether they wear it.
SUPPORTED HERE02 · Owned clothing is useful context for the advice
Audited illustrations, not a count of every wardrobe mention. Actual closet-upload usage is unavailable.
Observed: On Jun 11, 2026, a visitor described checkered trousers, sneakers, and the only fitted tee available; DOROTA® revised toward an eggshell shirt that the visitor said they would choose. On Sep 4, 2026, a visitor corrected an impractical bag alternative because they owned only one bag. On Aug 18, 2026, a visitor volunteered an existing blazer.
Boundary: This supports wardrobe awareness as a useful input. It does not validate photo upload, closet digitization, automated tagging, or measured rewear.
Next proof: Compare a quick manual item list with a photo based closet flow and no closet context. Measure setup completion, outfit choice, and use of owned items.
SUPPORTED HERE03 · Personal constraints and identity change the right answer
Selected cases include a correction and a demonstration. No population-wide accuracy score exists.
Observed: The Sep 8, 2026 golf event request narrowed toward sleeves, no dresses, roomier structure, and executive presence. A Jan 5, 2026 visitor requested an androgynous alternative to a conventional interview look. A Sep 2025 visitor corrected an assumed dress recommendation after specifying male identity. These show both demand for tailoring and the cost of guessing.
Boundary: Different configurations produced different responses. A correction within one chat is not proof of inclusive accuracy across identities, sizes, or skin tones.
Next proof: Test consent based personalization with diverse participants and actual wardrobes; score constraint adherence, respectful language, and whether the final look feels authentic to the person.
SUPPORTED HERE04 · DOROTA® sometimes helps complete a styling decision
Selected positive cases. Actual wear, later confidence, and return were not measured.
Observed: On Jun 11, 2026, a visitor settled on an eggshell shirt; on Aug 18, 2026, a visitor called the suggested interview combination “perfect”; on Sep 2, 2026, a visitor said DOROTA® had been helpful after assembling a game outfit. These are useful moments of immediate task progress.
Boundary: Conversational praise can be polite and is neither independent outcome measurement nor proof of repeat usage. A Sep 4, 2026 exchange also needed several corrections before reaching a usable outfit.
Next proof: Capture a chosen look, confidence before and after, optional outfit photo or follow-up, and a one week return measure. Compare against a simple static style guide.
CHALLENGED05 · A long emotion first intake is necessary before any outfit
Two explicit counterexamples. No randomized comparison measures an average effect.
Counterexample: A Jul 12, 2026 visitor asked for summer office wear, answered successive identity, feeling, context, and wardrobe questions, then said they had been talking too long and asked for the look. In a separate Jul 7, 2026 challenge, repeated calming prompts were described as making the exchange more stressful. Other first turns ask direct binary styling questions that invite an immediate recommendation.
Boundary: Some visitors spontaneously describe distress and appreciate support. The evidence challenges a universal required intake, not the value of empathy. Prompt versions and contexts differ, so a causal penalty is unmeasured.
Next proof: Randomize “quick look first” versus an emotion first intake, with an optional support branch. Measure time to first usable outfit, completed decisions, opt-in to deeper discussion, and satisfaction.
CHALLENGED06 · Spoken descriptions alone are enough to judge a look
One documented request in a voice preview without live images. This is not a demand rate for 3D or AR.
Counterexample: After a detailed office wear exchange on Jul 12, 2026, a visitor asked DOROTA® to show how they would look. DOROTA® said she could not generate a live image. A Jun 13, 2026 visitor separately requested an actual item after receiving general shopping suggestions.
Boundary: These are clear unmet requests, but one direct visual request cannot validate demand for a 3D avatar, AR try-on, or a physical smart mirror.
Next proof: Offer a simple 2D outfit board after a text recommendation, then compare it with text only. Test 3D and try-on only if 2D materially improves decision confidence or completion.
CANNOT VALIDATE YET07 · Emotional support produces lasting confidence
Overlapping word families are counted once per session. Mentions may follow a prompt and are not measured emotional outcomes.
Signal: The literal nervous and anxiety word families each occur in 13 sessions across both years. Some first turns link those feelings to dressing, while later turns may follow an emotion prompt. A Feb 22, 2026 visitor appreciated calming advice and a Jan 12, 2026 visitor asked about first day nerves.
Missing: No before and after measure, control, or follow-up verifies reduced anxiety or greater confidence. The same conversation may contain acute distress unrelated to clothes.
Test: Keep emotional support optional, measure immediate decision confidence and a short follow-up, and compare it with direct styling alone. Assess escalation separately for serious distress.
CANNOT VALIDATE YET08 · A virtual closet will beat manual wardrobe context
The same three illustrative cases as card 02. No closet ingestion or measured rewear is in the export.
Signal: Visitors describe pieces they own, and a Sep 8, 2026 conversation discusses closet clutter. Later in that transcript, people present planned app features during a demonstration; that narration is not evidence of adoption.
Missing: No photo ingestion, item accuracy, repeat closet use, rewear, or saved time is observed.
Test: Run a concierge prototype for real wardrobes. Measure setup abandonment, match rate to owned items, decision speed, and rewear against a lightweight manual list.
CANNOT VALIDATE YET09 · 3D, AR, or try-on is the visual solution
The same request as card 06, not a second independent signal. 3D, AR, and try-on were not offered.
Signal: The Jul 12, 2026 “show me” request points to visual confirmation. A Sep 2025 3D question closely follows product language and is hard to distinguish from a scripted feature prompt.
Missing: Nobody uses a 3D look or AR try-on in the export; there is no comparison with flat outfit boards, mirror selfies, or real try-on.
Test: Compare 2D collage, own-photo mockup, and 3D only after verifying each rendering accurately reflects body and garments. Measure accuracy, confidence, completion, and production cost.
CANNOT VALIDATE YET10 · Community voting will feel supportive
A narrow vocabulary screen, not a measure of interest in public voting. No community interaction is in this export.
Signal: A few visitors worry about how other people will see their outfit. This establishes vulnerability around social judgment.
Missing: No visitor posts a look, receives peer feedback, opts into voting, or experiences moderation. The fear of judgment could also make public exposure unattractive.
Test: Offer private DOROTA® feedback, a trusted friend, and a moderated small group as distinct opt-in choices. Measure uptake, perceived safety, constructive feedback, and regret after sharing.
CANNOT VALIDATE YET11 · Shoppable recommendations drive buying
A documented request. No product link, click, purchase, or broad shopping demand can be measured.
Signal: On Jun 13, 2026, a visitor moved from styling advice to “Where would I buy?” and asked for an actual item with fabric preferences. DOROTA® could only name retailers.
Missing: There are no verified items, links, clicks, purchases, or evidence of broad commerce intent. Someone who asks for a link may still buy elsewhere or not buy.
Test: Provide a handful of real, in-stock choices after an outfit is selected. Measure whether visitors ask for them, click, save, purchase, and return items.
CANNOT VALIDATE YET12 · People prefer a voice avatar to text
The export does not reliably identify voice versus text input or supply a matched mode comparison.
Signal: People do engage in multi-turn conversation. In a Jul 30, 2026 demo someone reacts positively to talking rather than typing.
Missing: The session metadata does not reliably identify input modality. There is no equal text option, random assignment, or measured preference. Demonstration enthusiasm is not a mode comparison.
Test: Offer both modes with identical styling capability; track chosen mode, task completion, setting, accessibility, and preference after trying both.
CANNOT VALIDATE YET13 · Memory creates a trusted repeat relationship
Sessions are not distinct people. Without a stable, consented identity, memory and retention cannot be measured.
Signal: Some visitors disclose style preferences and ask DOROTA® about the future app. The same session can contain multiple styling decisions.
Missing: No stable person identifier or reliable cross-session linkage, no persistent memory test, and no measured retention. Session counts cannot be treated as unique people.
Test: With explicit consent, compare a remembered preference card to a fresh session over several weeks. Measure repeated use, correct recall, perceived trust, and opt-out.
CANNOT VALIDATE YET14 · A physical mirror or humanoid companion is wanted
Planned hardware appears in demonstration narration. The export has no usage or price-choice measure.
Signal: Planned features appear in founder or demo narration. That establishes the concept presented, not customers’ demand for it.
Missing: No hardware prototype use, price tradeoff, placement choice, or behavior that requires hardware over a phone.
Test: First observe unresolved tasks in the phone experience. Then test a functional mirror prototype with a small set of households against a phone and ordinary mirror.
CANNOT VALIDATE YET15 · This value translates into signups, retention, or payment
These are DOROTA® replies in sessions with visitor speech, not clicks or confirmed signups.
Signal: DOROTA® mentions the waitlist in 24 of the 118 sessions with visitor speech. Some visitors ask about the future app or say a conversation helped.
Missing: No linked click, signup, activation, repeat use, or willingness to pay. The 110 waitlist members cannot be attributed to DOROTA® from this export.
Test: Instrument an explicit opt-in handoff after a completed styling task and link it, with consent, to verified signup, activation, four week retention, and a real pricing choice.
Evidence ladder for the next release
Prove the core job
Ask a real visitor to pick an outfit for a real event from clothes they own. Record a completed choice and later wear.
Identify the missing artifact
Compare immediate advice, a 2D look, and an actual product option only where requested. Measure completion and confidence.
Test the larger bets separately
Virtual closet, social feedback, AR, and hardware each need exposure, adoption, and an incremental benefit over simpler alternatives.
Method: read visitor turns and surrounding DOROTA® replies, then separate spontaneous requests, prompted answers, and feature narration. Dates identify illustrative sessions, not unique individuals. Status is qualitative and does not count how many independent customers validated a claim. No raw transcripts, names, IP addresses, or credentials are displayed.
ALPHA TEST | PAID AD CAMPAIGN
What the paid test produced
“Emotionally Intelligent Style” · google / cpc · Google Analytics export covers Jan 1, 2025 – Sep 27, 2026.
SEPTEMBER 6–8, 2026
A short alpha paid-ad experiment with $9.47 USD in reported spend.
Founder-confirmed ad run: Sep 6–8, 2026. The GA4 campaign exports cover Jan 2025 – Sep 2026. Google's AI daily summary places campaign sessions on Sep 6–8, 2026, but its daily rows add to 868 versus 869 in the export. A raw campaign-by-date CSV is needed to verify the daily split.
GA4 reports 9.471173 in cost, displayed here to the nearest cent. USD confirmed by Sidney.
The first-user campaign filter shows 872 new visitors within Cross-network, or 97.8% of the 892 Cross-network new visitors across all campaigns. A separate Cross-network export confirms those 892 were reported in the Sep 6–7, 2026 window. The named campaign has no daily acquisition table in the supplied files. Its filtered report also shows 852 Total users, fewer than 872 New users; the reason remains unverified. Separately, the events report shows 853 Total users on the campaign-filtered page_view row; it does not report 853 Active users.
From ad delivery to recorded action
Select a stage for its measures and definitions.
The test ad was served 8,235 times
Impressions and clicks come from the GA4 advertising export. An impression or click is not a distinct person or a website session.
What happened after a visit
Event counts can repeat across pages or visits. These rows do not form a measured signup funnel.
GA4's enhanced-measurement scroll commonly fires at 90% page depth, and form_start records an initial form interaction. A form start is not a form submission. The exported event name is ads_conversion_Contact_Us_1; its configuration and relationship to the waitlist have not been verified.
Campaign sessions alongside other traffic
Same Jan 2025 – Sep 2026 acquisition export. Other traffic includes direct, organic, referral, and uncategorized sessions.
| Traffic segment | Sessions | Engaged sessions | Engagement rate | Events | Key events |
|---|---|---|---|---|---|
| Named paid campaign | 869 | 406 | 46.7% | 4,396 | 4 |
| All other session rows | 2,476 | 922 | 37.2% | 10,709 | 2 |
| Report total | 3,345 | 1,328 | 39.7% | 15,105 | 6 |
Other session rows are a mixed comparison group, not an untreated control. Differences in engagement do not prove the ad caused better visits.
Four ads_conversion_Contact_Us_1 events occurred across two tracked visitors and two sessions. There is no evidence that this event represents a confirmed waitlist signup.
The traffic and world map elsewhere use unfiltered GA4 exports. Subtracting 869 sessions would not produce an ad-free count of distinct visitors or a corrected country map.
Sidney confirms the experiment ran Sep 6–8, 2026. Google's AI summary lists Sep 6, 2026: 574; Sep 7, 2026: 291; Sep 8, 2026: 3 campaign sessions. Those sum to 868, one below the campaign's 869-session export. Its engaged-session rows sum to 405 versus 406 in the export. A raw campaign-by-date CSV is needed to explain the one-session difference and verify daily results.
Sources: GA4 “Traffic acquisition: Session campaign,” “Key event performance,” “Events Including Campaign Data,” and “User acquisition With Campaign Data,” Jan 1, 2025 – Sep 27, 2026, plus the Cross-network user-acquisition export filtered to Sep 6–7, 2026. The report window is wider than the website map's Aug 2025 start. Ad cost, impressions, and clicks come from the advertising report; session measures come from traffic acquisition; event-name and people counts come from the campaign-filtered events report. Currency: USD, confirmed by Sidney. Cost per key event is not a verified cost per signup.
06 / PLANNING
Growth and focus
Explore the 2026 year-end outlook, or review what the selected historical period can show.
GA4 traffic and DOROTA® conversation signals are available. No dated signup series is available.
13 weeks approximates Sep 28 – Dec 31, 2026. The starting count remains the last reported Sep 28, 2026 figure. The default 5.25% rate is an editable planning assumption, not measured signup conversion.
07 / WHAT IF
Waitlist target calculator
Change the visitor and conversion assumptions to see the effect on the target.
There is no confirmed waitlist balance for this selected period. The calculator below always starts with the latest confirmed 110 members and models future visitors, regardless of the historical view above.
Planning math starts with the last confirmed 110 members and rounds projected signups to the nearest whole person. The 5.25% default is an editable assumption inherited from an earlier estimate, not a measured rate.
SCENARIO LAB · WHAT WOULD IT TAKE?
Find the path to the target
Each tile projects the total waitlist from 110 members at a chosen visitor count and assumed signup rate. Select a tile to load it into the calculator.
These are deterministic scenarios, not measured conversion rates or statistical confidence intervals. The 5.25% default remains editable and unverified.
Compare your scenarios
Save the current calculator assumptions in this browser. Saved views stay on this device.
08 / METHODS & OPERATIONSTranscript quality and measurement notesOpen the technical and operational observations behind the product read.DETAILS ↓
The first-turn and waitlist counts below follow the selected year. Other examples and counts describe the full export.
The first visitor turn is the bottleneck
102 of 220 sessions have no recorded visitor turn. Their median reported duration is 9 seconds, versus 132 seconds for sessions with a visitor turn. This may reflect testing, audio setup, or a weak opening.
Specific styling can carry the conversation
In longer exchanges, people describe occasion, weather, comfort, identity, and pieces they already own. DOROTA® can weave these details into useful suggestions. Some direct requests face several questions before advice arrives.
Fixed intake rules can miss the moment
In 42 of 118 two-way sessions, DOROTA® asks for a name or pronouns within her first three replies. In examples involving distress or audio trouble, that question arrives before addressing the immediate need.
Sessions are a mixed sample
The export spans 23 system-prompt versions. July 28, 2026 accounts for 38 of July 2026’s 47 sessions, and several transcripts contain apparent demonstrations or tests. Month-to-month volume is not a clean acquisition trend.
Product answers need a current source
Ten sessions mention a “Winter 2025” launch, including three in 2026. A September 2026 voice transcript renders MIRROR | MIRROR® as “Miramere,” and DOROTA® initially treats it as an unknown product.
Interest is visible, attribution is missing
24 of 118 two-way sessions mention the waitlist in DOROTA®’s replies, including 5 of 11 in September 2026. The export does not show whether anyone clicked or signed up afterward.
Transcript counts use DOROTA® sessions only. A two-way session contains at least one visitor speech turn. Examples are qualitative; they do not establish how many unique people experienced each issue or what caused it. No full transcripts or personal details are published here.
| HYPOTHESIS | WHY TEST IT | SMALL EXPERIMENT |
|---|---|---|
| Answer first, personalize second | Direct styling questions and audio checks sometimes receive an intake question instead of an answer. | Compare the current opening with an intent-aware version. Measure first reply completion, time to useful advice, and satisfaction. |
| Check the audio path | 102 sessions have no visitor turn, but the export cannot separate abandoned loads from mic or playback problems. | Log permission, audio readiness, first heard reply, first visitor turn, and errors. Segment internal demos from external traffic. |
| Make the waitlist handoff visible | Transcript mentions do not reveal clickthrough or signups. | Show a contextual on-page button after a helpful exchange. Connect session, button click, and confirmed signup with privacy-aware event IDs. |
| Version facts and safety behavior | Outdated launch claims, brand recognition errors, and awkward responses to distress appear in examples. | Use a maintained facts source and a focused evaluation set covering brand names, capability limits, corrections, and distress. |