---
title: "What is pre-development software?"
description: "Pre-development software connects parcel facts, zoning, risks, project assumptions and deliverables before a real estate development commitment."
last_updated: '2026-10-10'
---

<!-- Generated by scripts/seo/sync-discoverability.mts; source-sha256: e8182ce7f1876ada5770f03a8b93b2b159bc3a91fd8c60d42e60eb60854605ec -->

# What is pre-development software?

Pre-development software helps real estate teams evaluate a property before committing to acquisition, design or approvals. It brings parcel facts, local rules, site risks, program options and financial assumptions into a shared decision process.

Useful outputs include a sourced feasibility report, a go/no-go brief and a list of unresolved questions for professional review.

## What jobs does it cover?

Site screening starts with the parcel, jurisdiction and applicable zoning. Feasibility adds constraints, a proposed program, costs and financial assumptions. Teams compare scenarios and preserve the evidence behind a decision.

Deliverables tell clients, lenders, municipal staff and project partners what is known, what is assumed and what needs confirmation. The workflow comes before construction scheduling and site supervision.

## What should you check before choosing a platform?

Citation granularity: can you open the source and identify the provision behind a rule? Published coverage: can you check your municipality and address before paying?

Freshness: does each record show its date and source, and are amendments acknowledged? Exports: do reports retain citations, assumptions and unresolved questions instead of presenting every number as a fact?

Financial assumptions should remain editable and distinct from sourced zoning facts. A permitted envelope alone does not establish that a scheme is physically practical, financially viable or approved.

## How the capability categories compare

Tools in this category cover one or more of four capabilities. Compare them by what each one answers and how it shows its sources.

Pre-development capabilities, what to check, and what Bucky covers

| Capability | What it answers | What to check | Bucky |
| --- | --- | --- | --- |
| Zoning lookup | Which zone applies to a parcel, and the numeric rules for that zone. | Does each value link to the bylaw section that sets it? Does it say when a value is conditional, not extracted or changed by an overlay map? | Yes, where the municipality is live. Each value carries a section citation and a status such as cited, conditional or not extracted. |
| GIS and parcel data | Where the lot is: its boundary, area, identifier and the mapped overlays that touch it. | Is the parcel source named? Are overlays checked separately from the base zone? | Yes: parcel boundary, area and identifier from municipal records, and overlay checks where the municipality publishes them. Bucky is not a GIS editor, and a parcel boundary is not a survey. |
| Site intelligence | What the parcel facts, local rules and constraints mean together for one site. | Are unknowns kept apart from sourced facts? Can you see which facts are missing for the address? | Yes: one address returns the parcel, zone, envelope and coverage status together, and marks what is missing. |
| Feasibility and pro forma | Whether a proposed program fits the site, and what it could cost and return. | Are financial assumptions editable and kept apart from sourced zoning facts? Do exports keep citations and open questions? | Yes: project analysis tests a program against the site, with editable pro forma assumptions and PDF or CSV export. Cost and market inputs are assumptions to review, not appraisals. |

## What Bucky does not do

Bucky does not manage construction, schedules or site supervision. It does not produce architectural or construction drawings, and it does not issue permits or approvals.

It does not replace a survey, an appraisal, a legal opinion or a professional’s signed work. Coverage varies by municipality and data layer, so check the address before you rely on a result.

## How Bucky supports the workflow

Bucky turns an address into sourced site intelligence, project analysis and decision-ready deliverables. Teams can use the web workspace or connected agent tools to inspect coverage, screen a site and preserve the work in project context.

Start with coverage for the actual address, review the methodology, and then test the proposed program. Coverage varies by municipality; a professional remains responsible for decisions and signed work.

## Common questions

### What is the difference between site intelligence and feasibility?

Site intelligence describes the property, rules and constraints. Feasibility tests a proposed project against those facts and explicit program and financial assumptions.

### Does pre-development software replace a planner or architect?

No. It supports research, scenario testing and communication. Professional judgment and municipal approvals remain separate.

### Where should I start?

Check coverage for the address, inspect the sources behind local rules, and identify the unknowns that could change your decision.

## Sources

- [Bucky: how Bucky sources and cites local rules](https://buckybuild.com/en/methodology)

[Glossary](https://buckybuild.com/en/glossary) · [Coverage](https://buckybuild.com/en/coverage) · [Methodology](https://buckybuild.com/en/methodology) · [MCP](https://buckybuild.com/en/mcp)
