Inspace AIOS

The system
so far.

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.

Prepared for Jonty Peacocke & Cameron Rutherford Friday 31 July 2026 Phase 1: Foundation

At a glance

Where things stand

2 Capture channels live Website form and your info@ inbox. Both tested end to end.
22 Project pages built Named case studies, written and photographed, awaiting your sign-off.
3 Ready to switch on Jobman push, auto-replies, and failure alerts. Built and waiting.
5 Decisions we need Mostly quick calls. Friday should clear nearly all of them.

How it works

The whole system, on one page

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

Your website inspace.nz, the enquiry form
Google Ads Meta (Facebook and Instagram) Google search results
Your inbox info@inspace.nz, watched every 2 minutes
0800 number Once the telco line is live

The AIOS

Catches every enquiry. Loses none.

Records it the second it arrives Reads emails and separates real enquiries from noise Notes exactly which ad or search brought them Flags repeat enquiries instead of deleting them Replies to the customer and alerts your team Holds the enquiry until Jobman confirms it landed

Runs on Railway, in an account that transfers to Inspace at handover.

Your systems, unchanged

Jobman Your pipeline and the master record. Every enquiry becomes a contact and a lead here.
Your dashboard Enquiries, sources and conversion in one view
Xero Reached through Jobman, as it is today. Later phase, read-only.
Customer records Jobman Unchanged. The AIOS feeds Jobman and never becomes a second CRM.
Enquiries in transit Your Railway database Held only until Jobman confirms receipt, so nothing is lost if a system is briefly down.
Email Microsoft 365 Your existing mailbox. We read info@ and send from it. Nothing is migrated.
Website & domain Cloudflare Already in Inspace's own Cloudflare account.
Money Xero Untouched. The AIOS never creates an invoice.
Ad accounts Google & Meta Set up in Inspace's name from day one. We manage them as an invited partner, so the history and audiences stay yours.

Built and running

Working today

Live

The new website

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.

Live

Website enquiry capture

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.

Live

Email enquiries from info@

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.

Live

Knowing where enquiries come from

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

Ready when you are

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.

Ready

Enquiries flowing into Jobman

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?

Ready

Instant reply to the customer, alert to your team

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.

Ready

Alerts if anything breaks

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

What we need to move

Friday

Google Ads and Meta access

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.

Decision

Which Jobman pipeline for website enquiries?

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.

Decision

Pricing on the website: yes or no?

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.

Input

The numbers you want to see

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.

Content

Proof for the website

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

Can you count your builder work?

The 30% target has no scoreboard yet

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:

6.7% name a builder or construction firm in the job description
4% are actually tagged with Jobman's β€œBuilder” type
86 of 99 clear builder jobs are filed as Residential or Commercial instead

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

The road to go-live

In order, because each step depends on the one before it.

01

Connect Google and Meta

Friday. Wire up tracking so every enquiry can be traced back to what produced it.

02

Switch on Jobman and the automatic replies

Once you have confirmed the pipeline. Enquiries then flow to your team and into Jobman without anyone typing anything.

03

Build your dashboard

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.

04

Point inspace.nz at the new website

The switch itself takes minutes and is reversible. Your email is untouched by this.

05

Hand everything to you

The code, the hosting and the domain all transfer into Inspace's own accounts. You own it outright.

After the foundation

Where this goes next

Phase 2: The engine

Cut the manual work

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

What your customers see

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 BDM role, automated

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

Someone at the wheel

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.