Building Outkitted, Week 6: One Closet, Three Surfaces

Six weeks in, and the thing I keep coming back to is a sentence I wrote on a sticky note before I wrote a single line of anything: one closet, every pursuit.

I want to explain what that actually means now that it’s real, or at least real enough to click around. Because for a while it was just a nice phrase. This week it started behaving like a plan.

Three surfaces, one identity

Outkitted isn’t a blog with an app bolted on, and it isn’t an app with a blog for SEO. It’s three surfaces that share one spine.

The App — your closet and your loadouts. Every piece of gear you own in one place, and the specific kits you build from it: a day-hike loadout, an overnight loadout, a “throw it in the car for the coast” loadout.
The Field Notes — this. Honest notes on building the thing, plus what I’m learning as I actually use it.
Gear guides — the reviewed, opinionated writeups. Not a spec dump. What I’d actually carry and why.

The reason they live together is that they’re the same idea seen from three angles. Your closet is the private version. A loadout is the sharable version. A gear guide is the researched version. Same gear, same weights, same honesty — just pointed at different jobs.

I’ve started calling the way they connect the flywheel, which sounds more grandiose than it is. It just means each surface should feed the next. A gear guide should let you drop an item straight into the app. A loadout you’ve built should be one tap from the guide that reviews the same tent. The journal points at both. Nothing sits on an island.

Here’s the decision I’m most sure about, and it’s the one most people would tell me is wrong.

There is no signup wall. You can open the app right now and start building your closet without making an account, without an email, without anything. Your gear data lives in your own browser — local-first. I never see it unless you decide, someday, to send it somewhere.

I keep getting the reflex to add a wall, because every playbook says to. Capture the email. Gate the value. Build the list. And every time I get close, I remember what it feels like to land on a tool that’s genuinely useful and be asked to hand over an identity before I’ve been shown a single reason to trust it.

Adoption beats friction. If the first thing I do is ask you to sign up, I’ve told you the account matters more than the closet. It doesn’t.

“No account needed” isn’t a limitation I’m apologizing for. It’s a feature. It means you can try Outkitted in the time it takes to read this sentence, and if it’s not for you, you close the tab and nothing lingers. That’s the deal I’d want, so that’s the deal I’m building.

The honest tradeoff: local-first means I can’t email you, can’t see usage, can’t do the growth-hacking things. I’m choosing to be a little blind in exchange for being a lot more trustworthy. I think that’s the right trade for a tool about the stuff you carry into the backcountry.

Building this without being an engineer

I should be straight about something: I’m not a developer. I’ve never shipped software before this. Six weeks ago I could edit a spreadsheet and that was roughly the ceiling.

I’m building Outkitted with a lot of AI assistance, and I want to describe that honestly, because the way it gets talked about online is usually either “AI builds your whole startup while you sleep” or “AI writes garbage and you’ll regret it.” Neither has been my experience.

What was surprisingly easy: getting from nothing to a thing on screen. The first working version of the closet — add an item, give it a weight, see it in a list — came together far faster than I expected. For someone who’d always assumed software was a locked room, watching an idea become clickable in an afternoon was genuinely moving. I’m not going to pretend it wasn’t.

What was humbling: everything after “it works on my screen.” The gap between a demo and a thing that doesn’t quietly lose your data is enormous, and it’s exactly the gap I didn’t know existed. I’ve learned what “state” means the hard way. I’ve reintroduced the same bug twice because I didn’t understand why the first fix worked. AI is a spectacular tutor and a fast pair of hands, but it can’t want the product for you, and it can’t tell you which of two reasonable choices is right for the thing you’re actually trying to make. That part is still me, sitting there, deciding.

The useful reframe: I’m not “coding.” I’m making a hundred small product decisions a day and using AI to turn them into working software. The decisions are the job. The typing is the easy part now, which is exactly backwards from what I assumed.

The one rule I keep

Every week I have more ideas than time, so I need a filter, and this is it: don’t ship anything that doesn’t feed the loop.

A feature that makes the app prettier but doesn’t connect a guide to a closet, or a closet to a loadout, gets parked. It might be a good idea. It’s just not this idea yet.

The other half of the rule is about honesty over features. I would rather show you one true number than five fuzzy ones. Right now that number is weight plus cost. When you build a loadout, you see what it weighs and what it cost, totaled, no rounding-in-my-favor. That single honest pair does more for a real decision than another shelf of features would. If I can only get one thing right, it’s that the numbers don’t lie to you.

What’s next

The next phase — I’ve been calling it Phase B — is optional accounts. The keyword is optional. The local-first closet stays exactly as it is. But at some point you’ll be able to, if you want, sync your gear across devices and share a loadout with a clean link. Send someone “here’s my exact overnight kit” and have it just open.

Here’s the part I want to be disciplined about: I’m not building sharing until someone asks “how do I share this?” out loud. Not because I don’t believe in it — I do — but because the wall-less, account-less version has to earn the feature by people wanting to pass it around. Build the demand first, then build the door. If nobody asks, then sharing was my idea, not yours, and I should listen to that too.

So that’s week six. Three surfaces, one closet, no wall, and a rule I’m trying hard not to break.

If any of this sounds like a tool you’d actually use, go build a loadout in the app, poke around the gear guides or the rest of the field notes, and then tell me where it falls short. I mean that literally — the feedback is what tells me what to build next, and right now yours would be some of the first I get.