Treat an investor-required acquisition as two decisions that must both hold up: whether the smaller company improves your product, and whether accepting the condition is worth the financing risk. Do diligence before agreeing, protect the roadmap in writing, and make sure the deal creates value after the round closes.
Mika, an illustrative composite founder, was still in her office in Accra at 5:17 on a Friday, her laptop balanced beside a cold cup of sobolo. Her lead investor had called with an answer to the round: they would participate if her company acquired a smaller startup whose product Mika’s team had dismissed six months earlier.
Back then, the product looked thin. It solved one visible part of a workflow Mika’s team had chosen to leave alone. The founder had a small customer base, a lean engineering team, and a product Mika described after the demo as “a feature with a company attached.”
Now the investor saw something else: a faster route to distribution, a team already close to a customer segment Mika wanted, and a story that might make a difficult round easier to support.
The term sheet was still open on Mika’s screen. Her payroll was due soon. If she refused, the round could stall. If she agreed too quickly, she could spend the next year integrating a product her team still did not believe in, while the work that had earned customer trust stopped moving.
That was the actual decision.
Start with the customer map, not the investor’s enthusiasm
An acquisition can look sensible from an investor’s portfolio view while creating confusion inside the company that has to carry it out.
Mika’s first move was to put both products on one page. She listed the customers each company served, the people who used the product each day, the problem each product solved, and the point where a buyer would notice the difference. She asked a harder question than “Can we add their features?”
Would their customers become stronger users of her product, or would they become another group with promises that had to be maintained?
This is where dismissed products can become valuable. The original assessment may have been right about the product itself and incomplete about its position in the market. A smaller company may have a narrow tool, but its customer conversations, distribution relationships, and understanding of a neglected workflow can matter more than its code.
It can also be a distraction with a persuasive slide deck. The distinction sits in the customer map. The Customer Map an AI Startup Cannot Afford to Lose matters here because an acquisition should deepen your view of the customer, not blur it.
Find the cost that will arrive after closing
The acquisition price is rarely the full cost. The expensive part often begins when two teams try to decide whose roadmap is real.
Mika asked the smaller company’s founder to walk through their last few customer requests. Which requests had been accepted? Which had been declined? Which commitments were already implied in sales conversations, even if they had never reached a contract?
Then she asked her own team what would pause if they took this on. A product manager named the release that would slip. An engineer pointed to the systems that would need to connect. Her customer lead raised the issue nobody wanted to say aloud: the acquired customers might expect hands-on support that Mika’s team had never planned to offer.
None of this made the deal impossible. It made its cost visible.
Scarce early-stage capital creates pressure to treat financing conditions as inevitable. Consolidation can make a deal feel like the responsible move. Durable businesses still need a clear reason to carry the extra work. If the acquisition steals attention from the product customers already pay for, the round may extend runway while weakening the company that needs to reach the next milestone.
Turn the condition into a diligence window
Mika did not give the investor an immediate yes or no. She agreed to a short diligence window and made the questions explicit.
Could the smaller company’s customers use Mika’s core product without a custom rebuild? Could its team explain the product decisions behind their roadmap? Were there obligations that would force Mika into work she would not otherwise choose? Would the investor still support the round if the diligence showed that a partnership, referral arrangement, or asset purchase made more sense than a full acquisition?
That last question mattered. An investor who says “acquire them or we walk” is asking you to accept all of the downside before you understand the shape of the deal.
By Monday, Mika had a smaller, clearer proposal. She would explore the acquisition only if the customer overlap proved real, the team could stay focused on the core roadmap, and the operating plan named what would be stopped to make room. She also asked for the financing commitment and acquisition condition to be documented together, rather than relying on the warmth of a Friday call.
The smaller founder received a direct answer too. Their company was not being bought to decorate a fundraise. There was either a product case worth building together, or there was no deal.
Make the roadmap survive the negotiation
Mika returned to the same sheet after the weekend, but the page had changed. Next to every proposed benefit was an owner, a customer assumption, and a piece of work that would be cut or delayed.
That is the test. A serious acquisition plan can explain what happens to the roadmap on Tuesday morning.
If the deal closes, your team needs to know which customer promise comes first, who owns the integration, and what will no longer be built. If it does not close, you need a financing path that does not leave the company waiting for an investor to resolve a problem they introduced.
Mika’s strongest negotiating position came from being willing to discover that the acquisition was wrong. She still wanted the round. She also wanted a company worth funding after it arrived.
Comments
No comments yet.