Know what is worth building.

Commercial and technical research for businesses weighing up a new idea, digital product or process change. Make the decision with evidence, clear assumptions and an honest view of the risks.

Get unstuck

Decision framework

Evidence before investment.

What do we know?
What are we assuming?
What should we test next?

An illustrative report framework. The research methods and outputs are agreed for each project.

Solihull · Birmingham · UK

A report should help you decide.

A feasibility study asks whether a proposal is workable and worth taking further. Commercial feasibility looks at demand, alternatives and the assumptions behind the business case. Technical feasibility looks at whether the proposed system can work within its constraints. Ampliflow brings those questions together for business and digital projects.

Frame the decision

Start with the decision the research needs to support. Are you deciding whether to build, buy, change course or test the idea first? Write down the audience, the constraints and the options before you gather any data. A long report is no substitute for a clear question.

Examine the commercial case

Look at the market and the competitors that matter to this decision. Then separate what you actually observed from what you assume about demand and customer behaviour. Search interest can show the questions people ask, but it does not prove they will pay. If you need primary customer research, that has its own agreed method and scope.

Test the technical assumptions

Consider the systems, data, integrations and permissions a proposal depends on. Some questions can be answered from documentation; others need access or a technical test. Record what has been verified and what remains uncertain before estimating a build.

Choose the next step

Compare realistic options and identify the evidence that would change the decision. Product discovery can clarify what a proposed app or service should do before development. The next step may be a smaller experiment, a scoped build or a decision not to proceed.

A better starting point

Bring the problem.
We’ll work through it.

No finished brief needed. These details help us understand the work before discussing scope.

The decision you need to make
The idea, process or product being considered
What evidence and systems already exist
The constraints and unanswered questions

Before you decide.

Is a feasibility study the same as a business plan?

No. A feasibility study tests whether a proposal should proceed and under what conditions. A business plan explains how an organisation intends to operate and deliver it. They can inform each other, but they answer different questions.

Do you provide both commercial and technical feasibility?

Yes. We discuss both the business case and the technical constraints. The depth, evidence sources, access and report requirements are agreed for the project. An assessment should distinguish verified findings from assumptions and estimates.

What does product discovery mean?

It is the work of understanding the problem, users, options and constraints before deciding what to build. It can help reduce uncertainty before app, website or automation development. It does not guarantee that a proposed product will succeed.

Is this a lender-approved or regulated assessment?

Don't assume that. If your report must meet a lender, regulator, grant or specialist industry requirement, tell us before we agree the scope. Commercial and digital feasibility work is not automatically a regulated financial opinion or a sector-specific certification.

Explore the next question.

Before you commission the work

What evidence would change your build decision?

Write down the assumption most likely to make the project fail: customer demand, access to data, an integration or the cost of operating it. Identify the smallest credible test and the result that would make you stop or change direction. A prototype can answer a technical question; it does not, by itself, prove demand for a product.