Connect LetSign to Claude and your assistant drafts the proposal, the pricing options and the contract from a single conversation - then stages it for your review. Your client opens one link, picks a plan, signs and pays into your own Stripe.
Claude does the thinking, LetSign does the contracting, Stripe does the collecting. You stay in the loop exactly once - at send time.
No SDK, no webhooks, no integration project. The whole setup is two connections and one prompt.
In claude.ai (or the Claude desktop app), open Settings -> Connectors, click "Add custom connector" and paste the LetSign remote MCP URL. OAuth is supported, and the only requirement is that the server is publicly reachable - LetSign is hosted, so it already is. Even faster: one-click install from app.letsign.ai for Claude. Claude's free plan includes one custom connector, which is all LetSign needs.
In the LetSign app, connect your own Stripe account once. From then on every payment - one-off, subscription, or save-card-on-file - is collected through your Stripe and lands in your account. LetSign never holds your money.
Talk to Claude the way you would brief a colleague. One proven opener:
"Draft the retainer proposal for Meridian Consulting from today's call notes - three tiers, the middle one at the number we discussed - and stage it for my review."
Claude stages the proposal; nothing sends itself. You read it, tweak anything you like (a discount, net-60 terms, a different tier), and press send. The human send-gate is a feature, not a limitation.
Your client opens one public link, chooses between the plans you offered (conditional pricing built in), verifies their email, signs a binding e-signature and pays through your Stripe - in a single sitting. Remember: the sender never signs. The client does.
Working in a terminal instead of a chat window? The same stack runs in Claude Code. Team standardized on OpenAI? There is a ChatGPT playbook too.
Claude drafts the whole proposal with up to several plans your client can choose from - three tiers, optional add-ons, the works - straight from your call notes.
"Has Meridian signed yet?" Claude checks proposal status through the MCP: opened, plan picked, signed, paid - without you opening a dashboard.
Client asks for net-60 or a 10% discount? Tell Claude, and it updates the terms and restages the proposal for your review.
One-off invoices, subscriptions, or save-card-on-file - collected through your own Stripe account at signature time, not weeks later.
And everything Claude does here, you can also do by hand. Every proposal, template and setting is fully editable in the LetSign app - full parity with the MCP. That two-way door is the essence of an agent-native contract: your agent and you work on the same object, and neither is a second-class citizen.
Yes. claude.ai and the Claude desktop app support remote MCP servers through custom connectors: open Settings, choose Connectors, click Add custom connector and paste the server URL. OAuth is supported, the server just has to be publicly reachable, and the free plan includes one custom connector, which is enough to run LetSign.
No. Adding the connector is a settings screen, not a config file. You connect Stripe once inside LetSign, then everything else happens in plain conversation with Claude. And if you ever prefer to work by hand, every proposal and template is fully editable in the LetSign app.
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.
You do. Claude drafts and stages the proposal, but nothing sends itself: a human reviews and presses send. And the sender never signs. Your client opens the link, picks a plan, verifies their email, signs a binding e-signature and pays through your Stripe.
Add the connector, connect Stripe, and let Claude stage the next proposal for your review.
START LETSIGN FREE