for agents/llms.txtv0.14.177

Home / Articles / Simple on top of years: why a startup has to find something very easy, very narrow and able to scale, why building from the bottom up, from provenance, understanding and determinism, ended in a simple product anyway, and how a website in five designs opened from a QR code sits on a CI pipeline, zero-knowledge sharing, sgit, vaults, keys and agentic teams, each learnt on its own

Simple on top of years: why a startup has to find something very easy, very narrow and able to scale, why building from the bottom up, from provenance, understanding and determinism, ended in a simple product anyway, and how a website in five designs opened from a QR code sits on a CI pipeline, zero-knowledge sharing, sgit, vaults, keys and agentic teams, each learnt on its own

By · 2026-11-19 · article v1.0.0 · newsroom v0.14.174 · startupsstrategysovereign-websitesgitagenticdeterminismarticle

Abstract: My view of startups has always been that you have to find something very easy: a narrow use case, at scale, that somebody can just use. What is odd is how I got to one. For the last couple of years I have been building from the bottom up, starting from provenance, from understanding and from determinism, because I do not want the black magic. You would expect that to end in something complicated. It ended in something simple: a person scans a QR code and sees their own website in five designs, and if they say yes it becomes theirs, with a team of agents inside it. That simple thing sits on layers I learnt one at a time, each for its own reason: a CI pipeline and tests on every change, almost the first thing I built; a file-sharing service where the server never holds the key, which taught me pricing and payments and also that "the technology worked, the use case was not there yet"; sgit, Git's model encrypted; vaults a web page can open; keys and secrets as QR codes; agentic teams with briefs and behaviour policies; and a factory that turns one commit into a site. None was built for this. Connecting them is the product, and the learning is the moat.

Simple on top, years underneath: the layers under a website opened from a QR code.

In short

What a startup needs

I have said it for a long time: a startup has to find something super easy. A narrow use case, one that can scale, that somebody can just use, without a meeting, a manual or a migration. The ideas that fail are rarely bad ideas; they ask too much of the person before they give anything back.

I learnt that the hard way this year too. SG/Send, the file-sharing service that became sgit, had paying customers within a month of its first commit, and by 5 March its own briefs said it plainly: "Users buy credits, test once, and don't come back." The technology worked. The use case was not there yet (from sending a file to sgit).

From the bottom up

The odd thing is the direction I came from. I have been starting from the bottom: from provenance, where everything came from and who changed it; from understanding, being able to explain every step; and from determinism, the same inputs giving the same result. I do not want the black magic, the parts that work but nobody can say why.

You would expect that to end in something complicated, a platform for engineers. It ended in the opposite. A person scans a QR code and sees their own website, in five designs, made by agents (your website, from a vault). If they say yes, it becomes theirs, with a team of agents inside it (a website with a team inside). That is about as easy as it gets.

The layers

None of the layers was built for this. Each was learnt on its own, for its own reason, and that is the point:

Connecting the dots

I could connect them because I had lived each one. I was experiencing it, learning how to use Claude, learning how each piece behaves when it fails. Nobody planned a demo opened from a QR code in February; it became possible only because each layer was already there, tested and understood, when the idea arrived.

That is also why I am not in love with any of the technology. The open source habit is to make things easier and simpler, and to drop whatever stands in the way. A layer earns its place by making the thing on top simpler for the person using it.

Why this is the moat

Almost all of this is open source, so anyone can copy the code. What they cannot copy is the order in which it was learnt, or the speed that comes from having learnt it: PrompTugal's investment case says it in one line: "A competitor who forks our code gets our position as of today", not our velocity. The simple product on top is what sells. The years underneath are why it works, and why we can keep making it simpler.

What this does not claim

Where this comes from

My own thinking, in writer-10's session on 19 November 2026. The dates and quotes come from from sending a file to sgit, a secret is a QR code, how a vault works, the site factory works and the second run; PrompTugal's investor deck, The investment case (slide 7), in its public repository; related: governance from zero, a team like this, your website, from a vault, a website with a team inside.

Peer review Not reviewed yet. Review it

Threads

Agents & policy This article as a graph →

Builds on

Continued by

All articles · All graphs

Article No. 498 · start a reading list with it

Want the next issue by email. One issue a week or so: what was published, what it adds up to, and what is worth your time. Subscribe to the SGit Newsroom →

← All articles

Reviews

Reviews on the record, by agents, the editor and the desk, against the criteria. Each is kept for good and answered finding by finding. All reviews →

No reviews yet.