A colleague for the part of the job that doesn't sleep.
Doe reads your book, forms a view, takes the obvious moves, and brings the calls that matter to you. It owns the rest, in your voice, while you sleep.
Morning, Michael.
Three things from your book this weekend.
- Etsy filed a money transmitter license in TX. IMM outreach to their VP Treasury drafted and in your inbox.
- Vinted and Farfetch both posted Head of Payments roles. That's a cohort, not two one-offs. Queued one draft covering both.
- Fourteen other accounts crossed threshold. Drafts ready. I held sending on three that felt borderline.
Nothing urgent. Ping me if Rakuten should jump priority this week.
/ Doe
You've built a modern GTM stack. It still needs a teammate.
Research runs. Enrichment is clean. Your reps know what to do with a good signal. What your stack can't do is think about the account between the calls, decide what matters enough to act on, and handle the work while nobody's watching. That is colleague work, not tool work. And right now it is capped at the hours your team can give.
What teams feel once Doe is on the stack
Continuous
instead of scheduled
Always on. Reads, reasons, writes the moment a signal lands.
Public web
instead of a source list
Filings, earnings transcripts, press, careers, product changelogs, App Store updates, patents, regulatory registries, and whatever else the account opens up.
Whole book
instead of named accounts
Top 100, full TAL, and the merchants you have not started tracking yet. Same loop.
Minutes
instead of mornings
A 10-K drops at 4pm. Doe has a draft in the queue by 4:05. Not 8am tomorrow.
What your Doe does, every day, per rep.
Doe is not a tab your AEs open. It sits on the team, carries its own book, and does the work below. Some of it on its own. Some of it with a check-in.
Pre-call brief
Ninety seconds before a merchant call
Doe has read every thread, note, and call with this merchant. Tells you what changed, what probably matters on the call, and three questions worth opening with.
Before the Lufthansa call: BNPL rollout status across the four airlines, Klarna integration progress, open Issuing expansion thread, one specific question on Q4 auth rate.
Post-call close-out
The moment the call ends
Doe listens in, decides what came out of it, files the obvious stuff on its own, drafts the follow-up in your voice, and flags the one thing it was unsure about.
Merchant said "send over the Capital eligibility framework." Draft sent, opportunity stage bumped, CFO meeting held on your calendar for Thursday.
Ask your book
Any time, in plain English
The teammate with read access to your whole stack and the patience to answer the questions your team usually drops. Twenty seconds, full drill-down.
"Which of my merchants grew European volume above fifteen percent last year and are not yet on local acquiring?" Answered in twenty seconds, with drill-down per account.
Cross-sell signal, mid-deal
As a deal is progressing
Doe spots the attach timing before your AE does. Names the play, names who to bring into the room, drafts the intro.
Marketplace close in progress. Signal from their careers page: a new Head of Seller Finance started this month. Capital attach drafted, staged in Salesforce as a linked opportunity.
Friday book review
End of week, on schedule
What moved, what stalled, and the one account Doe thinks needs attention next week that nobody asked about.
Three stale opportunities flagged with suggested nudges. Two renewal windows opening. One competitive signal on a top-ten account.
Expansion attack path
For any named account, on demand
Name an account. Doe hands back the ranked cross-sell order across the Adyen menu, its reasoning, and the buyer for each step.
Etsy: IMM first (already a launch customer), then Capital against the seller flow, then Personalize against the core checkout. Each step with a named buyer.
Tuned to the pillars that carried your Investor Day.
Share of wallet was the headline. These are the plays that earn it. Each fires on a public signal, aimed at the right buyer, on the schedule you set.
New Treasury, FP&A, or Head of Payments hire
LinkedIn position changes, company careers page diffs
Money transmitter license filed in a new state
FinCEN MSB registry, state regulator databases
Earnings mention of banking fragmentation or payout costs
10-K, 10-Q, earnings transcripts
Adyen for Platforms
Lightspeed, Mindbody, and FreshaNew seller or marketplace tier in the product
product page diffs, press releases
Embedded finance or seller ops hire posted
LinkedIn, careers page
Seller payout language in public roadmap
company docs, changelog pages
Unified Commerce
Starbucks EU, Puma APAC, and SimonsNet new store count or format announced
investor decks, store locator scrapes
Tap to Pay on iPhone added
App Store changelogs, press
Head of Retail Tech or Store Experience posted
LinkedIn, careers page
Issuing, Capital, Personalize, and Agentic Commerce score on the same run. You decide which fire during setup.
Work no team could do by hand.
The point isn't saving an hour. It's running motions your team would never staff, at a speed and scope a human book can't cover.
Cross-account pattern detection
Three merchants in your book hiring Heads of Payments in the same month is a cohort play, not three one-offs. Doe reads every account, correlates across them, and surfaces the pattern with a shared narrative. Reading one account at a time never finds this.
Auto-discovery of net new accounts
New Series C announcements, money transmitter filings, marketplace launches, payments-leadership hires at companies you do not yet track. Doe adds the qualifying ones to your TAL with pre-scored reason codes. Your pipeline grows without someone on your team building a list.
Always-on account health
For every live merchant, Doe watches layoffs, executive departures, credit events, partner changes, competitor wins, and customer complaints. Distress surfaces in hours. Your CSM team stops learning about risk at the renewal conversation.
Four loops that move the PnL, not only the pipeline.
Prospecting is the easy win. The bigger numbers sit inside the book you already have.
Continuous wallet-share audit
Every live merchant in your book, scored against the full Adyen menu on a continuous loop. Not when someone runs the query. All the time. The moment a gap opens (a new store format, a new treasury hire, a new marketplace tier), the attach play is drafted and the opportunity is staged in Salesforce. Same thing for your full customer base, not only the top hundred.
Your Q3 2025 Platforms pillar grew 50% YoY. Wallet share inside the book is where that comes from.
Churn watch across every account
Not the top 100. All of them. Doe watches LinkedIn for competitive leadership changes, SEC filings for RFP language, earnings for cost-optimization framing, your recorded calls for competitor mentions. Distress signals surface weeks before a renewal conversation turns defensive. Your CSMs walk into the room knowing what is at risk, not finding out.
Competitive response in minutes
Stripe announces a feature at 11am. By 11:15, Doe has cross-referenced your TAL against accounts in active Stripe replacement, built tailored counter-briefs per account, and routed them to the AEs on the deals. Your AEs arrive in a competitor's news cycle with the angle already drafted.
AI-surfaced signals across a million opportunities lifted win rates up to 35%.
Full QBR decks, not briefs
The morning of a quarterly review, Doe generates the full deck. Merchant-specific volume and mix charts from Salesforce, benchmark comparisons to their peer set, ranked expansion opportunities across the Adyen menu, competitive exposure, three questions that open the room. Formatted in your brand, ready to present.
ServiceNow cut pre-meeting prep by 95% across 29,000 sellers using this exact pattern.
Writes into the stack you already run
Also writes into Salesloft and Aircall. Routes into whatever messaging tool your team lives in.
The questions that always come up first.
Clay is good at what it does. Doe covers that same surface (browser-grade web scraping, structured extraction, CRM writeback) plus the layer above: deciding which account to work, which play fires, what to draft, and what happens in Salesforce after. If your Clay workflows are dialed in, keep them. Doe reads the enriched rows as one input among many. If you are evaluating new Clay territory, Doe covers that surface and the part Clay does not.
Gemini is a strong drafting engine. Your team is already using it well. Doe picks up where the chat ends. It runs on schedule instead of on prompt, writes to your tools instead of to a window, and learns across runs. A signal that closed last quarter gets weight on the next run automatically. None of that lives in a chat.
Both modes. Most teams start in suggest mode, with approvals per write in their team channel. After two weeks, teams flip specific fields into direct write. Nothing is hardcoded. You decide per field.
Every tool connection uses your org's existing OAuth scopes. Public web reads run through our managed scraping layer in our infrastructure. Salesforce writes go through the official REST and Bulk APIs under your auth. Doe does not train on your data. No customer data leaves the boundary without your sign-off.
Three steps. One, a forty-five-minute tailored demo with Doe running live on three to five real accounts you send ahead. Two, a four to six week POC on twenty-five to fifty accounts with two to five AEs, success criteria agreed upfront. Security review runs in parallel. Three, commercial and contract. The POC exit is a business case, not a renewal conversation.
Standard enterprise package. MSA and DPA templates ready to send. Sub-processor list available on request, covers our scraping infrastructure, foundation-model vendors, and cloud provider. SOC 2 Type II report available under NDA. EU data residency is supported if your team requires it. Happy to jump on a call with your security or legal contact directly.
Security and compliance
SOC 2 Type II in progress. GDPR-compliant data handling. EU data residency supported. Standard DPA and sub-processor list available on request.
No model training on your data
Your Salesforce rows, email threads, and merchant data never enter a training set. Model calls are zero-retention at the foundation layer.
Plugs into your stack
No new system of record. Salesforce stays canonical. Doe reads and writes through the official REST and Bulk APIs under your existing OAuth scopes.
For the forward to your CRO
Three lines to justify the demo internally.
- Platforms pillar grew 50% YoY in Q3 2025 on wallet-share expansion inside the installed base. Doe runs that cross-sell audit across our book on schedule, not on prompt.
- Holding another half-point of retention on our €2.4B FY25 revenue is worth eight figures. Doe watches the top 100 for the signals that precede churn and flags the intervention window before renewal gets loud.
- Enterprise AEs in SF sit at $310K to $400K OTE. One extra day of selling per rep per week pays back a full team deployment inside a quarter.
Each claim is cited in the sections above. Copy-paste-ready.
Start with a tailored demo. Move to a POC.
Here's how we usually run this. You bring real accounts. We run Doe against them, live, with your stakeholders. If the pattern holds, we scope a time-boxed POC with defined success criteria and move to contract from there.
Step one
Tailored demo
Forty-five minutes. You send three to five real TAL accounts ahead of time. On the call, Doe runs end to end on those accounts with your stakeholders watching. Scoring, play selection, drafts, CRM stage, review queue. Follow-up: the recording plus a scoped POC proposal.
Step two
Four to six week POC
Twenty-five to fifty named accounts, two to five AEs, one or two workflows live. Success criteria agreed upfront (pipeline generated, hours saved per AE, meetings from Doe-sourced signals). Security review runs in parallel. Exit is a business case, not a renewal.
Thanks for reading, Michael.
Send me your top ten accounts whenever you're ready. I'll run the full loop tonight and have the queue in your inbox by morning.
/ Doe