PlanBPlus · Work

Selected work

Platforms, portals and tools built around the work teams do every day, proven in daily operation.

Operational platformIn operation

NestMe

Context

A connected platform for room-based accommodation operations, in daily use across five states and territories: a staff workspace and mobile app, with applicant, tenant, partner and contractor portals working from the same records.

Problem

Room-based rentals connect listings, inspections, applications, leases, communications, partners, keys, and audit history. Generic property tools split that work into disconnected fragments.

What was built

One workspace for listings, inspections, applications, leases, keys, maintenance, payment evidence, bonds and expenses
A mobile app for the people on site, writing to the office's records
Applicant, tenant, partner and contractor portals, each seeing only its own slice
Our own e-signing platform, team task hub and messaging layer, built in
Automations that raise the routine work and send the routine notices
An audit trail behind operational actions and status changes

What it demonstrates

Product architecture and complex domain modelling
Replacing standalone tools with one platform, release by release
Product decisions shaped by daily operational use

Where it leads

Continued investment in finance, automation and AI assistance, on an architecture built to run other operators' businesses when the time comes.

nestme.com.au

E-signing platformIn operation

E-Sign

Context

Our own e-signing platform, built into the operations workflow rather than bolted on. Agreements are prepared from templates, sent, signed on any device, and finished with a certificate anyone can check.

Problem

When signing lives outside the system, agreements go out by email and come back as attachments, and proving which version was signed, by whom and when, means digging through inboxes.

What was built

A template editor with live fields, so an agreement is prepared from the record, not retyped
Signing on any device, with reminders that chase themselves
Documents frozen at send, with a recorded SHA-256 fingerprint
A signing certificate and a public certificate check for every signed document
Sign the official government form itself, signatures placed on the form
Counter-signing, and the finished PDF filed back on the record

What it demonstrates

Document integrity and verifiable records
An owned signing engine integrated with the operational records
Recorded signing events and document integrity checks

Where it leads

The same engine can sign anything a business needs signed: onboarding packs, supplier agreements, consent forms, with the certificate trail built in.

Team collaborationIn operation

TeamHub

Context

Where the team's work lives. Give each job an owner, a thread and a due date; let the platform raise the routine ones itself; see the day as one list.

Problem

When work is assigned in chat groups, threads scroll away, nobody is sure who holds what, and follow-ups get asked again.

What was built

My, Team and Today views: claim from the team pool, see your day at a glance
A thread on every task, with photos and @-mentions, so the discussion stays with the job
Quick capture from anywhere: type a sentence, get a task
Recurring work, placed on the calendar
Tasks raised automatically by the workflows that need them: a move, a bond, a signed lease
Push notifications when you are assigned, mentioned, answered or done

What it demonstrates

Replacing chat-group task tracking with structured, connected work
Notification design that informs without nagging
Automation that creates work only when a workflow calls for it

Where it leads

Multi-owner jobs and approval chains next, so larger pieces of work move across a team the same way a single task does today.

Email, SMS & inquiry captureIn operation

Connect

Context

One messaging layer for what a business sends and the replies it gets: templated email with a send ledger, two-way SMS, notices on a schedule, and listing inquiries captured inside the platforms they arrive on.

Problem

When messages go out from personal inboxes and phones, details slip and nothing is on record. Inquiries on external listing platforms arrive faster than a team can answer, let alone log.

What was built

Templates with live fields and attachments, for one recipient or a filtered list
A browser extension that captures inquiries inside the listing platforms and answers with the team's templates
Two-way SMS with confirmation and opt-out handled
A send ledger for every message: recipient, content, time and send status
Notices that send themselves on the schedule each office works to
Matched replies connected to the person and the workflow they belong to

What it demonstrates

Communication automation with safety rails
Multi-channel messaging on one ledger
Browser-extension engineering for work that happens on other platforms

Where it leads

More channels on the same ledger, and conversations that know the record they are about, so the right reply is one click away.

Partner, contractor & client portalsIn operation

Portals

Context

Secure portals for everyone outside the team: partners, contractors, applicants and tenants, each seeing exactly their slice of the platform, with no staff accounts to manage.

Problem

Without portals, partners ask for listings and bookings by phone, contractors get jobs by text, applicants and tenants wait on email, and every request lands back on staff.

What was built

Partner portal: listings, inspection times, bookings, payment instructions and payment-proof upload on a tokened link, in two languages
Contractor portal: job details, on-site reporting with photos, push alerts for new work
Applicant portal: apply online, track status, sign, and check the signing certificate
Tenant portal with nine language options: documents, living details and maintenance requests
Access scoped per audience, with revocable partner links and time-limited signing and job links

What it demonstrates

Controlled external access design
Self-service that removes work from staff instead of adding it
Practical multilingual UX

Where it leads

Any relationship a business runs by phone and email can get a portal: scoped, self-service, and connected to the records that matter.

Operations on the goIn operation

Mobile App

Context

The platform in the pocket of the people on site. Today's visits, moves, keys and receipts on a phone, writing to the same records as the office.

Problem

When on-site staff work from memory and messages and type it all in later, key handovers go unrecorded, receipts go missing, and the office only sees the day once it is over.

What was built

My Day: everything scheduled for you, in order
Move-ins and move-outs run from the phone, step by step
Key handovers recorded with a photo at the door
Receipts captured on the spot and filed to the right expense
Prospect capture at open homes
Installs from the browser, no app store required

What it demonstrates

Mobile-first design for field work
One record system across desk and site
Browser-installed mobile app delivery

Where it leads

Offline-tolerant work and richer on-site capture, so the platform follows the work wherever it happens.