Who already looks like the book.
Written in the company’s voice.
A person keeps the last word.
Invoices
Agents that issue the invoice.
An agent that runs the company's work — the invoice, the account, the email — in place of the team. The apps further down are a separate channel. Early access.
Invoice
The agent issues it.
Account
The agent collects it.
Email
The agent writes it.
Operator
A person keeps the last word.
FanMap
Scout
Join
foodify
Dawn
What an agent is.
An agent is a worker specified for one company. It is not a chat window, and it is not a pile of prompts with a logo in the corner. It takes a job the team already does and runs that job in their place.
The standing jobs are the invoice, the account, and the email. The agent issues the invoice. It collects the account. It writes the email in that company’s voice. If a person at the company would not send the line, the line is not done.
How we do it.
We sit with the people who do the job. If they cannot point at it in their week, we do not draw a system. Then we draw the boundary: what comes in, what the agent is allowed to remember, what it must not claim, which tools it may touch, and who can stop it.
Policy sits on the agent, not in a sidebar someone forgets. Spend, cadence, and silence are rules. The operator keeps the last word. That is the difference between an agent that belongs to a company and a tool that mails as you while you sleep.
How a company is run.
We do not hand over a login and a model. The operation is the drawing plus the person. One company, one set of jobs, one book. The apps — FanMap, Scout, Join, foodify, Dawn — are a separate channel. They are products the house issues. They are not the agent.
Early access is a seat at that table. It is not a case study, and it is not a pricing page.
The floor, and the book.
foodify is the restaurant. The agent is the book. They meet, and they are not the same product.
A table already has a QR. Most of those codes open a picture of a menu. foodify takes the code the guest already scanned and stands up the site that takes the order. The kitchen and the till see the same ticket. If the code cannot take the order, it is still a flyer.
The panel is the memory of service, not a wall of charts. What is on. What is off. What came in. What is still in the pass. A dish dies, a dish comes back, a ticket is late. Those are the gaps the floor can name. A person can stop a dish and correct a ticket when the site and the kitchen disagree.
The invoice is the agent’s job. A line that was never delivered. A tab that was never closed. A sale that sat in the book and nobody wrote down. The agent is specified to issue that invoice and to collect that account. A person reads the line before it goes out. We do not publish a number for how many we have closed. There isn’t one to publish.
Finding who to sell to is Scout, issued apart. The agent does not scrape a category and hope. If it cannot say why a name is on the list, the name is not on the list. The letter has to survive being read aloud by someone who works there.
The last word.
We do not publish clients we do not have. These are the notes an operator keeps. The agent does not get to overrule them.
That line was never delivered. Take it off.
The invoiceThe fish is off. Stop the ticket.
The floorWe do not claim that. Rewrite it.
The letter
Request issue.
Leave an email. We'll write when the first agents go out.
This is early access, not a login and a pricing page. We will write when the first systems go out. You are joining the house — then the apps, as they are specified.