PLYNTCustom Software · SydneyGet in touch
Home/Work
Selected Work · A.5

The problems we get called in for.

Same story every time: a business held back by software that almost fits. Here are three, and what replaced them.

A.5.1Index

Three engagements.

Sheet 01. Trades · Lead captureLeads landed at 7pm. Nobody saw them till 9am.<60sLead to alert
Sheet 02. Services · Booking & paymentsBookings ran on phone tag. Payment ran on chasing.1Source of truth
Sheet 03. Ops · Internal toolsThe business ran on a spreadsheet nobody dared touch.0Fragile spreadsheets

Note — representative engagements, anonymised. Figures are specified, not audited.

Sheet 01 / 03Trades · Lead capture & dispatch

Leads landed at 7pm. Nobody saw them till 9am.

A busy electrical business ran enquiries through a form that emailed a shared inbox. The website was fine. The problem was the sixty seconds after submit — and by morning, the customer had already called someone else.

BeforeForm emails a shared inbox
AfterSMS and email to the on-call tech in seconds
BeforeAfter-hours leads sit until morning
AfterAnswered before the customer calls the next name
BeforeNo idea how many were missed
AfterEvery enquiry logged on a status board
BeforeNobody owns the follow-up
AfterOn-call routing with response times tracked
<60s
Lead to alert
24/7
Covered after hours
Managed
Hosted & maintained
Sheet 02 / 03Services · Booking & payments

Bookings ran on phone tag. Payment ran on chasing.

Clients booked by phone, landed in a spreadsheet, and paid whenever they got around to it. Double-bookings and unpaid invoices were a weekly tax on the owner's time.

BeforeSlots booked by phone and email
AfterClients self-serve against live availability
BeforeA spreadsheet as the source of truth
AfterOne admin dashboard, no spreadsheet
BeforeDeposits chased after the fact
AfterStripe deposit taken at the moment of booking
BeforeReminders sent by hand, or not at all
AfterAutomatic email and SMS reminders
1
Source of truth
Auto
Deposits & reminders
Hrs/wk
Admin handed back
Sheet 03 / 03Ops · Spreadsheet to internal tool

The business ran on a spreadsheet nobody dared touch.

One enormous file held the whole operation — fragile, un-auditable, and impossible to onboard anyone onto without a week of hand-holding. We rebuilt its real logic, and kept the parts the team already liked.

BeforeOne master file, no validation
AfterValidated entry that rejects bad data
BeforeEveryone can edit everything
AfterRole-based access, per team
BeforeNo record of who changed what
AfterFull audit history on every record
BeforeA week of hand-holding to onboard
AfterNew staff productive the same day
0
Fragile spreadsheets
Roles
Safe team access
Days→hrs
Onboarding time
A.5.2What good looks like

How every project is judged.

It fits

Matches how you actually work — no workarounds bolted on to suit the tool.

It's measured

Leads captured, hours saved, errors gone. Outcomes, not features.

Looked after

We host it, secure it and update it. You never think about it.

It lasts

Standard tools any engineer can pick up, long after launch.

Let's spec yours.

Tell us what's slow, manual, or held together with tape.

Start a conversationSee services