Nobody Said Take My Money — Part 5 of 7

This is the post I least wanted to write, which is how I know it’s the useful one.

Between June 5 and June 18, 2026 — thirteen days — I produced more strategy than in the previous six months combined. New pricing. A reversed shutdown. A platform re-architecture. Four new product concepts. A message pivot. And then, at the end of it, the actual shutdown. From inside, every single day of it felt like clarity. From two weeks’ distance, it was a system under terminal stress, generating ideas faster than it could test them, because generating ideas was the only move that didn’t hurt.

Here’s the timeline, with real dates, so you can watch the cadence — because the cadence is the lesson.

The thirteen days

June 5–6. The festival. Two days, warm crowd, zero sales (Part 4). On the evening of the 6th I wrote the first shutdown decision: sunset Mother Hen as a bundle — the technology is sound, the product isn’t viable, root cause pricing. Note the shape of that diagnosis: it kept every piece of the work alive and blamed a number.

June 9. Rebuilt the pricing instead. New model: subscription at $29.99/month for the first coop, $14.99 for each additional, hardware sold essentially at cost. Anchor high, discount down, never raise. Breakeven: 48 subscribers. This was genuinely better pricing than what it replaced. It was also a detailed answer to a question no customer was asking.

June 11. Reversed the June 6 sunset — five days after “treating it as decided,” the bundle was back, now under the new cost-plus-hardware model. Same day: suspended sales entirely, pending a solar-power engineering effort estimated at four months. Also same day: evaluated and rejected an entire alternative radio architecture (LoRa — the gateway economics killed it). One day, three strategic reversals deep.

June 12. Re-architected the product line as a hub-and-spoke platform — the controller as a powered hub with standard cabling to satellite sensor modules. Wrote it up properly, with a decision record. Also spun a solar variant of a second product. The engineering was, as always, perfectly sound.

June 13. Evaluated adding a camera product. Wrote up the optics, the abuse cases, the cost model.

June 14. Big day. Pivoted the camera idea to bring-your-own-camera — an AI vigilance layer over the Ring or Nest camera the customer already owns; no new hardware, cloud-to-cloud. Drafted a multi-signal predator-detection architecture fusing camera, in-coop motion, and flock-distress audio. Resurrected the WiFi controller SKU that had been shelved months earlier. Sketched a door-control feature by having the controller emulate the door’s own RF remote. Four product directions in one day, each with real analysis behind it.

June 15. Started actual discovery — structured interviews and case collection on how predator losses really happen. This was the first genuinely new evidence gathered since the festival, and it was devastating in a quiet way: real losses skew heavily toward daytime, free-range kills — fox, raptor, dog — fast, over in minutes, discovered visually by someone standing in the yard. Checked against the first seven documented cases I collected, my coop-door-centric product would not have helped in at least five of them. The flagship fear I’d built around — the nighttime coop intrusion — was real but narrow. The product defended a subset of a subset.

June 17. Pivoted the marketing message to “door securement assurance” — reframing away from predators toward the reassurance of a confirmed-locked coop. Drafted ad copy. Planned a cheap message test.

June 18, morning. Sketched yet another idea: repurpose the existing door sensor onto the coop’s slide bolt, to sense locked rather than merely closed. Zero new electronics. Genuinely clever.

June 18, later that day. Wrote the real shutdown decision. Not the bundle this time — the business.

The pattern, named

Look at the cadence, not the content. Eight-plus strategic artifacts in thirteen days, most of them individually defensible — several were good ideas, and writing them up properly was good practice. Collectively, they were a symptom.

Here’s the mechanism I can only see in hindsight. After the festival, the core demand signal was in, and it was negative. Every existing, tested thing about the business now carried that verdict. But a new idea — the camera, the BYO pivot, the latch sensor, the message reframe — carried no verdict yet. Untested ideas are the only part of a dying venture that still feels alive, so a mind that isn’t ready for the verdict starts manufacturing untested ideas at exactly the moment it should stop. Pivot velocity went up as viability went down. That correlation, I now believe, is close to diagnostic.

And notice what punctured it: not another idea, but discovery — the June 15 interviews. The one activity in the whole thirteen days that gathered evidence instead of generating options is the one that ended the loop. The interviews didn’t suggest a better feature; they showed that the product’s core scenario was rarer than the fear it monetized, which no feature could fix. Three days later I wrote the shutdown.

The question that cuts through

If you find yourself in a June like mine, here is the filter I wish I’d taped to the monitor, and the reason half those documents shouldn’t have been written:

Does this pivot change who pays — or only what I’d build next?

The June 9 pricing: changes what they pay, not who. Hub-and-spoke, the camera, the latch sensor, the WiFi SKU: change what I’d build. The message reframe comes closest, and a version of it — tested against cold traffic with a pre-committed kill number — would have been legitimate. But when demand is the thing that failed, only new evidence of payment counts as a reason to continue. Everything else, however sound the engineering, however elegant the decision record, is motion. A builder in distress will always reach for the thing he knows how to do. I know how to architect. So I architected, daily, at a company that needed a customer.

One more honest note: the velocity wasn’t wasted thinking — several of those ideas were shelved intact with the platform, and one or two may earn a future on their own merits, tested properly this time. The waste was running strategy as a coping mechanism and calling it a roadmap. If your idea rate triples in the two weeks after bad news, you are not iterating. You are flinching, in a format that looks like work.

Part 6: Killing It Well — The Sunset Decision.