Your inbox already knows how you run the business.

We turn your customer emails, calls and your own explanations into a private knowledge wiki. Your Claude reads it before it drafts a reply, so the answer sounds like you and states your real policies.

Every rule you've ever explained, written down once.

Each card is one thing your business does, with the emails it came from. Your Claude follows the links between cards, so a question about one job surfaces the step it depends on.

Restriction3 sourcesVerified by owner

Bleed the brakes before any race-prep tune-up

Book the bleed with the tune-up, not after it. Allow one extra hour. If the pads are glazed, quote new pads in the same visit.

Related: glazed pads change the job · Saturdays are for small jobs only

How it works


Step 1

We read what you've already written

Emails, call transcripts, an interview with you, your videos. Every rule, time estimate and "we don't do that" becomes a card with its sources.

Step 2

You review it

Correct a card, and answer the questions we couldn't settle, like two emails that disagree about your hours. Your answer outranks every email.

Step 3

Your Claude connects

One connector in your Claude account. Before it drafts a customer reply, it looks up the cards that apply and writes in your terms.

When it isn't settled


When your own emails disagree, the card is marked unsettled and the question comes to you. Until you answer, your Claude tells the customer you'll confirm. It never picks one of two policies.

Answer once, and every future reply uses it.

Draft reply · for your review

Hi Jordan, a race-prep tune-up includes a brake bleed, so plan on the bike being with us for the day. We'd book it for a weekday, since Saturdays are for small jobs.

On the tubeless conversion, we'll confirm whether rim tape is included once we see the wheels.

Unsettled: two past emails disagree about rim tape. Question sent to the owner.

Privacy


Scrubbed before anything is read

Names, emails, phone numbers and addresses are removed before any AI model sees the text.

No training on your data

We use Anthropic's commercial API, which does not train on your inputs or outputs.

Raw files are deleted

Once your wiki is built and reviewed, the original exports are removed. The cards and their history stay yours.

No prices unless you want them

By default the wiki keeps time and scope, never money, so a reply can't quote last year's rate.

Already set up?

Log in to your workspace