Most feasibility studies fail before a single page is written. They fail at scoping, the step where the buyer decides what the study will examine and, just as importantly, what it will not. A study scoped too narrowly answers a question nobody was worried about. A study scoped too broadly spends the budget on analysis that does not change the decision. Getting the scope right is the difference between a document that protects six or seven figures of capital and a document that becomes an expensive formality in a loan file.
Scope is a decision, not a default. Before commissioning a study, the buyer should be able to write down, in one sentence, the decision the study is meant to inform. “Should we sign the lease and build out this location” is a decision. “Tell us about the market” is not. The decision drives the scope. Everything in scope exists to move the decision one way or the other. Everything that cannot move the decision is out.
The four domains a feasibility study covers
A complete feasibility study examines four domains. The scoping question for each is how deep to go, not whether to include it.
Market feasibility. Is there a real population of buyers, in the geography you intend to serve, with the income to pay your prices, in numbers large enough to capture a defensible share. The scope decision here is how local the analysis needs to be. A national product can be sized from federal data. A single physical location lives or dies on trade-area demographics within a few miles, and the study has to go that deep or it has not answered the question.
Financial feasibility. What does it cost to build and operate, what does it earn, and at what point does the math break. This is the domain buyers most often under-scope, asking for a base case and nothing else. A financial section without a downside scenario has not tested feasibility. It has illustrated an outcome. The scope must include at least one stress case, because the whole point of the study is to find the point of failure before you fund it.
Operational feasibility. Can the thing actually be run, week after week, by the people who will run it, with the suppliers and equipment and staffing available. For a software product this domain is shallow. For a restaurant, a hotel, a manufacturing line, or an acquisition where you inherit a cost structure, it is where the study earns its fee. Scope this domain to the operational complexity of the venture, not to a template.
Risk feasibility. What could go wrong, how likely each risk is, and what the response would be. The scope here is breadth. The study should name the risks that are specific to this deal, the zoning question, the single-supplier dependency, the key-person concentration, not the generic risks that apply to every business on earth.
Sizing the study to the bet
The right depth in each domain scales with the size and reversibility of the decision. A reversible decision with a five-figure downside does not need a sixty-page study. An irreversible decision with a seven-figure downside cannot be made safely with anything less.
Three questions set the depth. First, how large is the loss case if you are wrong. Second, how reversible is the commitment once made. A lease signed is harder to unwind than a pilot launched. Third, how much of the data lives outside your own four walls. A decision you can answer from your existing P&L does not need a study at all. A decision that depends on trade-area demographics, comparable operating benchmarks, and supplier quotes you do not yet have is exactly what a study is for.
What belongs in scope
A well-scoped feasibility study includes a market section sized to the relevant geography, a financial model with a base case and at least one downside case, an operational assessment matched to the complexity of the venture, a named risk register, comparable benchmarks from at least three to five similar operating businesses, and an explicit go or no-go recommendation. The recommendation is the deliverable. A study that does not commit to a recommendation has left the hardest part to the reader.
Comparable benchmarks deserve specific mention because they are the most common scoping omission. A financial model with no external comparison is a model with confidence, not a feasibility study. The benchmarks are what tell you whether your assumed revenue per square foot, your assumed occupancy, your assumed margin, are achievable in the real world or optimistic by a margin that sinks the deal. Scope them in.
What does not belong
A feasibility study is not a business plan and not a marketing document. Brand strategy, logo direction, a five-year vision narrative, and detailed go-to-market tactics are out of scope. They belong in the plan that comes after the study says proceed. Including them inflates the page count and dilutes the analysis that actually informs the decision.
A study also should not include analysis the buyer has already done and trusts. If you have a validated financial model from your existing operations, the study should stress-test it, not rebuild it from scratch. Paying twice for the same work is a scoping failure in the buyer’s direction.
The independence test
One scoping decision sits above all the others: who writes it. A study commissioned from the broker selling the building, the franchisor collecting the royalty, or the consultant whose follow-on engagement depends on the deal closing is not feasibility. It is advocacy with a title page. The scope should include a clear statement that the author has no financial interest in the recommendation, and the engagement should be structured so that the fee is the same whether the answer is proceed or do not proceed. If the author cannot write “do not proceed” on the cover without losing money, the study cannot be trusted, no matter how thorough the analysis underneath it looks.
This is not only good practice. For SBA-financed deals involving special-purpose properties, independence is a requirement, and lenders increasingly will not fund without an independent third-party study in the file. Scoping for independence from the start saves a rejected study and two lost weeks.
Putting the scope on paper
Before any work begins, the buyer and the author should agree, in writing, on the decision the study informs, the four domains and the depth of each, the comparable benchmarks to be sourced, the downside scenarios to be modeled, and the form the recommendation will take. That one-page scope is the contract. It is also the protection. A study that delivers against an agreed scope cannot quietly shrink into a base-case-only brochure, and the buyer cannot later complain that the study did not answer a question that was never in scope.
A feasibility study scoped this way, twenty to twenty-five pages across market, financial, operational, and risk analysis, with named benchmarks, a downside model, and an explicit go or no-go recommendation, is what Pondera delivers as the Feasibility Study Standard at $550 in five business days. The fee is the same whether the recommendation is proceed or do not proceed. That commitment is the product.
If the question on your desk is whether to commit the capital, scope the study to the decision and let it tell you the truth.