Condominium Presale and Deposit Management Software: Why the Lender Audit Finds Your Spreadsheet

Why presale administration breaks the tools built for it

Release three goes live Saturday morning. Forty-one units, eleven realtor teams, and a worksheet list four times longer than the inventory. By Sunday night the sales director has allocated units, and on Monday the contracts go out. Within two weeks the picture is this: nine contracts signed, three rescinded inside the statutory period, two purchasers who missed the second deposit instalment, one purchaser whose funds arrived from a third party the lawyer will not accept, one unit released back to inventory but still shown as sold on the price grid the realtors are working from, and a disclosure statement amendment pending because the parking allocation changed. The lender's quantity surveyor asks for the qualified presale schedule on Thursday.

The tools in use are usually Avesdo or Spark for the contract and inventory workflow, Lasso CRM (Customer Relationship Management) or a general CRM for lead capture and realtor relationships, a lawyer's trust ledger for deposits, DocuSign or similar for signatures, and a spreadsheet that the sales director actually trusts. Avesdo and Spark are purpose-built for this market and both handle the core transaction competently. Lasso is a solid new home CRM and was never intended to be a contract system.

The gap is not the contract. It is everything the contract implies afterwards. A presale contract is not a sale, it is a multi-year obligation with instalments that arrive on dates, a rescission window that must be measured precisely, an amendment history that changes what the purchaser agreed to, a deposit sitting in trust under rules that vary by jurisdiction, an assignment right that may be exercised, and a qualification status that a construction lender is relying on to advance funds. That object has to stay correct for three or four years while the building goes up, and packaged tools tend to model the sale event well and the four year tail loosely.

Problem 1: the inventory grid is a live pricing instrument and everyone has a different copy

Presale inventory is not a list of units. It is a release strategy: hold the best view units, price the lower floors to move volume, escalate prices between releases as absorption proves the market, reserve a block for a bulk purchaser, hold two units back for the equity partner. Units move between held, released, on worksheet, allocated, contracted, firm and back again.

What a custom build does: one inventory state machine, one source, everyone reading it. Every state transition is an event with a timestamp and an actor, so the grid at any past date can be reconstructed exactly, which is precisely what a lender audit or a dispute requires. Release configuration is data rather than a manual reshuffle, meaning a release defines which units, at which prices, to which channel, opening at a specific time. Price changes are versioned so a contract always references the price schedule in force when it was written. This is unglamorous and it removes an entire category of argument.

Problem 2: the deposit schedule is where the risk actually lives

A presale deposit is not one payment. It is typically a first instalment on signing, then further instalments at fixed dates or milestones over the following year or two, sometimes with a final instalment at occupancy. Each instalment must arrive, be verified, be deposited into the correct trust account, and be reconciled. In Canada, purchaser identification and source of funds obligations under anti-money laundering rules attach to this process, and third party payments raise immediate questions.

What a custom build does: model each instalment as an obligation with a due date, an amount, a status, and a document trail, then drive the chase workflow from it. Reconciliation against the trust ledger happens on a schedule rather than at quarter end, so a discrepancy between what the system says is held and what the lawyer's ledger says is held surfaces within days. Notices for late instalments generate from templates with the contract clause cited and the delivery recorded, because if you ever need to enforce a default you will need to prove the notice. Deposit protection or insurance requirements, where they apply, get tracked per unit rather than assumed.

Problem 3: rescission, amendments and material changes rewrite the deal after signing

Presale sales sit inside consumer protection regimes. In British Columbia the Real Estate Development Marketing Act requires a disclosure statement and provides a rescission period after receipt, and in Ontario the Condominium Act provides a cooling-off period for new condominium purchases. The specifics of period length, what starts the clock, and what constitutes proper delivery are jurisdiction-specific and belong with your counsel, not a software vendor.

What is universal is the operational consequence. The rescission clock starts from a delivery event you must be able to prove. A material change to the development requires an amendment to the disclosure statement, and that amendment goes to purchasers and can restart rights. Over a multi-year build there will be several: parking reallocation, amenity changes, completion date extensions, floor plan revisions. Each one produces a set of purchasers who received it, a set who acknowledged it, and possibly a set who now have a right to walk.

What a custom build does: treat the disclosure package as a versioned artefact, record delivery to each purchaser with method and timestamp, and compute the rescission expiry per contract rather than per project. Amendments become events that fan out to affected contracts with acknowledgement tracking. The report a developer needs and rarely has is a list of contracts whose rescission period is still open, and a list of purchasers who have not acknowledged the current amendment. Both are trivial once the model is right and impossible from a spreadsheet with 400 rows.

Problem 4: the lender audit is a scheduled exam you can pass or fail

Construction financing on a presale project is advanced against qualified presales. The lender and its quantity surveyor define qualification precisely: contracts firm and binding, deposits actually received and held per the agreement, purchasers at arm's length, no more than a stated share to any single purchaser or related group, contracts free of unusual conditions or side agreements, and often a minimum aggregate value rather than just a unit count.

What a custom build does: encode the lender's qualification criteria as an explicit ruleset and compute qualified presales continuously, not at audit time. Every contract carries its qualification status and the specific reason if it fails. Related party detection runs on purchaser entities and shared addresses or principals so concentration limits are tested rather than assumed. Then the export the quantity surveyor asks for is a report, not a three-day assembly exercise, and the number in the developer's board pack is the same number the lender will compute. Different lenders define qualification differently, so the criteria must be configurable per facility rather than hardcoded.

Problem 5: assignments and the long tail to closing

Between contract and completion sit years. Purchasers' circumstances change, and in strong markets assignments become a business of their own. Most contracts require developer consent, charge an assignment fee, and impose conditions including marketing restrictions. Each assignment produces a new purchaser who needs identification, a new deposit arrangement, tax consequences that vary by jurisdiction, and a change in the qualification picture the lender is watching.

What a custom build does: model assignment as a first-class transaction with consent workflow, fee calculation, document set and identification checks, rather than as an edit to the purchaser name field, which is how it gets handled in practice and why assignment history is usually unreconstructable. For the closing tail, drive selection cut-offs from the live construction schedule so a four week slip in drywall automatically moves the finishing selection deadline and notifies affected purchasers. Upgrade orders belong on the contract as amendments with their own pricing and payment terms, because they change the purchase price and therefore the closing adjustment.

What this costs and how long it takes

Across the 2,000-plus projects Digital Heroes has delivered, this is the honest shape. A first release covering inventory and release management, worksheet to allocation to contract workflow, the deposit schedule with instalment tracking and trust reconciliation, and a configurable qualified presale report runs $80,000 to $170,000 and ships in 12 to 18 weeks. A full platform adding disclosure versioning with rescission and amendment tracking, assignments with consent workflow, upgrade and selection management driven by the construction schedule, realtor commission tranches, and conveyancing handoff runs $200,000 to $500,000 phased over 6 to 12 months.

What drives price up in this category: the number of jurisdictions, because disclosure, rescission, deposit protection and trust rules differ and cannot be generalised across provinces or states. Multiple lenders with different qualification definitions. Electronic signature and identity verification integration, particularly where anti-money laundering identification requirements apply to the purchaser and the source of funds. Multi-currency and offshore purchasers. Realtor commission structures, which sound trivial and are not once you have tranched payments, co-operating brokerages, clawbacks on rescission and different rates per release. And integration with the developer's accounting system and the law firm's trust ledger, which is where the reconciliation value comes from.

Build versus buy, and when buying is the right call

Buy if you are selling a single tower under roughly 150 units, or if you develop occasionally rather than continuously. Avesdo and Spark are built for exactly this and are priced per project in a way that makes a custom build hard to justify. They handle contracts, deposits and reporting to a standard most developers do not exceed. Lasso CRM remains a reasonable front end for lead management alongside either.

Build when several of these are true. You have several projects running concurrently and need a portfolio view of trust balances, qualification and absorption that no per-project tool gives you. You operate in more than one jurisdiction with genuinely different disclosure and deposit regimes. Your release and pricing strategy is a real part of your edge and you want it modelled rather than executed by hand. You have had a lender audit produce a lower qualified number than your internal reporting. Assignments are a material part of your activity and currently untracked. Or you want the presale system to remain the record through occupancy and closing rather than handing off to a separate process at firm.

Our position: the tipping point is continuity, not volume. A developer who will sell presales continuously for the next decade is buying an institutional record. A developer with one tower is buying a service, and should buy the service.

How to choose a developer for presale software

Ask them to model the contract before they quote. The right answer separates unit, release, worksheet, contract, deposit instalment, amendment, assignment and qualification status, and treats inventory state as an event log rather than a status column. If they draw a CRM with a deals pipeline, they will build you a sales tracker and you will keep the spreadsheet.

Ask how they handle trust reconciliation. The system does not hold the money, the lawyer or brokerage does, so the value is in a scheduled comparison that surfaces discrepancies quickly. Anyone who suggests the application should be the trust ledger has misunderstood the regulatory structure.

Ask who owns the code, in writing, before kickoff. You should own the repository, the infrastructure accounts, and the right to hire another firm to continue. At Digital Heroes that is the default from the first commit. A presale system holds the contractual record of a multi-year obligation to hundreds of purchasers, and that record should never live somewhere you cannot reach.