Alyssa Castillo
Property development has a strange relationship with procurement.
Everyone agrees it is important. Nobody argues that appointing the right contractors, consultants, and suppliers matters. Yet procurement is often treated as a stage rather than a discipline. Something that happens after feasibility, after planning, and after the numbers have been approved.
The reality is very different.
Procurement begins long before the first tender is issued. In many cases, procurement begins the moment a developer starts evaluating whether a site is worth pursuing in the first place.
That may sound excessive, but every development appraisal contains procurement assumptions. The projected build cost assumes certain subcontractors can deliver the work at a certain price. The programme assumes materials can be sourced within a certain timeframe. The projected profit assumes the market can deliver what the appraisal says it can deliver.
The challenge is that property development does not happen inside a spreadsheet.
It happens in the real world.
Contractors become busy. Supply chains tighten. Materials become unavailable. Lead times increase. Labour shortages emerge. Interest rates move. Regulations change.
This is why procurement is one of the most important functions within the property development process. It is where assumptions meet reality.
At Morta.com, we regularly see development teams discover that procurement is not actually their biggest challenge. The real challenge is controlling the information that surrounds procurement. Tender submissions arrive by email. Supplier assessments live in spreadsheets. Cost reviews sit in PDFs. Commercial decisions happen in meetings. By the time construction begins, critical procurement information is often scattered across multiple systems.
The irony is that procurement has never had more influence over development performance than it does today.
According to the UK Government's Construction Playbook, early supply chain engagement and effective procurement planning significantly improve project certainty and reduce delivery risk. For experienced developers, that finding is hardly surprising. Most procurement problems do not suddenly appear during construction. They usually start much earlier.
Many developers separate feasibility from procurement.
The appraisal is completed first. Procurement happens later.
That approach sounds logical, but it creates problems.
A feasibility study is only as reliable as the assumptions supporting it. If a scheme is projected to generate a 20% margin because construction costs are assumed to be £180 per square foot, procurement eventually becomes the process of determining whether that assumption is actually achievable.
This is one reason experienced developers often engage contractors, consultants, and supply chain partners much earlier than many newcomers expect.
They are not necessarily seeking formal prices at this stage. They are testing assumptions.
Can the market realistically deliver the project within the proposed budget?
Are there procurement risks that have not been identified?
Are there specialist packages with unusually long lead times?
Will contractor availability affect programme assumptions?
The earlier these conversations happen, the fewer surprises emerge later.
According to the Royal Institution of Chartered Surveyors, early project planning and information management continue to play a critical role in controlling project risk and improving delivery outcomes.
Developers often focus heavily on land acquisition, planning, finance, and sales values during the early stages of a project. Procurement deserves the same attention because it ultimately determines whether the development can be delivered as planned.
The property development procurement process is often presented as a neat sequence of activities.
In reality, it is far messier than that.
Projects evolve continuously. Information changes. Design develops. Market conditions shift.
What remains constant is the developer's need to balance cost, quality, speed, and risk.
Before any procurement exercise begins, developers need clarity around what they are buying.
That sounds obvious, yet it is one of the most common causes of procurement problems.
Contractors struggle to price incomplete information. Suppliers struggle to commit to uncertain requirements. Consultants struggle to coordinate packages that have not been clearly defined.
The result is often predictable.
Tender returns become difficult to compare. Clarifications multiply. Procurement timelines extend. Commercial certainty decreases.
This is why successful procurement is rarely about obtaining the fastest quote.
It is about creating enough clarity that the market can respond accurately.
The quality of procurement outcomes is usually determined by the quality of information provided at the start of the process.
One of the biggest misconceptions about procurement is that it belongs exclusively to commercial teams.
In reality, procurement touches almost every stakeholder involved in a development, from developers setting commercial objectives and consultants preparing tender information to project managers coordinating delivery and contractors providing pricing and technical input.
Lenders may also influence procurement decisions through funding requirements and risk assessments. Because so many parties contribute to procurement decisions, effective information management becomes critically important.
A delayed response from a consultant may affect a tender return, a change in design information may affect procurement timelines, and a contractor's clarification request may impact multiple packages simultaneously. Because everything is connected, using different systems can cause problems. As a project grows, keeping track of information becomes even more important.
The difficulty is that many development teams continue managing procurement using tools that were never designed to support complex property developments.
Developers naturally compare prices. Construction is a commercial activity and procurement decisions have direct financial consequences.
The danger arises when procurement becomes a process of selecting numbers rather than evaluating risk.
A significantly lower tender should always prompt further investigation.
Sometimes the explanation is positive. A contractor may have stronger supply chain relationships, greater efficiency, or a better understanding of the project.
Other times, the explanation is less encouraging. Scope gaps may exist, programme assumptions may be unrealistic, certain risks may not have been included, or resources may already be committed elsewhere.
The challenge for developers is that these issues rarely become visible during tender evaluation and instead emerge during delivery, where a procurement decision that initially appeared to save money gradually generates delays, disputes, variations, and management challenges.
By the time the issue becomes obvious, the original saving has often disappeared entirely. This is why procurement should be viewed as a risk management exercise rather than a price comparison exercise, with the objective being not to appoint the cheapest contractor, but the contractor most likely to deliver the required outcome.
As development businesses grow, many begin exploring direct procurement strategies. The appeal is understandable.
Direct procurement offers greater control over suppliers, greater transparency over costs, and in some cases improved commercial outcomes.
However, direct procurement also transfers additional responsibility to the developer.
When a main contractor manages procurement, many coordination activities sit within their scope.
When developers procure directly, they assume responsibility for managing relationships, delivery schedules, approvals, and communication across multiple suppliers.
This creates opportunities but also introduces risk. The question therefore is not whether direct procurement is better. The question is whether the development team has sufficient visibility and control to manage it effectively. Many developers underestimate the administrative burden associated with direct procurement. The challenge is not ordering materials; the challenge is coordinating information.
Purchase orders, delivery schedules, approvals, supplier documentation, programme requirements, and commercial decisions all need to remain aligned.
As projects become larger, maintaining this visibility becomes increasingly difficult without dedicated systems.
Property development is becoming more complex.
Developers are managing larger portfolios, more stakeholders, and greater volumes of information than ever before.
Procurement sits at the centre of this complexity.
A single package may involve tender documents, contractor submissions, commercial reviews, clarifications, programme updates, supplier assessments, and contract documentation.
Each item generates information, and each decision affects subsequent decisions. The problem facing many developers is not a lack of information; it is information fragmentation. Critical procurement data often exists across emails, spreadsheets, cloud storage systems, PDFs, meeting notes, and messaging platforms, and teams spend significant amounts of time searching for information that already exists.
This is one of the reasons purpose-built property development software has become increasingly important, as the challenge is no longer simply managing procurement itself but managing the growing volume of information, decisions, and stakeholder interactions that surround it.
Historically, development teams relied on multiple disconnected systems, using one platform for project management, another for reporting, another for communication, and another for procurement. The result was predictable: information became fragmented, visibility decreased, and decision-making slowed. This is where software for property developers is beginning to change the way projects are delivered.
Rather than forcing teams to manage procurement across multiple systems, platforms such as Morta bring together project planning, cost planning, contractor collaboration, procurement workflows, reporting, communication, and delivery management within a single environment.
For developers, this creates something that is surprisingly difficult to achieve using disconnected systems.
Clarity.
Instead of searching for information across multiple locations, teams gain visibility over procurement activities alongside the broader development lifecycle.
Supplier information, tender evaluations, project planning, cost reporting, and contractor collaboration become part of the same process rather than separate activities. The result is not simply improved efficiency; it is improved decision-making.
Developers spend enormous amounts of time managing uncertainty across markets, planning, construction, and finance, and procurement exists because developers are trying to reduce as much uncertainty as possible before committing capital. The strongest procurement strategies are not necessarily the most complicated; they are usually the most disciplined, beginning early, relying on accurate information, and focusing on capability as well as cost.
They create visibility across the entire development team.
Most importantly, they recognise that procurement is not a standalone activity.
It is connected to every stage of the development lifecycle.
From feasibility and appraisal through to delivery and handover, procurement decisions influence the outcome of the project.
The developers who understand this consistently place themselves in a stronger position to protect programme, manage risk, and maintain profitability.
If you're learning how to develop a procurement strategy for property development, it is tempting to focus exclusively on tendering, contractor appointments, and supplier negotiations.
Those activities matter, but they are only part of the picture.
Successful procurement starts much earlier. It begins during feasibility. It continues throughout planning and design. It influences cost certainty, programme certainty, quality, and risk long before construction begins.
As developments become more complex, managing procurement effectively increasingly depends on managing information effectively.
That is exactly why more developers are turning to Morta.
Morta was built specifically for property developers who want greater control over project planning, procurement, contractor collaboration, cost reporting, and delivery management.
By bringing critical development information into a single platform, teams can reduce administrative burden, improve visibility, and make better commercial decisions throughout the project lifecycle.
If you want to simplify property development procurement and gain greater control over your projects, book a discovery call with Morta today.
