The client portal: build it or subscribe to it?
Property managers and commercial clients increasingly want a portal, not a phone call: work orders in, photos and certificates out, status they can self-serve. The question is whether you rent one monthly or build one that is yours. This argument doesn't have to happen in the abstract: I built a live client portal you can click around right now, no signup, then we can talk honestly about which side you're on.
First, click the thing
The exhibit: a live client portal for a fictional field-service business. The client opens a job, watches the progress bar move (the same one you see), pulls the invoice and the paper trail, all without texting you "any update?". It is a branded front door that turns the maintenance relationship into a record that keeps itself.
That demo is real, running software. I built it because commercial clients kept asking my own ventures for visibility, and the answer "I'll email you" does not win the contract.
The honest case for subscribing
A portal bundled inside a bigger platform, or a standalone portal product, earns its keep in specific situations, and pretending otherwise would be salesmanship:
- You already run the platform deeply. If your jobs, invoices and documents all live in one system already, its portal module inherits that data for free. Turning it on beats building anything.
- You need it tomorrow. A subscription switches on today. A build takes weeks.
- Your clients' needs are genuinely standard. If the vendor's idea of "what a client sees" matches what your property managers actually ask for, the fit costs you nothing.
The honest case for building
- Your data is scattered, permanently. Real maintenance shops run a job app plus Xero plus a compliance folder plus a spreadsheet. A subscription portal wants everything inside its walls; a custom portal reads from where the job history and certificates actually live.
- The portal is the sales pitch. The paper trail is what makes a maintenance contract sticky, because switching to a cheaper trade means giving up the whole record. Your portal wearing your brand is a retention feature; a generic vendor login is not.
- Fixed cost, not a forever tax. A portal build is a one-time fixed price. Per-client or per-seat portal pricing compounds monthly, forever, and climbs every time you win another property manager, which is exactly when you can least afford a per-head tax on growth.
- It becomes yours to extend. Certificate reminders, an owner-facing summary, per-property views: bolt-ons to a system shaped for your clients, not feature requests into a vendor's queue.
All-in on one platform whose portal already fits your clients: use its module. Running the normal Australian mixed stack (job app + Xero + a compliance folder) and winning maintenance contracts on the strength of your paper trail: a built portal reads from where your data actually lives, wears your brand, and stops charging you more every time you grow.
Subscribe vs build, side by side
| Question | Subscribe (portal module) | Build (custom portal) |
|---|---|---|
| Best when | You already run one platform whose portal fits your clients | Job history and certificates span a job app, Xero and a compliance folder |
| Cost shape | Per client or per seat, climbs as you win work | One-time fixed; standalone from $1,500, full portal from $3,500 |
| Your data | Must live inside the platform | Reads from where it already lives |
| Branding | Generic vendor login | Your brand; a retention feature |
| Time to live | Today | Weeks, or inside 60 days on Ops Care |
| Ownership | Rented; charges grow with your client list | Licensed to you, yours to extend |
The maths worth doing
Skip the vendor ROI calculator and run one honest comparison. Take the monthly cost of the portal tier you would need, times the number of clients or seats it charges for, times 24 months, plus the setup nobody counts. Put that next to a fixed-price build plus an Ops Care plan if you want it maintained and extended monthly. For most maintenance shops adding property managers over time, the build side of that ledger wins before the second year is out, and the portal is genuinely yours.
Do not take my word for the workflow: the demo is the argument. If the screen would win you the next maintenance contract, the audit works out what your version needs to read from.
What your version would involve
The 30-minute Tech Leak Audit maps where your job data, photos and certificates actually live and what a v1 portal reading from them looks like. Standalone builds start from $1,500 fixed; a full property-manager portal is usually scoped as a bigger build from $3,500 depending on how many systems it has to join, and honest v1 scoping goes in the proposal. Or it ships inside the first 60 days of an Ops Care plan and keeps growing monthly from there. The what-your-clients-see version of this is on the property manager portal page, and the sister build-vs-buy call for margin lives at job costing: build vs buy. The missing paper trail is one of the leaks the State of Trades Admin 2026 data finds across the trade, and it bites hardest for plumbing and maintenance shops carrying compliance certificates.
Build vs buy a client portal: common questions.
Should I build or buy a client portal?
Buy the module if you already run one platform deeply and its portal matches what your clients ask for. Build a custom portal if your job history and certificates are scattered across a job app, Xero and a compliance folder, and the portal is part of how you win and keep maintenance contracts. For most maintenance shops on a mixed stack, building wins on both fit and cost over time.
Isn’t building a portal more expensive than subscribing?
Upfront, yes; over time, usually not. A build is a one-time fixed price, while per-client or per-seat portal pricing compounds monthly and climbs every time you win another property manager, which is exactly when a per-head tax on growth hurts most. Run the sum over 24 months and the build side usually wins before the second year is out.
Can a custom portal pull from my job app, Xero and my compliance folder?
Yes, and that is the reason to build. A subscription portal wants everything inside its own walls. A custom portal reads from where the job history, invoices and certificates actually live, so clients get a single self-serve record without you first migrating the whole business into one vendor.
Will the portal carry my branding?
Yes, and that matters more than it sounds. Your portal wearing your brand is a retention feature: the paper trail is what makes a maintenance contract sticky, because switching to a cheaper trade means giving up the whole record. A generic vendor login does not do that work for you.
How much does a client portal cost and how long does it take?
Standalone builds start from $1,500 fixed; a full property-manager portal is usually scoped as a bigger build from $3,500 depending on how many systems it has to join, with honest v1 scoping in the proposal. It takes weeks, not the afternoon a subscription switches on, or it ships inside the first 60 days of an Ops Care plan and grows monthly.
Do I own the portal once it is built?
You own your data, your credentials and your platform accounts, exportable any day. The portal software itself is licensed: I keep it running and improving under Ops Care, with a source buyout price written into your agreement from day one if you ever want it outright. No hosting ransom, no lock-in on your client records.
Not sure what fits your shop? Ask me, not a sales rep.
A 30-minute Tech Leak Audit and a one-page written finding inside 48 hours. Three prioritised fixes, no pitch, and the report is yours either way.