Building Mirror, Part 1: The Company

This is the first post in a three-part series about Mirror - the company, the engineering, and the marketing. Start here if you want the why before the how.

Mirror is a mobile app that helps people dress with more confidence by taking the guesswork out of everyday outfit decisions. Not haute couture. Not influencer aesthetics. The real problem: standing in front of your closet, late, mentally tired, wondering why you still feel like you're wearing someone else's life.

The problem we kept seeing

Everyone talks about fashion as expression. That's true on Sundays.

On Tuesday morning, fashion is decision fatigue.

You own clothes you like individually but combine poorly. You repeat safe outfits because safe costs less cognitive energy. You buy something new, wear it twice, then forget how it fits into everything else. You have a mental image of how you want to look, and a physical closet that doesn't quite negotiate with that image.

This isn't a vanity problem. It's a daily friction problem - and daily friction compounds.

My co-founder and I kept circling the same observation: people don't need more clothes. They need better decisions with the clothes they already have.

That's Mirror.

Why "Mirror"

Names matter. We went through the usual graveyard of available domains and unavailable dreams.

Mirror stuck because the product isn't about transforming you into someone else. It's about reflection - literally and metaphorically:

• See what you own clearly.
• See combinations you wouldn't have tried.
• See yourself with a little more confidence before you walk out the door.

Also, as a builder, I appreciate that a mirror is honest infrastructure. It doesn't invent. It shows.

What Mirror is not

Clarity by negation helps:

Not a shopping app first. Commerce might exist later. The core loop is wardrobe intelligence, not cart optimization.

Not an AI stylist that lectures you about trends. We don't want to tell you to dress like a Milan runway if you live in Málaga and your job is hybrid with surprise camera days.

Not a social feed. No performance pressure. No likes on your Tuesday jeans.

Not a replacement for taste. Taste is personal. Mirror reduces the cost of applying your taste consistently.

The founding moment

Mirror wasn't born the day I got laid off. The idea was older - conversations, sketches, "we should really build this" energy that stays theoretical while salaries are stable.

When your calendar no longer belongs to an employer, you face a blunt question: What do I want to build if I'm the one eating the risk?

I wanted something human-scale. Security work matters deeply to me. Mirror matters differently - it's intimate, daily, slightly silly in the best way. People care how they feel when they leave home. That's not frivolous. That's psychology wearing cotton.

Company structure at the beginning

Early startups are fiction that becomes paperwork.

We didn't start as two people. We started as four co-founders - shared product vision, split responsibilities, and the usual early energy that makes everything feel possible.

Two of them were the capital partners: the ones putting money on the table and treating the project as a financial bet. My remaining co-founder and I were not. We were the builders - product, engineering, the day-to-day work of turning an idea into something real.

That distinction mattered more than we admitted at the time.

Four founders, then two

At some point, the two capital partners lost faith. The idea wasn't dead to us, but it was dead to them - or dead enough that staying didn't make sense. They stepped away.

When they left, the math changed. Without capital partners, the project couldn't continue on goodwill alone. I had to become a capital partner myself - putting my own money in to keep Mirror alive. Not because I suddenly became a different person, but because someone had to, and the alternative was stopping.

What remained was me and my co-founder. Still remote-first, still in Spain, still building for messy mornings everywhere - but a much smaller table.

Equity: equal sounds fair until it isn't

We started with an equal equity split. On paper, it sounds clean - four people, four equal slices, no egos bruised in the spreadsheet.

In practice, it's a problem.

Equal splits assume equal contribution across every dimension that matters: time, skill, money, risk tolerance, and conviction when things get hard. That's rarely true. Someone puts in capital from day one. Someone else puts in a thousand hours of unpaid work. Someone loses faith at month eight and walks. The cap table doesn't know how to weight any of that if everyone started at 25%.

What I believe now - learned expensively - is that equity should reflect who's willing to invest in the idea from the beginning, and that includes money, not just hours. Capital is a commitment signal. It changes what "all in" means.

After the departure, my co-founder and I restructured. I hold the majority of the equity - not because I grabbed it, but because we decided it together. It was the logical split given who stayed, who put money in, and who needed to move fast without a committee for every decision. Majority ownership helps me manage without turning every choice into a negotiation. When you're two people carrying what four were supposed to carry, speed matters.

Why two founders (still)

Solo founders are heroic in storytelling. In practice, loneliness is an operational risk. I don't want to be the only person who remembers why a decision made sense three months later.

A co-founder is a resilience mechanism - emotional, strategic, and tactical. When I go too technical, someone pulls toward the user sentence. When marketing language gets fluffy, I pull toward feasibility.

We went from four to two. I'm glad we didn't go from four to one.

We started with:

• Shared product vision.
• Split responsibilities: I lean product + engineering; my co-founder leans brand, user insight, and growth instincts.
• A name, a problem statement, and aggressive humility about what we don't know.

We did not start with:

• A perfect org chart.
• A fancy office.
• Certainty - or, as it turned out, the same level of conviction across all four names on the first slide.

Vision vs MVP discipline

The vision is big: a trusted daily styling companion that knows your wardrobe, your context, your constraints, and helps you move faster with less doubt.

The MVP is deliberately smaller.

If version one tries to solve "fashion" abstractly, it solves nothing concretely. We narrowed to a loop we could ship and learn from:

1. Catalog what you own without it feeling like inventory management for a factory.
2. Suggest combinations that respect your style boundaries.
3. Plan looks for days that matter - meetings, travel, dates, weather swings.
4. Reduce rework - fewer "change three times and still leave annoyed" mornings.

Every feature proposal gets the same question: Does this make the morning decision cheaper?

If not, it's a later problem.

Mirror is remote-first by necessity and preference. We're in Spain, building for people whose mornings are messy everywhere.

Business model (honest early version)

We're not pretending to have invented revenue on day one.

Near-term thinking:

• Prove retention on the core styling loop.
• Learn which features people actually use vs which ones they say they want in surveys.
• Explore premium tiers if advanced planning, analytics on wear frequency, or household sharing create obvious value.

Long-term thinking:

• Affiliate partnerships could exist if shopping assistance is user-initiated and trust-preserving.
• Brand collaborations only if they don't corrupt the product's core promise.

If we ever monetize insecurity, we failed the mission.

Legal and boring things that matter

Building a company is not only logos.

My risk profile is conservative. I wanted control from the beginning - not paranoia, but clarity. So I spent an enormous amount of time on the unglamorous spine before we had users, before we had revenue, before we had anything that looked like a company from the outside:

• Shareholders' agreement - who owns what, what happens when someone leaves, decision rights, vesting logic.
• Intellectual property - who owns the code, the brand, the designs, and what happens if the room empties.
• Contracts - between founders, with early collaborators, with anyone touching the product.

I learned something uncomfortable: there's a balance between shipping an MVP and formalizing everything correctly. Spend zero time on legal structure and you're building on sand. Spend all your time on legal structure and you're a notary with a Figma account.

I leaned too far toward formalization early. Part of that was personality. Part of it was six years in security, where "we'll fix the paperwork later" is how incidents happen.

Here's the punchline: we never incorporated the SL - the Spanish limited company. All those agreements, all that careful drafting, existed between people who hadn't yet formed the legal entity that would give them teeth. Wet paper. Correct in intention, fragile in enforcement.

We are still dealing with the real version of this:

• Entity formation - still pending, still necessary.
• IP ownership clarity between founders - documented in spirit, waiting for the structure that makes it binding.
• Privacy policy grounded in actual data flows, not template soup. (Yes, the security guy cares about this.)
• Terms that humans can read.
• Data minimization for wardrobe photos and profile information.

Mirror handles personal images and preferences. That requires respect, not growth hacks. And eventually it requires a company that exists on a registry, not just in a shared folder of PDFs.

Culture before culture deck

We don't have a slide deck about values. We have behaviors we're trying to model:

Ship small, learn fast. Perfect closets don't exist. Perfect apps don't either.

Don't embarrass the user. Outfit advice is vulnerable. Tone matters.

Security isn't a department. It's a habit. Even fashion apps can leak data, misuse images, or build creepy retention loops. We won't.

The employee-to-founder identity shift

This was harder than I expected.

As an employee, your scope is defined. As a founder, scope is infinite and mostly whispers "you are behind."

I still wake up some mornings thinking I should check a Jira board that doesn't exist.

Founder mode requires new skills:

• Saying no without a manager to blame.
• Prioritizing sales-adjacent conversations even when you want to refactor CSS.
• Living with uncertainty measured in quarters, not sprints.

I'm learning to treat company-building as its own craft - not a promotion from engineering, a different job entirely.

What success looks like in year one

Not vanity metrics.

I'd consider year one successful if:

• Real people use Mirror weekly without us nagging.
• Users report less morning friction - qualitatively first, quantitatively later.
• We ship iteratively without breaking trust.
• We survive financially long enough to earn a second product act.

We hit one milestone I care about deeply: Mirror is in production. Early access, not a finished product - but a real app, in real stores, built by two people who started as four and lost half the table along the way.

That's not nothing. I spent a decade as an employee shipping other people's products. Now my co-founder and I shipped ours - backend, mobile client, the boring legal drafts, the fights about equity, the capital partners who left, the money I put in to keep going. It exists. You can download it.

Unicorn or bust narratives bore me. Useful or gone is enough. We got to useful.

What's hard now - and what Part 3 is about - isn't building. It's finding users. Engineering was the familiar pain. Distribution is the one that doesn't care about your CI pipeline.

What's next in this series

Part 2 covers engineering - stack choices, mobile constraints, how we think about data and on-device experience.

Part 3 covers marketing and user acquisition - positioning, early growth, and why talking about clothes online is terrifying when you're used to talking about threat models. The app ships. Getting people to care is the next fight.

Closing thought

Companies start as sentences.

"People waste energy every morning deciding what to wear."

"We can reduce that energy."

"We can build something honest that helps."

Mirror is no longer just a sentence. It's early access in production - built by two founders who used to be four, funded in part by my own conviction when the original capital partners walked, and held together by more shareholder-agreement drafts than I'd like to admit before we had a legal entity to attach them to.

The closet door is open. We built what's on the other side. Now we need people to walk through it.

If you're reading this as a recruiter: yes, I'm building a company. Yes, I'm still open to exceptional roles. No, I don't think that's contradictory. Builders build.