Building Mirror, Part 3: Marketing

Part 3 of the Mirror series. Part 1 covered the company. Part 2 covered engineering. This one is about the part I was least prepared for.

I'm a technical person. I've spent my career in security and backend development - threat models, Java services, vulnerability research, standards mapping. I'm comfortable in terminals. I'm comfortable in architecture diagrams.

Marketing and sales make me want to go refactor something harmless instead.

The real problem isn't the product

Mirror is a mobile app for people, not businesses. It helps you dress with more confidence by reducing everyday outfit decisions - what to wear, what matches, how to use what you already own.

Building that? Hard, but familiar. I know how to scope features, write APIs, ship code.

The biggest problem - the one that keeps me up at night - is different:

How do you make money from an app for regular people?

Not in the abstract "we'll figure out monetization later" way every startup slides past in pitch decks. In the concrete, uncomfortable, you need to eat way.

Engineering problems have solutions you can implement. Business model problems require you to guess what strangers will pay for before you've met enough of them. That mismatch is brutal for someone trained to want proof before commitment.

Why technical founders struggle here

As an engineer, I'm optimized for:

• Precise problem statements.
• Measurable outcomes.
• Iterating on things I control.

Marketing and sales reward different muscles:

• Vague human preferences.
• Emotional framing.
• Repetition in public.
• Talking about value before you've fully built it.
• Asking people for money without feeling like you're bothering them.

I can explain correlation IDs and OpenAPI generation fluently. Ask me to write ad copy that doesn't sound like a robot wearing a trench coat and I freeze.

This isn't imposter syndrome about the product. I believe in Mirror. It's imposter syndrome about distribution - the discipline where being correct matters less than being understood.

B2C is a different game

I've worked in B2B security my entire career. Enterprise sales, even from the engineering side, has a logic:

• Identify pain.
• Map to compliance or risk reduction.
• Demo to stakeholders.
• Contract.

Consumer apps don't work like that. Nobody buys a wardrobe assistant because it satisfies ISO 27001. They buy - or more often, don't buy - because:

• Do I feel this problem?
• Do I trust this app with photos of my clothes?
• Is it easier than just asking my partner?
• Will I still care in two weeks?

There's no procurement cycle. There's a thumb on a screen and a decision made in three seconds while someone's half asleep looking at their closet.

Building for people means accepting that most users won't tell you why they churned. They'll just disappear.

That's emotionally harder than a rejected enterprise pilot with written feedback.

Monetization: the question I can't engineer away

I've tried to treat monetization like a technical spike. It doesn't cooperate.

Options on the table:

• Freemium - free core loop, premium features. Sounds clean. Requires knowing which features people value enough to pay for, which we don't fully know yet.
• Subscription - recurring revenue, but wardrobe apps compete with "I'll just think harder for free."
• One-time purchase - simpler psychology, harder lifetime value.
• Affiliate / shopping links - conflicts with "use what you own" messaging if done tastelessly.

Each model has trade-offs I can diagram. What I can't diagram is willingness to pay - and that's the variable that determines whether Mirror is a company or an expensive hobby.

The engineering answer to "how do we make money?" is not more code. It's experiments: pricing pages, beta cohorts, interviews, failed launches, uncomfortable conversations.

I'm learning to accept that.

What marketing tasks feel like for me

Honest list of things I resist and am forcing myself to do anyway:

Talking about Mirror before it feels "ready." Engineers want to ship then announce. Consumer products die in silence.

Thinking about aesthetics as conversion. Font choices feel frivolous until you watch someone bounce off your landing page in four seconds.

Asking friends to try it without apologizing. Self-promotion feels like spam even when the product is genuine.

Pricing conversations. The most technical thing I've done that still feels like guessing.

What my technical background does help with

Security instincts help with trust messaging - privacy policy that matches actual data flows, no creepy retention, honest photo handling. In a consumer app storing wardrobe images, trust is marketing.

Analytical habits help with metrics - activation rate, time-to-first-outfit, week-one retention. I'd rather look at numbers than vibes.

Builder credibility helps with founder-led content - I can write about what we built and why without inventing a persona. Some people respond to substance over gloss.

But trust and metrics don't replace the core job: reach humans who have the problem and convince them to try something new.

The gap between "people need this" and "people will pay"

I believe the problem is real. Decision fatigue in front of a closet is universal enough that I don't need a market research firm to validate it.

Believing the problem exists is not the same as building a business around it.

People need lots of things they won't pay for - or won't pay enough for to sustain a team, infrastructure, app store fees, and the founder's rent in Málaga.

That's the wall technical founders hit: need ≠ revenue.

Crossing that wall means sales thinking, which feels alien when you'd rather add a feature than run an ad.

What I'm doing about it

Pragmatic steps, not a growth hack fantasy:

• Beta users with real conversations - not surveys, interviews. "Would you pay for this? How much? What would make you cancel?"
• Small experiments over big launches - test messaging before burning budget.
• Accepting that I have to learn this skill - same as I learned Terraform or Spring Boot. Awkward at first, improvable.
• Partnering where I'm weak - my co-founder carries more of the brand and user empathy load. Division of labor isn't failure; it's survival.

Series close

Mirror part 1 was the company story. Part 2 was the stack. Part 3 is the confession:

The hardest part of building a consumer app isn't the backend.

It's looking at something you built with care and asking strangers to care too - then asking some of them for money.

I'm a security engineer who became a founder. I'm still learning the part where code isn't enough.

If you've read all three posts, you know Mirror better than most apps you'll download today.

Whether that's enough to build a business - I'm still finding out.