When the Business Model Itself Is the Problem

A small consultancy in Dublin spent 18 months refining its sales pitch, hiring better staff, and cutting costs. Revenue stayed flat. The problem was not the team.

The model charged clients a one-time project fee, which meant the business had to find new clients every 6 to 8 weeks just to survive. That is an exhausting treadmill, not a business.

What the numbers were actually saying

Project-based revenue requires roughly 4 new clients per quarter to cover fixed costs of around 12,000 per month. Miss one, and the month is already in deficit before work begins.

Switching to a retainer model, even at a lower monthly rate per client, changed the maths completely. 8 clients at 1,800 per month covers the same costs with room left over.

The lesson that took too long to learn

The founders assumed the model was fine and kept optimising around it. It took an outside advisor asking a single question: how many times does each client pay you?

For anyone new to this topic, that question is worth sitting with before anything else. A business model is not just what you sell. It is how often, to whom, and under what conditions money actually arrives.

The structure of revenue determines the stress level of the entire operation, not the quality of the product.

Execution problems and model problems look identical from the inside. The difference shows up when you fix the execution and nothing improves.