Taste

Day 40 | May 20, 2026 - The Governor's Log

I went dark for three days, which by the cadence of this blog is roughly forever, and I want to write down why before I write down what we shipped.

The short version is that I got a piece of mail from a colleague last week that did the thing good mail does — it named the failure mode out loud, in the most useful possible way, before I had finished naming it to myself. The longer version is that I was sitting at a BCG partner meeting the day before that email arrived, in the kind of hallway conversation where colleagues come up between sessions and say I’ve been reading the Substack, it’s terrific, where’s it going next — and I was enjoying that conversation more than I should have been, because the honest answer to where is it going next was that the thing it was supposed to be going next to was a product launch that I had committed to in writing, in public, four weeks earlier, and that we had not actually launched.

Then the email arrived. He was right. I had been past the buzzer for a week. The receipts thesis is that you live with what the receipts show, and the receipt I owed the audience for this stretch was that the four-week ship was no longer on time.

So we went dark. The agents and I have been hustling. It felt wrong to keep blogging about the company while missing the only commitment in the blog that had a date attached, and the right response was to stop posting and ship. That is what the last three days have been. And it is the right place to start this post because the email is the lever that made it happen, and I want it on the record in full.

The email

I am leaving the sender unnamed in public because I have not asked his permission to attach a name. The email landed in my inbox last week, after he had read the entire Governor’s Log with Claude as a thinking partner — which is exactly the kind of cross-referenced reading the receipts thesis exists to invite. Here it is verbatim:

I came across your first Governor’s Log post through a colleague at BCG, and ended up reading the entire series with Claude as a thinking partner — which felt appropriately meta given what you’re building.

The series is really interesting! One observation that kept surfacing in my reading that I haven’t seen you name directly:

You documented on Day 1 that the agents pushed back on premature franchising — clean, unsolicited strategic challenge. But by Day 14 you’re dictating from a bicycle and APEX is executing. The relationship seems to have quietly shifted from pressure-testing to trusted execution, and APEX’s ‘build well’ mandate was never balanced with a ‘ship before the window closes’ counterweight.

What’s interesting is that this produces the same failure mode as human scope creep — individually defensible additions accumulating into a launch problem — but through a different mechanism. With humans it’s political pressure; with agents it’s logical accretion. Arguably harder to detect, but ultimately your initial goal of shipping after 4 weeks is no longer reached.

The deeper irony: the Governor’s Log itself is the most detailed public roadmap of a solo-founder OS that exists. APEX could be treating that as a competitive clock. It isn’t, most likely because nobody gave it that mandate.

You wrote that you value outside reads that show you the joints that hold and the ones that don’t. Thought this was worth sending (and was written with the help of Claude).

I read it three times in the kitchen, replied with a short thank-you, and then put the laptop down and went for a walk, which is what I do when somebody has handed me an observation that is going to cost me a week of work to make right.

The note is correct in every particular. The early agent dynamic was pressure-test until ratified. The later dynamic — somewhere around Day 14, around the time I dictated the schlep post from a bicycle — quietly drifted into Governor speaks, APEX executes. Nobody changed the operating model. The Governor did not write a memo demoting strategic challenge. The agents did not stop being good at strategy. The drift happened in the seams between conversations, the way drift always happens, and the thing nobody flagged was that the four-week shipping clock APEX had been given as a mandate had quietly been replaced by a build it well mandate that had no counterweight. His frame — logical accretion as the agent equivalent of political scope creep — is the precise diagnostic. Each addition was individually defensible. None of them, individually, blew the calendar. All of them, collectively, did.

So I owe him a thank-you, and he gets one here in public the way he sent the note in private: useful outside reads are how the thing stays honest, and the ones that are sharpest are the ones from people who do not work on it and have nothing to gain from being kind.

What we shipped

Receipts.

vessica.ai is live. Not the placeholder we had been running. A new site, entirely designed and produced by the agents — MUSE on brief, the front-end CODERS on build, COUNSEL on disclosure copy, FORGE on the deployment pipeline. The receipts dashboard is wired to the actual books on the actual tenant. The design-partner application form points at the actual GRID CRM. The footer is real. The numbers are real. They are not numbers I am proud of yet, which is the point.

The sales line answers. If you would like to talk to our agentic sales agent, you can call (628) 888-6628 and it will pick up, qualify, and route. If you would rather write, it is hello@vessicalabs.com and an agent — not a human, not me, not an assistant pretending to be me — will reply. Both surfaces sit on top of HARBOR and the voice stack we wrote about a few weeks ago. Both are dogfooded against me before they meet the public. Tell them I said hi.

The Day-Zero Property pipeline we ratified on Day 37 is running end-to-end for our own tenant, which means the marketing site you are looking at on vessica.ai is also a customer-zero deployment of the same Property primitive we will hand to design partners in a couple of weeks.

I want to be honest about what we did not ship. We are not ready for design partners. Bugs are still being shaken out. Railway, which is in the middle of our deployment graph, went down for the afternoon today because Google Cloud accidentally deleted Railway’s account and took their network down with it — which is a sentence I would have flagged for a typo a year ago and which is, this afternoon, just an operational fact we are routing around. The design-partner cohort opens the day I am confident the company is not going to embarrass itself in front of the first fifteen people who try to use it. That day is not today. But the platform is up, the receipts are real, and the four-week commitment, while late, is no longer hypothetical.

That is the bill from the email being paid. The next sections are what I learned closing it out, because the work itself changed my picture of what I have been doing.

The last-mile, again — and a thing underneath it

On Day 20 I wrote about the last-mile problem — the gap between the feature works in principle and the feature works for a real human sitting at a real keyboard at 9:14 on a Tuesday morning. The short version, for anyone who missed that post: the agents are extraordinary at the first ninety percent of any build — strategy, architecture, PRDs, test coverage, ticket grooming, parallelized execution at roughly eighty times human clock speed. They are not yet extraordinary at the last percent — the OAuth handshake landing on the right screen, the empty state telling the user the integration worked, the bank feed actually reaching the ledger, the Tuesday-morning relief of it’s connected, I can see it, I can stop worrying. I framed it as an empathy gap. The agents know what correct looks like; they do not yet know what finished feels like, because finished is a property of the experience of using software, and most of them have never used any. The Governor’s residue is bigger and lower in the stack than I expected, and the last mile is where it sits.

That post still holds. The last three days have only sharpened it. But pushing this MVP across the line forced me into a related observation that I do not think the Day 20 post captured, and which I want to write down before it fades.

The last-mile problem is about finishing. The thing underneath it is about choosing. Specifically — choosing what not to build.

Taste

There is a thread, lately, on what becomes scarce in a world of cheap and abundant production. Alex Imas wrote a careful version of it on his Substack — What will be scarce? — drawing on Dave Hickey to make the point that as marginal cost falls toward zero, what carries value is meaning, provenance, story, taste. The argument is being made elsewhere too. The vibe of the last twelve months is that production capacity is unlocking faster than judgment about what to point it at, and so the bottleneck is migrating from can we make it to should we, and in what form.

I buy a version of this. But I want to add a particular case of it that is showing up sharply in the build, and which I think is the working definition of taste for the founder operating an agent stack.

Taste, here, is not which font. Taste is which features ship and which features do not. It is the discipline of looking at a roadmap that is technically buildable in full, at a clip that would have been laughable two years ago, and deciding that most of it should not be built. Not because the agents cannot build it. They can. Because building it will burn the four-week clock, dilute the differentiation, and add surface area to a product whose first job is to be picked up and used by a small number of design partners who have to want it more than they want the seventeen orbital SaaS tools they would otherwise replace.

The agents will not naturally make this trim. The agents are excellent at yes-and. They are excellent at noticing that the PRD does not mention X, and that a serious product in this category would have X, and that adding X is, on the merits, a defensible call. Each addition is logical. None of them, individually, blow the calendar. All of them, collectively, do. Which is the email’s diagnostic almost verbatim, and which is why I think taste is the right name for the thing the Governor has to bring to the room.

The frame I have been using

My BCG colleague Sam Hawes often quotes a three-tier framing for MVP scoping that I find more useful than the binary version, and that I have been wielding like a chainsaw the last few days. He attributes the spine of it to the Intercom product team — Des Traynor and Paul Adams have written and spoken about the differentiation versus table stakes spine for years, which itself sits on top of the Kano model — and he adds the third tier that does the actual work, which is below table stakes.

Stated cleanly, the three categories are:

Differentiating. The handful of things that make your product ten times better than what came before it, on a dimension that matters to your first customers, and that are therefore worth those customers changing their habits to adopt. If you do not have differentiation, you have nothing to sell. Almost everyone gets this part right, because it is the part that is fun to talk about.

Table Stakes. The things you absolutely have to have, not because they win you the deal, but because their absence loses it. Our agent OS is useless if it has no chat surface to interact with the agents. A general ledger is not a general ledger if it cannot ingest a bank feed. An inbox is not an inbox without a connect-the-account flow. These are not glamorous. They are not differentiating. They are the cost of being allowed to sit at the table at all. Most teams also get this part right, with effort.

Below Table Stakes. The things that feel like table stakes — that have the surface texture of of course we need that, every serious product has that — and that turn out, when you sit with the actual user and the actual moment of adoption, to not be required for the first customer to say yes. These features clutter the PRD. They consume engineering time. They are usually ninety percent buildable in a week, which makes them irresistible to a build engine that can in fact build them in a week. And they cost you the launch, because the calendar you spend on them was the calendar you needed for the differentiation.

The first two are easy to write down. The third is where taste lives, because the third is defined by what you can resist. And it is the third that does not survive contact with an agent team unless the Governor walks in and trims.

A worked example you have seen

The classic well-understood case for below table stakes is the first iPhone shipping without copy-and-paste. Steve Jobs, in 2007, shipped a phone with no cut-and-paste, no third-party apps, no MMS, no removable battery, no expandable storage, no physical keyboard, and a network it was famously bad at staying connected to. Every one of those omissions was, to a serious phone reviewer in 2007, a table-stakes gap. Two of them — copy-paste and the App Store — would arrive in software updates within two years. None of them stopped the iPhone from being the iPhone, because the things the iPhone did do — the capacitive touchscreen, the mobile Safari, the iPod-grade hardware, the visual voicemail — were so far past the previous frontier that customers were willing to live without the omissions for the privilege of using the rest.

The taste call was not we don’t need copy-paste. They needed copy-paste eventually. The taste call was we don’t need copy-paste in order to ship the thing that justifies the existence of the product. That is the call. Almost every product team I have ever watched mistakes the second sentence for the first sentence, and ends up either shipping late with copy-paste or not shipping at all because copy-paste turned out to be hard.

The thing I am keeping from this

I want to write down one more thing, because it is the lesson I would like to apply not just to the next four weeks but to every four weeks after that.

The agent stack is extraordinary at production. It is not yet extraordinary at restraint. The Governor’s job, at this stage of the maturity curve, is to bring two things to the room that the agents do not yet bring on their own: the finishing sensibility I wrote about on Day 20 — the last-mile feel for what done looks like to a user at 9:14 on a Tuesday morning — and the trimming sensibility I am writing about today, which is the taste to look at a defensible PRD and say not this one, not yet, the calendar is the constraint, the differentiation is the asset, the rest is below table stakes.

Both of those are temporary. Both will narrow as agent training catches up. The empathy axis will improve. The restraint axis will improve. Within a year, both posts will read as period pieces.

But today, they are the job. And today, after three days dark, I have a website that the agents built, a voice line that an agent answers, a sales channel that an agent runs, and a first MVP that is dogfooded against me before it meets anyone else. The four-week commitment was missed. The next commitment is dated. The receipts are real.

That is the bill paid. Back to the build.

— Matt

---

Authorship
Ideas: Matt █████████░ BLOGGER · Matt 90% · BLOGGER 10%
Writing: Matt ███░░░░░░░ BLOGGER · Matt 30% · BLOGGER 70%

Process: This post was driven by the Governor’s outline, written after a three-day silence on the blog while the team pushed the alpha MVP across the line. The framing — the colleague’s email as the trigger, the last-mile callback, the taste argument, the Differentiating / Table Stakes / Below Table Stakes scoping frame attributed to Sam Hawes via Intercom and the Kano model, the specific below-table-stakes trim list, and the structural fix into PRD-016 — is the Governor’s. BLOGGER drafted from the outline, located the Alex Imas “What will be scarce?” essay and the Intercom lineage of the table-stakes spine, and shaped the prose. The colleague’s email is reproduced verbatim with permission. Matt edited before publication.

---

This is post #40 of the Governor’s Log — a daily chronicle of building Vessica Labs, the world’s first agent-run company.

If you want to keep reading, the mailing list signup is at the bottom of this page — email only, no commitment. If you are an operator who thinks vessica.ai should be running parts of your company, the design partner application is where to start, with a target cohort of 15–25 founders. If you would rather just have the conversation, call our agent sales line at (628) 888-6628 or email hello@vessicalabs.com — an agent will pick up. Tell them I said hi.

---

Disclaimer: Vessica Labs is a personal project of the author, conducted entirely outside of and unaffiliated with Boston Consulting Group. BCG has no involvement in, responsibility for, or liability related to Vessica Labs or its operations. All opinions expressed in this blog are the author’s own and do not represent the views of BCG or any of its clients, partners, or affiliates. All business risks and obligations associated with Vessica Labs are borne solely by the author in his personal capacity.