How to run a financial feasibility analysis in Giraffe

Use the Analytics app (right-hand panel) to build a full financial feasibility model for your scheme — revenue, construction costs, and profit, all driven by what you draw on the map.

Before you start: import the Australian Developer Feasibility template

The Australian Developer Feasibility pack is available for paid accounts. Reach out to sales for access.

The fastest way to dive in is using a template. You can find some preconfigured Analytics templates in the content library.

To load one: go to Content Library, search, then select the Australian Developer Feasibility Pack, and click Import.

⚠️ Do this at the very start of your project. Importing a template replaces your existing usages. When prompted, choose Replace (not Keep Both) — this wipes any assumptions you've already entered, so import before you start configuring anything else.

Understand the Australian Developer Template layout

Once imported, Analytics behaves like a spreadsheet, with tabs across the top:

Tab	What it shows
Default	Your profit & loss
Area	Site, GBA, GFA, and NSA areas by usage
Metrics	Summary stats — parking spaces, unit counts, net rent by usage
Inputs	Global assumptions that apply across the whole model (like the "yellow cells" in an Excel model)

Set up your grouping

Analytics works like a pivot table — you choose how to split results into columns (by phase, building, or usage). Grouping by layer or layer group is usually the clearest approach.

Each layer becomes its own column. Renaming a layer (e.g. to "Scenario 1") relabels its column accordingly.
Duplicating a layer lets you compare scenarios side by side — hide one to isolate the other on the map.

⚠️ If grouping is set to "no grouping," Giraffe adds all layers together, which will double-count your numbers. Always confirm grouping is set correctly before entering assumptions.

To exclude a layer entirely (e.g. a reference/design library layer you don't want counting toward totals), go to the settings icon → hide layer.

Understand where your numbers come from

Every property in your model comes from one of two places:

The usage — assigning a usage (e.g. Residential, Commercial) to a geometry brings in a full set of default properties (efficiency, parking rates, hard costs, sale price, etc.).
The geometry itself — you can also add a property directly to an individual building.

If a property is set in both places, the value on the geometry always overrides the usage default.

Giraffe also auto-calculates geometry-based values — like area or unit count — directly from what's drawn, and feeds these into your formulas.

Tip: Click any number in the P&L to see its formula and trace exactly where it's pulled from (a usage default, a geometry override, or a calculation based on the drawn area).

Enter your assumptions

Start with Usages — set efficiencies (GBA→GFA, GBA→NSA) and core assumptions like hard costs, rent, yield, outgoings, and lease term for each usage type.
Click the save icon in the usage editor after any change — updates won't flow through to Analytics otherwise.
Override at the building level if a specific building needs different assumptions than the usage default (e.g. a premium sale price on one tower).
Check the Inputs tab for assumptions that apply globally regardless of usage — professional fees, land value, design costs, sales & marketing costs, etc. Click a title (not the number) to edit these.

Reading formulas

Click any number in the model to see how it's calculated. You'll typically see one of three formula types:

Per-feature formulas — pulled directly from the map (e.g. area × sale price)
Totals/subtotals — sums of a section (e.g. gross revenue = sum of all revenue lines)
Derived formulas — built from numbers already calculated elsewhere in the model (e.g. professional fees = total construction cost × fee %)