The point is not to say "Auckland is busy." The point is to compare public market movement with the firm's own benchmark so leadership can see whether the practice is actually improving, or simply getting busier because the wider market is getting busier.
Architecture firms often have useful signals scattered across unrelated places: consent data, tender notices, property listings, broker commentary, enquiry logs, proposal records, win/loss notes, project workload, margin, and staff capacity. On their own, those signals are hard to organise and easy to ignore.
This snapshot turns those disconnected signals into a simple business read. If the market is rising but the firm is not improving win rate, project quality, margin, or delivery capacity, then the firm may be growing with the market while weakening in relative terms. The reverse matters too: if the market is flat or falling but the firm is improving quality, margin, win rate, or delivery capacity, that may be evidence of real outperformance rather than simple market momentum.
The benchmark is the relationship between the market and the firm's current work stages:
- market signal;
- enquiry;
- qualified lead;
- proposal;
- win;
- active project;
- margin;
- capacity.
Each snapshot should compare external demand against those internal stages. Are more relevant enquiries arriving? Are enquiries becoming qualified proposals? Are proposals turning into better wins? Are active projects protecting margin? Is capacity still healthy? This is where unorganised, unrelated data becomes useful business insight.
The button on this page generates a dated Auckland market snapshot. In a real firm, this would normally arrive as an email snapshot rather than a web page.
The current browser preview shows:
- official Auckland and New Zealand consent signals;
- current GETS public tender signals;
- a deliberately simple example firm baseline;
- a benchmark layer for comparing market movement with firm-stage performance;
- source gaps that need connectors or manual review;
- a leadership-readable interpretation of what should be watched next.
This version uses sourced public counts rather than invented sample numbers.
- Stats NZ building consents for the official demand baseline.
- Stats NZ CSV data for regional, territorial, local-board, and non-residential consent signals.
- GETS current open-tenders RSS for public procurement and built-environment tender signals.
Current Auckland snapshot inputs include:
- 39,087 new dwellings consented nationally in the year ended April 2026, up 16 percent.
- 16,687 new dwellings consented in Auckland in the year ended April 2026, up 21 percent.
- 1,716 Auckland Region all-construction consents in April 2026.
- 528 April 2026 all-construction consents across the Auckland infill proxy areas used here.
- 19 current Auckland built-environment matches in the GETS open-tenders RSS feed.
- $8.9b national non-residential consent value in the year ended April 2026, down 0.4 percent.
The current page uses a deliberately simple example baseline: 22 staff, 7 active projects, and an 18 percent target margin. That is realistic enough for a browser preview of a mid-sized practice, but it is not a complete business metric by itself. A real firm would connect or manually enter its own benchmark and define exactly what margin means, such as gross project margin, contribution margin, operating margin, or another internal target.
Useful internal fields would include:
- monthly enquiry count;
- qualified-lead count;
- proposal count;
- win rate;
- average project value;
- preferred project types;
- active project load;
- margin by project type;
- staff capacity;
- delivery risk.
Without this internal layer, the snapshot can describe the market but cannot say whether the firm is outperforming it. The more realistic benchmark is the relationship across stages: demand, enquiry, qualified lead, proposal, win, active work, margin, capacity, and delivery risk.
Trade Me is the best first property-listing connector to investigate because it has a documented developer path.
- Trade Me Developer API is the starting point.
- A real version should register an application, get approved credentials, and follow Trade Me's API terms.
- Residential property should use the Residential Search API rather than generic scraping.
- Commercial sale and lease endpoints can be investigated for commercial opportunity signals.
- realestate.co.nz, Bayleys, Colliers, JLL, CBRE, developer websites, and broker reports should stay in the manual or permissioned-feed bucket until a documented access path is confirmed.
The real output should be short enough to read in an inbox:
- generated date and source freshness;
- market movement since the last snapshot;
- firm benchmark movement by stage;
- relationship between demand, enquiries, proposals, wins, margin, and capacity;
- what changed;
- what is missing;
- what leadership should review next.
The strongest version would run on a schedule, but also trigger when thresholds change: demand rises, proposal quality drops, win rate weakens, margin slips, capacity tightens, or low-margin work grows faster than preferred work.
This could become a small internal market-intelligence loop for architecture firms. It would not replace judgement. It would organise public market data and private firm data into a repeatable snapshot so leadership can make decisions from evidence instead of scattered signals.
The value is the relationship map: market movement on one side, the firm's actual commercial position on the other.