HouseholdPilot takes private household operations end to end for busy households and family offices: every request, renewal, delivery, and document is captured, classified, and screened by deterministic validation and privacy gates before a named principal approves anything. An item missing its owner or due date can never be approved — the validation gate blocks by name — and a Sensitive item (Payment, Credential, or Medical) can never be approved in this flow — the privacy gate blocks by name and hard-routes it to the principal. Nothing books, pays, or messages without explicit human approval.
$1,500 fixed HouseholdPilot Pilot — one household workspace taken end to end for you: household intake, classification, validation and privacy gates, approval queue, runbook dispatch, and audit trail, live in about 10 business days. You approve every item from your phone; nothing dispatches without your explicit human approval.
Billing is not connected on this page yet — the next step after the demo is a pilot request, and we confirm scope and price before any charge. Price above is an untested hypothesis, not proven demand. Billing not connected.
1. Household intakeA household request, renewal, delivery, or document is captured (mock intake in this demo; your household inbox/form at pilot).
2. ClassificationEach item is classified Maintenance / Delivery / Document / Renewal / Needs decision with confidence (mock classifier in this demo).
3. Validation & privacy gatesTitle, category, household owner, and due date are checked; Sensitive (Payment / Credential / Medical) items are screened. Incomplete or sensitive items are blocked by name.
4. Human approvalA named household principal reviews the evidence and approves. Nothing books, pays, or messages without explicit human approval.
5. Runbook dispatchOnly an approved item dispatches (mock dispatch in this demo) with a RUN-MOCK id, joining the runbook outbox and audit trail.
Live demo — take one household workspace end to end
SAMPLE DATA The households, members, vendors, and dispatches below are sample data, honestly labelled, so you can see the whole journey end to end. Intake here is a mock intake adapter, classification is a mock classifier adapter, and dispatch is a mock dispatch adapter — no real booking, payment, or message happens, and no data leaves this page.
Runbook outbox & dispatches SAMPLE
Dispatched runbook items (RUN-MOCK ids) appear here — for this tenant only.
Gate rules
Required fields (title, category, household owner, due date) must be present, no Sensitive flag (Payment, Credential, Medical) may be approved in this flow, and the same item can never appear twice in one workspace. Incomplete, sensitive, or duplicate items are blocked by name — the failing rule is stated, never worked around. A named principal approves every dispatch; the audit trail shows who approved what, and when.
Audit trail
HouseholdPilot ready. Every intake, classification, block, approval, and dispatch is logged here — for this tenant only.
Support & legal
Support: pilot households get email support and a shared issue log; gate rules and privacy handling are reviewed with you weekly during the pilot. HouseholdPilot prepares household operations for human approval — it does not book vendors, move money, give medical, legal, or financial advice, or replace the principal's judgment; a named approver remains responsible for every dispatch, and sensitive items are hard-routed to the principal for handling outside this flow. This demo stores data only in your browser; pilot deployments add real accounts, encrypted credentials, server-side tenant separation, and buyer inbox/calendar access under your credentials before any real item is handled. Sample data is fictional. Billing is not connected.
Next step: run the demo, then request a pilot via the contact step on this page — we confirm scope, household, and price before any charge.