A repeated question about local support becomes a buying signal when prospects can name the work they would approve if that support existed. Until they connect the concern to a decision, treat it as a hypothesis worth testing, not a reason to hire.
The signal hiding inside the objection
In 1959, Honda sent Kihachiro Kawashima to Los Angeles to establish its motorcycle business in the United States. The company expected to compete with larger motorcycles. The small Super Cubs Honda staff used for local errands were not central to that plan.
Then people began asking about them.
Richard Pascale documented the episode in his California Management Review article, “Perspectives on Strategy: The Real Story Behind Honda’s Success.” Dealers showed interest in the small bikes. A Sears buyer approached Honda about selling them. Honda initially resisted because the Super Cub did not match the market strategy it had carried from Japan.
That resistance matters. The eventual success of the Super Cub can make the decision look obvious in retrospect. It was not obvious while Kawashima’s team was trying to establish an unfamiliar company in an unfamiliar market. The questions arriving from buyers contradicted the plan, but questions alone did not guarantee sales.
The team eventually followed the demand it could observe. The Super Cub became central to Honda’s American growth.
Three South African prospects asking a Ghanaian SaaS founder the same question creates a similar decision, on a smaller scale. The question may expose a condition of purchase. It may also be a courteous way to delay saying no.
The founder still has to discover which one it is.
Ask what the local hire would unlock
“Who will support us locally?” contains too little information to justify payroll.
The useful follow-up is concrete: “If we had support in South Africa, what would become possible that you cannot approve today?”
One prospect might need someone available during its working day. Another might worry about implementation at a Johannesburg office. A third may be testing whether the company will still answer after the contract is signed. Those concerns require different responses. None automatically requires a full-time employee.
I would also ask who raised the issue and where it sits in the buying process. A concern from the person who controls the budget carries different weight from a question added by someone attending an early product call. Timing matters too. If local support appears after the buyer has agreed on scope, security and commercial terms, it may be the remaining approval condition. If it appears before the buyer has explained the problem, it may be a general hesitation.
The next question removes more ambiguity: “If we solve that concern for the first contract, are you prepared to move forward?”
The answer does not need to be enthusiastic. It needs to produce a next step: a paid pilot, procurement review, implementation date or contract discussion. Continued interest without movement remains weak evidence.
This is the same distinction I make between interest in a working demo and willingness to expose a real process to it. Kojo’s demo worked, but Monday’s invoice put his runway at risk because technical progress and commercial commitment were moving at different speeds.
Test local support before building a local team
A founder with limited runway should test the smallest credible version of the requested capability.
That could mean assigning one person to South African business hours for a paid pilot, scheduling support windows in advance, using a local contractor for implementation, or travelling for the first deployment if the contract can carry the cost. The right test depends on what the prospect says local support must accomplish.
Put the test in writing. Define who responds, during which hours, through which channel, and what happens when an issue needs escalation. Then ask the prospect to accept that arrangement as part of a commercial next step.
This turns an abstract concern into something both sides can evaluate. It also prevents a premature hire from becoming a substitute for closing the sale.
The risk runs in both directions. Refusing every local request can make a remote company look absent when the buyer needs accountability. Hiring after three conversations can consume runway before demand has been proved. The founder needs evidence stronger than repetition and cheaper than a permanent team.
A conditional commitment provides that evidence. For example: the prospect signs a paid pilot if named support coverage is available. Two customers agree to start within the same quarter. A contract includes enough implementation work to fund a local contractor.
Without that connection, the founder has learned that buyers notice geography. That matters, but it does not yet fund a role.
Let commitments change the plan
Honda’s team in Los Angeles did not build its American strategy around every comment it heard. It changed course when repeated interest connected to dealers, distribution and actual demand for the Super Cub.
That is the standard I would apply on Monday.
Record each prospect’s exact concern. Ask what decision local coverage would unlock. Offer a bounded support arrangement. Request a paid commitment tied to that arrangement. If two or three prospects move, the founder has evidence for a contractor, partner or first hire. If none moves, the question was probably carrying another objection.
Repeated concern deserves investigation. Repeated commitment deserves investment.
Comments
No comments yet.