Development Pro Forma: What to Track Before Ground Breaks

A defensible development pro forma tracks six categories of pre-development data that most developers model once and never revisit, including land and acquisition costs with closing-date actuals, hard cost estimates validated against current subcontractor bids, soft cost allocations tied to permit timelines and local fee schedules, financing assumptions stress-tested at today’s rates, contingency reserves sized to project complexity, and a revenue model grounded in comparable lease or sale data rather than aspirational pricing. 

When these inputs are structured correctly from pre-development and carried forward into execution, the pro forma becomes a live financial control tool rather than a static planning artifact. Developers using platforms like Built that connect pro forma assumptions to real-time budget tracking report 80% faster capital cycles and catch budget variances before they compound across the project lifecycle.

What Is a Development Pro Forma?

A development pro forma is a financial model that projects all costs, revenues, and profitability for a real estate development project from acquisition through stabilization. It’s the document investors, lenders, and equity partners use to decide whether a deal pencils.

Most developers think of it as a spreadsheet exercise. It isn’t. The pro forma is the financial DNA of the project. Every capital call, every draw request, every investor distribution ties back to assumptions made here. When those assumptions are wrong or outdated, the entire capital structure starts drifting.

A complete pro forma covers two phases. The first is the development phase, which includes land acquisition, pre-development costs, hard and soft construction costs, financing, and contingency. The second is the operating phase, involving projected net operating income (NOI), vacancy and absorption assumptions, debt service, and long-term returns.

The key metrics that drive decisions include internal rate of return (IRR), equity multiple, yield on cost, and cash-on-cash return. Lenders focus on loan-to-cost and debt service coverage. Equity partners focus on IRR and preferred return hurdles. A pro forma that can’t speak to both sides of the capital stack doesn’t close deals.

What Belongs in a Development Pro Forma

Every pro forma starts with the same building blocks. The difference between a defensible one and a fragile one is how precisely each line item reflects current market conditions rather than assumptions from the last project.

• Land and acquisition costs: Purchase price, closing costs, title and survey, environmental reports, demolition, and any earnest money or option payments. These aren’t estimates. They should be actuals the day the deal closes.
• Hard costs by trade: Site work, concrete, structural steel, framing, mechanical/electrical/plumbing (MEP), building envelope, interiors, and finish packages. Cost codes should align with AIA G702/G703 billing format from the start. When your cost structure matches how your GC bills, draw reconciliation doesn’t require manual translation.
• Soft costs: Architecture and engineering (A&E) fees, legal, permits, impact fees, utility connections, environmental compliance, marketing, and leasing commissions. Soft costs are where most pro formas underperform because developers anchor to prior project percentages rather than current local fee schedules.
• Developer fees: Typically 3%-5% of total project cost. Structure and timing matter for tax purposes, especially in Low-Income Housing Tax Credit (LIHTC) and affordable housing deals with complex capital stacks.
• Financing costs: Construction loan interest (carried as an interest reserve), origination fees, loan processing costs, and debt service during lease-up. If mezzanine or preferred equity is part of the capital stack, the cost of that capital belongs here too.
• Contingency: A hard cost contingency of 5%-10% is standard, but the right number depends on project type and complexity. This is insurance against the assumptions you got wrong, and every pro forma has some.
• Revenue projections: Rent roll by unit or suite, absorption timeline, vacancy rate during lease-up, concessions, and projected stabilized NOI. For-sale projects replace rent with projected sale prices, absorption pace, and closing cost assumptions.

Pre-Development Assumptions That Make or Break Your Numbers

The pro forma is only as good as the assumptions behind it. Here’s what to track and validate before you put a shovel in the ground.

1. Land basis with closing-date actuals

Replace your indicative offer price with the actual acquisition cost the day you close. Include every cost incurred to control the site, including option payments, earnest money, title, survey, environmental Phase I and Phase II reports, and legal fees associated with purchase. A $200K gap between your modeled land basis and actual closing costs flows directly into your return calculations.

2. Hard cost validation via current bids, not historical benchmarks

A concrete bid from 18 months ago isn’t a concrete bid today. Validate every major trade line against current subcontractor pricing. If your GC is providing a guaranteed maximum price (GMP), make sure the buyout schedule is reflected in the pro forma timeline. If you’re using construction management at risk, build in the variance range.

3. Soft cost timeline alignment with permit schedules and local impact fees

Permit timelines vary wildly by jurisdiction. A four-month permit assumption in a municipality that’s averaging nine months adds five months of carry cost your pro forma didn’t model. Pull actual permit processing times for your jurisdiction. Check current impact fee schedules, utility connection costs, and any special assessments. These change year over year and differ by project type.

4. Interest rate stress testing at +100-200 basis points

Here’s where pro formas break most often. For example, a $35M mixed-use development with four equity partners, a construction lender, and two mezzanine sources. The original pro forma modeled interest at 5.5%. By the time permits cleared eight months later, rates had moved to 7.25%. That shift alone added $630K in carry costs the original model didn’t account for.

Stress-test your financing assumptions at 100 and 200 basis points above your base case. If the deal doesn’t work at +200 bps, you need to understand that before you close on the land, not after.

5. Contingency sizing by project type

Not all contingency is created equal. Standard ranges by project type include the following:

• Rehab/renovation: 5% of hard costs
• Ground-up, single use: 7%-10% of hard costs
• Complex mixed-use or adaptive reuse: 10%-15% of hard costs

Undersizing contingency is the most common way developers manufacture returns that don’t survive execution. A pro forma with 3% contingency on a ground-up mixed-use project is just  fiction.

6. Revenue assumptions with comparable data

Don’t model revenue from the top down. Start with comparable lease or sale data from the submarket. Adjust for unit mix, finish level, and concession packages. If your rent assumptions exceed the top of the comp set by more than 10%, document why. Lenders and equity partners will ask.

For-sale projects need comparable sale prices per square foot, projected absorption pace, and realistic closing timelines. Optimistic absorption assumptions are the revenue-side equivalent of undersized contingency.

How to Keep Your Pro Forma Defensible During Execution

The transition from planning to execution is where most pro formas die. The model that closed the deal sits in a shared drive while the project runs on a different set of numbers. Here’s how to prevent that.

• Monthly review cadence, not quarterly: Construction moves fast. Material costs shift, change orders stack up, and permit delays compound. A quarterly review means you’re looking at 90 days of accumulated drift. Monthly reviews catch variance while it’s still correctable.
• Change order impact assessment: Every change order should be evaluated against the original pro forma, not just the current budget. A $150K change order on a $40M project looks manageable in isolation, but if it’s the fourth change order this quarter, and the contingency line is already 60% consumed at 30% completion, the pro forma is telling a different story than the budget.
• Budget-vs.-actual tracking in real time: The pro forma projected costs. The budget allocated them. Actual spending reveals whether those projections hold. When these three data points live in separate systems (or separate spreadsheets on separate desktops), nobody sees the full picture until it’s too late to adjust.

For construction CFOs managing accounts payable cycles across five or more active projects, the question is whether you’ll catch a pro forma drift before the lender does. Every draw package that goes out with numbers that don’t reconcile to the original pro forma is a credibility problem waiting to surface.

For owners managing a portfolio, the risk is the aggregate drift across all projects when each one runs on a different spreadsheet with a different version of the truth. One project at 8% over budget is a conversation. Five projects each 3% over is a pattern your capital partners will notice.

Lender reporting alignment

Your pro forma, your budget, and your draw requests should tell the same story. When the lender’s construction monitoring report flags a variance you didn’t know about, you’ve lost control of the narrative. Align your internal reporting cadence with your lender’s draw and inspection schedule.

Common Pro Forma Mistakes That Erode Project Margin

Even experienced developers make assumptions that look reasonable at the time but erode margin through execution.

• Using stale cost estimates from prior projects: A per-square-foot cost from a project that broke ground 14 months ago doesn’t reflect today’s labor market, material costs, or subcontractor availability. Every pro forma deserves fresh bids for its top five cost lines.
• Underestimating soft costs: Permits, impact fees, and utility connections are the line items developers most frequently undercount. In some municipalities, impact fees alone can run $15,000-$25,000 per unit on a multifamily project. If your pro forma uses a flat percentage from a different jurisdiction, you’re likely underbudgeted.
• Best-case timeline assumptions with no buffer: A 16-month construction schedule with no weather days, no permit delays, and no material lead-time issues is a best case, not a base case. Every month of delay carries interest, insurance, and overhead. Build timeline contingency the same way you build cost contingency.
• Failing to stress-test financing assumptions: The interest rate environment at deal sourcing may not match the rate environment at closing or during construction. Pro formas that model a single rate scenario without sensitivity analysis are fragile by design.
• Building the pro forma once and never updating it: This is the most damaging mistake because it’s invisible until it compounds. Manual draw packages carry a 3%-5% error rate. Each error triggers a lender question, then a resubmission, then more days on the clock. Over a 14-month project, that pattern of small errors and small delays can shift total project cost by hundreds of thousands of dollars. And a single lien event from a missed compliance step can cost $50K-$500K, wiping out margin that was already thin.

Why the Pro Forma vs. Budget Distinction Matters

A development pro forma is a pre-development financial projection used to evaluate project feasibility and secure financing. A construction budget is an execution-phase spending plan derived from the pro forma, organized by cost code and used to manage actual expenditures against approved line items.

When these two documents disconnect, you lose visibility into whether the project is meeting its original financial targets. The budget may show you’re on track for the month, but if the underlying pro forma assumptions have shifted (rates moved, timeline extended, soft costs exceeded the original model), the budget alone won’t tell you.

This is where most developers lose control. The pro forma closes the deal. The budget runs the project. However, nobody is tracking whether the project that’s being built still matches the project that got financed. The fix is a system that connects the pro forma to the budget to the actual spending in real time, so the numbers your lender sees match the numbers your team is working from.

How Built Connects Your Pro Forma to Project Execution

Built is the platform that keeps your pro forma connected to what’s actually happening on the project. From the first deal you evaluate through stabilization, every financial assumption you make is tracked, validated, and visible to the people who need it.

• Deal pipeline management: Built’s AI pulls key data from offering memorandums (OMs) automatically, cutting manual data entry on deal intake by roughly 90%. Every deal is tracked from first look through closing. Investment committee (IC) memos and letters of intent (LOIs) generate from deal data in minutes, not days.
• Capital stack modeling: Model waterfall structures, pro rata distributions, and pari passu arrangements across multiple funding sources. Map every source to a single budget. Track sources and uses in real time from pre-development through stabilization. When the capital stack has four equity partners, a construction lender, and mezzanine debt, you need a system that handles the complexity without manual reconciliation.
• Budget management: Budget vs. actual is live, not assembled. Built’s AI flags line items trending over budget before the invoice gets approved, not after the draw goes out. You see variance when it’s still correctable. On a $50M project at 6% interest, every week a draw sits unprocessed costs roughly $5,800 in carry. That’s why 60% less admin work and 75% less time on audit prep create margin protection.
• Excel Add-In: Analysts keep their existing underwriting models in Excel. Built adds the data layer and version control with bidirectional sync. Your underwriting model stays current without manual updates.
• Full lifecycle coverage: Pre-development through stabilization on a single platform. With $317B+ in real estate dollars on its platform and 300+ lenders already connected, Built means your draw submissions, compliance documentation, and lender reporting run through the same system your lender is already using. That eliminates the translation layer between your numbers and theirs.

MiKen Development, for example, grew from building four houses to managing 250+ with Built. CFO Andrew Newby put it directly: “Built has been a part of our growth and, from a financing perspective, allows us to take on more projects.”

That’s the real measure. It’s not whether the real estate development software saves time on any single task, but, rather, whether it gives you the capacity to take on the next project without adding headcount or complexity. For developers managing a portfolio across the full real estate project lifecycle, that capacity is the difference between growing and grinding.

See It In Action.

Development Pro Forma FAQs

What is a development pro forma?

A development pro forma is a financial model that projects all costs, revenues, and returns for a real estate project from land acquisition through stabilization or sale. It includes hard costs, soft costs, financing, contingency, and revenue assumptions. Lenders and equity partners use it to evaluate whether a deal is financially viable before committing capital.

How do you keep a pro forma accurate during construction?

Review it monthly, not quarterly. Compare actual costs against the original pro forma assumptions (not just the current budget) and assess every change order for its impact on total project returns. Align your internal reporting cadence with your lender’s draw and inspection schedule so the numbers always reconcile.

What assumptions should a development pro forma include?

A complete pro forma includes land acquisition costs, hard costs by trade, soft costs tied to current permit and fee schedules, financing assumptions stress-tested at multiple rate scenarios, contingency reserves sized to project complexity, and revenue projections grounded in submarket comparable data.

What’s the difference between a pro forma and a construction budget?

The pro forma is a pre-development financial projection used to evaluate feasibility and secure financing. The budget is an execution-phase spending plan organized by cost code. The pro forma answers “Should we do this deal?” The budget answers “Are we spending within plan?” Both need to stay connected through execution.

What are the most common pro forma mistakes in real estate development?

The most frequent errors are using stale cost estimates from prior projects, underestimating soft costs (especially permits and impact fees), modeling best-case timelines with no buffer, failing to stress-test interest rate assumptions, and building the pro forma once without updating it through execution.

How does a pro forma connect to draw management in construction?

The pro forma sets the cost baseline. The budget allocates that baseline by cost code. Draw requests pull from the budget to request funding from the lender. When these three layers are connected, every draw submission reconciles back to the original financial plan. When they’re disconnected, variance compounds undetected.

How do lenders evaluate a development pro forma?

Lenders evaluate loan-to-cost ratio, debt service coverage, interest reserve adequacy, and the realism of cost and revenue assumptions. They compare your projected costs against third-party estimates and your revenue assumptions against market comparables. A pro forma with unsupported assumptions or missing sensitivity analysis raises immediate concerns about execution risk.