Numbers alone don't make decisions. Here's what they mean in practice.
Viability is not a single number — it is a combination of metrics that together paint a picture of whether a development project is worth pursuing. Different thresholds apply depending on the type of project, the market, and the developer's risk appetite.
As a starting point, here are the benchmarks most professionals use when evaluating a development appraisal:
But context always matters. A 12% RoC in a low-risk market with pre-sales may be safer than a 25% RoC in an untested location with no comparable evidence. Your risk profile, market conditions, and track record all influence what "viable" means for you.
There is no universal "good" number. Viability is the combination of return metrics, risk profile, and market context. Use benchmarks as a starting point, not as absolute rules.
Even a project that looks profitable on paper can carry hidden risks. The appraisal dashboard surfaces these risks through specific metrics and patterns. Knowing what to look for can prevent costly mistakes.
These warning signs rarely appear in isolation. A project with thin margins and high peak funding is significantly riskier than one with just thin margins alone. Always look at the full picture.
Watch for combinations of warning signs. A single weak metric might be manageable, but multiple warnings together indicate structural risk in the project.
The same appraisal tells different stories depending on who is reading it. Each stakeholder focuses on different metrics because they carry different risks and have different objectives.
Focuses on Profit, RoC, and IRR. The core question: "Is this worth my time and capital?" Developers need to see that the return justifies the risk, effort, and opportunity cost of tying up their equity.
Focuses on LTV, LTC, and sensitivity analysis. The core question: "What is my downside exposure?" Lenders want to know their loan is safe even if things go wrong — they care about the floor, not the ceiling.
Focuses on scenarios and sensitivity. The core question: "What should I advise my client?" Consultants need to present a balanced view of upside potential and downside risk across multiple assumptions.
Focuses on IRR, MOIC, and equity requirement. The core question: "What is my return on capital?" Investors compare this project against other opportunities and need to see efficient use of their equity.
Understanding your audience changes how you read and present the same data. A developer might celebrate a 25% RoC, but a bank reviewing the same project will focus entirely on what happens in the downside scenario.
Know your audience before presenting results. The same project data supports different narratives depending on whether you are talking to a developer, lender, consultant, or investor.
The base case is your best estimate — but real estate development rarely goes exactly to plan. Sensitivity analysis tests what happens when your assumptions are wrong, and that is where the real insight lives.
Consider two projects:
Which project would you rather build? The answer depends on your risk tolerance, but the point is clear: the base case alone does not tell you enough. Sensitivity analysis reveals how robust your project truly is.
The sensitivity heatmap in Profivo tests two variables simultaneously across a range of values. The more green cells you see, the more resilient the project. A heatmap dominated by red means small changes push the project into loss territory.
The base case tells you what could happen. Sensitivity tells you what could go wrong. Always check both before making a decision.
Profit and cash flow are two fundamentally different concepts, and confusing them is one of the most common mistakes in development appraisal. A project can be profitable on paper but still run out of cash during construction.
Profit is the final number: total revenue minus total costs. It tells you what you earn when the project is complete. Cash flow is about timing — when money comes in and when it goes out. During construction, costs accumulate every month while revenue typically arrives only after units are complete and sold.
This timing gap creates a funding requirement. The peak funding metric in Profivo shows the maximum amount of cash your project needs at any point during its lifecycle. This is the real capital requirement — the money you need access to, whether through equity, debt, or a combination.
The break-even month shows when cumulative revenue finally exceeds cumulative costs. Until that point, the project is consuming cash. After that point, it starts paying back. If break-even comes later than expected — because sales are slow or construction is delayed — you need more capital for longer.
Profit is theoretical. Cash flow is survival. Always check peak funding and break-even month alongside profit to understand the real financial demands of your project.
The same data can support or undermine your case depending on how you present it. Different audiences need different entry points into the appraisal, and leading with the wrong metrics can derail a conversation before it starts.
Lead with headline metrics: Profit, Return on Cost, and IRR. These are the numbers that drive go/no-go decisions. Follow with a risk summary showing the downside scenario and key sensitivities. Boards want confidence that the team has stress-tested the assumptions.
Lead with LTV and LTC ratios — these are the metrics lenders use to evaluate their exposure. Show the sensitivity analysis to demonstrate downside protection, and emphasize conservative assumptions like contingency buffers. Banks care about getting their money back, not about your upside.
Lead with IRR, MOIC (Multiple on Invested Capital), and equity multiple. Investors compare opportunities, so time-weighted returns and capital efficiency matter most. Show them how their equity works and when they get it back.
Use the full dashboard with all scenarios for comprehensive decision-making. The internal team needs to understand every angle — from headline profitability to detailed cash flow timing to worst-case scenarios. This is where Profivo's complete view adds the most value.
Match your presentation to your audience. Lead with the metrics they care about most, then support with the detail they need to build confidence in the project.
See these metrics in action with your own numbers.