From quote to signed and paid
The intended flow puts the quote, the signature and the payment on the deal itself. None of that ships yet, and the deal that carries it does.
- Quotes on the roadmap
- Payment on your own Stripe key
- Deal and cadence work today
The short answer
- The intended mechanism: a quote with line items sits on the deal, goes out as a PDF, is accepted with a typed signature, and carries a payment link charged on your own Stripe key. Payment moves the deal stage.
- None of it is available. Quotes, e-signature, payment links and the paid-to-stage rule are one roadmap feature in the local-services pack.
- What works today is the part around it: the deal with its stages and probability, tasks with owners, an email cadence chasing an unsigned quote, and every stage change written to the audit log.
Trigger to logged, as designed
Where each step stands right now.
- 1
Trigger: a deal reaches the quoting stage
The deal exists today with its stage, probability and weighted value, and a contact or a company link that is optional on both sides.
- 2
The quote is built
Line items, totals and terms on the deal itself. On the roadmap. Today the document is produced in whatever tool you use and attached to the deal as a file.
- 3
It goes to the customer
As a PDF from the quote. On the roadmap. Today it is an email you send, and the thread lands on the deal timeline.
- 4
The human chases it
This part works. A follow-up cadence runs on its schedule, pauses when the customer replies, and the reply appears in the shared inbox.
- 5
Acceptance and payment
A typed signature and a payment link on your own Stripe key, with paid moving the stage. All on the roadmap.
- 6
What gets logged
The stage changes and every touch, with the actor recorded, today. The quote, signature and payment events when the feature ships.
What gets configured
Read the status column before planning anything around this.
| Object | What you set | Status |
|---|---|---|
| Deal and stages | Your stage names and the probability on each | Available |
| Follow-up cadence | Steps chasing an unsent or unsigned quote | Available |
| Files on the deal | The quote document you produced elsewhere | Available |
| Audit on stage changes | Actor recorded on every move | Available |
| Quote with line items | Products, quantities, totals, terms | On the roadmap |
| PDF and typed e-signature | How the customer accepts | On the roadmap |
| Payment link | Charged on your own Stripe key from your vault | On the roadmap |
| Paid moves the stage | The stage a payment lands the deal in | On the roadmap |
Where it stops and a human starts
Money stops with a person, permanently. The default policy table puts every action that spends or takes money in the human-only class, and no agent mode changes that. An agent may draft the follow-up; it does not send an invoice.
The payment design keeps you in the middle as well. When it ships, the charge is planned to run on your own Stripe key held in your instance's vault, so the money goes to your account and the customer sees your business rather than a platform.
Today the flow stops at the document. If quoting and taking payment inside the CRM is the reason you are shopping, this is not the product for that yet, and the changelog is where that will change.
Questions
- Can I send a quote from SalesCrew today?
- Not as a quote object. You can attach a document to the deal and email it, and the thread lands on the timeline. Line items, PDF, signature and payment are one roadmap feature.
- Whose Stripe account takes the payment?
- Yours, by design. The plan is a payment link on your own key stored in your instance's vault, so nothing sits between you and your revenue.
- What can I do today about unsigned quotes?
- The most useful part, which is chasing them. A cadence that runs on its own schedule and stops on a reply is available now, and that is where most of the lost revenue actually is.