What makes a development project successful? Lessons from a real case

In property development, people often focus on the visible stages of a project, such as construction, development progress, building costs and the finished product. These are tangible, measurable and the easiest aspects to discuss. But experienced practitioners understand that by the time a project reaches construction, most of the key decisions have already been made.

As Dan Oliver noted at a recent session hosted by Property Development Solutions, success in development is rarely created during execution. Instead, it is often determined much earlier, through key decisions about land acquisition, feasibility analysis and project structure: “If you get the early decisions right, everything that follows becomes easier.”

This article draws together lessons from a real project discussed during that session. Based on an actual case, these insights are particularly relevant to developers who already have some experience but are continuing to build and deepen their capabilities across multiple projects.

Start with the market, rather than the site

One of the most common mistakes among novice developers is to start thinking about a project from the site itself. The instinct is often to see a piece of land and immediately imagine “what it could become”. A more mature approach reverses that thinking entirely: “We do not start with what the project could become, but with what the market can actually support.”

The distinction may seem subtle, but it is crucial. A development project is not determined solely by the physical characteristics of its site. It is defined by the product the market will accept at a particular time, in a particular location and at a particular price.

In a recent project, every decision was grounded in a realistic assessment of buyer demand. Pricing assumptions remained cautious, while the product mix closely reflected proven demand in the surrounding area, down to very specific local market segments.

This market-based assessment directly influenced the project's feasibility, specifically:

The acceptable purchase price for the land
The overall approach to planning the project
And whether the project itself made sense

In many cases, developers fail not because of poor execution, but because the project was based on unrealistic expectations from the outset.

Feasibility analysis: a methodology, rather than a procedural formality

Feasibility analysis is often treated as a procedural step to complete before moving a project forward. In practice, however, it is a core tool for identifying and understanding risk.

As Dan Oliver emphasised during the session: “A truly effective feasibility analysis must hold up not only under ideal conditions, but also under pressure.”

A highly disciplined approach to feasibility analysis was taken on one of his recently completed projects, going well beyond simply running the numbers:

Keep revenue assumptions restrained: Avoid relying on optimistic expectations of market growth, and adopt more conservative sale prices and sales rates
Make cost estimates comprehensive and realistic：Include not only construction costs, but also all “soft costs”, such as consultant fees, compliance costs, financing costs and a contingency allowance
Carry out stress testing: Test not only feasibility under ideal conditions, but also whether the project remains viable if costs rise, timelines extend or sales slow

This approach reflects a deeper principle: “The purpose of feasibility analysis is not to prove that a project is viable, but to determine whether it remains viable when things do not go to plan.”

Where does the real risk lie?

A common view in property development is that the greatest risk lies in construction. That is understandable: construction is capital-intensive, time-sensitive and complex to execute.

Yet recent project experience has demonstrated precisely the opposite: “The predevelopment stage is where risk is most concentrated, rather than the construction stage.”

Before construction actually begins, developers face a range of highly uncertain factors, such as:

Resource consent processes taking far longer than expected
Changes to policy and regulatory requirements
Unforeseen problems emerging from site conditions
Holding costs continuing to accumulate while approvals are awaited

Against this backdrop, provided the early groundwork is sound, construction becomes more of an execution process than a primary source of risk.

A project's success does not depend on having no risk at all, but on whether those risks have been identified and understood early. By anticipating potential problems, developers can build sufficient flexibility and buffers into the project structure, helping it remain resilient and manageable amid uncertainty.

Look beyond a single metric: assessing more than profit margins

Developers often regard profit margin as the central measure of a project's quality and feasibility. While margins certainly matter, they are only part of the overall assessment.

As Dan Oliver put it: “We do not look at a project in isolation; we look at how all its elements work together.”

A high profit margin on paper does not guarantee a successful project. Margins must be understood within a wider framework, including the timeframe, level of risk, alignment between the product and the market, and the team's ability to deliver.

During the session, Dan also noted that profit margin represents more than potential earnings: it also reflects the balance between risk and return.

Although this particular project faced numerous challenges, the key to its smooth progress was its overall alignment:

The product closely matched market demand
The project timeframe was realistic
Risks were thoroughly identified and understood
The team had the ability to execute and deliver

No single factor underpinned the project's success. Instead, all its elements worked together to form a complete and robust system.

The importance of the team

Another central theme was the team's decisive role in a project's success or failure: “A successful project depends not only on the developer, but on the entire team behind them.”

This is particularly important for developers who are still building experience. Capability never exists in isolation: a team can strengthen it and fill gaps.

Builders, architects, consultants and specialist advisory teams all help shape the overall quality of a project. A team with the right mix of expertise can:

Identify potential problems earlier
Provide more forward-looking professional advice
Strengthen confidence among all parties, including financial institutions

In this case, the team's expertise played an important role throughout the project, reducing uncertainty and providing strong support for key decisions.

Clarity before speed

In property development, speed is often seen as a competitive advantage, particularly in a highly competitive market. However, the session emphasised a key prerequisite:

“Speed at the financing stage is built on clarity and discipline.”

Rushing ahead without fully understanding a project does not create efficiency; it magnifies risk. By contrast, taking time early on to clarify the project structure and think through key issues can enable more efficient progress later.

This case demonstrated that clearly. Project decisions were not rushed, but were based on a thorough understanding of the full scope of the development, including identifying risks and repeatedly checking that the project structure was sound.

This approach of establishing clarity before moving forward made later execution smoother, reduced uncertainty along the way and strengthened confidence among everyone involved.

What lenders really value

Financing is often viewed as a hurdle in the development process. From another perspective, however, it is an important test of a project's quality.

As Dan Oliver noted: “The most important question is always: how will this loan be repaid?”

That question shifts the focus from “Can the project be built?” to “Can the project succeed?”

Lenders assess more than construction capability. They consider the feasibility and overall soundness of the entire project, including:

Whether the feasibility analysis is realistic and reliable
Whether the profit margin is reasonable
Whether the product meets market demand
Whether the team can execute, and whether the exit strategy is clearly defined

There is also a factor that is difficult to quantify but critically important: whether the project makes sense. In other words, a project needs to be logically coherent and workable in practice, rather than built on idealised assumptions.

The key to this project's smooth passage through those assessments was that it had been structured around the end result from the outset. The exit route was not considered only after completion; a successful exit had been incorporated into the overall plan from the beginning.

Consider the exit strategy from the outset

An important lesson from this project is that the exit strategy should be incorporated into the overall plan from the beginning, rather than considered only towards the end. “Financing decisions are ultimately driven by how the project will end.”

Developers must consider early on how capital will be recovered. Whether the project is intended for sale, long-term ownership or refinancing, the exit route should be clear and realistically achievable.

Many well-developed projects include multiple exit routes to address uncertainty caused by market changes. This reduces reliance on a single outcome and strengthens resilience, allowing developers to adjust their strategy flexibly rather than being forced down a fixed path.

Build capability through structure

For developers who are still building experience, the path forward can sometimes seem uncertain. But experience is only one ingredient of success: “We do not take a one-size-fits-all approach.”

With a sound project structure, professional support and a coordinated team, developers at different stages of experience can all deliver successful projects. The key is not to eliminate risk entirely, but to understand and manage it effectively.

Numerous real cases show that success is not reserved for seasoned developers. It belongs to those who are disciplined, think clearly and are willing to structure their projects correctly from the outset.

Good outcomes begin with the earliest decisions

Ultimately, the central principle of successful development is that outcomes are determined early.

“Excellent projects are not ‘created’ during construction; they are ‘determined’ through land acquisition, feasibility analysis and early planning.”

Everything that follows is an extension and consequence of those initial decisions.

This project succeeded because it had the following characteristics:

It was grounded in reality from the outset
All key assumptions remained cautious
Risks were thoroughly identified and understood
The project structure was robust and sound, and the team could execute

These principles may seem straightforward, but the real challenge is applying them consistently over the long term.

Key takeaways for developers

Start with market demand, rather than a site's potential
Use feasibility analysis to test risk, rather than to “endorse” a project
Recognise that most risk arises before construction
Assess projects as a whole, rather than focusing solely on profit or cost
Build a strong team to improve decision-making and execution
Prioritise a clear structure and sound logic before pursuing speed
Define the exit strategy early and allow room for change