I had the domain. I had the name. The obvious next move was to build a real website.

So I built almost nothing.

Check it out: mee.contact

What “bare minimum” actually means

Right now, mee.contact is a homepage and a journal. That’s it.

The homepage answers two questions and stops:

• Why: One line on what I’m building and why the hand-off should be automatic instead of typed.

• Where: A way to follow along if you want the story, not just the eventual app.

No feature tour. No waitlist gimmicks. No pricing table for a product that isn’t shipped. If a visitor can’t tell what this is and how to follow it in ten seconds, the page has failed — no amount of polish fixes that.

Why “Where” points at Substack, not the site

The honest answer is speed and habit, not ideology.

Writing is faster for me right now than producing video. I tried video in the past and failed.

I can turn a rough voice memo like this one into a real post the same day. Video means scripting, recording, editing — a production step I don’t have room for yet, on top of building the app.

Substack also solves distribution for free. Every post goes out as an email the moment I hit publish — no separate list, no separate tool, no “please subscribe to my website” friction I’d have to build myself. If I only wrote on mee.contact, I’d still have to point people back to the site every single time just to get the email out. Substack already does that job.

And there’s a selfish reason too: writing in public, on a platform built for writing, is making me a better writer. That’s worth something on its own, separate from the app.

Why the journal section exists anyway

The site’s /journal is the same content I publish on Substack — same titles, same words. Not a separate blog with a different voice. A deliberate duplicate.

Why bother? SEO. I want mee.contact to show up when someone searches for this journey, not only Substack. Is duplicating content “correct” by the textbook? Maybe not. But for a brand-new domain with almost no pages, having the writing live on the site helps me show up at all.

I still publish first on Substack. That’s the main goal — writing habit, email distribution, build-in-public. The website copy is for discovery. Every post still links back to Substack so readers can follow along there if they want.

And honestly: without AI helping automate a lot of this plumbing, I wouldn’t think twice about it. Maintaining two surfaces by hand would kill time I should spend on actually building the product. The automation is what makes the SEO mirror cheap enough to keep.

What’s deliberately not here yet

I’m setting up the pieces in an order on purpose: idea → hosting → connecting the pieces → then just building.

Not shipped yet, and I’m saying so out loud so I don’t sneak scope in later:

• Real hosted profile pages at /p/{id} — the actual product surface NFC and QR will point to.

• Anything resembling a feature list, screenshots, or “get early access” funnel.

Those are real work, and they deserve their own post when they’re real — not a placeholder box on a homepage that quietly never gets filled in.

Why this belongs in a build journal

The tempting move was to spend a week making the website “look done” before writing another line of app code. I don’t think that week would have made the app better. It would have made me feel more done without being more done.

So: name, why, where — live, today, at mee.contact. Come check it out. Everything else waits until it’s earned its place on the page.

Recap

I’m Luciano Huapaya. I’m building mee.contact in public — an app to automate the contact exchange so you can stay present when you meet people.

• Personas for what you share.

• Connections for who you meet.

• Events for where you met them.

Not on the App Store yet. This is the journal of getting there.