Works with Google Workspace · Set up in about twenty minutes
JJane

Copy her in.
She takes it from there.

Jane is an assistant that lives in your inbox. Put her address in Cc and she books the meeting, remembers the document, chases the reply that never came, and writes the first draft of the proposal when you ask for one.

Follow-ups

Nothing you are owed falls through.

The moment you copy her on a customer thread she starts watching who owes whom a reply. Every weekday morning, one short list — and replying to the person is what clears the item. There is nothing to tick off and nothing to maintain.

Jane <jane@yourcompany.com>Follow-ups: 2 waiting on you, 1 gone quiet

Waiting on a reply from you:

1.Ron Levi <ron@acme.com>“Artemis pricing” — asked you something 2 business days ago
2.Kim Alvarez <kim@northwind.test>“Rollout plan” — wrote 1 business day ago, no reply yet

No answer from them:

3.Dana Cole <dana@caspers.test>“Site survey” — you wrote 6 business days ago and have heard nothing back
Reply “done 2” or “snooze 1 until Monday”. “mute 3” drops a thread for good.

Counted in business days

Mail arriving on Friday afternoon comes due on Monday afternoon, not Saturday. A reminder you cannot act on teaches you to ignore the ones you can.

“Thanks, will revert” is a real reply

It restarts the clock without moving the ball back to you. A tracker that gets this wrong spends its life nagging about the word “thanks”.

The knowledge base

Everything the company knows, in one place that answers back.

Forward her a deck, a datasheet, a price list or a signed scope and she reads it — including the pages that are pictures rather than text. Then ask her about it in plain words, months later.

You → JaneWhat is the inspection time per vehicle?

Under twelve seconds for a full drive-through scan, including the undercarriage.

From “UVeye capability overview.pdf”, page 4 — read from the page image, so worth checking the figure before you quote it.

The answer names its source

Every claim points at the document it came from, so you can check rather than trust. Where a figure was read off a picture rather than a text layer, she says so — a misread number quoted to a customer is the one way this does damage.

PDFSlidesScansSpreadsheetsCall notes

She says “I don’t know”

When nothing on file answers the question, that is the answer — with what she looked at. A confident paragraph assembled from nothing is worse than a blank.

Slides and scans are read, not skipped

A deck where every number is inside a picture is read page by page and explained in context, rather than indexed as a list of headings that answers nothing.

Filing is deliberate

What you send to her joins the company base. What she merely sees on a thread is judged: a product deck is shared, a customer’s priced proposal is not.

It notices its own gaps

Every few days she tells you what keeps being asked and never answered — usually one forwarded document away from being fixed.

Proposals

A first draft, laid out like the last one that was agreed.

Ask for a proposal and she reads your whole relationship with that prospect — this thread, your earlier threads with them, the notes from your calls, and your own template — then sends you a PDF.

You → JaneJane, build a proposal for BG Trucking

Draft proposal for BG Trucking — 2 pages, attached.

Where the figures came from
$17,500 per month — from your message on 14 Aug at 09:12
Twelve lanes, three depots — from “BG Trucking <> call notes”, 12 Aug
800 inspections a month — from Kim’s message on 11 Aug

Left blank, because nobody has said
Installation cost · Contract term · Start date

Reply with the missing pieces and she rebuilds it. “Send it without the draft marking” gives you a clean copy.

Every number is traced

Each figure is matched against the exact text it came from. One that cannot be traced is named above the draft rather than left quietly inside it.

A price your customer said is not a price you agreed

Numbers a prospect put in an email are refused as the origin of a term. Only what your side stated can set one.

Gaps stay visibly blank

What nobody has stated is marked to be confirmed, in its own colour, rather than filled in with a plausible figure that reads as agreed.

She learns which ones won

Tell her a proposal closed and she takes its shape — section order, how the pricing table was laid out — for the next one. Never its prices, and never the customer it was for.

Meetings and calls

Booked from the thread it was discussed on.

“Jane, set up 30 minutes with Ron on Thursday afternoon.”

She reads the thread for who and when, checks the calendar, and sends the invitation with a video link. If the time is ambiguous or it is not obvious who Ron is, she asks you rather than guessing — and a guess is the only thing here that could reach a customer.

If you use Granola, the notes from your calls become part of the knowledge base too: she can answer from what was said, and remind you of what you agreed to do.

Jane → youBooked: Ron Levi, Thursday 2:00pm

Thursday 4 Sep, 2:00–2:30pm ET. Invitation sent to Ron with a Meet link.

From your calls: you said you would send the revised lane pricing before this one.

What she will not do

The limits are the point.

This is what makes her safe to put on a live customer thread, so it is worth reading as closely as everything above.

She does not write to your customers

Answers, drafts and reminders come back to you and nobody else. The only thing that ever reaches another person is a calendar invitation you asked for.

She does not answer mail you did not address to her

Copy her on a note to a customer and she watches the thread. She will remind you about it and will not reply to it, however much it reads like a question.

She does not invent a number

Every figure in a document is matched against the text it came from, and one that cannot be traced is named above the draft.

Colleagues do not see each other’s customers

You share a knowledge base of company documents. Your correspondence, your reminders and your accounts’ files stay yours.

Getting set up

Five steps, and three of them are ours.

About twenty minutes in total, most of it waiting for a mailbox to be created.

  1. You

    Tell us about your company

    Your name, your timezone, and who should be able to give her instructions.

  2. Us

    We set her up

    Your workspace, your own separate database, and the link that connects her.

  3. You

    Create her mailbox and approve access

    Add a user in your Google Workspace and approve the permissions once. Scoped to that one mailbox, revocable by you at any time.

  4. Us

    We connect and check

    We confirm she can read her mail and see the calendar, and tell you she is ready.

  5. You

    Copy her on something

    Send her a document and ask a question about it. If she answers, you are live.

Everything you will be asked for

Your data

She sees the mail you copy her on. Nothing else.

Jane gets her own mailbox in your Google Workspace, and the permission you grant is scoped to that one account — not your inbox, not your drive, not anything else. You can revoke it from your own Google settings at any time, without asking us.

Where several colleagues use her, each gets their own reminders and their own customers. What is shared is the company’s knowledge base: the decks, datasheets and templates somebody deliberately filed.

Each customer’s data lives in its own separate database schema, and nothing Jane holds is used to train a model.

FAQ

Questions, answered.

Do I have to change how I work?

No. You keep using email exactly as you do now and put her address in Cc when you want her to see something.

What if she gets something wrong?

Everything she produces comes to you first, so a mistake costs you a moment rather than reaching a customer. The one exception is a calendar invitation, which only goes out when you have asked for one.

How much of our history does she read for a proposal?

The thread you asked on, your earlier threads with that same prospect, the notes from your calls with them, and the documents you have filed. Not a colleague’s separate dealings with the same company — those are theirs.

Can we use our own mailbox, or do you provide one?

Either. We recommend your own: your correspondence then stays inside your own Workspace and we hold nothing but a token for that single mailbox. The setup guide explains what hosting it with us would change.

Does she work with Outlook?

Not yet — she needs a Google Workspace or Gmail mailbox today. Say so on the form and we will tell you where it stands.

Try her on one thread.

Tell us about your company and we will set her up. Nothing here commits you to anything, and nothing connects until you approve it.

Get started