A Few Polygons

A whole development feasibility hangs off a handful of shapes on a map. That isn't a limitation. It's the design.

Draw a rectangle on a parcel. Give it a height and a use. You have made almost nothing — a few polygons, a number or two — yet you have said the only thing about a building that matters before it exists: where it sits, how big it is, what it does. Design intent, stripped to its core.

Most software captures the opposite. A BIM model is heavy by construction — thousands of objects, a faithful description of what a building is. It answers a question you can only ask once the scheme is settled. At feasibility the scheme isn't settled; it's the thing you're trying to find. The heavy model arrives too late to help you choose and too expensive to discard when you were wrong.

Intent is lighter than description. A massing polygon doesn't claim to be the building. It claims what the developer means to do with the site, in a form small enough to move — drag it, split it, raise it, change its use in a second. Twenty development scenarios in an afternoon is a different decision than one scheme in a fortnight, and optionality is the whole game at feasibility.

What the polygon feeds

The lightness would be worthless if the polygon just sat there. Each one is a handle the algorithms take hold of. Footprint and height become gross floor area, unit mix, and yield. The boundary is tested against setbacks, height planes, and zoning controls. Area draws a construction cost; use and yield draw a value; the two resolve into a residual land value and an IRR. A few coordinates, and a pro forma falls out.

The intent is tiny. The economic consequences are not. That gap is the platform.

This is the tri-linkage at work. Geometry, zoning, and finance read from the same shape, so moving the polygon moves all three at once — push the massing up a floor and the yield rises, a height plane may break, the land value re-prices, instantly and together, with no re-keying between three tools and three consultants. Because intent lives as data, that same polygon can also feed a solar study, a traffic count, an embodied-carbon estimate, or a model built on the SDK. The shape is generic on purpose; the analysis is where the specificity goes.

So a masterplan in Giraffe stays light by design — not because it can't hold detail, but because the feasibility decision doesn't need it. It needs intent expressed fast, tied to money tightly, cheap to change. A few polygons carry the intent; the algorithms turn it into an economic case.

This is lightweight thinking, not shallow thinking. Lotus built fast cars by taking things out — Colin Chapman's rule was simplify, then add lightness. Tesla stripped the dashboard to a single screen. In both, removing the inessential is what produced clarity and speed at once, not a trade of one for the other. A feasibility model wants the same discipline: hold only what the decision turns on, and the answer comes both faster and clearer. That is what Giraffe is aiming for.