Enterprise DNA

Instead of Property Inspect

Stop renting Property Inspect. Own your inspection records.

We build your version around your inspection cycle and your report layout, bring your inspection history and property list across, and run it for you. Inspections, tenancies and repairs end up in one database with your agency's name on it.

Property Inspect lists plans at A$69, A$100 and A$400 a month, with extra users and extra properties charged on top.

  • check_circleYour data in a database you own
  • check_circleOpen source, no lock-in
  • check_circleBuilt and run by Enterprise DNA

Where the monthly plan goes

You are paying for a second home for data you already hold

Your property list, your tenants and your owners already live in your property management system. An inspection app asks you to keep a second copy, priced by how many people use it and how many doors it covers.

group

Every extra property manager is another line

Standard includes two users, then $10 a month for each one after. Pro includes ten, then $15 each. Hire a leasing assistant or a second inspector and the plan changes, even though the number of inspections has not.

home_work

A property cap on every tier

Solo covers 100 properties and charges $0.60 a month for each one past that. Standard and Pro charge $0.20 for each property past their cap. Take on a new building and the inspection bill grows before anyone has walked through it.

sync_alt

Talking to your other systems costs the top plan

The connections to MRI, Yardi and the public API sit on Pro at $400 a month. On the cheaper plans your property list and tenancies are kept in step without those connections.

history

How far back you can look depends on the plan

Solo keeps a 30 day audit trail. Standard keeps two years. An unlimited history, the thing you want when a bond dispute from three tenancies ago turns up, is a Pro feature.

description

Your report layout, inside their template library

Solo gets ten templates and no custom ones. Custom templates arrive on Standard, and white-label reports without their branding arrive on Pro. The layout your owners are used to is something you rent back.

link_off

Findings kept apart from the tenancy

The app records a leaking tap. Whether the owner approved the repair, which tradesperson went, whether they invoiced and whether the tenant was given notice can still sit in other systems for someone to join up.

What you get instead

Inspections as part of the tenancy, not an app beside it

The cycle

Which properties are due, and which have slipped

Ask what is due this month and see every property against your own inspection cycle, with the last visit, the tenant and the day the next one falls due.

  • check Properties never inspected shown as never, and the rest by how far past the cycle they are
  • check Vacates tracked in the same records as the inspections
  • check Each property carries its own cycle
  • check No cap on properties or on the people who can ask

Notice

Entry notice checked before the car leaves

A routine visit needs written notice to the tenant, and the period depends on where the property is. The check happens when the inspection is booked, not after the tenant complains.

  • check An inspection booked with too little notice is flagged instead of saved as served
  • check The notice period kept in one rule file you set to your state or country
  • check The date notice went out stored against the visit, so the file shows it

Findings

From a note in the lounge to a finished repair

Each finding is recorded room by room, and anything that needs fixing becomes a maintenance job linked back to the inspection it came from.

  • check Jobs sorted by who they wait on: the owner, the tradesperson or you
  • check Approved work nobody has sent a tradesperson to, found without a spreadsheet
  • check Anything marked for action in a room becomes a line on the repair list
  • check Healthy homes and smoke alarm items checked against the same property record

Reports

Your report, in your colours, from your own records

The owner report is rendered from the findings in your own brand, and it is marked sent only once it really has been sent.

  • check One brand file sets your logo, colours and agency name on every report
  • check Every inspection kept for as long as you choose, with no plan limit on history
  • check Every past visit kept with the property and its tenancy, ready for the bond conversation at the end
  • check Owner monthly summaries and arrears letters built from the same data

Make it yours

Design your own Property Inspect replacement

Everything starts from the open-source base. Then it gets your name, the parts you run, your rules and your data from Property Inspect. Try it here, and we build the real one.

2. What it runs

3. Make it fit

4. Your colour

Your business · your Property Inspect replacement Your version
YB Your business

auto_awesome

Answered from your own database

Build my version

We build it from the open-source base, bring your Property Inspect data across and run it for you.

Switching

How to switch from Property Inspect

Moving off Property Inspect means exporting what your plan allows, loading it in with a test run first, and checking the result before you drop the old subscription.

  1. 1

    Export your records from Property Inspect

    Property Inspect's export depends on your plan, so check with them first about what you can pull out. Get your property list, tenancies and past inspection reports out in whatever format the account allows. Reports themselves are PDFs or shareable links, so keep those as documents attached to each property rather than expecting them to come across as data.

  2. 2

    Run a test import first

    Before anything touches your real records, there's a test run that loads your file and shows you what would happen without changing anything. Use it to catch mapping problems, missing fields or mismatched property names while nothing is live yet. Only move to the real import once the test run looks right.

  3. 3

    Check what the import flagged

    Every property that comes across has its compliance items set to unknown rather than assumed fine, because the old system saying nothing is not the same as being compliant. Go through what the import flagged, missing dates, unmatched tenancies, gaps in the record, and decide what needs chasing up and what you can leave as a known gap.

  4. 4

    Run both side by side

    Keep Property Inspect running for a short stretch while you use the new system for real work, booking inspections, recording findings, checking arrears. This is where you catch anything the export missed or the import got wrong, before your team is relying on the new records alone for daily decisions.

  5. 5

    Switch off Property Inspect

    Once the side by side period has shown the records match and your team is comfortable working from the new system, cancel the Property Inspect subscription. Your inspection history stays as documents attached to each property, and everything going forward runs through the one database instead of a separate app.

construction

Where the real effort goes

The export and import handle the data itself. The real work is deciding how your own fields, inspection stages and notice rules map into the new records, and how much history from Property Inspect you actually want to bring across rather than just archive. That judgment call is where time goes, and it is what Enterprise DNA does when you have them install and run this for you.

Not ready for a call?

Get your Property Inspect switch plan by email

We will send you the step-by-step plan for moving your business off Property Inspect, what the move really involves, and how we would do it for you.

One email with your plan. No spam, and you can unsubscribe any time.

Two ways to start

Try the free version, or have Enterprise DNA build yours

Open source

Do it yourself

Free

  1. 1 Clone the repo from GitHub
  2. 2 Run npm run demo and open the folder in Claude Code
  3. 3 Ask which inspections are overdue, or type /inspections-due
  4. 4 Load your property list, then map your Property Inspect records in when ready
Get it on GitHub

Omni by Enterprise DNA

Have Enterprise DNA build and run it

One setup fee, then a monthly retainer

  • check We bring across your properties, tenancies and past inspection reports, and check nothing is missing
  • check We set the entry notice rules to your state or country and the cycle to your management agreements
  • check We add a phone app for the visit with photos and offline mode, if your team wants one
  • check It runs inside Omni, our managed Command Center, beside your mail and your accounting
Book a discovery call

Questions

Instead of Property Inspect, answered

Our inspectors take photos on a phone. What happens to that? expand_more

The free version does not have a phone app with a camera or offline mode, so keep using what you have for the walk-through itself. The free version handles the rest: whether the visit is due, whether notice went out, the findings, the repairs and the report. When Enterprise DNA builds your version, we add a phone app for the visit so photos and findings land straight in your own records.

Can we bring our old inspection reports across? expand_more

Yes, but check what your plan lets you export first. Property Inspect produces reports as PDFs and shareable web links, and its connections to MRI, Yardi and its public API sit on the Pro plan. Your property list and tenancies come across in one import with a test run first. Past reports can be kept as documents against each property. Mapping the detail into your records is part of what Enterprise DNA does when we set yours up.

We are in Australia. Do the notice periods fit our state? expand_more

The rules sit in one plain-English file. The free version starts with New Zealand's periods. You set your state's entry notice and inspection limits once, and every check uses them. When Enterprise DNA builds your version we set it to your state and your management agreements. It is your rule book, not legal advice.

Is this only an inspection tool? expand_more

No, and that is the point. The same records hold owners, tenancies, arrears with the next notice due, repairs, compliance items and owner summaries. Inspections stop being a separate subscription and become part of the tenancy they belong to. Trust accounting stays in the system your auditor already knows.

What does it cost to add another property manager? expand_more

Nothing in the free version. There is no seat count and no property cap, because the records sit in your own database. If Enterprise DNA builds and runs your version, you pay a setup fee and then a monthly retainer for the work we do, not a charge per person or per door.

Bring your inspection schedule and your last Property Inspect invoice

30 minutes with Sam. We look at how many inspections your team does a month, what the report has to show your owners, and what happens to the findings after the visit. If it fits, we build your version and run it. If not, the free version is yours to keep.

Property Management for Claude Code is free and open source, published by Enterprise DNA.

Done paying for Property Inspect?

Get your version built