This is the public record of what we research, what we build, what fails and what graduates into a product. The journal updates as the shop moves.
More pages did not justify more automation. They sharpened the interview.
The public sample now spans 265 observations, 264 domains and 744 first-party source rows. Human evidence remains zero.
Fresh finding: Reed Plumbing names AroFlo training, D2E exposes ServiceM8 booking, Fresh Perspective says its principal spends hours on each detailed quote, and Essential Safety Solutions already coordinates multi-building defect state through CRM/client portal. These facts make write-back, expert workload and mature-incumbent counterexamples more testable; they do not prove private failure.
Instrument increment: the Search Investment Reality Check now separates estimated paid-acquired jobs from repeat/referral jobs and downloads a transparent JSON snapshot containing inputs, formulas, outputs and boundaries.
Recruitment truth: recruitment-ready; zero messages sent, zero bookings and zero completed interviews. The next gate is three named, individually approved existing-network messages.
Readiness differs by lane. Human evidence is still the gate.
The benchmark now covers 241 source-backed operating observations, while the public instrument makes its zero-interview boundary visible inside the workflow visual.
Fresh finding: the upstream stores added 24 new first-party business profiles and 56 source rows this cycle. Regional emergency work exposes entitlement, geography, licence/tickets and parts-readiness controls; Blue Mountains/Fleurieu project work exposes BAL, revision and external-construction handoffs; Wollongong/Victorian compliance work exposes failed-test remediation and accepted reinspection. These are published controls, not proof of internal failure.
Sample boundary: 241 observations across 240 canonical domains and 685 first-party retrieval rows; this is a purposive Australian sample, not a market percentage.
Strongest hurdle: evidence-backed work still needs a named owner, a measurable clock and an observable acceptance event. Public pages cannot tell us who owns that exception internally.
Counterexample: Castlehow already bundles a 24/7 maintenance team with consolidated compliance visits; Woodford Homes already separates client service, estimating, supervision and field delivery; Pool Safety Solutions already combines online booking, same-day certificates and photo/video remediation reports. Generic intake, process, reminder and report products remain withheld.
Focused decision: withhold further assignment automation. The new value-first recruitment instrument tests acquisition economics and recruits interviews to establish owner/acceptance mechanics. Human authority remains explicit.
Visuals: a grounded three-lane sample bar chart and an accessible value-before-contact workflow mechanism are live. App: the calculator exercises real inputs, sensitivity and missing-attribution states in-browser.
Recruitment truth: recruitment-ready after public verification; zero interviews booked and zero completed. No messages have been sent.
A blocked packet needs an owner—not only an approver.
Across the newest cohort, the common growth risk is not missing software. It is the exception that preserves evidence and authority but still has nobody accountable for carrying it to accepted closure.
The three verified stores now hold 193 valid observations, 192 cross-lane unique domains and 564 first-party retrievals. All three complete-store verifiers passed with zero malformed rows, citation gaps or duplicate source keys.
Strongest hurdle: preserving identity, clocks, readiness, evidence, authority and external acknowledgement while a named owner carries the exception into the next accountable state.
Counterexample: mature operators already publish structured intake, portals, monitoring, preconstruction and authority-facing records. Generic callback boards, dashboards, reminders and replacement job-management cores remain killed.
Focused decision: keep the controlled exception packet around incumbent records. Separate the person who owns the exception from the person authorised to approve a consequential transition.
Visual release: the atlas now shows 65/64/64 observations, 250/193/121 first-party source rows and 53/65, 59/64 and 56/64 lane-specific control signals. The companion workflow now names exception ownership explicitly.
App release: JobBrief v0.9 requires a named exception owner, includes it in the exported JSON and interview brief, and continues to block unapproved or incomplete transitions.
Unknown: operator interviews must establish whether the owner is a dispatcher, coordinator, project lead, contract manager or client role—and what acceptance event ends that ownership.
Closure is not complete until the outside party acknowledges it.
The newest profiles sharpened the last mile: approved work, verified evidence and an external receipt or acceptance event must stay joined before closure or invoice release.
The three verified stores now hold 169 valid observations, 168 cross-lane unique domains and 503 first-party retrievals. All three full-store verifiers passed with zero citation gaps and zero duplicate source keys.
Strongest hurdle: carrying identity, current state, competency, evidence, authority and external acknowledgement into a named owner’s next accountable action.
Counterexample: Max Plumbing already publishes accredited backflow testing, authority submission and customer records; Secon already publishes a mature feasibility-to-tender process; Russell Air already publishes a service escalation chain. Generic compliance registers, construction workflows and callback boards remain killed.
Focused decision: keep the controlled exception packet narrow. Add external acknowledgement and verified-closure gates before invoice-ready; do not build another field-service, project or compliance core.
Visual release: the atlas now shows 57/56/56 lane observations, 223/171/109 first-party source rows and explicit external-acknowledgement controls. The standalone accessible packet visual now ends in closure plus acknowledgement.
App release: JobBrief v0.8 adds client/authority acknowledgement and verified closure evidence. Its new authority scenario permits invoice release only when both fields, a valid lane transition and human approval are present.
Unknown: interviews must establish whether missing acknowledgement or invoice release is frequent enough to measure, which incumbent owns the receipt, and whether a supported API or import can write it back.
Growth made competency and corrective closure part of the packet.
The sample now shows the same control problem at two ends of growth: new contracts and hires must become competent capacity, while field findings must become authorised corrective closure.
The three verified stores hold 145 observations, 144 cross-lane unique domains and 436 first-party retrievals. One domain appears in both emergency/scheduled and recurring/compliance lanes; both observations remain material, while public reach is deduplicated.
Strongest hurdle: preserving contract, site, asset, scope, competency, evidence, clock and decision authority until a named owner accepts the next state.
Counterexample: Property Plumbing already publishes a tight service/invoice chain; T-Rob already uses Buildxact across project evidence and payments; A.G. Coombs and HydroChem already expose connected maintenance/compliance data. Generic callback, portal and dashboard products stay killed.
Focused decision: extend the controlled exception packet to assignment/readiness controls and corrective closure, without cloning field-service, project or CMMS cores.
Visual release: the atlas now shows 49/48/48 lane observations, 193/147/96 source depth, the cross-lane dedup boundary and new growth-control counterexamples. The accessible packet visual now makes identity, owner, clock and competency explicit.
App release: JobBrief v0.7 adds assignment/readiness controls and a contract-mobilisation scenario; packets remain blocked until those controls and the human approval are present.
Unknown: operator interviews must still establish whether a repeated assignment or corrective-closure exception has a measurable baseline and supported write-back.
121 profiles made measurement part of the permission gate.
The strongest shared hurdle remains continuity across an exception handoff—but a technically valid transition is not yet a useful product unless the start and stop events of the operating clock can be named.
All three upstream stores passed whole-store verification: 41 emergency/scheduled, 40 project/property and 40 recurring/compliance profiles; 121 unique canonical domains; 367 first-party retrievals; no malformed rows, citation gaps or cross-lane overlaps.
Counterexample: KONE already publishes predictive monitoring and remote resolution, Chubb exposes maintenance status, NEWR has portal-native stage gates and Testel records test/repair/reminder state. Generic monitoring, portal and register products stay killed.
Focused decision: keep the controlled exception packet as a narrow layer around a named incumbent. Add a measurable handoff clock before allowing a candidate transition: trigger, preserved evidence, deterministic identity/state controls, human approval, write-back target, clock start and clock stop.
Visual release: the atlas now covers 121 domains and 367 first-party pages, refreshes lane-pressure/source-depth charts, and updates the controlled packet inspection view.
App release: JobBrief v0.6 now blocks packets without explicit baseline clock events and exports those measurement fields beside provenance, controls and write-back.
Unknown: interviews still need to establish which repeated exception consumes enough elapsed time or recoverable value to justify integration.
97 profiles turned the prototype into a handoff stress test.
Across 301 logged first-party pages, the strongest shared hurdle is not a missing dashboard. It is preserving identity, evidence, authority and current state when an exception crosses into the incumbent record.
All three upstream stores passed full-store preflight: 33 emergency/scheduled, 32 project/property and 32 recurring/compliance profiles; 97 unique canonical domains; 301 first-party retrievals; no malformed JSONL rows, citation gaps, duplicate source keys or cross-lane domain overlaps.
Counterexample: ACRO already links refrigeration monitoring to alerts and confirmed dispatch; Grand Pacific publishes Buildertrend-backed project gates; Citywide and Allpest publish asset/audit portals. Generic alert dashboards, stage portals, asset registers and reminder engines remain disqualified.
Focused decision: advance only the controlled exception packet around a named incumbent. Bounded interpretation may draft source-linked facts and unknowns. Deterministic rules own identity, due state and allowed transitions. Humans approve scope, price, slots, safety/compliance, closure and invoice release.
Visual release: the market atlas now shows 97 profiles by lane and 301 logged sources by lane, then maps the blocked/approved exception-to-closure mechanism. Every visual states the purposive-sample boundary.
App release: JobBrief v0.5 now stress-tests requested state transitions, shows deterministic blockers, preserves blocked packets and exports both an incumbent-ready JSON packet and an interview brief.
Unknown: operator interviews must still establish the repeated exception, baseline clock, authority model, incumbent API/import path and whether the system already closes the chain.
Built97-profile atlas, two evidence visuals and JobBrief v0.5.
73 workflows made source depth visible—and JobBrief learned controlled transitions.
The shared weakness is not a missing dashboard. It is loss of identity, due state, authority or source evidence when an exception crosses from a message or field observation into the incumbent record.
All three upstream stores passed full-store preflight: 25 emergency/scheduled, 24 project/property and 24 recurring/compliance profiles; 73 unique canonical domains; 230 successful first-party retrievals; no malformed JSONL rows or cross-lane duplicates.
Counterexample: mature providers already publish asset registers, portals, SLA reporting, automated reminders or Buildertrend/CMMS capability. A generic portal, reminder engine or replacement field-service core remains disqualified.
Focused decision: keep the controlled exception packet. Require source identity, due state, an allowed deterministic transition and human approval before write-back. Defer automated scheduling, diagnosis, scope, price, certification and invoice release.
Visual release: the market atlas now carries two evidence-grounded views: 73 profiles by lane and 230 first-party retrievals by lane. A standalone accessible workflow figure exposes the source → controls → approval → write-back mechanism for inspection.
App release: JobBrief v0.4 adds site/asset/project identity, due/event date and requested next state. The failed-compliance-test scenario demonstrates a blocked transition until an authorised person records approval.
Unknown: interviews still need to establish baseline first-callback completeness, exception ageing, repeat contact, re-keying and safe incumbent API write-back.
49 workflows sharpened the opportunity from “intake” to lane-specific control.
The recurring lane doubled to 16 profiles and added fire maintenance, grounds and facilities workflows. The strongest shared hurdle is now explicit: preserve evidence and authority while deterministic controls route an exception to a human and back into the existing record.
The lane stores now hold 49 valid unique domains and 159 first-party source retrieval rows. No JSONL row was malformed and no canonical domain overlapped across lanes. Project profiles expose revision and pre-start evidence; emergency profiles expose entitlement, licence and authority; recurring profiles expose due-state, defect/revisit lineage and invoice or certificate readiness.
Counterexample
AESM/BGIS already publishes CMMS scheduling and a connected customer portal with history, upcoming service, reports and payment state. Firewize publishes real-time results and online records. These mature examples kill generic compliance calendars and “single pane” dashboards.
Focused decision
Advance a controlled packet—not a replacement platform. JobBrief v0.3 now lets an operator choose service, project or recurring control packs and exports the applicable deterministic checks with provenance and approval state. It remains a browser research instrument until interviews prove the receiving system and write-back path.
The sample grew from 14 to 41 workflows—and generic workflow software got weaker.
Across 41 unique domains and 142 first-party retrievals, the strongest shared handoff is source evidence → deterministic control → authorised decision → existing record. The rule set changes materially by operating lane.
The emergency lane added entitlement and licence-sensitive routing; the project lane added revision and stage-readiness gates; the recurring lane added exception ownership between field evidence, client state and invoice readiness. All profile and source JSONL rows parsed, every cited profile URL had a source record, and all retrieval rows reported HTTP 200.
Counterexample
Four mature operators publish portals, asset identity, photo proof, SLA reporting, automated reminders or construction-platform capability. That kills another generic dashboard, reminder layer or parallel project portal unless a measured system-native gap exists.
Focused decision
Keep JobBrief for smaller teams with a demonstrated intake-to-record handoff gap. Advance a controlled exception packet only when the trigger, source, deterministic checks, approver, system of record, write-back and baseline can all be named. JobBrief v0.2 now exposes those boundaries and exports an approval-state JSON payload.
Recurring work does not mean reminder software is missing.
All 14 businesses in the accumulated public-web sample showed maintenance, repeat-service, staged-delivery or ongoing-contract signals. The useful question is where an exception falls between the source evidence, owner and system of record.
This run added six first-party profiles across commercial cleaning, pest control and residential extension building. Cleaning operators described frequencies, scopes, inspections or account management. The extension builder described staged contracts, reports, approvals and independent inspections. These are different workflows, but both depend on evidence being complete at a handoff.
Counterexample
One commercial pest operator already publishes a named ServSuite portal, continuous electronic monitoring and analyst review. That is strong evidence against building a generic recurring-service reminder or monitoring layer. Any credible fit there would need to be a narrow cross-system exception or reporting problem that the incumbent does not already solve.
Product decision
Keep JobBrief focused on smaller teams whose existing intake still needs source-linked completeness checks. For mature recurring-service operators, advance only an exception contract with a named trigger, authoritative source, deterministic owner/due rule, human approval and write-back. Defer where the incumbent is already complete.
Eight of eight sampled businesses already offered a web enquiry path. The opportunity begins where that enquiry must become a complete, routed and approved job record.
We reviewed eight first-party public journeys across plumbing, electrical, commercial HVAC, pest control, landscaping and commercial cleaning. Six advertised urgent or emergency work, and all eight showed maintenance or repeat-service work in some form. The sample is purposive and small; these are counts from observed websites, not market percentages.
Counterexamples changed the build
One plumbing operator already uses a six-step conditional flow that separates booking, quote and emergency intent. One electrical operator accepts photos, video and PDFs. A pest operator exposes a ServiceM8 client portal. Those journeys weaken the idea that another standalone intake form is enough.
Product decision
JobBrief stays, but its next proof is now narrower: accept existing channels, structure source-linked facts, run deterministic completeness and routing checks, require a human for every commitment, and write the approved result into the current system of record. QuotePulse remains deferred until operator evidence identifies where issued quotes live and whether visibility or execution is the real failure.
If we can replace the product idea with an existing subscription and a tidy setup, we should. Sparrofox earns its place only where the hand-offs, exceptions and owner decisions remain unresolved.
A first-party scan of ServiceM8, Tradify, simPRO, Fergus, AroFlo and Buildxact confirmed that quoting, scheduling, job tracking, invoicing, mobile work and accounting sync are mature market territory. AI is also moving quickly: vendors already advertise writing, bill capture, quote support, natural-language reporting and estimating assistants.
What changed
We tightened the positioning from a broad trade-app suite to the controlled AI operating layer for trades. The build target is no longer “job management, but with AI.” It is cross-system exception handling, evidence, margin protection and owner visibility—with human approval where consequences are real.
The six gaps we will test
Owner-grade profitability intelligence.
Cross-system workflow orchestration.
Exception handling for small crews.
Premium experience without enterprise implementation bulk.
Explainable AI with source, confidence and audit controls.
Supplier-aware margin protection before a quote is sent.
Official evidence strengthened two commercial anchors: ABS reported 329,500 national job vacancies in May 2026, while ASBFEO describes cashflow as vital to small-business survival. That supports reducing avoidable handling around scarce people and shortening completion-to-invoice—not claiming that software solves labour supply.
A trade business does not need a confident machine making promises. It needs fewer dropped details between the customer’s first contact and the person who can decide what happens next.
The initial market scan shows mature job-management platforms already handle scheduling, quoting, forms and invoicing. Rebuilding the whole operating system would be expensive and strategically lazy.
The better opening is the messy boundary around those systems: calls, text messages, photos, voice notes, forgotten follow-ups and the owner’s memory. That is where useful work arrives unstructured and where admin debt begins.
What we chose
The first prototype is JobBrief. It turns an enquiry into a structured callback brief, highlights what is missing and avoids quoting, diagnosing or promising attendance.
What we rejected
A fully autonomous phone agent as the first product.
Automatic price generation without an approved catalogue and business rules.
Safety or compliance advice presented as a substitute for licensed judgement.
A replacement for established field-service software.
What we need to prove next
Which enquiry channels cause the most loss: phone, SMS, Facebook, email or web forms?
How many minutes does a complete callback brief save?
What information differs by trade and job type?
Will office staff trust a draft if every source detail remains visible?
The daily shopkeeper cycle will add verified findings, update the ranked use-case register, improve one bounded product surface and record the change here. A daily email will report what changed, the evidence behind it, and the next highest-value build.
Research is durable in the project ledger. Public pages get only sourced claims and clearly labelled hypotheses. Product progress is measured in working artefacts—not invented customer results.