Jonas's offer paid the bills. Saying yes would have killed the market research he still needed.

The Feature Request I Said No to on Tuesday

The fastest path to revenue usually isn't the right one. When a German prospect offered to pay for a custom workflow, saying yes would have paid the bills for a quarter but let one buyer's specification replace the market research we still needed to do. I turned it down on Tuesday, and it was the clearest decision I made all month.

Jonas had been on our radar for eight weeks. He ran operations for a mid-sized logistics firm in Hamburg, and his team had spent two years juggling three systems that refused to talk to each other. His email landed at 9:04am: "We need a workflow that pulls shipment status from our ERP, reconciles it against carrier updates, and flags exceptions before dispatch. Can you build this? We're ready to sign."

The money was real. The timeline was fast. And the longer I sat with his spec, the more I realized it was a trap wearing a very comfortable suit.

The seduction of a willing payer

I've written before about how three buyers wanting different products reveals the real shape of demand. Jonas was the opposite problem: one buyer who wanted one very specific thing, and was prepared to write a check for it.

Build his workflow, and here's what we got: three months of runway, a reference customer in Germany, and a product that served exactly one company's internal process. We wouldn't have a product. We'd have a consulting engagement wearing a product's clothes.

The pull was genuine. Asenda operates across Africa, Germany, and the US, and a European logistics reference would open doors that have stayed shut for most of our first year. I could feel the pitch writing itself: "Trusted by a Hamburg logistics firm." It was a good story. It was also a story about what one operations manager thought he needed, not about what the market actually wanted.

What saying yes would have cost

I don't mean the obvious costs, though those were real. An engineering hire to staff the engagement. A quarter of our roadmap diverted into someone else's internal tooling. The quiet death of the discovery we were supposed to be running.

I mean the strategic cost.

Jonas had spent two years inside his problem. His spec was brilliant at describing his current pain and useless at describing what other people with different pain might pay for. His workflow assumed his ERP, his carriers, his exception rules. Every hour we spent encoding that specificity was an hour we didn't spend asking whether other logistics teams in the DACH region had the same problem, or a different one, or none at all.

I kept coming back to one question: what were we actually selling? A workflow is a feature. A feature that one buyer demands is a specification. A specification that one buyer pays for is a distraction.

The uncomfortable truth was that we needed market discovery more than we needed revenue. The three months of runway Jonas offered would have bought us comfort while our real questions went unasked.

The difference between a sale and a signal

So on Tuesday I told him no, and I told him why. I said we weren't ready to build his workflow because we hadn't found enough people like him yet. We knew his problem intimately. We didn't know if it was a market.

To his credit, Jonas didn't argue. He asked what we were learning instead, and I walked him through the discovery calls we'd been running with logistics startups in Accra and Johannesburg. The conversation shifted. By the end he was less interested in the workflow and more interested in why the same reconciliation problem kept showing up in three different markets.

I still don't know if we made the right call. We have less revenue this quarter than a yes would have bought us, and there are days I wonder whether the discovery we bought with that no will ever pay for itself. But I know this: a payer is not a market, and a market is the only thing that turns a workflow into a product.

The Emeka's user dip piece keeps echoing in my head. He expanded under external pressure and watched his metrics fall. I chose to stay narrow and watch my bank balance stay flat. Neither of us gets to know if the other path was better.

That's the honest part of this job. You make the call with the information you have, you live with the outcome, and you keep asking whether the shape of the demand you're chasing is real. Jonas is still one of the best conversations on my calendar this month. He just isn't the product.