The castle is the moat

Entry 21-2 ended with “now comes the hard part: users”, and the Reddit launch delivered the first lesson about them. Three subreddits tried: the Google Keep one flopped, its people want to discuss Keep’s features, not replacements ▸ 7:42; a three-minute demo got six likes, so it was re-cut at double speed to ninety seconds; r/SideProject responded warmly, with the caveat logged for honesty: that community is so relentlessly positive it produces zero negative feedback ▸ 9:14. Net: 20 to 25 registrations ▸ 9:51.

The teaching came from one comment: import my notes from Google Keep, in bulk. And the analysis behind why that unglamorous feature matters names something bigger: what stops people from changing notes apps is that they already have their whole little castle built in the old one ▸ 11:01. Switching means two hours of manual copying, or living split across two apps indefinitely. Most people choose neither and stay.

nadie abandona el castillo, ni por un castillo mejor →

Which reframes the whole competitive question. The incumbent’s moat isn’t its features, it’s the user’s own accumulated data; the user is self-imprisoned by their history. And the attacker’s sharpest weapon is therefore not a better feature but a door in the wall: a migration tool that moves the castle intact. Called on camera “una feature fuerte, of the kind where if you build it, you get many more conversions” ▸ 12:06.

The pattern generalizes to everything this company will build: for any product replacing an entrenched tool, ask where the user’s castle lives and how it travels. Picky’s photo-to-menu importer, decided days later, is the same weapon aimed at paper menus. For Zenota the feature went to standby, other projects called ▸ 12:55, but the principle got extracted and it stays…