Inspace AIOS
A plain-English map of what is built and running, what is ready to switch on, and what we need from you to go live.
At a glance
How it works
Every enquiry, wherever it comes from, travels the same path. The AIOS catches it, works out what it is, records where it came from, and hands it to Jobman. One direction only. Nothing is typed in twice, and no system is replaced.
Where enquiries arrive
The AIOS
Runs on Railway, in an account that transfers to Inspace at handover.
Your systems, unchanged
Built and running
Rebuilt from scratch: faster, built for search, and designed around getting an enquiry rather than just showing work. Twenty-two named project pages, each with real materials and specifications.
Currently on a preview link. It goes to inspace.nz at go-live.
The quote form on the website posts straight into the system. Repeat enquiries are flagged rather than dropped, so nothing is ever lost and nothing is double-counted.
Tested in a real browser, end to end.
The system watches your info@ inbox every two minutes and works out which messages are genuine enquiries and which are not. Anything it is unsure about goes to a review list rather than being guessed at.
Tested: an email arrived and was captured as an enquiry in 22 seconds.
Every enquiry quietly records its origin: a Google ad, a Facebook ad, a search result, or a direct visit. This is what makes it possible to say which marketing actually produced work, rather than guessing.
Already recording. It starts paying off the moment the ad accounts are connected.
Built, tested, switched off
These are finished and tested. They are deliberately switched off so that nothing reaches your customers or your live Jobman until you have signed off.
Creates the contact and the lead in Jobman automatically. If the person already exists in Jobman it reuses that contact rather than creating a duplicate.
Tested against your live Jobman: created, verified, then removed. One decision needed: which pipeline should new website enquiries start in?
An enquiry gets an immediate acknowledgement from info@, and your team gets notified straight away. Speed of first reply is usually the single biggest lever on how many enquiries convert.
Held in test mode on purpose, so no test emails ever go out from your real inbox. Switched on at go-live.
Watches the enquiry path around the clock and emails immediately if it stops working or if a notification fails to reach anyone. It means a silent failure cannot quietly cost you enquiries.
Built and tested. Goes live alongside the website cutover.
Over to you
The last piece of the marketing picture. Once connected, we can wire up tracking and start reporting on which channels actually produce enquiries and work won.
You run four lead workflows. New website enquiries currently default to βResidential - With Designβ. Tell us where they should actually land and we will set it.
We have real indicative figures from your recent kitchens. Showing a range qualifies enquiries before they reach you; hiding it keeps more enquiries but lower quality. Your call, and we can go either way.
Cameron's focus areas are clear: client experience, financial performance, staff culture. We need the specific figures you want on a dashboard so we build the one you will actually open.
Reviews or testimonials, your guarantee in your own words, and the headline numbers: years trading, projects completed, any awards or memberships. We will not invent any of these.
Worth ten minutes on Friday
Builders come through relationships, not enquiry forms, so this is not a website problem. It is a measurement one. We looked at your full Jobman lead history, nearly 1,500 leads:
One encouraging signal inside that: among your most recent leads the builder share roughly doubles, so the push toward builders is already visible in the data. It just is not being counted.
The builder's name is being written into the description rather than recorded as a category, and the same job is sometimes tagged two different ways. One recent job appears twice as Residential and once as Builder.
Which means that if you ask in six months how the builder push is going, Jobman cannot currently give you a straight answer. That matters more than any website change, because it is the difference between growing a channel and guessing at it.
Worth agreeing on Friday: one consistent way to tag builder work, whoever enters it and wherever it came from. We will make the system hold it properly, including from email, where a builder's project manager realistically would reach you.
Sequence
In order, because each step depends on the one before it.
Friday. Wire up tracking so every enquiry can be traced back to what produced it.
Once you have confirmed the pipeline. Enquiries then flow to your team and into Jobman without anyone typing anything.
Once we have your KPI list. One place to see enquiries, sources and conversion. The groundwork is already running: the system now reads your Jobman pipeline directly and has started recording it daily, so the dashboard launches with history behind it rather than starting from zero.
The switch itself takes minutes and is reversible. Your email is untouched by this.
The code, the hosting and the domain all transfer into Inspace's own accounts. You own it outright.
After the foundation
Phase 2: The engine
Deeper links between Jobman, Cabinet Vision, Microvellum and Xero. Costing that draws on your drawings instead of being rebuilt by hand. Less double entry, fewer transcription errors.
Phase 3: The client experience
Indicative designs earlier in the conversation, and project tracking so a client can follow their job from first drawing to installation.
The unhired seat
The business development role you have scoped but not filled, covering lead follow-up, conversion reporting and keeping lead status current, is exactly what this system is built to carry.
From go-live
Once the ads are connected and enquiries are flowing, the system needs an operator: managing the campaigns, watching the numbers, chasing what the data surfaces, and extending the AIOS as you need it. That is the ongoing arrangement we should agree before cutover, so nothing goes live unattended.