A unicorn headline should not change a pre-seed founder’s roadmap unless it changes the evidence beneath the business. When three paying customers need the same fix before Friday, shipping that fix usually matters more than rebuilding the company around the category investors celebrated this morning.
At 8 a.m. in Accra, Kojo had the headline open beside a support message from his oldest customer. Kojo is a composite, but the decision is familiar: his small team had built a paid workflow tool, three customers had requested the same repair, and Friday was the last credible delivery date.
The headline pointed elsewhere. An African fintech had become a unicorn after a large raise. Kojo could already see the pitch deck rewrite: payments infrastructure, transaction data, financial services for small businesses. The market would look larger. The story would sound more fundable.
His actual customer had a simpler problem. A broken approval step forced staff to repeat work by hand.
If Kojo spent the week reframing the product, the fix would slip. One customer had already said the current process could not continue. Renewal was now in doubt, and the other two accounts had hit the same fault. By Friday, Kojo might have a sharper fintech story and fewer paying customers.
The headline changed the comparison
The dangerous part of a unicorn announcement is rarely the news itself. It changes what a founder compares their company against.
At 7:59, Kojo was asking, “What must we repair for the people paying us?”
At 8:01, he was asking, “Are we building in the wrong category?”
That second question feels strategic. It also contains a trap. The unicorn’s financing round reflects its company, market position, timing and investor case. Kojo had none of that evidence. He had a headline, a workflow tool and three customers pointing to the same defect.
I have felt this pull while building products across different markets. A company in the US raises money around one category, a European product announces expansion, or an African startup becomes the proof that a sector can produce a large outcome. For a few hours, every adjacent product starts to look as if it should move closer.
The useful question is narrower: what new fact about your own customers arrived with the news?
For Kojo, none had.
Three requests were stronger evidence
Three customers asking for one fix does not prove a large market. It proves something more immediate: the product is being used deeply enough for the same failure to hurt more than once.
That signal deserves attention.
Kojo opened the three requests side by side. The language differed, but the failed moment was the same. Someone completed a task, sent it for approval and then had to reconstruct part of the work after the approval step broke.
The repair would not make an impressive funding slide. It would make the tool dependable at the point where customers had begun organising real work around it.
This is where I separate a product decision from a financing story. A product decision should follow observed behaviour, repeated friction and the cost of leaving that friction unresolved. A financing story may help explain the size of the opportunity, but it cannot substitute for those things.
The same discipline appears in what Monday must prove when only six weeks remain. When runway is short, the next release needs a job. “Makes us sound like a fintech” is too vague. “Protects three paying accounts” is a job.
Fintech required a different company
Rebuilding the product as fintech would involve more than adding payments and changing the homepage. Kojo would be choosing new operational responsibilities, customer expectations and failure modes.
Money movement creates a different standard of trust. A delayed workflow is frustrating. A missing or disputed payment can stop a business from operating. The product, support process and team would need to meet that difference.
That move might still become sensible. Kojo’s customers could reveal that approvals end in payments, reconciliation creates the real pain, or the product already sits at a financial control point. Those would be reasons to investigate.
The unicorn headline was a reason to pay attention, not a reason to rebuild.
Kojo wrote two columns in his notebook. Under “known,” he put the three requests, the broken approval step and the renewal risk. Under “possible,” he put payments, a larger market and investor interest.
He chose from the first column.
Friday produced the next question
With the deadline close enough to make another delay visible, Kojo reduced the week to one release. The team repaired the approval step, tested the path that had failed and sent the update to the three customers.
The fintech idea stayed in the notebook. It earned a customer interview question, not a sprint.
That distinction matters on limited runway. You do not need to ignore market news. You need to price the distraction correctly. A headline can justify an afternoon of research. Repeated customer pain can justify the week.
On Friday, Kojo still did not know whether the company would ever become fintech. He knew something more useful: the workflow held through approval, and the customer who had warned that the current process could not continue could use it again.
On Monday, he could ask what happened after approval. If customers consistently moved from that workflow into a financial task, the fintech question would return with evidence attached.
Comments
No comments yet.