The speed of the loop from a comment to a feature is the moat, not the technology

What is defensible is not the technology but the data, the relationships, the distribution, or the speed at which you ship. The loop (a user comments, an article is written, a feature ships, the founder uses it) is what is hard to copy: a reading list made for one person went from brief to live in 81 minutes, a link to a persona in 17 hours. Usage is also what gives a product its direction when agents can build in any direction.

Decided by. Nobody yet: a candidate for Dinis to read, comment on and decide (keep, rewrite, merge, cut, article first, later, not doing it).

Note. The times are from the git logs of sgit.ai and the newsroom, as the article says. a-company-in-the-review already says 'what is defensible is the record and the loop' for one company; this is the general claim for the chapter.

Where it comes from

I miss it, so it is working The loop is the moat; Direction is the scarce part (newsroom)
For a startup, the most important question is whether they miss it Pillar three: 'The technology is not the moat' (newsroom)

What it answers in the 2018 book

Feedback loops answered outline, Concepts

Where it goes

Chapter Ship it, and see if they miss it, part Start the company (drafting); topic Be a founder (or a one-person service).

Other ideas proposed for the same chapter: Ship it, give it away briefly, take it away, and ask whether they miss it, The miss-it test applies to the builders: if you can change it and still do not use it, something is missing, SG/Send: first commit on 8 February, live on 13 February, Stripe on 1 March, ten paying customers on 2 March, a feature request shipped in 90 minutes, The technology worked and the use case did not: 'users buy credits, test once, and don't come back'.

Node idea:the-loop-is-the-moat in graph.json; see it in the graph. Source: admin/content/graph/ideas.json.