For developers · Funding a project? →

The system that tells you when your numbers are wrong

Feasibility, claims, funding and your own fee on one verified dataset — with an integrity engine that catches the mistakes a lender would.

Free to prepare, right up to funding — you pay per project only when it goes ahead. See pricing

ExcelThe DA spreadsheetEmailXeroDropboxWordYour head
One DM360 record

The same number keyed in seven places. None of them agree.

DM360 holds it once, and every report is generated from it. See what a week looks like.

Every other tool runs the project. This one also runs your business.

The money spine

Feasibility → budget → certified claim → drawdown, on one dataset. Your bank works from your numbers, not a pack rebuilt every month.

Statutory clocks, per jurisdiction

Every Australian state and territory — the Security of Payment periods encoded and running from the day a claim is served.

Your own position

Fee against promote, modelled before you sign and tracked against what you actually collected. No other tool models the development manager's side of the deal.

How a project runs

The gate will not close without its evidence

NSW development runs on seven gates. DM360 records what was handed over at each one, who attested to it, and what it was evidenced by — and refuses to close the gate without all three. A development manager will recognise the structure on sight. The difference is that here it is enforced.

AcquisitionsGate 1

Gate 1: AcquisitionCloses on Approval to Purchase

Takes in the feasibility; hands on the project design brief.

Led by
Whoever owns new business
Signed off by
The investment decision — board, IC or the two people who decide

What DM360 records

  • Site and title: lots, title references, easements and a constraint register; zoning, FSR and envelope as fields, not prose
  • Versioned feasibility: hurdle margin and IRR, GFA and GBA kept separate, one version adopted
  • Cost plan Type A then B, typed and authored, bound to the gate
  • Positioning brief, versioned and authored

What it refuses

A feasibility whose floor space exceeds what the controls allow is flagged before it reaches a decision, not after.

PlanningGates 2–4

Gate 2: Concept DesignCloses on Approval to Lodge DA

Takes in the brief; hands on the coordinated design.

Led by
Whoever owns new business
Signed off by
Development control group

What DM360 records

  • Consultant engagement: packages tendered, agreements executed, appointments with disciplines
  • Document register: revision, status, issuer, reviewer, gate
  • Authority engagement: pre-DA meetings with dates and outcomes

What it refuses

An uncommenced instrument is never treated as in force; where a rule cannot be evidenced the answer is cannot verify, never a pass.

Gate 3: Design DevelopmentCloses on Approval to Commence Marketing

Takes in the coordinated design; hands on the marketing plans.

Led by
Whoever owns design
Signed off by
Development control group

What DM360 records

  • Cost plan Type C
  • Programme with baselines: milestones and critical path, so drift is measurable
  • Risk register: named owner, mitigation, event trail
  • Feasibility re-tested against the hurdle as costs develop

What it refuses

A gate cannot close against a feasibility version superseded since it was attested.

Gate 4: Project LaunchCloses on Approval to Launch

Takes in the marketing plans; hands on the launch materials and the consent.

Led by
Whoever owns sales and marketing
Signed off by
Development control group

What DM360 records

  • The consent as a record: conditions, deferred commencement terms, date satisfied, operates from, lapses on
  • Condition register: staged to the gate that must clear it, allocated to the responsible party, discharged against evidence
  • Sales ledger: areas, entitlements, list and contract prices, deposits, trust
  • Conflicts recorded rather than smoothed

What it refuses

A condition cannot be discharged by a tick; it needs the document and the attester's name.

DeliveryGates 5–7

Gate 5: Pre-ConstructionCloses on Authority to Commence Construction

Takes in the consent; hands on 75% documentation and the certificate.

Led by
Whoever owns delivery
Signed off by
Development control group

What DM360 records

  • Conditions precedent tracked to discharge
  • Certificates recorded with the certifier, their reference and the certificate document — certifier-supplied
  • Cost plan Type D
  • Procurement bound to stage and gate
  • Statutory declarations

What it refuses

A gate whose conditions precedent are ticked without evidence will not close, however complete the rest of the stage looks.

Gate 6: ConstructionCloses on The certificate permitting occupation

Takes in the authority to commence; hands on the certificate permitting occupation.

Led by
Whoever owns delivery
Signed off by
Development control group

What DM360 records

  • The progress claim chain: builder submits, PM administers, QS values, superintendent certifies, developer pays — five named roles in order, each recording who acted and when
  • Variations and extensions of time with the decision maker named and revised dates computed from the contract
  • Site and safety records
  • Facility drawdowns with covenants tested before the draw
  • The certifier inbox

What it refuses

A claim cannot skip a role; an unevidenced payment is recorded as not evidenced, never settled.

Gate 7: Project FinalisationCloses on Settlements

Takes in the certificate permitting occupation; hands on the completed project.

Led by
Whoever owns delivery
Signed off by
Development control group

What DM360 records

  • Handover assets, checklists and the certifier pack
  • Owners corporation transfer at the first AGM
  • Settlements
  • The evidence record intact: append-only, no delete path

What it refuses

Nothing from the first six gates can be removed to tidy the last one.

Six control documents, updated at every gate

Control documents updated at each gate: every document at every gate.
DocumentG1G2G3G4G5G6G7
Feasibility
Cost plan
Development programme
General arrangement drawings
Risk assessment
Project brief

42 document updates a project must produce, and a lender may ask to see any one of them beside the approval it supported.

The cost plan matures with the project

  1. Step 1 · Acquisition

    Type A

    Order of cost on area rates

  2. Step 2 · Acquisition

    Type B

    Elemental, against the yield schedule

  3. Step 3 · Concept and design development

    Type C

    Elemental, off the developing design

  4. Step 4 · Pre-construction

    Type D

    Trade-level, against tendered packages

The gate holds maturity as data, not as a filename.

What the system refuses

A gate will not close on a tick

Every requirement needs its document and the named person who attested to it.

A gate will not close over its own data

Enforced in the database, not the screen.

Nothing is deleted

Records are archived, evidence ledgers have no delete path, and a withdrawn item stays visible and stops counting.

An unknown never becomes a pass

Every check returns pass, finding or cannot verify — never rounded to compliant.

What a refused close looks like

Illustration · invented data

Gate 5 — Pre-Construction
  • Cost plan Type D, v4 — Evidenced
  • Programme baselined, 211 activities — Evidenced
  • Pre-construction conditions — 38 of 41 discharged — three with no document and no attester
  • Feasibility — Marked satisfied at v6, while v7 was issued after that attestation

Verdict: Gate close refused

  • Three conditions precedent carry no document and no attester.
  • The feasibility it was attested against has been superseded.

The gate reopens for correction. It does not quietly close, and nobody has to notice.

What DM360 is not

Not a lodgement system
DM360 prepares, checks and records. The responsible party lodges on the NSW Planning Portal, and certificates are certifier-supplied.
Not a certifier
Certification is a named qualified person's service under their own PI cover. DM360 records the act; it never authors it.
Not an AI product
AI proposes, deterministic code decides, and a named person accepts. No model judgement sits inside a finding a lender relies on.
Not a checklist
The value is maintaining the rules through regulatory change, each carrying its source and commencement status.
Not a payments business
DM360 holds no client money, directs no funds and operates no escrow.

Funding construction?

DM360 is the loan-level evidence feed for construction lenders — certifier-supplied progress, claimed → certified → drawn → paid on one attributed record, funds-to-complete re-tested on every certification, and the Security of Payment clock on the same screen. Non-custodial: you move every dollar; DM360 never decides a drawdown. The borrower’s project is onboarded free, so you can require it at no cost to them.

It catches the four ways construction money leaks:

  • Front-loadingA builder claiming disproportionate value early, ahead of actual progress.
  • Over-claimingA builder claiming more than the superintendent/QS has certified.
  • Retention driftRetention withheld or released off the contractual ladder — early release, or an unsecured substitution.
  • Covenant breachA valuation change that pushes LVR (or ICR) across a covenant threshold.

Each detected early, on the correct contractual basis, with zero false alarms — validated in simulation, not yet on live facilities; a paid pilot produces the live evidence. Deterministic rules, no AI in the detection. Inputs are certifier-supplied; DM360 is non-custodial and never makes the funding decision.

For lenders

Built by a developer, not a software vendor

DM360 was built by a development manager who ran the projects it models, on the sites and the claims it was written for. Every register in it exists because a real project needed it. The integrity engine exists because a real report was wrong. It is the tool its author wanted and could not buy.