Start with the workflow,not the model.
We map your real operational process, structure approved business rules, run a risk-sized scenario set, and measure what changes in a controlled 30-day pilot.
Control thread
From messy input to an inspectable receipt.
This is the operating pattern to understand before deeper factory detail. Gold marks decisions. Risk red marks a stop.
- Messy work arrives
An enquiry, form or internal request enters the lane.
- Model interprets
Extract, classify and ask — inside approved sources.
- Code enforces
Rules, calculations and hard checks stay deterministic.
- Safe stop
Missing facts or out-of-bound requests pause the lane.
- Draft prepared
A review-ready output is assembled for inspection.
- Human decides
Edit, approve, reject or stop. Authority stays with you.
- Receipt kept
The run remains inspectable after the decision.
Illustrative operational model
Where time may be recovered — then measured with your baseline.
Compare a fictional manual quoting example with the governed LYC pattern. Displayed timings are discussion prompts; the pilot records your actual starting point and outcome.
View
01 / Intake
Customer message intake
Inbound job request arrives via SMS, voicemail, email or web form.
Deciphering vague messages; calling back two or three times for basic dimensions.
Fast structured extraction; missing dimensions remain visible for clarification.
Baseline before evidence
The timings above are a fictional discussion model, not a customer study or savings claim. During discovery we record your current baseline; during the pilot we measure draft time, corrections, clarification turns and safe-stops against that baseline.Next useful step
If this resembles a bottleneck you own, show us one real workflow. We map boundaries before proposing a pilot.
Governed build loop
From business knowledge to a verified specialist.
Click through each stage to inspect deliverables, guardrails and acceptance artefacts. Counts are set for the specific workflow.
01 / Map
We map the way you already prepare a quote.
You provide the price lists, labour rules, exclusions, templates and travel criteria you currently use. We organise them into a clear working specification.
What this stage leaves behind
- Custom service catalogue and labour-rate mapping
- Clear list of work that needs separate review
- Structured extraction schema for customer enquiries
- Tested price calculation rules
Kept in check
A missing price is flagged for review instead of being guessed.| Line | State | Result |
|---|---|---|
| Timber boundary fence | Pricebook admitted | NZD 185.00 |
| Travel | Pricebook admitted | NZD 450.00 |
| retaining wall | Owner exclusion | Not priced |
Next useful step
If this names a bottleneck you own, show us one real workflow. We map the current process before proposing a pilot.
Collaboration
Your business rules. Our governed execution.
We build from your existing assets outward. No messy migration is required to begin discovery.
Rate book & catalogue
Business provides
Price lists, labour rates, callout fees and travel zones.
LYC bounds
Deterministic arithmetic the model cannot mutate or invent.
Scope & boundaries
Business provides
Inclusions, exclusions and permit or site-visit triggers.
LYC bounds
Boundary detection that flags unknowns for owner review.
Tone & communications
Business provides
Examples of quotes, emails and templates you already use.
LYC bounds
Draft generation that keeps every figure verified.
Approval & sign-off
Business provides
Who may approve, and at what threshold.
LYC bounds
A human gate where drafts stay drafts until signed off.
Day-30 evidence gate
Review the evidence before anything expands.
At the end of a 30-day pilot, we review enquiry completeness, draft timing, clarification turns, owner corrections, safe-stops and any incidents. If the workflow does not justify continuation, you can stop.
Ready to map one workflow?
Tell us about the repetitive task stealing time. We assess whether it is a strong specialist candidate before proposing a pilot.