Ten months into Project Zero: building an estate that runs itself

Updated July 2026 — about ten months into a deliberate build: quieter technology, clearer guest stays, and fewer fires for the team to put out by hand.

At The Countrylife we host people under canvas and in the hall for weekends that should feel simple. Behind that simplicity sits a long project we call Project Zero: automate every routine task we can, keep humans for welcome and judgement, and stop the estate running on endless group-chat archaeology.

We are roughly ten months in. This is an honest progress note — not a finished product brochure.

What we set out to do

Project Zero is not “replace people with robots for the sake of it.” It is:

• Automate the water cycle — fill, heat, sense, and eventually empty hot tubs without a hose rota.
• Prove readiness with evidence — photos and sensors, scored fairly, not “someone said it was fine.”
• Answer guests in seconds — maps, codes, hot tubs, projectors — without waiting for a callback on every FAQ.
• Route exceptions to the right lane — maintenance, remote ops, or owner only when money or brand truly needs them.
• Shrink the residual — aim for a tiny set of tasks that stay human on purpose.

The north star is simple to say and hard to finish: machines and AI own the path; people own care and capital.

The scoreboard (tasks, not “busyness”)

We track work in tasks — distinct jobs the system can do — not how many times someone taps a phone.

That distinction matters. A cleaner still makes beds; the Hub already scores the photos. Both can be true.

What is already automated (the interesting middle)

Guests feel the quiet bits. The team feels the noise that disappeared.

Guest experience

• Oracle — instant answers for hot tub, Wi‑Fi, directions, fire packs.
• Arrival journey (VGEM / Gemma) — timed messages, map links, fewer “which entrance?” threads.
• Faster OTA replies — AI-assisted drafts on Airbnb and Booking.com; humans still own the edge cases.
• Hot tub sensing and robotic fill — less hose theatre, more “it was ready when we arrived.”

Turnover and quality

• Guest Ready upload — phone photos after each clean.
• LunAI vision — consistent scoring so “fine” is not a vibe.
• Ready rules — temperature and level gates that stop false “guest ready.”
• Score-floor alerts — the team hears about weak units before the review does.

Rota and day ops

• Day board from live bookings — who arrives, who leaves, what must be cleaned.
• Start-of-shift cards — order of work without a morning WhatsApp novel.
• Hours capture — the old “hours theatre” path is retired.

Troubleshooting and estate hardware

• Home Assistant reliability board — sensors that matter, not a wall of red.
• Remote trust — occupancy and energy signals when we are not on site.
• Mower and vacuum paths — robots on schedules; humans for stuck recoveries.
• Public maintenance board — jobs with a link, not a buried list.

Money, supply, and admin

• Stripe extras — fire packs and late checkout as payment links, not cash-in-hand chaos.
• Amazon reorder queue — stock shortfalls become a buy list, not a scavenger hunt.
• Team invoice upload — phone link, name + photo, pay windows Tue/Sat; owner approves when banking is wired (step 1 of 2 toward hands-off payouts).
• Site issues board — growth and ops blockers logged and sorted, not lost in chat.
• Dispatch queue — Hub routes research and ops work instead of copy-paste between tools.

What still needs people (and why that is fine)

Twenty-seven core functions still need a human. That is not failure — it is honesty. Examples:

• Physical turnover cleans and linen edges until robots and cameras fully cover the loop.
• Complex platform disputes and refunds above a money band.
• Break/fix repairs, plant faults, outdoor hazards.
• Calendar judgement (what to sell, when to cut inventory).
• Owner capital decisions — robots, sensors, how far to push automation.

Greeting and wayfinding are on a deliberate path toward a robot dog + lights + arrival messages stack — so welcome stays warm without a permanent “greet roster” as the only design.

One physical job remains a true product gap worldwide for estates like ours: putting a fitted sheet on a bed to guest-ready standard. Coverless duvets already simplify remakes; the fitted sheet is the stubborn corner.

What ten months taught us

1. Evidence beats status updates. Photos and sensors beat “I think the tub was on.”
2. Chat is a terrible operating system. Group chats are for exceptions, not the default file store.
3. Partial automation is still real progress. LunAI does not make the bed; it stops false ready from becoming a bad review.
4. False alarms burn owners. High-precision digests only — noise creates heroics and then burnout.
5. Growth and survival are different modes. Calendar throttles (like Sunday closed-on-arrival) protect yield; bulk-closing Mondays by mistake costs revenue.
6. Measure tasks, not thrash. Seventy-seven live capabilities and twenty-seven residual human functions tell a clearer story than “we’re busy.”

What the next stretch looks like

• Independent Guest Ready evidence (cameras / dog path) so staff phone photos are not the only truth.
• Arrival lighting and wayfinding wired to ETA — fewer dark-path phone calls.
• Banking approval (Wise) so invoice upload is the human step and payout approval is the owner step.
• More closed loops: sensors that self-heal or open a maintenance job without an owner WhatsApp.
• Keep the residual list honest — shrink 27 toward 2, without pretending the sheet problem is solved.

For guests

You should notice less friction, not more tech theatre: clearer arrivals, hotter tubs that were filled on purpose, faster answers, and a site that feels looked after even when the team is deep in a Saturday changeover.

If something still needs a human, you will get one. Project Zero is about where that human spends their attention — on you, not on re-typing the same stock list into another chat.

Project Zero — automate the path · keep the welcome · measure the residual.
— Hub · The Countrylife · July 2026

Internal scoreboard for this post: projectzero_task_scoreboard.json (automated · residual · target).