How we show our work

The records every engagement leaves behind

These are the records a Fuchs & Agents engagement leaves behind: an approval log, a stop-and-flag draft, a leak-test report and a before-and-after time log, shown on a fictional business.

We have no client results to publish yet, and we won't invent any. Each example below uses a made-up business so no real customer data appears. To work with the formats yourself, see the demos.

Fictional business throughout: "Sample Landscaping Co." and its owner "Pat Example" do not exist. The rows below show the format of each record. They are not output from a client system and not a measured result.

Fictional business. Demonstration format only: not a client result and not copied from a live system. Rule 1: AI drafts, people decide

Approval log

Every draft has a named approver, and every decision is a row. Nothing goes out without one.

Approval log, Sample Landscaping Co. (fictional), one Friday
Time	Item	Drafted by	Checked by	Approver	Decision
08:02	Quote, back-yard irrigation repair	Drafting agent	Checking agent	Pat Example	Approved with one edit (crew size)
08:05	Payment reminder, invoice 1042	Drafting agent	Checking agent	Pat Example	Approved as drafted
08:06	Payment reminder, invoice 1043	Drafting agent	Checking agent	Pat Example	Blocked: open flag (see below)
08:11	Reply to a customer review	Drafting agent	Checking agent	Pat Example	Sent back: "too formal, shorten"

Fictional business. Demonstration format only: not a client result and not copied from a live system. Rule 2: stop and flag

A draft that refused to guess

The job notes for invoice 1043 have no total. Instead of estimating one, the draft marks the gap, and the open flag blocks approval until a person fills it in.

Draft payment reminder (fictional)

Hi Jordan, a friendly reminder that invoice 1043 for the hedge trimming on the 14th is now due. The amount is AMOUNT UNKNOWN. You can pay by the usual method. Thanks, Pat

OPEN FLAG Invoice total missing from the job notes. Approval blocked until a person enters it.

Fictional business. Demonstration format only: not a client result and not copied from a live system. Rule 3: isolation in code

Leak-test report format

Before a release, a unique marker is planted in one client's workspace and searched for from every other workspace. The release ships only when every planted marker is caught. This is what each row of the report records.

Leak-test report columns, with one fictional row
Release	Planted in	Searched from	Marker	Expected	Result
Release tag	Workspace A	Workspace B	a unique string	Not found from B	Recorded by the run, pass or fail

Rule 5: measured, not asserted

The before-and-after time log

Small-business clients keep a simple log: the task, the minutes it took before, the minutes it takes now with an agent's draft and their approval. With written permission, those logs are the only numbers we'll ever quote, and we'll report the median, not the best case.

Get the blank log

[PLACEHOLDER: two-minute walkthrough video on this fictional business, recorded on Joe's own stack, self-hosted with captions and a transcript. Not recorded yet.]