The tool is chosen last.
A service menu decides the answer before anyone has named the problem. Start from the problem instead, and choose the tool last.
Solveware · 19 October 2026
Start from the problem and choose the tool last. Any other order sells a business what the seller has, not what the business needs.
A firm built on a service menu starts in the wrong place. A campaign. A website. A strategy deck. An app. The menu is set before the client walks in. So the first question in the room is not what is wrong. It is which item on the menu fits.
What a menu does to a problem
A menu is a set of answers waiting for a question. When a business arrives with a problem, the menu bends the problem until it fits. Flat sales become a brand problem, because the firm sells brand work. A slow process becomes a software problem, because the firm builds software. The client leaves with a real deliverable. The problem stays where it was.
This is the trap of the traditional agency model. It is not a failure of talent. It is a failure of order. The firm is built to sell what it has, so it sells what it has. Clients are force-fit into services they do not need, simply because those services are what the firm exists to sell.
The cost is easy to miss. The work gets done. The invoice gets paid. The output looks good in the final presentation. Months later the same problem is back on the board agenda, with less budget and less patience.
A menu is a set of answers waiting for a question.
Start from the problem
Starting from the problem means the first piece of work is a question. What is actually in the way? It is usually not the symptom named in the brief. It is the constraint underneath it.
We name that constraint in the client’s words before we describe any work of our own. If the team says customers leave after their first month, that is the problem. Not a retention strategy. Not a loyalty programme. Customers leave after their first month. Stated plainly, a problem starts to show its own shape.
Only then do we look at tools. Strategy, software, service design, brand and film are all on the table. Each is a medium, not a product. We pick the one that removes the constraint most directly. Sometimes it takes two, in a set order. Sometimes nothing that exists fits. Then we invent the mechanism the problem needs.
What it looks like in practice
Take a retailer whose sales have gone flat. A menu-led firm hears flat sales and sells a campaign. The campaign runs. More people come through the door for a few weeks. Sales stay flat.
Start from the problem and the questions change. Where exactly do sales stall? In which stores, for which products, on which days? Who sees the gap first, and what do they do about it? In this example the answer is stock. It reaches the stores late, so shelves are empty on the days customers come in. Customers want to buy. They cannot.
That problem does not need a campaign. It needs a change to how stock moves. There are three ways to fix it: a new ordering process, a simple tool for store managers, or a view that flags a gap before the shelf is bare. The evidence decides which. The tool is chosen last, because only now is it clear what the tool has to do.
The campaign can still come later. Once the shelves are full, more customers through the door is worth paying for. Order matters. The right tool at the wrong moment solves nothing.
Agnostic is a discipline
Agnostic is an easy word to claim and a hard one to practise. It means being willing to say that the thing you do best is not what this problem needs. It means holding back a recommendation until the problem is named. And it means being able to build across strategy, software and film, so the choice of tool is a real choice and not a sales pitch.
That is how Solveware is built. We are an agnostic solutions hub. We do not sell predefined services. We put the result ahead of the category. Whether the answer is a strategy deck, a mobile app or a commercial, we adapt to the problem, not the other way round. If the problem needs a mechanism that does not exist yet, we build that too.
If your team already knows what is wrong, bring it to us in your own words. We will start there. The tool comes last.
