Stabicraft AI Opportunity Board
What AI could actually do here, and what it should not touch
Aluminium boat building · Stabicraft
Twelve places AI could do real work across a boat builder, from the sales floor to the shop floor, each one sized for value, effort and risk. The two that could be proved without any internal access are running on this page, answering from public documents and citing every claim.
Eight stops, advanced by hand. Nothing plays on its own, so you can stop and ask at any point.
16
public documents loaded, nothing internal was used
Cited
every answer traces back to its source and page
0
invented numbers about the business
Plain English questions across the loaded public documents, answered with a footnote on every claim, and a plain refusal when the documents do not cover it.
How Ask Stabi answers
What a board member asks it
Checks what the company has already put in public, so a board paper quotes the company's own words rather than a recollection of them.
Switch persona in the header and the questions change. The documents behind them do not: there is one corpus, read the same way at every level.
Tap one of the questions above, or type your own. Try one the documents cannot answer as well, and watch what it does.
Twelve places AI could do real work here, sized rather than sold. Two of them run on this page. The other ten are the screens deliberately not built yet, each one carrying what it would be worth, what it would take, what could go wrong and what it would be measured on.
Ask a question in plain English and get the answer with the document and page it came from, so it can be checked instead of trusted.
What we would measure: How often a question is answered straight from the material, and what share of answers carry a source the reader can open.
Running above, in Ask StabiThe options a buyer picks arrive as fields rather than as a paragraph of notes, and travel to the order without anyone typing them again.
What we would measure: Time from a configured spec to a held order, and the share of orders that reach the floor without a re-key.
The ERP grammar in the wire follows the published Greentree REST documentation. The demo posts to a simulated endpoint, never to anyone's server.
Running below, in the wireLeads that land as ADF or XML in an email become structured records, so nothing waits in an inbox for someone to notice it.
What we would measure: Share of enquiries arriving as structured fields rather than free text, time to first reply, and how many are still open after a week.
Marine dealer management systems keep their APIs behind certified partner programmes, so an ADF or XML payload sent as plain email is the one lane that reaches every dealer whatever software each of them runs.
The production detail, the quality check and the handover for each hull are captured where the work happens, so the file for that boat assembles itself.
What we would measure: Time to produce the complete record for one hull, how many records are complete at handover rather than chased afterwards, and the same for an export build.
The CPC scheme run by the New Zealand Marine Industry Association with Coastguard New Zealand carries a per-boat record-keeping obligation and an annual independent surveyor audit. Boats exported to Australia add the Australian Builders Plate. That paperwork exists whether or not anyone digitises it.
What the nesting software actually cut, and what was left over, lands against the job instead of staying in the cutting room.
What we would measure: Sheet yield per job, offcut reuse, and how much of the material cost on a job is real rather than estimated.
The nesting vendors ship this pattern for other systems: ProNest Data Sync, SigmaNEST SimTrans and Lantek Powersync all push cut results back to Epicor, SAP, Sage, Oracle or Tekla. No Australasian on-premises ERP appears on any of those lists, so in this part of the world the loop is usually left open.
The order becomes a draft work order with the parts list already attached, for a planner to check rather than to build from scratch.
What we would measure: How many work orders are typed from another screen, and how many parts lines are corrected after issue.
Bays, builds and the parts they are waiting on sit on one board, so a delay is visible before it reaches the floor.
What we would measure: How far ahead the schedule stays firm, how often a build waits on a part or a bay, and how much of the plan survives the week.
Scheduling is the card with the highest risk in the register on purpose. It touches the most people, and a plan nobody trusts is worse than the spreadsheets it replaced. It belongs after the low-risk cards have earned some trust.
Where the same option is built differently on two models, that difference is raised before a build starts rather than found at the bench.
What we would measure: Differences found before a build starts rather than during it, and how many rework hours follow each one.
When a claim arrives, the build record for that hull comes with it: what was fitted, who signed it off and when it left.
What we would measure: Time to assemble the history behind a claim, and how many claims need a second request for information before they can be answered.
The same fault appearing on the fifth boat is noticed as a pattern, not as a fifth separate job.
What we would measure: Time between the first and the fifth appearance of a fault, and whether a design or process change followed it.
The method a senior builder would explain in thirty seconds is captured with them and served back to an apprentice at the bench, in their words.
What we would measure: How much of what the senior builders know has been captured while they are here to capture it, how often an apprentice finds the answer at the bench, and first-time-right rates on the jobs it covers.
This one is built with the senior builders, not about them. Nothing is captured without the person who knows it sitting in the room, and the material carries their name on it.
Anything that sends or reads mail through the old Exchange interface moves to Microsoft Graph, and it is worth doing that move once rather than twice.
What we would measure: Whether every mail-driven job is on Microsoft Graph before the retirement date, and how many break in the switch.
Microsoft retires Exchange Web Services for Exchange Online on 1 October 2026, and Greentree 2026.1 adds Microsoft Graph mail in response. This is a vendor date, and the work lands on every site running Microsoft 365 alongside Greentree whether or not an AI project ever starts.
Two of these run on this page. The rest are cards, sized from the outside, and every one of them would be re-sized with the people who do the work before anything was built. The scores are a starting position for that conversation, not a quote.
Every system below is simulated, and every note is drawn from vendor and industry documentation rather than from any knowledge of Stabicraft’s own setup. The point of the panel is the shape of the work: which lanes exist, which ones do not, what each wire would hold, and where a careful design stops.
Every note below comes from vendor or industry documentation that anyone can read. None of it is a statement about Stabicraft's own systems, versions or configuration.
Greentree has no webhooks
There is no event push anywhere in the Greentree API documentation, so every consumer of Greentree data polls it on a timer. The REST API runs on Greentree's own embedded web server, port 9000 by default, with the URL grammar host:port/company/entity/identifier.
So: Anything sold to you as real time against Greentree is a poll. The interval belongs in the design, said out loud.
It authenticates twice, and it allocates the IDs
A call carries HTTP Basic credentials for a Greentree user plus the site serial number as an ApiKey header. A POST sent without an identifier creates the record, and Greentree allocates the id.
So: Every integration has to keep its own ID map, because the id only exists once the write has landed.
No off-the-shelf connector reaches Greentree
The MYOB connectors on Zapier, Make and Power Automate authenticate against MYOB's SME cloud line, AccountRight and MYOB Business OAuth, which is a different product from Greentree. MYOB has said a Power Automate connector is not in scope.
So: The supported build is a custom connector over the on-premises data gateway, not a recipe anyone can click together in an afternoon.
Exchange Web Services retires on 1 October 2026
Microsoft is retiring EWS for Exchange Online, and Greentree 2026.1 adds Microsoft Graph OAuth mail in response to it.
So: Every site running Microsoft 365 alongside Greentree has mail integration work coming regardless of whether an AI project ever starts.
Marine dealer systems are partner gated
The dealer management systems in this market, Lightspeed, Blackpurl, DX1 and Ideal, publish no self-serve API documentation, keep access behind certified partner programmes and have no iPaaS connectors. The lane that works with every dealer is an ADF/XML lead payload sent as plain email, alongside the manufacturer's own portal.
So: A dealer plan that assumes API access into dealer software is a plan that stalls at the first phone call. Email and the portal are the lanes that actually exist.
The nesting loop back to an ERP is unfinished industry wide
The nesting-to-ERP products, ProNest Data Sync, SigmaNEST SimTrans and Lantek Powersync, push cut results and remnant yield back to Epicor, SAP, Sage, Oracle and Tekla PowerFab. No Australasian on-premises ERP appears on any of those lists. Separately, CNC machine networks are kept off the business network by design.
So: A credible design stops at the nesting queue and says why, rather than drawing a line into a machine network that should stay isolated.
One place where the reading, the rules and the writing sit. Every wire below runs through it, and every wire has a credential story before it has a feature story.
Boat configurator (simulated)
Public website
Where a buyer picks hull, power, electronics and trim. The option codes used in the wire below are invented for this demo: a public 3D configurator does not usually publish a machine readable option vocabulary.
HubSpot CRM (simulated)
Cloud
Deals, dealers and contacts. Well documented API, private app tokens scoped per object type, and the easiest wire in the set to build.
MYOB Greentree ERP (simulated)
On premises
Stock, jobs, debtors and factory orders. Its REST API runs on Greentree's own embedded web server inside the network, so every wire to it is an inside-the-fence wire.
Microsoft 365 (simulated)
Cloud
Mail, calendar, Teams and files, reached through Microsoft Graph. The mail lane has a fixed date on it that has nothing to do with any AI project, see the vendor notes.
Dealer portal (simulated)
Cloud, run by the manufacturer
Where dealers place orders and raise warranty claims. Dealer-side systems stay partner gated, so the two lanes that reach every dealer are this portal and plain email.
Nesting and CNC (out of scope)
Machine network, kept separate on purpose
Where a careful design stops. A cut list leaves as a file for a person to pick up, and nothing reaches back the other way into the machine network.
Configured boat spec arrives
APIRuns on this pageBoat configurator (simulated) to AI layer (simulated)
Runs in the wire below. The option codes are illustrative placeholders, not anyone's real vocabulary.
Credential: Signed payload, no standing login
Create the deal with structured fields
APIRuns on this pageAI layer (simulated) to HubSpot CRM (simulated)
Each option becomes its own field rather than a sentence in a notes box, which is what makes it countable later.
Credential: HubSpot private app token
Poll for the matching debtor and stock
PollRuns on this pageMYOB Greentree ERP (simulated) to AI layer (simulated)
A poll, because Greentree publishes no webhooks. The interval is stated out loud rather than dressed up as real time.
Credential: Dedicated read-only Greentree user
Post the factory order
APIRuns on this pageAI layer (simulated) to MYOB Greentree ERP (simulated)
The only wire in the set that writes to a system of record, so it is the one with the tightest story around it.
Credential: Separate write user, Basic plus ApiKey
Mail and calendar through Microsoft Graph
APIDesign onlyMicrosoft 365 (simulated) to AI layer (simulated)
Worth sequencing against the Exchange Web Services retirement date below, because that work is happening anyway.
Credential: Entra app registration, Graph permissions
Dealer leads as ADF/XML email
EmailDesign onlyDealer portal (simulated) to AI layer (simulated)
The unglamorous lane that reaches every dealer, whatever software each of them runs.
Credential: Receive-only shared mailbox
Orders and warranty claims from the portal
APIDesign onlyDealer portal (simulated) to AI layer (simulated)
No dealer-side system credential is asked for or stored at any point, because dealer software is partner gated.
Credential: Service account on the manufacturer's own portal
Cut list out as a file drop
FileDesign onlyMYOB Greentree ERP (simulated) to Nesting and CNC (out of scope)
This is where the design stops on purpose. Nesting results come back through a person, not through a wire.
Credential: None, a file into a folder
One configured boat, from a choice on a website to a held factory order, through the same four steps a real build would use. Every system in it is simulated. The last step posts for real, so devtools shows a genuine request.
One pre-baked spec, no form to fill in. Roughly five seconds end to end.
A configured boat leaves the website
WaitingOption codes, not a paragraph of notes. This is what makes everything downstream possible.
It becomes a CRM deal with structured fields
WaitingEach option lands in its own field, so it can be counted, filtered and reported on later.
The ERP is polled for the matching debtor
WaitingNo webhooks exist on this ERP, so the wire waits and asks. The wait is shown rather than hidden.
A factory order is posted, and the ERP allocates the id
WaitingA create carries no identifier. The id comes back from the ERP, which is why an ID map is needed at all.
The boundary is worth agreeing before the features are. This is the boundary this demo actually runs inside, not a policy it promises to follow later.
What it may read
Public Stabicraft material, loaded on this page and listed in full beside the console.
What it may never read
Not restricted by policy, restricted by architecture. No credential to any of this exists.
What needs a human
The line is drawn at anything that leaves the screen or changes a record.
What it will refuse
Refusing is a feature of the engine, not a disclaimer. Press the button and watch it happen.
Do not take the refusal on trust
The public site says nothing about who owns Stabicraft, so the loaded documents say nothing about it either. This runs “Who owns Stabicraft?” through the same engine as every other question above.
There is no chart on this page, and that is on purpose. A chart drawn before the first baseline is taken is invented data. What follows is the measurement instead: what would be baselined in week one, what would be read every week, who would see it, and the monthly page a board would get once the numbers are real.
Capacity
Work that was not getting done starts getting done. More quotes answered the same day, more of the build record captured as it happens, more of the backlog cleared by the same team.
Quality
Fewer things found late. First time right on the jobs a change touches, fewer corrections after issue, and a claim answered from a record rather than from memory.
Export growth
The paperwork that comes with selling into another market stops being the thing that slows a build down. Records complete at handover, and compliance evidence assembled rather than reassembled.
Those three are the only frames used anywhere on this board. The capacity being freed up is capacity to do the work that is not getting done now, and the people who do the work are the people it is built with.
The low-risk cards from the register, the ones worth starting with. Every baseline is taken before anything is switched on, because a benefit nobody baselined is an anecdote.
| Opportunity | Baselined in week 1 | Read every week | Who sees it |
|---|---|---|---|
| Cited answers over company material | For two weeks, count the questions that get asked around the place, where the answer was found, and how long it took. | Questions answered from the material, and the share of answers carrying a source someone can open. | Whoever owns the material, in a five minute standing item. |
| Per-boat build records captured on the floor | Take ten recent hulls and time how long the complete record takes to assemble today, and how many were complete at handover. | Records complete at handover, and anything still being chased after the boat has left. | Production and quality, on the same weekly page. |
| Dealer enquiries normalised on arrival | Four weeks of enquiries: how each one arrived, how long until the first reply, how many went cold. | Enquiries arriving as structured fields, time to first reply, and anything still open after a week. | Sales and the dealer network manager. |
| The apprentice coach | Ask the apprentices what they had to stop and find out last week, and ask the senior builders what they were asked. | Answers found at the bench, methods newly captured, and first time right on the jobs it covers. | The training lead, with the senior builders who taught it. |
The skeleton, with every cell still empty. It fills from your own systems, starting with the week one baseline, and nothing goes in it that cannot be traced back to where it came from.
| Measure | Baseline | This month | Direction | What changed |
|---|---|---|---|---|
| Capacity: quotes and enquiries answered within a day | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
| Capacity: build records complete at handover | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
| Quality: first time right on the jobs in scope | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
| Quality: corrections raised after issue | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
| Export growth: compliance evidence ready at handover | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
| Adoption: people using it, and what they used it for | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 | to be baselined in week 1 |
One more rule worth agreeing up front: if a measure cannot be read out of a system that already exists, it does not go on the page. Counting something by hand every month is a job that quietly stops after the third month, and then nobody knows whether any of this worked.
Nothing on this page touches a Stabicraft system. It was built from public information only, by an applicant, and every connected system shown in the demo panels is simulated and labelled as such.