What would a healthier client pipeline actually look like?

 

If the profession is serious about improving pipeline quality, boundary clarity, and front-end sustainability, then it is worth asking a final practical question: what would a healthier client pipeline actually look like?

Not in theory. In practice.

A healthier pipeline would probably begin with stronger screening. Not all enquiries would be treated as equal from the first moment. There would be earlier testing of budget realism, decision-making readiness, project fit, and the client’s actual expectation of the first conversation.

A healthier pipeline would also normalise paid feasibility. Instead of allowing uncertainty to spread across unpaid conversations, the profession would make it easier for clients to understand the first structured step: what it includes, why it matters, and how it helps determine the right next move.

It would likely involve clearer boundaries around informal professional thinking. Introductory discussions could still be open and helpful, but the point at which professional judgment starts materially reducing uncertainty would be more clearly named as service.

A healthier pipeline would also require stronger language from architects themselves. Not aggressive language. Not defensive language. Just more confident language around value.

This is what we can discuss at first contact.
This is what sits inside a paid first stage.
This is the point at which meaningful project clarity begins.
This is how we help responsibly, not vaguely.

That shift matters because some pipeline problems persist not only because clients ask too much, but because the profession has been inconsistent in naming where value begins.

There is also a wider culture question here. If the market has become accustomed to drawing out early architectural judgment before commitment, then one architect alone will not change that pattern quickly. But repeated professional clarity can start to alter expectation. Over time, better boundaries can become more normal if enough practitioners hold them.

This does not require architecture to become transactional or cold. A healthier pipeline should still feel human. Clients should still feel welcomed, listened to, and guided. But guidance does not need to mean unstructured access to unlimited early expertise.

A stronger front end may actually improve trust. Clients often feel more secure when the process is clear, when they know what they are paying for, and when the project has a recognisable structure from the beginning rather than a blurred informal lead-up.

For small practice, this matters enormously. A healthier pipeline would mean less diffuse speculation, more viable early-stage engagement, cleaner transition from enquiry to commission, and less hidden transfer of uncertainty onto the architect.

Perhaps the most useful shift is this one: stop treating early-stage commercial ambiguity as inevitable background noise and start treating it as something that can be designed more intelligently.

Because that is what the pipeline is.

It is not just a stream of enquiries.
It is an operating system at the front edge of practice.

And like any operating system, it can either support the health of the practice or quietly erode it.

A healthier pipeline would not remove uncertainty. But it would distribute it more fairly, structure it more clearly, and place less of it by default inside unpaid architectural time.

That would be a better beginning for everyone.

What should a first paid stage actually cover?

If the profession wants stronger boundaries at the front end of practice, one question becomes unavoidable: what exactly should the first paid stage include?

Many problems in the client pipeline seem to grow out of vagueness. The enquiry begins. The architect listens, comments, asks a few questions, perhaps reviews the site or the brief, offers some early directional thinking, and only later tries to define where formal service actually starts. By then, value may already have been transferred without structure.

That suggests that the first paid stage may need to be more clearly named and framed.

Not every project will follow the same pattern. But in many cases, a sensible first paid step could include some combination of site and planning review, high-level feasibility, risk identification, broad yield or scope sense-checking, budget alignment, likely consent pathway observations, and a recommendation on next steps.

In other words, the first paid stage is not “design” in the fuller sense. It is structured early judgment.

That matters because it gives both parties a clearer contract around uncertainty.

The client is not yet paying for a full concept package or complete design process. But they are paying for professional reading, professional filtering, and professional reduction of ambiguity. The architect, in turn, is no longer being asked to supply that value informally.

This kind of structure can be healthy for both sides.

Clients get clarity on what they are buying.
Practices gain a legitimate boundary between enquiry and service.
The project gets a more stable basis for deciding whether to proceed, pause, revise, or stop.

It may also help solve a more subtle problem: many clients do not know what they need from an architect at the beginning. They know they need help, but not how that help should be staged. If the profession does not define the early stage well, clients will often try to create their own version of it through informal contact.

That tends to favour ambiguity, not structure.

A clearly defined first paid stage is therefore not only a protection mechanism. It is also a client-education tool.

Of course, naming such a stage is not enough by itself. The profession also needs confidence in explaining its purpose. It should be framed not as a barrier to starting, but as the proper way to begin responsibly. It is where the site is understood, the idea is tested, the risks are surfaced, and the likely path forward becomes legible enough for better decisions.

This is especially useful in small practice, where the cost of blurred beginnings is high. A well-structured first paid stage can improve fee conversations, reduce speculative drift, and create a more coherent rhythm between enquiry and commission.

Perhaps the deeper issue is this: if clients keep seeking early certainty, and if architects keep feeling overextended by front-end ambiguity, then the first paid stage is not a minor administrative matter.

It may be one of the profession’s most important front-end design problems.

And like all design problems, it benefits from clearer definition. 

Why do so many enquiries begin before budget realism?

Many architectural enquiries begin with optimism.

That is understandable. Clients begin with ambition, possibility, need, or pressure. They may know they want to build, extend, develop, or improve. But one of the most common weaknesses in early enquiries is not lack of interest. It is lack of budget realism.

Not a perfect budget.
Not a QS report.
Just a realistic sense of financial territory.

Without that, the early conversation is unstable from the start.

The architect may begin exploring options, discussing likely pathways, commenting on scope, testing feasibility, or helping the client understand what might be possible on the site. All of that may appear productive. But if the project does not have even basic financial grounding, those conversations can become professionally expensive very quickly.

This is where time starts disappearing into non-viable work.

The issue is not that clients should already know everything. Most do not. Architecture is not their daily field. But the question remains: should practices be screening earlier and more directly for budget realism?

Many still hesitate.

Some hesitate because money is awkward to discuss too early.
Some because they fear losing the enquiry.
Some because they hope feasibility work will eventually justify itself through later appointment.

But when budget realism is absent, the architect often becomes the one testing reality without being properly engaged to do so.

That has consequences.

The project may turn out to be too expensive in any workable form.
The client may expect a level of design exploration that was never commercially grounded.
The architect may spend time refining a path that the client cannot afford to follow.
And when the numbers finally become visible, it can feel as if the architect has somehow overreached, when in fact the project simply lacked viable foundations from the beginning.

Budget realism is not the enemy of design. It is what allows design conversations to become useful instead of speculative.

A healthier pipeline would not insist that every client arrive with a fully formed cost plan. But it would perhaps require some earlier testing of the basic financial frame. Is the project likely to sit in the right order of magnitude? Does the client understand current construction cost conditions? Are they willing to confront the real relationship between ambition and budget before substantial professional time is invested?

These are not hostile questions. They are stabilising questions.

Small practices, especially, cannot afford to treat budget ambiguity as harmless. Every under-framed enquiry competes with billable work. Every financially unrealistic project absorbs cognitive effort that could have gone into live work or viable leads.

So perhaps the profession needs to normalise something that still feels awkward: budget realism should not be a late-stage revelation. It should be an early-stage filter.

Not to shut projects down.
To make them more honest.
And to help both client and architect understand whether the conversation is moving toward a real commission, or only circling possibility.

If the financial ground is missing, the architect is often asked to supply it indirectly through unpaid time.

That may be common. But it is not necessarily wise practice.

The 2-metre rule that quietly redraws every granny flat design

Figure 3 from Granny flat Exemption Guidance

Recent Building Act changes introduce a building-consent exemption pathway for certain small standalone dwellings (commonly called granny flats), provided the specific exemption conditions are met (including notification and documentation requirements) and the work is carried out to comply with the Building Code.

Most people focus on the headline (no building consent). In practice, the design conversation usually turns on one condition that can make or break feasibility on a real site:

The exemption guidance commonly describes a minimum separation of 2 metres from any legal boundary and 2 metres from other residential buildings (subject to the definitions and measurement rules in the current guidance).

That single line is what often determines whether a “nice-to-have” layout becomes an awkward compromise—or a clean, buildable solution.

What the rule actually says (and how it’s measured)

In MBIE’s exemption guidance, the separation requirement is stated plainly:

“Two metres or more away from any other residential building or any legal boundary.”

Setbacks are measured from the legal boundary to the building as defined in the exemption guidance—so you shouldn’t rely on fence lines or assumed boundaries where accuracy matters.

This is why the 2 m rule is not just a planning-style “setback”—it’s a practical geometric constraint that affects:

• maximum possible footprint width and length
• where doors, decks, and services can go
• how you thread access around an existing home

Why “2 metres from existing buildings” is the real sting

The “2 m from boundary” part is easy to understand. The real catch on many sites is the second half:

2 metres from any other residential building

In many typical sites, that means maintaining a minimum 2 m separation from the existing dwelling on the same site (and from any other residential building), as interpreted under the exemption definitions.

So even if you have a generous backyard, you can’t always tuck the unit close to the main house to make the site “work” (for example, to preserve a driveway or avoid an easement). In effect, the exemption tends to require a clear separation corridor between the two.

Design consequence: you don’t just draw a boundary setback; you also draw a “no-build halo” around the existing dwelling. On compact sites, those halos collide—leaving an oddly shaped leftover patch that can dictate the plan more than your brief does.

How the 2-metre rule reshapes the configuration

1) It sets the maximum building width before you even start designing

If a site area allows a granny flat “somewhere,” the usable rectangle is still reduced by setbacks.

Illustrative example only:
Say the available “slot” between boundary constraints is 12.0 m wide. Less 2.0 m on the left boundary and less 2.0 m on the right boundary means the maximum theoretical building width becomes 8.0 m—before you account for driveways, turning, services, outdoor living, easements, or other constraints.

If the site is narrower—or you need vehicle access down one side—your workable width can quickly drop into the 5.5–6.5 m range, which heavily influences:

• corridor vs open-plan efficiency
• bathroom/laundry stacking
• whether you can do two bedrooms without a “railway carriage” feel

2) It pushes you toward long, shallow footprints

Because width is often the first casualty, designers typically respond with:

• longer rectangles (e.g., ~9–11 m long)
• tighter service spines
• fewer plan “jogs” (which consume width fast)

This is why many exempt granny flats end up as simple bars: it’s not aesthetic minimalism—it’s setback math.

3) It changes where the front door wants to be

The 2 m separation zone between buildings is tempting to use as:

• a walkway
• a services run
• an access path to keep the backyard functional

But that can also create a “back-of-house” arrival experience unless you deliberately shape:

• entry orientation
• lighting and privacy screening
• a small outdoor threshold that feels intentional

4) It affects decks, steps, and outdoor living (even when the rule talks about the building)

Even where separation is expressed in terms of the building, in practice you still have to think carefully about:

• eaves and gutters
• maintenance access
• overland flow paths and stormwater detailing
• how you keep water and overflow away from tight side yards

The “2 m corridor” quickly becomes multi-purpose: access + drainage thinking + maintenance + privacy buffer.

5) It interacts with other exemption “shape controls”

The exemption isn’t just about distance. It also includes other limitations and conditions that need checking in the current guidance before finalising massing and layout, such as limits relating to height, storeys, and construction approach (refer to the current guidance for the exact values and definitions), along with other construction conditions intended to keep the build “simple.”

That matters because when setbacks squeeze footprint options, people often try to “go up” or add split-level cleverness—exactly the kind of moves the exemption is designed to avoid.

The practical site-planning workflow that works

If you want to avoid redesign loops, start with a blunt feasibility overlay:

1. Confirm the legal boundary (preferably from a survey/base plan where accuracy matters).
2. Draw a 2.0 m offset inside all boundaries.
3. Draw a 2.0 m buffer around the existing dwelling (and any other residential building).
4. Only then test footprints (bars, L-shapes, corner placements), and check whether:
• the access/parking strategy still works
• services can connect sensibly
• outdoor space isn’t reduced to leftover strips

This approach makes the constraint visible early—before anyone emotionally commits to a plan that only works by “cheating” the separation.

Don’t confuse “building consent exempt” with “everything exempt”

Two reminders that stop nasty surprises later:

• The exemption is about building consent only—work still needs to comply with the Building Code, and there are notification/documentation steps to follow under the exemption conditions.
• Resource consent is a separate track. Whether planning approval is required depends on the district plan/NES settings, zoning, overlays, servicing, and site specifics—confirm with a planner or council before relying on any exemption pathway.

The bottom line

The new granny flat pathway is available in principle—and it can simplify delivery—but the 2-metre separation requirement is the condition that most directly shapes what you can physically fit on a site.

Treat it as the starting geometry of the project, not a compliance footnote:

• 2 m to boundaries defines the outer frame
• 2 m to the existing house defines the internal “no-build corridor”
• what remains dictates the plan typology (often long, simple rectangles) more than personal preference does

Disclaimer

This article is provided for general informational purposes only and does not constitute project-specific professional advice. Regulatory requirements, exemption conditions, planning controls, and infrastructure constraints vary between councils and may change over time.

Whether a granny flat or minor dwelling is permitted on a particular property depends on site-specific factors, current legislation, and compliance with the New Zealand Building Code and relevant District Plan provisions.

Before proceeding with design or construction, independent confirmation of the applicable requirements for your property is recommended.