You May Already Be Running a Concierge MVP

The specialist consultancy most ready to build a SaaS product is often the one that has never thought of itself as a software business at all.

There is a concept in startup methodology called the concierge MVP. It gets discussed mostly in the context of early-stage founders who want to test a product idea before building it. But the businesses it describes most accurately are often not early-stage at all. They are established expert-led consultancies that have been delivering the same outcome, through a repeatable process, for years. The software opportunity is not waiting to be created. It is hiding inside the service they are already running.

What is a concierge MVP?

The term is straightforward once you strip away the jargon. A concierge MVP means delivering the outcome your eventual product will automate, but delivering it manually, with human expertise doing the work that software will one day do. The client pays for the result, not the mechanism. You, meanwhile, learn in granular detail exactly what software would need to do to replace the human in the loop.

Consider a business that wants to sell a compliance-checking tool. It might start by offering a compliance review service: an analyst checks documents against regulation and returns a structured report with a confidence score attached to each finding. The client pays a retainer. The analyst is, in effect, the product. Over three months you discover that most of the analytical work clusters around a small number of document types, that clients always want an audit trail for their own regulators, and that the questions they actually ask are quite different from the ones you anticipated. None of that would have emerged from a product specification written in advance. All of it is now available to inform the software you go on to build.

That is what makes the concierge approach genuinely useful: the service phase is not a delay to the product. It is the most accurate requirements-gathering you will ever do, and it pays for itself while it happens.

Are you already running one without realising it?

If your business delivers a repeatable process for clients, charges for outcomes rather than time, and applies an internal method or framework to produce those outcomes, there is a reasonable chance you are already running a concierge MVP. You are just calling it the service.

Consider what this looks like in practice. A growth advisory that analyses a client's acquisition funnel and produces a prioritised action plan. A due diligence practice that synthesises data from multiple sources into an investment memo. A regulatory consultancy that reviews a client's documentation and returns a structured gap analysis. In each case, the business has a method, applies it consistently, and charges for the output. The method is the proto-product. The clients paying for it are already validating demand, before any software exists.

The critical shift is recognising this for what it is. Not a service that competes with a potential product, but a service that is the first version of one. The clients who keep coming back are not just buying your time. They are buying the outcome your method reliably produces, which is precisely what a SaaS product sells.

Which parts of your service are worth productising?

Not every aspect of what a consultancy does is a good candidate for software. The parts worth examining closely share a few characteristics: the work is broadly repeatable from client to client, it involves processing or structuring information rather than purely creative judgement, and it takes more time relative to the value it produces than you would like. These are the places where software can absorb volume and structure so that your expertise concentrates on the decisions that genuinely require it.

There is also a useful signal in how clients talk about your work. When they start asking whether they can access the process directly, whether there is a dashboard or a portal, or whether they can run their own queries between engagements, they are describing a product they would pay for. They are not asking for more of your time. They are asking for the method, packaged independently of the person delivering it.

The inverse signal matters too. If delivery is consuming more of your capacity than you can comfortably scale, and the constraint is not the quality of the thinking but the hours required to produce it, that is a strong indication that the bottleneck is operational rather than intellectual. Software tends to be a better answer to operational bottlenecks than hiring.

The question of when to stop doing it by hand is one most people ask too early. The concierge phase should run long enough that you have seen the full range of what clients actually do with the work, not just what you expected them to do. That range is what shapes a product worth building. A SaaS built before that range is understood tends to be a product built for your first client rather than your tenth.

What you end up with, if you take the concierge path seriously, is something considerably more valuable than a validated idea. You have paying clients already invested in the outcome, a set of requirements drawn from real use rather than assumption, and pricing anchored to demonstrated value rather than competitive guesswork. You know what clients will pay because they have already paid it, repeatedly, for the thing the software will eventually do.

If your methodology already works as a service and you want to understand which parts of it are ripe to become a product, that is exactly the kind of work our SaaS Product Build partnership starts with. We help identify where the software opportunity sits inside your existing operation, then co-build it with you and share the upside. The incentive is aligned from the start: a product that actually sells, not one that merely gets built.