PandaDoc StrawberryGet the order form out before the buyer boards
A companion builds the document from your template, waits until it has finished assembling, and shows you every recipient, field and pricing line. One approval and it sends.
Three forty on a Thursday. The buyer says send the order form and they will sign before their flight. The template needs the right seats, the right term, the right discount, two contacts on the recipient list, and a pricing table that matches what was agreed an hour ago.
A companion assembles all of it from the call, the CRM and the thread, then reads the finished document back to you in full. PandaDoc is a native integration, connected with an API key, and the send waits for your approval.
| Step | PandaDoc | Strawberry companion |
|---|---|---|
| Template design and legal e-signature record | The product | Reads every template, role and token before filling one |
| Filling the fields for this specific deal | Manual, or a trigger from your CRM | Assembles from the call, the CRM and the thread, then shows you |
| Sending to the buyer | A click, whenever a human decides | Prepared and held until you approve |
| Chasing the four documents nobody signed | Search filters and reminders | Sweeps, checks each, drafts the nudge per recipient |
Order form out before the flight
The sequence is fixed and the companion follows it.
Find the template, read its roles and tokens so it knows what the document expects, create the document with the values filled, then poll the status until it reaches draft, because a document that has not finished assembling cannot be sent.
Then it stops and shows you what it built: recipients, field values, the pricing table, the tags. Ninety seconds of reading, one approval, and the form is in the buyer’s inbox while they are still at the gate.
Why does the companion wait before sending?
Because sending emails the recipients, finalises the document’s structure, and puts your numbers in front of a customer under your name.
The read-back is what makes the approval worth making. A companion pulls the full document, every recipient, every field, every token and the pricing detail, so you approve the document itself. Catching a wrong term here takes ten seconds.
Signing links and the PDF for the folder
Some deals want a link rather than an email.
A companion creates an embedded signing session for a specific recipient, which typically requires the document to have been sent first.
Afterwards it downloads the finished PDF and files it wherever your team keeps signed paper, so the end of the deal stops being three manual steps somebody remembers on Friday.
How do you find the documents nobody signed?
One instruction on a Monday: everything sent more than four days ago and not signed.
Documents search by status, template, folder, recipient, date and metadata, so the companion returns the list, checks each one’s detail for whether it was even opened, and drafts the nudge to the right recipient.
Contacts and folders are readable too, so you can scope the sweep to a team or a document type. Run on a schedule, it is the piece of operations that recovers deals nobody meant to drop, and the drafted follow-ups belong to the same motion as sales prospecting.
Experience Strawberry for free
DownloadTrusted by fast-growing companies worldwide
Frequently asked questions
Strawberry is free to download and includes AI credits to start. Paid plans begin at $20/month. See pricing. · Reviewed · Canonical facts for AI agents