The Year-Long Bet, Re-Earned Monthly

Conviction and governance under overrun · Neon One, 2022–2023

Problem

Donation matching and endurance pledges — my primary initiative — targeted major-donor dollars that were transacted offline, invisible to the platform. Estimated at ~3 months, the project ran over a year.

My role

Initiative owner. Set the structure that let a 4x overrun continue without becoming either sunk-cost momentum or a platform-wide stall.

Outcome

The bet paid off: customers adopted the features and the platform began capturing high-end donations previously transacted offline.

Situation

Grassroots fundraising platforms under-serve the top of the donor pyramid. Matching gifts and endurance pledges — a donor pledging against someone's fundraising progress — were a clear competitive gap with large revenue potential, because those dollars were moving offline where the platform earned nothing. Engineering estimated ~3 months. The deeper the team dug, the more of the payments system turned out to need refactoring or rebuilding that nobody had counted on. Three months became twelve.

The decisions

Monthly go/no-go, taken seriously. Every month I met with leadership to review progress and genuinely reconsider cancelling — not a status meeting, a re-decision. Every month we deliberately re-affirmed it as top priority based on the evidence at hand. Continuing was a choice we kept re-earning, not a default we drifted into.

Contain the bet. I isolated one to two developers on the project so the rest of the team kept supporting the platform normally. The overrun never stalled everything else — which is precisely what made the monthly "continue" call affordable. A bet you can't contain is a bet you can't honestly re-evaluate.

Protect the estimators. I don't estimate; I ask the engineers to. When they're wrong, my job is to reassess and shield them from leadership's frustration — everyone misjudges at this complexity, and an engineer who gets burned for an honest estimate stops giving honest estimates.

Outcome

Customers deployed matching and endurance pledging, and the platform started capturing donations that had previously bypassed it entirely. The overrun also produced a durable operating principle: I now cap estimate horizons — rarely beyond ~50 hours for sponsored work, rarely beyond 2–3 months for feature work — because the larger the project, the more it's exposed to unknowns. For anything bigger, I'd rather commit to "this is a multi-month project; let's reassess regularly" than defend a single number. Structure for the uncertainty instead of betting on it.

What it shows

Running a long, uncertain project without sunk-cost marching or rage-quitting: contain the blast radius, re-earn the go decision on evidence, and keep the engineers honest by keeping them safe.