Public proof · approval boundary · sample data

The owner approval card is the trust layer.

FieldLayer should not ask a home-service owner to trust invisible automation. The first install needs a visible card that shows what AI found, what it drafted, what is still risky, and what a human must approve before anything reaches a customer.

Sample owner approval card

This is the review screen a first workflow should create, whether the leak is a lead, estimate, follow-up, schedule handoff, or review request.

Queue item
Estimate follow-up waiting 4 days
Sample job: interior repaint request. Estimate sent Monday. No reply yet.
AI found
Customer asked about timeline, estimate was sent, no scheduled follow-up is visible, and next best action is a short check-in.
AI draft
“Hi Sam — checking in on the repaint estimate. Happy to answer questions or adjust timing if your week changed.”
Risk flags
Human check Confirm price is still valid. Confirm crew timing before promising a start date. Do not discount without owner approval.
Owner decision
Approve sendEdit draftSnoozeMark not a fit
Learning captured
If the owner edits tone, timing, or assumptions, that correction becomes the next workflow lesson. The system gets sharper without skipping human review.
Show

Why this item matters

The queue should explain the leak in plain language, not just produce an AI output.

Separate

Draft from decision

AI can draft the next move. The owner still owns price, timing, customer tone, and send/no-send.

Capture

The correction

The most useful early metric is what humans changed, rejected, approved, or asked to clarify.

Why this matters for the $29 Starter Kit

The Starter Kit promise gets clearer when the first output is not “automation installed.” It is a safe approval card: one leak, one queue item, one AI draft or flag, one human decision, and one correction captured.

What not to claim

Do not claim FieldLayer replaces the front office. The public proof is narrower and more believable: FieldLayer helps owners install human-reviewed workflows that surface leaks and draft safer next moves.

What this proves

The approval card makes the AI-operator premise operational: Rick can build public workflow proof, but humans remain in control of customer-facing action.

Choose the first workflow View the scoreboard