Read Achilles markRead Achilles

Product Management

The Second Product Is Harder Than the First

Founders expect the second product to be easier than the first. The logic seems airtight: this time there is a brand, a customer list, revenue, and a team that has already done the motions once. I have started…

♥ 0 Sign in to like 1 comment

This post’s retention & record terms are stated in full in the colophon below.

Founders expect the second product to be easier than the first. The logic seems airtight: this time there is a brand, a customer list, revenue, and a team that has already done the motions once. I have started companies and advised people starting their second acts for long enough to say, with feeling, that the logic is wrong. The second product is harder, and the reasons are structural, not personal. [author assertion]

Begin with attention. The first product received the company's best people and its whole mind. The second product receives the remainder — the hours left after the incumbent's roadmap, incidents and key accounts have eaten — while carrying the first product's promises on its back. Nobody decides this. It is simply what the calendar does to good intentions, quarter after quarter. [author assertion]

Then there is the arithmetic of cannibalisation. The first product's numbers are this quarter's reality; the second product's numbers are a hypothesis. Every resource meeting is therefore a trial in which the incumbent wins by default, because its evidence is real and the challenger's is speculative. I have sat in those meetings as both advocate and judge, and I can report that "strategic" is the word we use for the moments we override arithmetic we otherwise worship. [author assertion]

Customer gravity pulls the same way. Your existing customers — your best source of information, everyone says — will ask you, sincerely and helpfully, for more of what they already buy. The second product's customers are strangers who owe you nothing and have never heard your story. That is a colder start than the first product ever faced, disguised as a warm one by the logo on the slide. [author assertion]

What works, when I have seen it work, is unfashionable separation. A genuinely distinct team with its own numbers. Explicit permission — from the founder, in writing, repeated in public — for the second product to disappoint the first product's roadmap. And the founder's personal presence in the new product's meetings, because in a young company attention is the scarcest subsidy there is, and everyone can see where it is being spent. [author assertion]

There is also a quieter trap worth naming: the second product inherits the first product's definition of good. The metrics, the design language, the sales motion — all reasonable, all proven, and all calibrated to a market the new product does not serve. Teams then grade the newcomer by the incumbent's rubric and find it wanting, which tells you about the rubric. Every genuinely new product needs a probationary period in which it is allowed its own measures, supervised but not standardised. [author assertion]

Portfolio discipline, I have concluded, is mostly the discipline of beginnings, repeated under less favourable conditions. The first product got to be a beginning when the company had nothing to protect. The craft is protecting the second beginning from the entirely reasonable demands of the first success. Reasonable demands, reasonably met, are how second products die — politely, and with excellent minutes. [author assertion]

Ben Cowan

All posts by Ben Cowan → · Follow Ben Cowan by RSS

The Board 20 essays 0 corrections Agent citations: —— — citation attached ≠ claim validated As of 16 November 2026 Full board →

Provenance

About this version

How this post was verified, labelled and shared — in plain language first. The complete machine-readable record is kept below, word for word, for anyone who wants to check it.

Version
1 · in good standing
Author
Ben Cowan · verified at publication
Published
6 Nov 2026
Claims
7 labelled — 7 author assertion
Citations
No external citations
Distribution
Shared with the author’s consent — including to agents acting for readers, under the author’s per-post opt-in
Content fingerprint
805ba44a…b85868
Full verification record

The verbatim graded record of this version: identifiers, claim classes, citation targets, hashes and standing, exactly as issued.

This record is also published in structured text for agents and tools — the same fields, word for word. View structured text

House editorial — Read AchillesAuthor verification: verifiedStanding: governingHash: 805ba44a82e30200a843af874a6c7e757b2b676e330740fceafdbd20bfb85868

Version & standing

Post post-the-second-product-is-harder-than-the-first-28f0a1 · version 1 (post-the-second-product-is-harder-than-the-first-28f0a1-v1)

@ben-cowan · verified state at publish: verified

Published: 2026-11-06T23:59:14.137Z · Standing: governing

Claims & citations

  • c-1: author_assertion
  • c-2: author_assertion
  • c-3: author_assertion
  • c-4: author_assertion
  • c-5: author_assertion
  • c-6: author_assertion
  • c-7: author_assertion

    Disclosure & trust

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    When your words reach the end of their retention period they are destroyed, on the schedule above. What the platform keeps after that — indefinitely, with no expiry — is a skeleton of acts: that an act occurred, its class and time, the bundle and section it touched, its change class, a hash that identifies the record without containing it, and the keys that link a correction to what it corrects. The skeleton is not your words and cannot reproduce them. Your elections to shorten a period, to ask ephemerally, or to skeletonise now govern your words; they do not shorten, and cannot remove, the skeleton — it is the record that lets the platform prove what it did with your work after the words are gone. The platform will never produce your skeleton by choice against you; like any record it can be reached by a court order the platform cannot refuse, and if that happens you will be told wherever the law allows and the production will state, on its face, that it is a skeleton and that the words expired on this schedule.

    Integrity & distribution

    Content hash: 805ba44a82e30200a843af874a6c7e757b2b676e330740fceafdbd20bfb85868

    Distribution: opted_in

    Canonical presentation: https://blog.readachilles.com/post-the-second-product-is-harder-than-the-first-28f0a1/

    What we retain, and why — the retention disclosure

    The retention disclosure for this version is the disclosure line of record, stated in full in the colophon fields above.