Choose the sales operator if she is already producing repeatable evidence of demand and the engineer would mainly deliver what the investor memo predicted customers would want. With one salary left, fund the constraint visible in the business now, then make the next hire from what that work reveals.
In 1985, Intel’s Andy Grove faced a version of this decision with far more than one salary at stake. Intel had built its identity around memory chips, but Japanese manufacturers were winning that market and the company’s position was deteriorating. Grove asked chairman Gordon Moore what a new chief executive would do if the board replaced them. Moore’s answer was that the new leader would get Intel out of memory.
Grove replied that they should walk out, return as the new leaders, and make that decision themselves.
The plan can survive after its assumptions fail
Grove recounts the exchange in Only the Paranoid Survive. The decision mattered because memory was woven into Intel’s history. Leaving it meant redirecting resources toward microprocessors while the outcome was still uncertain.
The investor memo in Accra carries a smaller version of that institutional weight. It names a senior engineer because the fundraising story probably included a delivery plan, hiring sequence and product milestones. Once investors have read it, the hire can begin to feel committed even when the underlying assumptions have changed.
Meanwhile, the sales operator is in Lagos opening conversations with prospective customers. She is hearing where the offer stalls, who controls the budget, which promise earns a second meeting and which requested feature disappears when payment comes up.
That evidence may invalidate parts of the memo. It may also confirm them. Either result is useful.
A plan deserves loyalty while its assumptions remain true. When the market starts returning different information, protecting the plan can cost more than revising it.
Find the constraint before choosing the title
The decision should turn on the company’s present constraint.
If customers are ready to pay but the product cannot meet a defined technical requirement, hire the engineer. The evidence should be concrete: deals are blocked by the same missing capability, buyers accept the price, and delivery capacity is the reason revenue cannot move.
If conversations are happening but demand remains vague, the company has a learning and distribution constraint. Hiring the engineer adds build capacity before the founder knows what deserves to be built.
This distinction matters because senior engineers create momentum. Once hired, they need a roadmap, access and decisions. Work will be found for them. Features will ship. Payroll will continue. None of that proves the company has moved closer to revenue.
The sales operator can make the commercial uncertainty legible. Give her a narrow market, a clear offer and a defined period to turn warm introductions into paid commitments or explicit rejection. Track the objections that repeat. Record who attends each call, who can approve spend and what happens after a proposal arrives.
This is the same reason Kojo restored the manual work between interest and payment in Distribution Slides: Why Kojo Restored the Manual Steps That Turn Interest Into Payment. Interest can flatter a roadmap. Payment exposes what the buyer values enough to act on.
Put both hires through the same test
An investor memo and an active sales pipeline often use different kinds of evidence. The memo describes a plausible future. The pipeline records present behaviour. Compare them on the same terms.
Write down the result each hire must produce before the remaining runway ends.
For the engineer, name the customer commitment that depends on the technical work. “Improve the product” is too broad. A useful case sounds closer to this: several qualified buyers require the same integration before they can proceed, and the team cannot deliver it with its current capacity.
For the sales operator, define progress beyond meetings. Introductions matter, but they can hide weak demand. A stronger case includes qualified opportunities, proposals requested, commercial objections documented and payment steps reached.
Then test reversibility. A founder can support a sales operator with demos, manual onboarding and tightly scoped delivery while learning what buyers need. A senior technical hire commits more runway to a product direction and usually takes longer to unwind.
This does not make sales the automatic choice. It means the engineer needs evidence tied to revenue, rather than a place in a document written before the latest customer conversations.
Make the next payroll decision easier
Intel’s move away from memory did not guarantee that its next chapter would work. Grove and Moore acted because the evidence beneath the old allocation had changed. Continuing to fund the familiar plan would not restore the market they were losing.
The Accra founder needs the same discipline on a smaller balance sheet. The salary should follow the clearest current constraint, even when that choice makes the investor memo untidy.
Give the Lagos operator a short, explicit commercial mandate. Ask which doors led to a decision-maker, which proposals reached a real budget conversation and which product requests appeared repeatedly after price entered the discussion. If those conversations expose a technical bottleneck, the case for the engineer becomes stronger and more specific.
Friday payroll is the wrong moment to preserve the appearance of certainty. Use the remaining salary to buy the evidence that makes the next decision less dependent on a memo.
Comments
No comments yet.