Outbound Playbook

Use this when sending the first 20-30 prospect emails for Aoexl PDF.

Positioning

Lead with:

• embedded signing inside the prospect's app
• hosted signing links for external recipients
• templates for repeatable onboarding flows
• webhook callbacks and completion artifacts

Do not lead with:

• broad compliance promises
• "perfect mobile"
• advanced identity verification
• generic "all-in-one PDF platform" messaging

Best First Wedge

The strongest story right now is merchant onboarding.

Why it works:

• the demo PDF already matches a real workflow
• it shows embedded and hosted paths clearly
• it naturally leads into templates, webhooks, and completion artifacts

Short Email Template

Subject:

Embedded signing for merchant onboarding

Body:

Hi {{FirstName}},

I’m reaching out because Aoexl PDF is built for teams that want signing inside their own product instead of sending users through a generic external flow.

We’re strongest on:
- embedded signing UX
- hosted signing links
- reusable templates
- webhook callbacks and completion artifacts

We currently demo this with a merchant onboarding packet end-to-end.

If that’s relevant, I can send a 2-minute walkthrough or a docs/demo link.

{{YourName}}

Slightly More Direct Version

Subject:

White-label signing for workflows

Body:

Hi {{FirstName}},

Most signing products are built as standalone destinations.
Aoexl PDF is aimed at the opposite use case: keeping the signing flow inside your app while still supporting hosted links when you need to involve external recipients.

Today the clearest use case is onboarding-style packets:
- embedded signing in your UI
- templates for repeatable forms
- hosted signing links
- webhook-driven completion flow

Happy to send a short walkthrough if useful.

{{YourName}}

Demo Link Follow-Up

Sharing the two best starting points:

- Demo: {{demo_url}}
- Docs: {{docs_url}}

The fastest thing to look at is the merchant onboarding demo. It shows the embedded signer flow, hosted link path, and the post-signing artifact story more clearly than a generic editor would.

2-Minute Walkthrough Script

1. Start on the merchant-onboarding demo.
2. Say the wedge in one sentence: "Aoexl keeps signing inside your product, while still supporting hosted signing links for external recipients."
3. Point out:
   • embedded signing
   • hosted signing requests
   • templates
   • webhooks
   • completion artifacts
4. Open a signature field.
5. Show the signer flow on mobile-sized view briefly.
6. Save / complete.
7. Mention the post-signing story:
   • signed PDF
   • completion certificate / audit trail
   • webhook callback
8. End with docs/contact CTA.

First Objections To Expect

• "We already use DocuSign."
• "Do you support mobile?"
• "Can this be white-labeled?"
• "How do webhooks work?"
• "How fast is integration?"

Use:

• Outbound Objections
• SDK Quickstart
• Signing Requests
• Webhooks

Before Sending Real Volume

Make sure these are true:

1. public docs URL is live
2. demo and contact CTA are visible
3. one hosted signing request has been tested end-to-end recently
4. one real-device mobile signer pass has been completed
5. the short walkthrough is recorded