Blue Grouse project book

Curated Home Cleaning

A project-book reflection of the Curated Home shared lane — designed to preserve progress, decisions, system direction, and next steps without exposing unrelated private/admin continuity.

Shared collaboration on the surface, durable continuity underneath.

What this project is becoming

Premium, high-trust residential cleaning with systems

Curated Home is being shaped as a premium, high-touch residential cleaning business for central Vancouver Island, with a strong emphasis on reliability, no-ambiguity service standards, senior-safe support options, preference memory, and repeatable service quality.

  • Central Vancouver Island geography already scoped
  • Customer-facing site scaffold exists
  • Pricing and ops pages exist
  • Shared collaboration lane and reflection model exist

Why this reflection matters

Shared project clarity without continuity bleed

This page is meant to help Marcus, Tammy, and Sasha stay aligned on Curated Home progress while preserving the separation between this business lane and unrelated private/admin or autonomy-development continuity.

  • ops.bluegrouse.ai remains the internal authoritative dashboard
  • This page is the project-scoped reflection surface
  • It should derive from canonical Curated Home records, not ad hoc chat memory

Current focus

Where the work really is

Service architecture and offer clarity

Turn the market framing into concrete service tiers, checklist boundaries, and a no-ambiguity premium offer that can be priced and explained clearly.

Client onboarding and preference capture

Design the premium intake and home-preference capture flow so the business can deliver high-touch, property-specific service rather than generic cleaning.

Operational systems and app direction

Translate the Gemini app ideas into practical development lanes and a build order that supports lead capture, client records, cleaner instructions, workflow status, and later billing/retention.

Shared collaboration lane discipline

Keep Curated Home collaboration, Telegram workflow, and reflection-page content scoped to the business so the project lane stays useful and does not absorb unrelated private continuity.

Three app development lanes

How the software should be divided

Lane 1

Client experience lane

  • premium onboarding form / home curation intake
  • lead capture and conversion path
  • client portal / booking and add-ons later
  • proof-of-clean delivery and polished follow-up
  • preference memory, scent choices, pet notes, special requests

Lane 2

Cleaner operations lane

  • cleaner authentication / scannable code support
  • property-specific instructions and zone checklists
  • arrival / completion logging
  • photo verification and issue reporting
  • route density and zone-day logic for island geography

Lane 3

Business system lane

  • lead capture database and follow-up pipeline
  • client contact database tied to onboarding and jobs
  • house cleaning status / job-state tracking
  • eventual billing, subscription, and retention systems
  • client preference, household note, and important-date memory

Still to be decided

Operating choices that need a real answer

  • Email integration: what inbox/tool should own lead intake, confirmations, and follow-up?
  • Calendaring model: what calendar system should own schedule truth and team availability?
  • Lead capture mechanism: what is the first practical intake route — site form, app intake, phone-assisted workflow, or all three in sequence?
  • Client database model: what is the first canonical record for a household/client and where does it live?
  • MVP boundary: brochure + intake first, or booking/ops workflow immediately?

Gemini-derived business systems direction

What needs to integrate cleanly

  • premium onboarding form tied to service preferences
  • photo verification / proof-of-clean logic
  • route optimization and zone-day scheduling
  • staff-side property briefs and live instructions
  • future AI concierge / smart client communication

Business systems roadmap

The core systems Curated Home needs

1. Client lead capture

Create a polished mechanism for capturing new prospects from the website and future shared workflows, with immediate routing into follow-up rather than inbox drift.

2. Client contact database

Store household records, contact details, property facts, service cadence, preferences, pets, off-limits zones, and relationship notes in one canonical system that hooks directly into capture.

3. House cleaning status tracking

Track the state of active jobs and recurring service from lead → quote → onboarding → scheduled → cleaned → followed up, with room for property-specific cleaner instructions and proof-of-clean later.

4. Billing and retention

Eventually support invoicing, recurring billing, package/subscription logic, retention tracking, and simple visibility into who is recurring, who is drifting, and who needs follow-up.

5. Household memory and relationship detail

Preserve high-touch details like scent preferences, pets, access notes, sensitive surfaces, family/household preferences, and important dates so the service feels genuinely curated rather than generic.

What has already been built

  • project brief derived from the Gemini handoff
  • customer-facing site scaffold for curatedhomecleaning.ca
  • separate pricing page and internal ops page
  • shared Curated Home lane decisions and Telegram operating rules
  • this reflection page as a derived project-scoped surface

Boundaries

This page should continue to reflect Curated Home strategy, tasks, systems direction, and milestones — not Marcus’s broader private continuity, unrelated admin work, or autonomy/operator development unless directly relevant to Curated Home delivery.