LPlatesDriver case study Tricity Pigs · tradie systems · pre-launch product

SHOWCASE BUILT AROUND A REAL TRADIE WORKFLOW

WE BUILT THE SYSTEM
BEHIND THE TRADIE.

Tricity Pigs started as an electrical-service concept. We pushed it further: customer messaging, quote intelligence, a maintainable rate engine, scope controls and market data working together as one operating system.

  • MESSAGINGjob context attached
  • 36-RATEeditable pricing model
  • MARKETevidence-led inputs
CUSTOMER MESSAGINGMARKET-AWARE QUOTING36-RATE ENGINESCOPE GUARDRAILSDEMAND DATATRADIE-FIRST WORKFLOW CUSTOMER MESSAGINGMARKET-AWARE QUOTING36-RATE ENGINESCOPE GUARDRAILSDEMAND DATATRADIE-FIRST WORKFLOW

01 / THE BUILD

NOT JUST THE FRONT PAGE.
THE BUSINESS LOGIC UNDER IT.

The showcase is about the systems behind the tradie: how a lead becomes a scoped job, how a quote gets built, how market evidence informs pricing, and how the operator can keep the rules editable instead of being trapped inside generic software.

WHAT WE BUILT

SIX PARTS.
ONE WORKFLOW.

Each piece solves a real operating problem. Together they turn Tricity Pigs from a brochure site into a usable tradie system.

01

CUSTOMER + JOB

Customer Messaging

SARAH · MIDLAND JOB #TP-204

Kitchen power keeps tripping.

Send a switchboard photo and I’ll attach it to the job.

Customer conversations stay connected to the job instead of disappearing across texts, calls and inboxes.

  • Enquiry context stays with the job
  • Message-to-quote hand-off
  • Clear customer communication trail
  • Designed for field use
03

RATE ARCHITECTURE

Structured Rate Engine

Fault find$231
Power point$170.50
EV chargerQUOTE
Industrial dayQUOTE

Behind the calculator is an editable 36-item model that keeps the pricing logic visible and maintainable.

  • Labour classes and hours
  • Materials, markups and service fees
  • Overrides and margin checks
  • Customer price + internal economics
04

SCOPE + RISK

Scope & Compliance Guardrails

PUBLISHQUOTE ONLYPUBLISH RANGEADD-ON

The system distinguishes repeatable jobs from work that needs inspection, scope confirmation or a compliance gate.

  • Publish / quote / range / add-on rules
  • Job-specific inclusions and exclusions
  • Authority gates stay visible
  • Reduces accidental over-promising
06

OPERATOR WORKFLOW

Tradie-First Workflow

ENQUIRYSCOPEQUOTEBOOK

The pieces are designed around the operator’s day instead of forcing the operator to work around the software.

  • Message → scope → quote → booking
  • Business rules stay editable
  • Useful on a phone in the field
  • Less duplicated admin

WHAT THIS SHOWS

WE MODEL THE BUSINESS.
THEN BUILD THE SOFTWARE.

West Aussie Pallets proved the operating-system approach in one business. Tricity Pigs shows the same thinking applied to a tradie: research first, encode the operator’s knowledge, connect the workflow, then build the interface around it.

01 / RESEARCH

Understand the industry

Demand, pricing, job types, risk and customer expectations before UI decoration.

02 / MODEL

Encode the know-how

Labour, materials, scope, margins and rules become software logic the operator can maintain.

03 / CONNECT

Join the workflow

Customer message, job context and quote become one path rather than separate admin islands.

THE SELLING POINT

USEFUL SOFTWARE
STARTS WITH THE WORK.

We can take a real operator, a real market and a messy real-world workflow, then turn that knowledge into a focused product instead of another generic template.

LPLATESDRIVER / BUSINESS SYSTEMS

Business researchBUILT IN
Pricing logicEDITABLE
Customer workflowCONNECTED
Private operating rulesCONTROLLED
See LPlatesDriver ↗