A label can put nine hundred messages in one place. It cannot tell you what is inside them, and it cannot tell you which job they belong to. Dray reads the pile, files every message, invoice and photo against the thing it is actually about, and keeps that record as it happens.
Before any of the filing matters, Dray clears years of noise out of the way. It does two things, not one: it clears what is already there, and it writes the rule into Gmail so the same senders never pile up again. Across every account you own, in the same conversation.
The rule lives in Gmail, not in Dray. It keeps working whether or not you ever open this again.
Grouped by sender across every account at once, not one inbox at a time. Usually four or five names account for most of it.
Archive, label or bin everything matching a query. Dray shows you what it would touch and changes nothing until you say yes.
Dray writes the rule into Gmail itself. It runs on Google's side for every future message, with Dray closed and nothing of ours awake.
fig. 01 · nothing bulk happens without being shown to you first
Every business has one: the label with hundreds of near-identical messages in it. Applications to a job post. Brokers asking for access. Payment receipts. Delivery notifications. A rule got them into one place, and then everything stopped, because the only part worth having is inside the body where no filter, search or label can reach it.
Ask Dray for the table and you get the table. Who, from where, when, how much. It reads the pile on demand and gives you rows.
This is the part you can try in the first five minutes, on mail you already have.
fig. 02 · a real label from a real mailbox. 943 messages, one sender, one subject line.
Nobody fills in a blank “list your projects” box accurately. So Dray does not ask. It reads the addresses that keep recurring in your own subject lines, proposes them in your own words, and you say which are real.
Then every message gets a Dray/ label in your own Gmail. Not in a silo of ours. If you cancel tomorrow, the filing is still there.
Real tool calls, in the order Claude makes them.
fig. 03 · file_messages, unedited output shape
A message Dray cannot confidently place is left exactly where it is and reported to you. That is the whole design. An unfiled message costs you a glance at a queue. A change order filed against the wrong property costs you the belief that any of it means anything.
Two jobs that look equally likely is a coin flip, and a coin flip fails the same test as a blank. The one number we hold ourselves to is how often a filing gets corrected.
Tell Dray where something belongs and it moves it, takes the old label off, and learns from it. The rest of that conversation files itself, and the people on it start counting as evidence for that job.
Someone who appears on every job proves nothing. Someone who only ever writes about one proves a lot. Dray weighs them that way, which is why your foreman does not drag half your mail onto whichever job he is busiest on.
A tidy inbox is worth something the day you do it and nothing three months later. The dossier goes the other way. Every month it holds more of what actually happened, and it pays out on three completely different clocks.
A dispute, an insurance claim, a lien. Ask for the full record of a job and you get every message in order, who was on it, and every attachment listed with a pointer straight back to it. The alternative is billing hours to rebuild it out of a search box.
job_dossier · detail: full
Dray reads the figure off a quote or an invoice when you ask, and keeps it against the job with a pointer to the message it came from. At tax time the ledger is a list, not an archaeology project.
job_ledger · quotes · invoices · payments · change orders
A question with an answer, instead of twenty minutes of scrolling. The dossier is assembled as the job happens, so the answer is already there before you think to ask for it.
job_dossier · across every account at once
The quote is a PDF. The takeoff is a spreadsheet. The change order is a photo of a page. Dray opens the file and answers from it, and when you ask it to, puts the figure in the job’s ledger with a pointer back to the message it came from.
The document itself is never copied. It stays in Gmail and is fetched at the moment you ask. A scan with no text layer says so plainly instead of guessing.
Invoices, quotes, contracts, permits. The text layer is extracted and read, so “what does this one total” is answered from the file.
Rent rolls, takeoffs, ledgers. Shared-string tables resolved, so the rows come back as rows rather than as indices.
Agreements and letters, with their paragraph structure intact rather than flattened into one line.
Receipts, site photos, pictures of paperwork. Handed to Claude as an image it can actually look at.
fig. 04 · across every inbox at once, so “find the August invoice” does not need you to remember which company it came to.
Dray reads your sent mail and measures how you actually write: how you open and close, how long your replies run against what they answer, the phrases that keep coming back. Separately for clients, for trades, for family. Nothing to set up and no sliders, because people describe their own writing badly.
Plenty of tools imitate a writing style. The useful part is that this one is answering from a thread it has already filed, about a job it already knows the history of.
Hi Sam, Thanks so much for your patience on this! I'm happy to confirm that Thursday works perfectly on our end. Would it be at all possible to move things to 4pm? I hope this works for you! Looking forward to it! Best, Alvaro
Hey Sam, Thursday works. Can we push it to 4? I'll have the revised numbers with me by then. Does that still leave you enough time before the board pack closes? - Alvaro
fig. 05 · same request, three relationships
Add Dray as a custom connector in Claude. No install, no daemon, no config file. Same on desktop, mobile and web.
Google's own screen, in your own browser. Finishing it connects your first inbox. Add the rest whenever you like and they act as one.
Dray reads your mail and proposes them, in your own words, out of your own subject lines. Confirm the real ones and it files the backlog behind them.
Drafting and sending are different tools, and only one of them sends. It needs you to ask, in that conversation, for that draft. Bulk changes show you what they would touch before touching it. Mail goes to Trash, never deleted, and Dray does not ask Google for the permission that would let it.
Dray keeps what it worked out, not what you wrote: which job a message belongs to, the figures you asked it to put in a ledger, and how you write. Message bodies, subject lines and attachment files are never written down. The filing itself is a Gmail label, so it belongs to you.
Google tokens are encrypted before they are stored, every change is in an audit log only you can read, and deleting your account is a button that revokes our access with Google and then erases the rest.
During the beta, Google shows an “unverified app” warning when you connect. That warning is real and we will not pretend otherwise. Verification for Gmail access takes months and an independent security assessment, and we are in the middle of it. To continue, click Advanced, then Go to Dray. If that bothers you, wait for us to finish. That is a completely reasonable thing to do.
Dray’s use of information received from Google APIs adheres to the Google API Services User Data Policy, including the Limited Use requirements.
Everything for 14 days, with no card. Not a limited tier: the whole product, every inbox, every job, the lot. There is no free plan afterwards, because a product you use every day should be worth paying for and we would rather say so.
Priced against an afternoon of an office admin, not against a productivity app. If Dray saves you one dispute you would otherwise have rebuilt by hand, it has paid for a year.
fig. 06 · 25 founding seats, because the point of a founding cohort is a small group who shape the product rather than the largest number we can sign. The price is held for life.