一気通貫
STACK RECIPE

The AI SDR stack.

An agent that finds the thread, works the deal and closes it: contract signed, payment collected into your own Stripe. One human review stands between the call and the money.

START LETSIGN FREE SEE PRICING
THE STACK

Five layers, one motion.

Every layer is swappable; the shape is not. An agent that listens, a contract layer that closes, and your own Stripe that collects.

THE AI SDR STACK THE BRAIN Claudethe agent: reads the call, drafts the deal, tracks the close THE EARS Call recorderFathom, Granola or Fireflies: the conversation becomes notes the agent can read THE CLOSER LetSign MCPcontract, conditional pricing, binding e-signature, payment: one link THE RAIL Your Stripeone-off or subscription, collected at signature time, straight to your account THE MEMORY Your CRM (optional)e.g. HubSpot as a data source the agent reads for context, nothing more One call in, one signed and paid contract out.
HOW THE MOTION RUNS

From hello to paid, in five steps.

No SDK, no webhooks, no integration project. The stack runs on two connections and one prompt.

1

The conversation happens

You take the sales call the way you always do. Fathom, Granola or Fireflies records it, so the numbers, objections and names your client actually used come out the other side as notes the agent can read. If you keep a CRM like HubSpot, the agent can read context from there too; the stack treats it as a data source, nothing more.

2

The agent drafts the personalized proposal

Point Claude at the call notes and it authors the proposal through the LetSign MCP: the scope in the client's own words, conditional pricing tiers your client can choose between, the terms you discussed. One proven opener:

PROMPT

"Pull my notes from this afternoon's call with Arden Labs and draft their onboarding proposal in LetSign - three tiers, the middle one at the number Priya quoted - then stage it for my review."

3

You review and send - the gate

The agent stages the proposal; nothing sends itself. You read every line, adjust a tier or a clause if you like, and press send. The human send-gate is a feature of the stack, not a limitation.

4

The client picks a plan, verifies and signs

Your client opens one public link, chooses between the plans you offered, verifies their email and signs a binding e-signature. Remember: the sender never signs. The client does.

5

The money lands in your Stripe

Payment is collected at signature time through your own Stripe account: one-off, subscription or save-card-on-file. LetSign never holds your funds.

This page is the recipe; the deep dives live one level down. Start with the Claude playbook for the connector setup, see how Stripe payments plug in, or read what makes a contract agent-native in the first place.

WHY THIS STACK CLOSES

Mechanism, not magic.

PERSONALIZATION

It quotes the call back

The proposal is drafted from the transcript, so it opens with the client's own words, their numbers, their deadline. Not a template with a name swapped in.

NEGOTIATION

Zero re-editing when terms move

Client wants net-60 or a smaller tier? Tell the agent in one sentence; it updates the terms and restages the proposal for your review. No export, re-edit, re-send cycle.

ONE FLOW

Sign and pay in one sitting

The same link carries plan choice, email verification, binding signature and payment. There is no gap between yes and paid where the deal can cool.

SWAP TABLE

Every layer has understudies.

The recipe holds no matter which brand fills each slot. Swap freely; the LetSign layer and your Stripe stay put.

LAYERIN THIS RECIPESWAP IT FOR
The agentClaudeClaude Code, ChatGPT (requires Developer Mode), Cursor
The recorderFathomGranola, Fireflies, or any tool that turns the call into notes the agent can read
The automation railPlain conversationn8n or Make when you want scheduled, trigger-driven runs instead of a chat window
FAQ

Stack questions, answered.

Do I need all of these tools?

No. The minimum stack is an agent, LetSign and your own Stripe account. A call recorder like Fathom, Granola or Fireflies makes the proposal far more personal because the agent drafts from what was actually said, and a CRM is an optional data source the agent reads for context. Start small and add layers when you feel the gap.

Where does the money go?

Into your own Stripe account, directly. LetSign never holds funds: when your client pays at signature time, whether one-off, subscription or save-card-on-file, the charge runs through the Stripe account you connected, and the payout follows your normal Stripe schedule.

What does LetSign cost?

The Free plan is $0 with a 0.20% fee on payments collected through it. The launch plan is $19 per month until October 1, 2026, and that price is locked until October 1, 2028; after launch the standard price is $49 per month. Paid plans pay 0% on payments up to $20,000 per month, then 0.05% above that.

Can I run this without code?

Yes. In claude.ai, adding LetSign is a settings screen: open Settings -> Connectors -> Add custom connector, or install in one click from app.letsign.ai. Connecting Stripe is a guided flow inside LetSign. And everything the agent does is fully editable by hand in the LetSign app, so you can run whole deals without touching the MCP at all.

RUN THE RECIPE

One call in, one signed and paid contract out.

Install LetSign free, connect your Stripe, and let the agent stage the next proposal for your review.

START LETSIGN FREE