Triage inbox
Tenant requests arrive as email and SMS. Each one is read, classified, scoped against the owner's approval limit and turned into a job before any tradie knows it exists.
| Actions |
|---|
No results. No request matches every filter you've set.
Portfolio
Twelve months of completed maintenance across the managed portfolio. Every job in these charts is also a priced row in the price book —
Jobs per month by trade
Show data table
Average time to fix
Days from tenant request to job completed, by month.
Show data table
Spend by trade
Twelve months of completed-job invoices.
Show data table
Price book
What jobs actually cost, by job type and suburb, from invoices the portfolio has already paid.
Priced from — real portfolio jobs. hipages sells leads and quotes. These are completed-job prices — what the work cost after it was done, in the suburb it was done in.
Median job cost — trade by suburb
Shade = median cost of a completed job. Select a cell to filter the table below.
Show data table
| Range p25–p75 | Actions |
|---|
No results. No priced row matches every filter you've set.
Job feed
| Actions |
|---|
No results. No open job matches every filter you've set.
My schedule
Jobs you've accepted. Accepting locks the job to you — the agency is notified immediately.
Nothing accepted yet. Accept a job above and it lands here.
My flow
One-off jobs arrive once and end. Portfolio jobs arrive every month, from the same handful of agencies, at a price you already know.
Where your jobs come from
Jobs completed each month, split by source.
Show data table
Revenue through TradeFlow
Invoiced value of portfolio jobs booked through the platform, by month.
Show data table
About this play
The second-order thesis behind this demo, in plain English.
The first-order wedge
The obvious product is an AI assistant for residential property managers: it reads the tenant emails, drafts the replies, and handles the maintenance requests. That is useful on day one for a single agency with nobody else on the platform, which is what makes it a viable way in. It is also not the business.
What the wedge quietly accrues
Triaging a maintenance request produces something valuable as a by-product: a job. Not a lead, not an enquiry — a specific piece of work at a specific address, already classified by trade, already scoped, already approved by the owner to a dollar figure, with the tenant's availability attached. A single agency running 300 properties throws off more repeat trade work in a year than thousands of one-off consumers. It also accrues the thing nobody else has: what those jobs actually cost, by trade, by suburb, after the work was done.
The two parties it connects
On one side, property managers, who hate chasing three quotes for a $300 job and would rather the system just book someone reliable. On the other, tradies, who currently pay lead-generation platforms for a phone number and a bidding war. Marketplaces like hipages and ServiceSeeking sell consumer leads one at a time. This arrives with recurring, portfolio-scale flow — pre-scoped, pre-funded jobs that show up every week from the same agencies. That asymmetry is why the tradie side is the one willing to pay.
Endgame
Give the PM assistant away cheaply — it solves the cold-start problem by being worth using with zero tradies on the network. Once job flow exists, charge the tradie side: a subscription for guaranteed portfolio flow, or a take-rate on the work. The third-order prize is the pricing dataset itself, which underwrites instant quoting and maintenance-warranty products nobody can price without it.
What would validate it
Two conversations. A property manager confirming they would accept an auto-suggested tradie for sub-$500 jobs without collecting quotes. And one tradie saying what they would pay per month for guaranteed portfolio flow.