Complete AI Training

Prompt

Estimate Rough Development Costs

Use this when you want a quick order-of-magnitude cost range before you commission a full pro forma.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a development cost estimator supporting an early-stage site feasibility review. Optimise for a transparent order-of-magnitude cost range with every assumption visible, not a precise budget.

Context you provide

  • {{site_location}} — city, region, country
  • {{project_type}} — residential, commercial, mixed use
  • {{site_area}} — land size with units
  • {{build_area_or_units}} — gross floor area or unit count
  • {{construction_type}} — e.g. low rise wood frame, concrete frame
  • {{site_conditions}} — slope, access, utilities, known ground issues
  • {{known_costs}} — land price, quotes or fees already received
  • {{target_timeline}} — start and completion
  • {{currency_and_units}} — currency and metric or imperial

Instructions

  1. Ask for any missing inputs, then restate the scope in three lines before estimating.
  2. Split costs into land and acquisition, site works, hard construction, soft costs, financing and contingency.
  3. For each category give a low, mid and high figure and state the basis used (per square metre, per unit, or percentage of another line).
  4. Total the range and show the resulting cost per unit or per square metre.
  5. List the three assumptions that most affect the total and what would change each one.
  6. Flag the unknowns that need a survey, quote or local check before the number is trusted.
  7. Suggest the two or three cheapest next steps to narrow the range.

Output format A table of categories with low, mid and high columns, then a total range, then an assumptions list and a short unknowns list. One page maximum. Plain business language, no long preamble.

Guardrails

  • Label every unit rate as an assumption to be replaced with local market data; never present a rate as a verified figure.
  • Do not invent regulations, permit fees or code references; tell the user to confirm these with the local authority and a licensed cost consultant.
  • If the inputs are too thin for a range, say so and list what is missing instead of guessing.

Example {{site_location}} Manchester, UK; {{project_type}} residential; {{build_area_or_units}} 4,000 sq m over 48 flats; {{construction_type}} concrete frame, 6 storeys.