Feasibility Software That Turns A Parcel Into A Defensible Pro Forma

Feasibility is the go/no-go call on a specific parcel with a specific program. It stacks hard cost, soft cost, contingency, permit timing, and exit value into an ROI range, and it returns a verdict — pencils, does not pencil, or pencils under specific conditions. It is the artifact a principal reads before signing an LOI.

This feasibility software is calibrated for the pre-acquisition and pre-development window, not for institutional underwriting. Institutional underwriting requires a full financial-modeling package with debt, equity, waterfalls, and returns modeling; that is a different tool. Feasibility is the earlier step — is this parcel worth the institutional-underwriting effort in the first place.

What a feasibility study has to contain

Six components. (1) Parcel record and buildable envelope. (2) Intended program — unit count, mix, size, quality tier. (3) Hard cost, priced against the local labor and materials market. (4) Soft cost, sized as a percentage of hard cost with the components (design, permits, legal, financing) broken out. (5) Contingency, sized against the program's uncertainty level. (6) Timeline — permit, construction, and lease-up or sale, priced with financing carry. The feasibility verdict comes from stacking those six into an ROI range and comparing to a target return. A range that clears the target under most scenarios is a pencils verdict; a range that clears the target only under optimistic scenarios is a conditional pencils; a range that fails to clear even under optimistic scenarios is a does-not-pencil.

Scenarios, not point estimates

A feasibility verdict built on point estimates is fiction. The hard cost is a range, not a number. The permit timeline is a range, not a number. The exit value is a range, not a number. The pro forma has to stack the ranges and return a range for the ROI — with an explicit sensitivity view showing which input drives the outcome most. The software runs the scenarios automatically. The output is not one number; it is a distribution with the tenth-percentile, fiftieth-percentile, and ninetieth-percentile ROI. The principal reads the distribution, not the point.

Sensitivity analysis

The sensitivity view identifies which input variable has the largest impact on the outcome. On most development pro formas the answer is exit value — a five-percent move in the exit value produces a much larger swing in ROI than a five-percent move in hard cost. Knowing that shapes the diligence priorities: an exit-value-driven pro forma needs a rigorous comps analysis; a hard-cost-driven pro forma needs a rigorous GC bid. This is the analytical layer that most feasibility spreadsheets skip. The scenarios exist in the spreadsheet as separate tabs, but nobody looks at the tabs side-by-side to see which lever actually matters. The software surfaces the sensitivity by default.

The feasibility PDF

The output is a branded feasibility PDF. It contains the parcel record, the intended program, the six components, the scenario distribution, the sensitivity view, and the verdict. A principal reads it in five minutes and can defend the go/no-go call to a capital partner. The PDF is what an analyst historically built manually over a day or two per parcel. The software produces it as a byproduct of running the scenarios, which is what lets a team scale feasibility across ten or fifteen parcels a week instead of two.

When to use feasibility software vs. a full underwriting tool

Feasibility answers 'is this worth underwriting.' Underwriting answers 'is this worth financing.' The two tools live at different stages and have different depth. Feasibility runs on every LOI candidate; underwriting runs on the parcels the LOI closed on. Some teams try to use one tool for both. It never works — feasibility becomes too heavy to run on volume, or underwriting becomes too light to satisfy the lender. Two tools, two stages, one project record connecting them is the pattern that scales.

A real-world workflow: a Friday-afternoon go/no-go on three LOI candidates

A developer has three LOI candidates on the desk Friday afternoon: a 6-unit duplex-plus-fourplex assembly at $780K, an 18-unit garden multifamily at $2.4M, and a mixed-use with ground-floor retail at $1.9M. Each needs a feasibility verdict by Monday. Historically the analyst spent the weekend building three spreadsheets. On the feasibility software each parcel runs in about 8 minutes. Parcel A returns a distribution: p10 ROI 12%, p50 ROI 19%, p90 ROI 26% — pencils under most scenarios. Parcel B returns p10 8%, p50 15%, p90 22% — pencils conditional on rent growth assumptions. Parcel C returns p10 4%, p50 11%, p90 18% — does not pencil against the firm's 18% target. Verdicts land in 25 minutes; the weekend is free.

Implementation guidance for feasibility rollout

Set the target return in week one. Most developers set an unlevered p50 target between 15% and 22% depending on the market and asset class. The target drives the pencils/conditional/does-not-pencil verdict logic; without it, feasibility outputs a distribution but not a decision. The failure mode is running feasibility only on the parcels that look good. Feasibility is most valuable on the parcels that look good but shouldn't; the discipline is to run it on every LOI candidate, not just the ones the analyst is excited about. Teams that skip feasibility on 'obvious wins' find themselves with a portfolio of pro formas that assumed different contingency policies and different cost bands.

A real-world workflow: a Friday-afternoon go/no-go on three LOI candidates

A developer has three LOI candidates on the desk Friday afternoon: a 6-unit duplex-plus-fourplex assembly at $780K, an 18-unit garden multifamily at $2.4M, and a mixed-use with ground-floor retail at $1.9M. Each needs a feasibility verdict by Monday. Historically the analyst spent the weekend building three spreadsheets. On the feasibility software each parcel runs in about 8 minutes. Parcel A returns a distribution: p10 ROI 12%, p50 ROI 19%, p90 ROI 26% — pencils under most scenarios. Parcel B returns p10 8%, p50 15%, p90 22% — pencils conditional on rent growth assumptions. Parcel C returns p10 4%, p50 11%, p90 18% — does not pencil against the firm's 18% target. Verdicts land in 25 minutes; the weekend is free.

Implementation guidance for feasibility rollout

Set the target return in week one. Most developers set an unlevered p50 target between 15% and 22% depending on the market and asset class. The target drives the pencils/conditional/does-not-pencil verdict logic; without it, feasibility outputs a distribution but not a decision. The failure mode is running feasibility only on the parcels that look good. Feasibility is most valuable on the parcels that look good but shouldn't; the discipline is to run it on every LOI candidate, not just the ones the analyst is excited about. Teams that skip feasibility on 'obvious wins' find themselves with a portfolio of pro formas that assumed different contingency policies and different cost bands.

Reading and defending a feasibility distribution to a capital partner

The feasibility distribution is the artifact a capital partner reads to underwrite the developer's underwrite. A p10/p50/p90 distribution is more useful to a sophisticated partner than a point estimate because it exposes the underlying uncertainty rather than hiding it. Reading the distribution: the p50 is the honest expected outcome; the p10 is the downside case that determines whether the deal can survive a bad scenario; the p90 is the upside that motivates the deal. The spread between p10 and p90 signals uncertainty — a narrow spread on a well-scoped project, a wide spread on a project with unresolved variables. Defending the distribution: every input's range is traceable to a source. The cost range comes from the metro's construction-cost distribution; the timeline range comes from the jurisdiction's permit-timing distribution; the exit range comes from the comps. When a partner asks 'why is the p10 so low,' the answer is the specific input driving the tail, not a hand-wave.

Use Cases

  • Six-component stack: Parcel, program, hard cost, soft cost, contingency, and timeline — the components a defensible feasibility requires.
  • Range-based inputs: Every input is a range; the ROI is a distribution with p10, p50, and p90 — no point-estimate fiction.
  • Sensitivity view: Which variable moves the ROI most — the input that drives where diligence priorities go.
  • Branded feasibility PDF: Principal-ready output with parcel, program, distribution, sensitivity, and verdict — five-minute read.
  • Verdict logic: Pencils / conditional / does-not-pencil with the explicit conditions attached — no vague scoring.
  • Target-return verdict logic: Firm-configured target return drives pencils/conditional/does-not-pencil verdicts; verdicts include the specific conditions where applicable.
  • Weekend-free feasibility batch: Multiple LOI candidates run in parallel on Friday afternoon; verdicts land in minutes rather than requiring the weekend.
  • Target-return verdict logic: Firm-configured target return drives pencils/conditional/does-not-pencil verdicts; verdicts include the specific conditions where applicable.
  • Weekend-free feasibility batch: Multiple LOI candidates run in parallel on Friday afternoon; verdicts land in minutes rather than requiring the weekend.

Frequently Asked Questions

How can developers reduce due-diligence time?
By running feasibility on every LOI candidate before diligence starts, so diligence is only paid for on parcels that clear the feasibility bar.
Why choose software instead of spreadsheets for feasibility?
Spreadsheets model point estimates. Feasibility requires distributions and sensitivity — the analytical layer spreadsheets skip.
What information should be available before purchasing land?
The feasibility verdict — pencils, conditional, or does-not-pencil — with the conditions attached. Offering on a parcel without a feasibility verdict is offering on hope.
How can developers reduce due-diligence time?
By running feasibility before diligence is scoped. Parcels that fail feasibility never enter the paid-diligence pipeline; the diligence budget stays focused on parcels with a real chance of closing.
How can Buildora IQ streamline pre-development workflows?
By producing the feasibility verdict at the resolution the principal needs — a distribution with a verdict, not a spreadsheet with a point estimate. The verdict is the anchor pre-development builds against.
How can developers reduce due-diligence time?
By running feasibility before diligence is scoped. Parcels that fail feasibility never enter the paid-diligence pipeline; the diligence budget stays focused on parcels with a real chance of closing.
How can Buildora IQ streamline pre-development workflows?
By producing the feasibility verdict at the resolution the principal needs — a distribution with a verdict, not a spreadsheet with a point estimate. The verdict is the anchor pre-development builds against.
What information should be available before purchasing land for a feasibility-driven decision?
The distribution not just the point estimate, the sensitivity analysis, and the underlying source citations for each input range. A partner reading the feasibility should be able to interrogate each range to its source.
Is this a full pro forma?
It is a pre-underwriting feasibility. The output feeds a full pro forma; it does not replace one. Institutional underwriting requires a deeper modeling package.
Can I customize the target ROI?
Yes. The target return is a project setting; verdicts are calculated against it.
Does the software model debt and equity?
Feasibility models the total cost and the total exit — the returns are on total capital. Debt-equity waterfalls live in the downstream underwriting tool.
How is the exit value calculated?
From the metro's comps for the asset class, adjusted for the intended program's unit sizes and quality tier. The comps grid is visible with the feasibility.
How is contingency sized?
Contingency is a percentage of hard cost, tuned to the program's uncertainty level — ground-up gets a larger contingency than value-add, and a discretionary-entitlement pro forma gets more than a by-right pro forma.
Can I run scenarios with different quality tiers?
Yes. Quality tier is a program setting; running the same parcel at three quality tiers is a common exploration.
How is the p10/p50/p90 distribution derived?
From Monte Carlo simulation over the input ranges: cost, timeline, exit value, contingency utilization. The simulation runs 10,000 iterations by default; the percentiles report the outcome distribution.
Can I model a preferred-return waterfall?
Feasibility models unlevered returns on total capital. Waterfall modeling with preferred returns and promotes lives in the downstream underwriting tool.
How is the exit value sensitivity separated from the cost sensitivity?
The sensitivity view displays the ROI response to each input variable separately. Teams identify the dominant variable (usually exit value or cost) and prioritize diligence accordingly.
How is the p10/p50/p90 distribution derived?
From Monte Carlo simulation over the input ranges: cost, timeline, exit value, contingency utilization. The simulation runs 10,000 iterations by default; the percentiles report the outcome distribution.
Can I model a preferred-return waterfall?
Feasibility models unlevered returns on total capital. Waterfall modeling with preferred returns and promotes lives in the downstream underwriting tool.
How is the exit value sensitivity separated from the cost sensitivity?
The sensitivity view displays the ROI response to each input variable separately. Teams identify the dominant variable (usually exit value or cost) and prioritize diligence accordingly.
Can I customize the confidence-interval percentiles?
Yes. Some firms prefer p20/p50/p80 for a tighter uncertainty view; others prefer p5/p50/p95 for a fatter-tail view. The percentiles are configurable per project.
How is the exit value range calibrated to the specific parcel?
The comps grid selects three-to-five most-relevant properties; the exit range is the distribution of those comps adjusted for the specific parcel's location within the metro.

Related Resources

Get Started

Buildora IQ analyzes any property and generates floor plans, cost estimates, and feasibility reports in minutes — done in under 2 minutes. Start free See all features.