Deal Sourcing Property A UK Developer's Guide to Success

A site looks cheap. The agent says there’s strong interest. You run a quick view, sketch a massing option, and start spending money. Then the deal dies late. Access doesn’t work the way the title plan suggested. The local authority policy position is tighter than the selling details implied. CIL was never carried properly. By the time you realise the margin was fiction, you’ve burned weeks, fees, and internal attention.

That’s not bad luck. It’s usually a workflow problem.

Often, deal sourcing property is treated like a hunt for discounted land. In practice, the better operators treat it as an early filtering system. They don’t win because they look at everything. They win because they reject the wrong sites quickly, then move hard on the few that stand up under scrutiny.

That matters even more in the UK because volume creates competition. Between 2013 and 2022, the UK accounted for 1,673 property acquisition deals, or 24.8% of the European total, according to S&P Global Market Intelligence’s analysis. If you’re buying, funding, or underwriting sites in that market, speed without discipline is expensive.

Introduction The Hidden Cost of a Bad Deal

A bad deal rarely looks bad at the start.

It usually arrives with one attractive feature doing all the selling. Low guide price. Big plot. Good postcode. Existing structure with obvious conversion angle. The problem is that one positive headline can hide three or four viability killers underneath. That’s why so many teams confuse activity with progress. They’re busy, but they’re not qualifying risk early enough.

The commercial damage goes beyond wasted due diligence spend. A failed deal drags your pipeline, distracts your technical team, and slows decisions on better opportunities that need attention now. Lenders feel it as well. If the first proper review exposes basic omissions, confidence drops fast.

Practical rule: If a site only works when every assumption is favourable, it doesn’t work.

Good sourcing is less about finding land and more about building a process that links lead generation, viability, planning, and finance from the first conversation. That means the front end has to produce evidence the back end can trust. If sourcing and underwriting speak different languages, the handoff will fail.

This is the core distinction in this market. Strong teams kill weak deals early, preserve resources, and package live opportunities in a form that can get funded.

Building Your Deal Sourcing Engine

A sourcing engine gets tested on Monday morning, not in a slide deck.

An agent sends over a tired mixed use block at 8:15. A direct to vendor reply lands at 9:40. By lunch, your planner has flagged a small infill site from a committee report. If those leads enter the business in three different formats, with three different standards of evidence, the team slows down fast. Good opportunities get buried with weak ones. Underwriting starts from scratch. Finance loses confidence because the front end has not captured what the back end needs.

That is why the engine matters. The job is not just to generate leads. The job is to collect them in a format that lets you judge price, planning, access, delivery risk, and lender appetite without rebuilding the file every time.

Build channel mix around evidence quality

Relying on one lead source creates blind spots. Portals show what the market already knows. Agent emails can be useful, but they often arrive after the pricing story has been framed for someone else’s agenda. Direct to owner outreach can produce better terms, though the hit rate is lower and the follow-up burden is higher.

Use a mix. Above all, hold every channel to the same intake standard.

On market stock still earns its place because it keeps your view of values, buyer demand, and product type current. It also helps train judgement. A sourcer who cannot read a weak brochure, spot the missing information, and ask the right commercial questions will struggle off market as well.

Useful on market filters include:

• Stale listings. Long exposure often points to pricing friction, access issues, lease complications, title problems, or a planning story that falls apart under review.
• Price reductions. These can indicate movement in seller expectations, but only if the revised number still leaves room after build cost, finance, and profit.
• Development language. Terms like “subject to planning”, “potential”, “rear land”, “vacant upper parts”, and “income with asset management angle” justify a quick appraisal.
• Asset mismatch. A building that no longer suits its current use can create the best angle. Old offices in residential locations, oversized houses on corner plots, or parades with underused uppers are common examples.

Take a secondary retail parade with rear access and empty upper floors. The brochure talks about passing rent. The real question is whether the existing income supports hold costs while you work a planning application, whether the uppers can be accessed and serviced properly, and whether local policy will support conversion or intensification. If those points are not captured at intake, somebody later has to redo the work.

Off market works when you target pressure, not volume

Off market sourcing gets romanticised. In practice, it is admin heavy, slow to mature, and easy to do badly.

The useful version starts with owner circumstances. Probate cases, withdrawn sales, tired landlords, buildings with rising vacancy, refused schemes with a better fallback position, and owners sitting on management problems all deserve attention. Each one has a different conversation. A family dealing with an estate wants certainty and a clear route to completion. An overexposed landlord may care more about speed and reduced hassle than top headline price. A failed applicant may need a buyer who can reshape the scheme rather than abandon the site.

Professional referrers matter here. Architects, planning consultants, insolvency practitioners, and local solicitors often see stress before the open market does. They also judge quickly whether a buyer wastes time. If you ask vague questions, chip late, or fail to close after calling something “proceedable”, referrals dry up.

Public sector and institutional disposals belong in the engine too. They are slower and more process driven, but they reward teams that can read bid criteria, answer compliance points properly, and package evidence in a way credit and legal teams can work with.

Owners care about outcomes. Price matters, but certainty, timing, and problem-solving often decide who gets the deal.

Standardise intake before you scale outreach

Smaller teams often struggle to maintain oversight. Every lead arrives with different notes, different assumptions, and different gaps. The result is avoidable delay.

Use one intake template across every source. Keep it commercial. Keep it short enough for the team to use.

Capture:

1. Lead source and contact route
   Agent, direct to owner, referrer, public disposal, planning portal, or repeat seller.

2. Seller position
   Why they may transact now, what pressure exists, and what timeline they are likely to accept.

3. Property and site basics
   Address, use class, approximate area, tenure, access position, occupancy, and any obvious title or rights of way issues.

4. Planning angle
   Existing consent, refusal history, local plan allocation, likely policy support, and the point most likely to block progress.

5. Commercial snapshot
   Guide price or expected price, current income, likely exit route, and the one assumption that makes or breaks viability.

6. Evidence collected on day one
   Brochure, title plan if available, planning references, comparable evidence, photos, and notes from the initial call.

That last field matters. Lenders and brokers do not trust enthusiasm. They trust evidence that can be checked. If the sourcing team collects the right documents and records the right assumptions at the start, the underwriting file forms much faster and with fewer contradictions.

A short explainer can help newer team members think in workflows rather than one off deals:

Common failure points inside the engine

The weak points are usually operational, not theoretical.

• Portal dependence. Public stock helps with market reading, but it rarely gives enough seller context on its own.
• Generic outreach. Owners ignore messages that show no understanding of their situation or asset.
• Poor policy tracking. Teams that do not watch planning portals, committee decisions, and refusal reasons miss where value is shifting.
• Equal treatment of every lead. A marginal site with no access solution should not consume the same time as a site with clear planning support and a motivated seller.
• No underwriting fields at intake. If basic cost assumptions, exit route, tenure points, and planning history are missing early, the deal file breaks later under credit review.

A sourcing engine should produce two outputs. More opportunities, and better prepared opportunities. The second one is what protects time, keeps the pipeline investable, and stops weak deals reaching expensive stages of review.

The Five Minute Viability Test

A deal comes in at 10:14. By 10:20, you should know whether it deserves another hour of your team’s time.

That sounds harsh, but it is how good pipelines stay clean. Early appraisal is not about proving a deal works. It is about killing the weak ones before they absorb search fees, consultant time, legal review, and internal attention that should be reserved for live opportunities.

The first question is simple. Can this site support the price being asked once real costs, planning friction, finance, and profit are carried properly? If the answer is unclear at a rough-cut level, the lead is not ready for deeper work.

Run a rough residual first

Start with the exit, not the asking price.

Use current local comparables to set a realistic GDV. Then strip out build costs, fees, finance, planning contributions, abnormal works, contingency, and your target profit. What remains is your rough residual land value. The exercise takes minutes if your sourcing team records inputs in a standard format. Teams that want consistency at this stage usually work better with a defined development viability workflow than with ad hoc spreadsheet edits passed around by email.

Precision is not the objective here. Range is.

If your top-line residual is materially below the guide price, there are only three possibilities. The seller is ahead of the market, your assumptions are wrong, or the scheme needs a different angle. All three are useful answers. What is not useful is spending two weeks ordering reports to avoid admitting the deal is tight.

Check what breaks viability fastest

Some issues destroy margin before you ever reach formal due diligence. These are the first ones worth checking.

Metric	What to Check	Green Flag Example	Red Flag Example
Asking price position	Compare guide price with rough residual	Seller pricing leaves room for planning risk and profit	Price already assumes consented land value
Access	Review title plan, aerials, street layout	Clear, practical entry and service arrangement	Ransom strip risk or constrained access geometry
Planning context	Read local policy and map layers	Existing allocation or policy support for proposed use	Obvious policy conflict or hidden designation
CIL and obligations	Check likely charging schedule and requirements	Limited planning burden relative to scheme scale	Large uncarried liability or Section 106 exposure
Flood and environmental signals	Review mapping and local constraints	No immediate abnormal signal	Flood exposure or constraints likely to force redesign
Seller motivation	Understand why the site is available	Timing pressure or genuine need for certainty	Aspirational seller testing the market

These checks are not separate from underwriting. They are the first layer of underwriting. If the sourcing note cannot explain access, likely planning position, main cost risks, and the basis of value, the deal file will fall apart later when a lender, investor, or credit team asks for evidence.

A five minute example

Take a corner plot with a tired building and a guide price that looks cheap against nearby flat values. Newer sourcers often stop there. Experienced buyers keep going.

Check whether the comparable evidence is current and comparable. Check whether demolition, remediation, retaining works, or utility upgrades are likely. Check whether access works for the density being assumed. Check whether policy limits height, massing, parking, or unit mix. Check whether CIL or Section 106 will absorb the apparent discount. Then ask the uncomfortable question. Is the owner selling a site, or selling hope?

Cheap land often becomes expensive land once true constraints are priced in.

A workable five-minute test should produce a short written view, not a gut feel. Proposed scheme, value basis, major cost lines, likely planning stance, and the main reason to proceed or reject. That short note becomes the start of a lender-ready evidence trail if the deal survives. If it fails, you have still saved money, protected team capacity, and kept the pipeline focused on opportunities that can stand up under proper scrutiny.

Deep Dive Due Diligence and Planning Checks

A site can pass the first screen, stack up on a quick appraisal, and still turn into dead money once proper checks start. I have seen deals lose margin at every stage for the same reason. The buyer priced the headline idea, not the site that existed.

At this stage, the job is to pressure test the assumptions that will end up in the lender file. If your sourcing note says six units, due diligence needs to show why six units are realistic, what could force that down to four, what that does to GDV, and whether the land price still makes sense after the change. That is the difference between finding a lead and qualifying a deal.

Read policy at site level, not headline level

Planning policy only helps if it applies to the scheme you are underwriting.

A site may sit inside a settlement boundary or an allocation area and still struggle on design code, overlooking, daylight, parking, amenity space, heritage setting, highways comments, or unit mix. Biodiversity net gain, drainage strategy, and affordable housing triggers can also change the economics fast. None of that is secondary. These items sit inside build cost, programme, and net developable area.

Backland and tandem plots are a good example. On paper, the plot depth works and the GDV looks attractive. In practice, the authority may object to the relationship with the host house, refuse the access arrangement, or push for a lower massing approach. One dropped unit can remove your profit. A delayed decision can remove your buyer.

Policy review needs to produce underwriteable outputs. Proposed unit count. Likely planning stance. Main conditions or obligations. Key reasons the authority may resist the scheme. If those points are vague, the appraisal is still speculative.

Check the physical realities before you trust the appraisal

Desktop reviews miss the things that cost real money on site.

Start with the basics and write them down in a way a QS, lender, or investor can follow later:

• Levels and topography: Sloping sites affect retaining works, drainage design, access gradients, and foundation assumptions.
• Access and servicing: Bin stores, turning heads, fire access, delivery constraints, and visibility splays can cut the scheme back.
• Trees and ecology: Root protection areas, habitat constraints, and seasonal survey requirements can reshape the layout and delay programme.
• Flood and drainage: A viable planning position can still carry expensive attenuation, pumping, or reduced floor area.
• Neighbour impact: Overlooking, overshadowing, and window relationships often reduce density long before the architect finishes the first layout.

This part needs discipline. If the site visit raises a cost risk, put a line in the appraisal or note the assumption clearly. If you leave it as a vague concern, it gets forgotten until someone is already committed on fees.

Legal detail decides whether the scheme can actually be delivered

A workable planning concept is not enough. Title can still damage value, delay funding, or stop implementation.

Review ownership, access rights, easements, restrictive covenants, ransom strips, boundary gaps, and any rights reserved to adjoining owners. Rear access is a repeat offender. Sales particulars often describe it as if it is settled, then title review shows the route is narrower than expected, conditional, shared, or missing altogether. At that point the scheme has a logistics problem, not just a legal one.

Assembly risk matters too. Before legal costs start to climb, it helps to review land ownership map workflows for UK development sites so you can see who controls adjoining land, where access dependency sits, and whether a clean exit is realistic if the scheme needs third-party cooperation.

Planning consent does not fix title defects, and clean title does not fix a weak planning case.

Use pre-apps selectively

A pre-app is worth paying for when the response will change your land bid, scheme design, or decision to proceed.

It is less useful where the fundamentals are already poor. If access is weak, neighbour impact is obvious, and policy support is thin, a pre-app usually confirms problems you should already have identified. That is not due diligence. That is paying for reassurance after the deal has already failed.

Use pre-apps to test a live planning judgment. Keep the questions tight. Record the response properly. Then feed the result back into density, timescales, professional fees, and contingency.

By the end of this stage, the file should show three things clearly. What you believe can be built. What could stop or reduce it. What that downside does to land value, margin, and fundingability. If the evidence is not strong enough to survive that test, the right move is to kill the deal early.

Creating Lender Ready Evidence Packs

Friday afternoon. A sourcing agent sends over a site they are certain will fund. By Monday, the lender has kicked it back. No clear capital stack, no evidence behind GDV, no explanation for planning risk, and no audited trail from headline appraisal to cashflow. Time goes. Seller confidence drops. The deal gets marked as weak before credit has even examined the merits.

A lender ready pack prevents that outcome. It gives a credit team enough verified information to test the proposal quickly, challenge the assumptions properly, and decide whether the scheme is fundable on terms that still leave profit in the deal.

What a lender actually needs

The gap is not finding deals. It is packaging them to underwriting standard from day one. The source material on lender expectations makes that point clearly and explains the knowledge gap around lender ready deal packaging in this lender ready packaging reference.

Credit teams are trying to answer five commercial questions:

1. What is being bought or built, and what is the business plan
2. How is the scheme being funded, and where does the lender sit in the capital stack
3. Which assumptions drive value, programme, and debt service
4. What can go wrong, and what does that do to profit, covenant headroom, and exit
5. Which documents prove the case, rather than merely describe it

That last point is where weak files fail. Agent particulars, a light appraisal, and a few comparables are not evidence. They are prompts for more questions.

Build the pack in a fixed order

A fixed structure saves time because underwriters know where to find the answer and your team knows what is missing before submission.

Use a standard pack format:

• Executive summary: Site, proposal, planning position, purchase basis, requested facility, and key credit points.
• Transaction summary: Agreed price, acquisition costs, vendor position, exclusivity status, and target exchange and completion dates.
• Appraisal summary: GDV build-up, development costs, fees, finance assumptions, profit on cost, and margin on GDV.
• Cashflow and debt case: Monthly spend, drawdown timing, interest roll-up, peak debt, covenant tests, and repayment route.
• Planning and technical evidence: Policy note, pre-app response if relevant, surveys, constraints, unit mix, schedule, and professional comments.
• Title and legal note: Ownership, easements, access, covenants, ransom risk, and any third-party dependency.
• Risk register: Itemised risks, financial impact, owner, mitigation, and whether the issue is priced, insured, deferred, or unresolved.
• Appendices: Plans, comparable evidence, consultant reports, heads of terms, correspondence, and version-controlled models.

Order matters. If the appraisal says one thing, the cashflow says another, and the executive summary rounds both into a cleaner story, the lender assumes the file has not been controlled properly.

Build lender evidence while sourcing, not after appraisal

This is the part many operators leave too late.

If the sourcing team records the right evidence at first review, the pack writes faster and the underwriting questions get narrower. Every lead should carry source notes for pricing, comparable rationale, planning status, title constraints, access position, and likely debt route. That means the front end of sourcing is already producing material credit can use, instead of forcing someone to rebuild the file from scratch after terms are agreed.

That is also how you keep finance realistic. A useful benchmark is to shape the submission around the information lenders usually request for funding property development in the UK, then collect that evidence while the deal is still being qualified.

Send a base case, then show where the model breaks

A single upside case does not help credit. It usually signals that nobody has tested the downside.

Include the base case, then run stress cases that reflect real pressure points. Sales values soften. Build costs rise. Programme slips. Planning takes longer. Refinancing terms tighten. Exit values move against you. The point is not to produce drama. The point is to show the lender where the scheme stops working and whether there is still enough headroom to lend safely.

I would rather see a pack that admits a thin margin under stress than one that hides risk in broad assumptions. At least the first file can be priced correctly.

Lenders fund evidenced risk, priced properly. They do not fund optimism written in tidy prose.

A good evidence pack does two jobs at once. It improves the chance of getting a credit decision quickly, and it exposes weak deals before you waste legal fees, consultant time, and management attention.

From Appraisal to Underwriting A Clean Handoff

Friday afternoon. Terms are agreed, the agent wants proof of funds, and credit asks three basic questions the sourcing file cannot answer. Which appraisal is current. What planning assumptions sit behind the GDV. Why the debt request does not match the latest build cost line. That is how a live deal starts drifting.

The problem usually starts much earlier. Sourcing has treated appraisal as the finish line, while underwriting treats it as the starting file. If those two functions use different inputs, different model logic, or different document sets, the deal slows down at the point where speed matters most.

A good handoff starts at first appraisal. The sourcing team should be building a file that underwriting can test without rebuilding it. That means one live record, one current model, one document library, and a clear log of what changed and why. If that discipline is missing, the underwriting team spends its time re-keying numbers, chasing PDFs, and challenging assumptions that should already have been evidenced.

The commercial cost is real. Delay can mean a missed exchange date, a revised vendor expectation, extra consultant fees, or a lender losing confidence in the sponsor's grip on the scheme. I have seen decent opportunities get marked down because the team could not produce a clean audit trail from initial appraisal to credit submission.

A workable handoff file carries the same core information through every stage:

• Lead source and seller context
• Current pricing position and deal status
• Planning basis and known constraints
• Area schedule, unit mix, and programme
• Cost plan assumptions and contingency
• GDV evidence and comparable rationale
• Debt strategy and key covenant assumptions
• Open risks, owner, and next action
• Decision history with dated revisions

That record matters because underwriting does not only test headline margin. It tests whether the story, numbers, and evidence all line up. If the appraisal says six flats at a certain exit value, the plans, comparables, cost plan, and debt request need to point to the same scheme. Once that alignment breaks, confidence drops fast.

Re-keying is where errors creep in.

An analyst lifts land cost, NSA, programme dates, and finance terms from the sourcing model into a credit model. Then a revised comparable pushes GDV down, but the loan request stays tied to the older case. The committee paper now reflects one version of the deal and the data room reflects another. Nobody set out to create risk, but the process did it anyway.

The fix is operational, not cosmetic. Use a standard intake template, force version control, and log underwriting queries against the live file rather than in side emails. Questions should attach to assumptions, evidence, or missing documents, with a named owner and deadline. That creates a clean chain from first look to credit decision.

A practical internal workflow looks like this:

1. Appraisal signed off internally
2. Model, plans, and source documents checked against each other
3. Underwriting pack generated from the live record
4. Credit queries logged against the file
5. Assumptions revised or evidenced
6. Decision issued with conditions recorded
7. Approved case moved into execution with the same dataset

The benefit is simple. Underwriting can spend its time judging risk instead of reconstructing the deal. Sourcing also gets sharper because repeated credit objections expose weak filters, lazy assumptions, and evidence gaps at the front end.

As noted earlier, the four stage pipeline described in this four stage pipeline reference points to post-agreement fallout as a recurring problem. In practice, cleaner handoffs reduce that fallout because the deal has already been shaped around the questions credit will ask.

The teams that convert well do not rely on speed alone. They present a file that is traceable, current, and financeable from day one.

Measuring Sourcing Success with the Right KPIs

Most deal sourcers track the wrong headline. They focus on deals done.

That number matters, but it’s too late to help you manage the pipeline. By the time you know completions are down, the problem has already happened upstream.

The market doesn’t offer much transparency here. Verified source material notes that the deal sourcing industry has a lack of transparent data on pipeline predictability, with most advice focused on fees per deal rather than the challenge of maintaining consistent deal flow, as described in this review of deal sourcing pipeline gaps. That’s exactly why internal KPIs matter.

Track the funnel, not just the outcome

A useful sourcing dashboard should answer simple management questions.

• Lead velocity: Are enough new opportunities entering the pipeline from each channel
• Qualification rate: How many leads survive your first screen
• Evidence completion rate: How many qualified leads reach a standard fit for internal review
• Conversion by channel: Which sources produce viable, financeable deals rather than just enquiries
• Time in stage: Where deals stall
• Win loss reasons: Why do you lose live opportunities

If your portal leads generate activity but almost nothing survives viability, that tells you the channel is noisy or your filters are weak. If deals pass viability but die in credit review, your issue is probably packaging, assumptions, or unresolved risk.

Build your own evidence base

There’s no point complaining about a lack of market data if you aren’t creating your own.

Start basic. Log lead source, asset type, location, date received, status, and reason for rejection or progression. Over time, patterns show up. You’ll see which introducers bring credible stock, which planning contexts produce delay, and which assumptions keep causing disputes at funding stage.

A practical example. If you notice a repeated drop off between offer accepted and finance submission, that points to a workflow gap. Maybe surveys are being ordered too late. Maybe title review starts after commercial terms are already agreed. Maybe the team is still packaging each deal from scratch.

Use KPIs to allocate people, not just report performance

The point of measurement is action.

One acquisitions manager may be excellent at direct to vendor conversations but weak on early technical filtering. Another may reject weak schemes quickly and save the business money even if they progress fewer deals. Raw deal count won’t show that. Stage conversion and reason codes will.

The teams that scale deal sourcing property properly don’t run it on instinct alone. They use data to understand where margin is being protected and where it’s leaking out of the process.

Conclusion From Sourcing Deals to Manufacturing Opportunities

The best operators don’t treat sourcing like a hunt for cheap sites. They treat it like a manufacturing process for fundable opportunities.

That changes everything. You stop chasing volume for the sake of it. You screen harder. You underwrite earlier. You do deeper planning and legal work before emotion gets involved. You present opportunities in a form lenders and investment committees can use.

That’s the commercial edge. Not more leads. Better qualified leads, cleaner evidence, fewer dead deals, and faster confidence when a site does stack up.

In UK development, the gap between a promising lead and a financeable opportunity is where most profit gets lost. Close that gap and your pipeline gets stronger, your capital partners trust your process more, and your team wastes less time on schemes that were never going to work.

---

If you want a more structured way to move from site lead to viability, planning review, and lender ready underwriting, Domus gives UK property teams one connected workflow instead of disconnected spreadsheets, documents, and email chains. It’s built for developers, lenders, and capital operators who need faster appraisals, better governance, and cleaner handoffs from sourcing through to investment decision.