Building a Data-Driven Acquisition Strategy

Most acquisition teams have a clear sense of their investment mandate in conversation. When you ask what they are targeting, they describe it precisely: asset type, geography, price range, yield expectations, preferred tenancy structure. The description is coherent and specific.

The problem is that this mandate lives in people's heads and in informal team norms, not in a form that a data pipeline can evaluate against. The gap between "we know what we want" and "our systems consistently find what we want" is the gap that a data-driven acquisition strategy is designed to close.

Why Informal Mandates Fail at Scale

An informal mandate works when the team is small and the deal volume is low. When two people are reviewing a handful of properties per month, shared mental models are sufficient to maintain consistency.

The failure mode emerges when volume increases, team members change, or the acquisition program operates across multiple asset classes simultaneously. Different team members applying the same informal mandate to the same property will disagree on whether it fits, and neither will be able to articulate precisely why their view is correct. The result is inconsistent triage, wasted inspection time, and deals pursued outside the strategy that are only recognised as off-mandate during due diligence.

The discipline of encoding a strategy into explicit, machine-readable criteria exposes these disagreements before they produce operational waste. When a team goes through the process of specifying their criteria in a form the system can evaluate, they typically discover that the informal mandate contains several points of genuine ambiguity that need resolution.

The Strategy Specification Framework

A machine-readable acquisition mandate requires specifying parameters across five dimensions.

Geographic scope should be defined at suburb or SA2 level, not at a vague "Inner Sydney" description. "Inner West from Strathfield to Newtown, excluding suburb X because of flood overlay" is a specification. "Inner Sydney" is a conversation starter. The distinction matters because your data pipeline needs to apply this criterion to every candidate property without human interpretation.

Asset class and subtype need to be enumerated rather than categorised. "Commercial" is not specific enough. The relevant question is whether you are targeting freehold commercial, strata-titled commercial, ground-floor retail with upper residential, warehouse and industrial, or some combination. Each has different comparability pools, different tenancy dynamics, and different signal patterns that indicate vendor motivation.

Financial parameters need to include a price ceiling, a yield floor, and your position on renovation or capital expenditure requirements. An acquisition strategy that targets gross yields above 5.5% but is silent on capital expenditure tolerance will surface properties requiring $400,000 of remediation work that technically meet the yield criterion but do not actually fit the financial model.

Ownership and tenancy preferences expose some of the deepest ambiguities in informal mandates. Does your strategy prefer vacant possession or income-producing properties? How much remaining lease term is acceptable? Are you comfortable with month-to-month tenancies as long as the tenant has strong covenant history? These preferences often exist as tacit knowledge in the team without having been explicitly resolved.

Disqualifying factors are as important as inclusion criteria. Heritage overlays, contamination flags, unresolved strata disputes, and proximity to planned infrastructure corridors may all be disqualifiers for specific strategies. Encoding these explicitly prevents the system from surfacing candidates that will fail on the first inspection call.

Translating Preferences into Weighted Scores

Not all criteria are equally important to a given strategy, and some criteria represent strong preferences rather than hard disqualifiers. A yield floor is a hard disqualifier; anything below 5.2% does not proceed. A preference for remaining lease terms above 24 months is a soft preference; a property with 18 months remaining might still be worth pursuing if other attributes are strong.

Weighted scoring converts these soft preferences into a ranked output. The weighting exercise forces the team to make explicit decisions about priority: when a property that is in the ideal suburb has a below-preference lease term and a strong yield, how does it rank relative to a property in a secondary suburb with an ideal lease and a median yield? There is no universally correct answer; the answer depends on the strategy, and encoding it explicitly ensures consistency.

One operational benefit of explicit weighting is that it makes the scoring system auditable. When a team reviews their shortlist at the end of the week and notices that a property they would have immediately pursued is ranked 8th, they can look at the scoring breakdown and understand exactly why. That visibility allows them to calibrate the weights iteratively against their actual deal outcomes.

The Feedback Loop Between Strategy and Data

A strategy specification is not a static document. Markets shift, mandate priorities evolve, and the team's understanding of what constitutes a genuine fit improves over time.

The most productive acquisition teams we work with review their strategy specification quarterly, using their actual deal outcomes as calibration data. Properties that converted to acquisitions get reviewed against the original score to see whether the scoring model correctly anticipated their value. Properties that were pursued and declined during due diligence get reviewed to understand whether the scoring model should have flagged the disqualifying issue earlier.

This feedback loop is most valuable at the weight level, not the parameter level. The parameters, the geographic boundaries, the price range, the asset class definitions, tend to be relatively stable. The weights, how much the remaining lease term matters relative to yield, whether PPSR signals should carry more or less weight in the off-market scoring, are the settings that benefit from iterative calibration.

The Limits of Explicit Strategy Encoding

An encoded strategy is a systematic expression of current mandate. It is not a substitute for the qualitative context that makes a specific deal good or bad independent of its score.

A property that scores well on all criteria may sit adjacent to a recently approved mixed-use development that will substantially change the street's character and the asset's income profile in 18 months. That information exists in planning documents, but the scoring model may not have access to it or may not weight it correctly. A property may have scored poorly because the current asking price exceeded the price ceiling, but the vendor has indicated through an agent that they would accept a price 12% below asking. The scoring model sees the asking price, not the vendor's real position.

We are explicit with acquisition teams that a high strategy-fit score means "this property is worth investigating based on the data we can see." It does not mean "this is a good deal." The judgment about whether it is a good deal remains with the team, informed by the scored shortlist rather than replaced by it.