AI that earns its place.

1. 01

   Follow the work before automating any of it

   We sit with your team and follow one job the whole way through. Most of what gets sold as an AI problem is a form in the wrong place or a field somebody types twice.

   • The job, end to end: enquiry, quote, schedule, do, invoice, chase
   • What we write down: who touches it, what they open, what they re-type
   • What you get: a map of where the hours go — yours to keep
2. 02

   Connect the tools you already pay for

   Most businesses do not need another platform. They need the five they already own to stop needing a person in the middle re-typing the same customer's details.

   • Enquiry form into the CRM, once
   • CRM into the quote, then the quote into the invoice
   • All of it into one report nobody rebuilds by hand
3. 03

   Draft with software, publish with a person

   Software gets you to a rough draft in seconds. Somebody who knows your business decides what goes out with your name on it, and that order never reverses.

   • A first draft of an ad
   • A reply to an enquiry you answer forty times a month
   • A summary of a long phone call
   • The skeleton of this month's report, ready to be corrected
4. 04

   Answer the calls you are currently missing

   A missed call after hours is a job that went to somebody else. A voice assistant picks up, takes the details and books the job.

   • It says what it is, in the first sentence
   • It takes the name, the address and the problem
   • It books into your calendar and texts a confirmation
   • It hands anything unusual or upset straight to a person
5. 05

   Put your own documents behind the answers

   Rather than answering from general knowledge, the assistant reads your material and tells you which document the answer came from. The industry calls this retrieval.

   • What it reads: price lists, SOPs, warranty terms, past jobs, supplier specs
   • What it returns: the answer, plus the file and the line it came from
   • Why that matters: a person can check it in one click
6. 06

   Build the tool when the spreadsheet runs out

   Job boards, quoting tools, approval queues and dashboards. These are custom platforms first and AI second — the model is a feature inside the tool, never the reason it exists.

   • A dashboard that replaces three logins and a weekly export
   • A quoting screen that raises the invoice from the same record
   • An approval queue, so nothing goes out unreviewed
   • A mobile app for the field team and a console for the office
7. 07

   Write down what the software is never allowed to do

   Agreed in writing before anything touches a live account, because it is a business decision rather than a technical one.

   • Which actions need a human signature
   • Which data never leaves your environment
   • What gets hidden or removed before a model sees it
   • What happens when the software is not sure
8. 08

   Keep it private where privacy is the real requirement

   Most businesses do not need this level of isolation and we will say so. The ones that do need it built properly rather than promised.

   • Models run on hardware you control, not a third party's
   • Encrypted storage and role-based access
   • An audit log of who saw what, and when
   • Written in the contract, not described on a call
9. 09

   Make the business readable to the assistants

   The visibility half. One clear description of what you are, facts marked up so nothing has to be guessed, and pages that answer the question at the top.

   • One description of your business, matched everywhere it appears
   • Structured data — facts written in a format machines read directly
   • Pages shaped like the question, answered in the opening lines
   • A deliberate decision about which AI crawlers get in
10. 10

    Measure it, then keep watching it

    Automations fail quietly and mentions disappear quietly. Both need watching on a schedule rather than when somebody happens to notice.

    • Logging on every automation, and an alert when one stops
    • A monthly check on what the assistants say about you
    • A report a non-technical person can read without a translator
    • The failures included, not just the wins

Two of these ten are big enough to have their own page. Step six — dashboards, internal tools and platforms — is covered by custom platforms and dashboards. Step nine is covered by generative engine optimisation, with SEO services underneath it.

1. Week 1

   The walkthrough

   We follow the work rather than the org chart. The output is a written map of where the hours go, and you keep it whether or not you hire us.

   • Who touches a job, and in what order
   • What they open, and what they type twice
   • Where a job sits waiting for somebody
2. Week 2

   The shortlist, with the boring options left in

   A ranked list of fixes, each with a reason and a rough effort. It deliberately includes the ones that need no AI at all.

   • Sometimes the fix is a mandatory field, not a model
   • Sometimes it is one integration nobody ever built
   • You see the order, and the reasoning, before work starts
3. Weeks 2–6

   One workflow, built narrow and built properly

   We finish a single job end to end inside your existing systems instead of demonstrating six half-things. Narrow and finished is the only version that survives a busy week.

   • One job, chosen because it is the expensive one
   • Built into the tools you already own
   • Working on real data, not a sample file
4. Weeks 4–10

   The person in the loop, placed on purpose

   Nobody should have to guess who to ring when something looks wrong, so it is decided and written down before go-live.

   • Which steps stop and wait for an approval
   • Who gets told when something escalates
   • What happens when the software is unsure
   • One named owner per automation
5. Monthly

   The report, and the failures in it

   On a fixed rhythm, good news or bad. If something went backwards you hear it from us first.

   • What ran, and how often
   • What broke, and what a person had to correct
   • What the assistants said about you this month
   • What we are changing next
6. Ongoing

   Re-reading the tools

   Models, prices and limits change without a changelog and sometimes without notice. Part of the retainer is somebody whose job is to notice.

   • A model gets retired, or gets better
   • A price changes, or a limit moves
   • We tell you when something we relied on stopped being true

Nothing goes live without a named owner and a written rule for what it may do on its own. That is a Compound requirement, not a preference — and it is the difference between a build and an experiment.

• Runs on its own

  Writing the first version of something

  Quick, cheap, and always read by somebody before it leaves the building.

  • A first draft of an ad
  • A reply to an enquiry you answer every week
  • A summary of an hour-long call
  • The skeleton of a report, ready for a person to correct
• Runs on its own

  Finding the answer inside your own documents

  The answer comes back with the document it came from, so a person can check it in one click.

  • Price lists and rate cards
  • Procedures, warranty terms and contracts
  • Notes from jobs you did two years ago
• Runs on its own

  Doing the same small thing ten thousand times

  The work nobody was ever glad to be doing.

  • Copying a detail from one system into another
  • Tagging, filing and transcribing
  • Chasing a quote nobody replied to
• Runs on its own

  Watching for the thing that broke at 3am

  It watches continuously, because the failures that cost you money are the quiet ones.

  • A data feed stops arriving
  • A form starts failing silently
  • Ad spend spikes overnight
  • An automation stops running and says nothing
• Signed before it ships

  Deciding what your business actually is

  Written down once, then every page, ad and assistant answer is held to it.

  • What you sell, and what you do not
  • Who you are for
  • What is true enough to publish
• Signed before it ships

  Deciding what an automation may do on its own

  Where a mistake would cost you a customer, a person signs. It is a business decision rather than a technical one.

  • Drawn before anything goes live
  • Written down, not agreed on a call
  • One named owner per automation
• Signed before it ships

  Talking to your customers when it matters

  A voice assistant can take an after-hours booking. It hands over the moment a call stops being routine.

  • It tells the caller what it is
  • It hands over when somebody is upset or unusual
  • It leaves a transcript, so nothing rests on memory
• Signed before it ships

  Reading the report and changing the plan

  Specialists who sit together in Melbourne, on your account. The report is where the plan changes.

  • Why a number moved
  • What we are doing differently because of it
  • What we would stop doing altogether

• Custom platforms and dashboardsJob 03 in full. Most of the AI we ship lives inside a tool somebody uses all day, so this is where the build work is described properly.
• Generative engine optimisationJob 01 in full. Getting named inside AI answers, rather than automating work inside your own business.
• SEO servicesThe foundation underneath it. No version of AI visibility works on a site ordinary search engines cannot read.
• The data layer an AI system reads fromThe reason any of this is measurable. Visits from assistants and enquiries handled by an automation have to be counted separately.
• Improve lead qualityQualifying, routing and scoring. Usually the first place automation pays for itself, because a bad lead costs your team the same hour as a good one.
• The technology divisionThe people who build the platforms — Australian hosting, integrations, escrow and the procurement paperwork government work comes with.