The accept section: package summary, exclusivity slots you can add and remove, the discounted totals, the contact details, the contract step, and a payment form themed to match the page. On success the customer lands on a confirmation page which fires an idempotent welcome-email send.
Also called: checkout · start my subscription · pay the down payment
- 1Selecting a package elsewhere on the page scrolls here and highlights the section
- 2Exclusivity slots add a per-slot monthly amount up to the configured maximum
- 3The discount helper is applied to every cents figure so the totals agree with the rest of the page
- 4The success page fires the welcome send; a server-side atomic claim dedupes it against the payment webhook
A builder who has just signed and paid and then receives nothing has been handed every reason to doubt the decision, and that is what happened whenever the payment provider's notification failed to arrive. Choosing a package, adding exclusivity slots, signing and paying now all happen in the proposal itself, and the welcome email fires from two independent places so it lands even when the payment notification does not. The claim on it is atomic, so the two paths can never both send.
- Sign-up requiring a back-and-forth outside the page
- Welcome emails lost when a payment webhook does not arrive
- Duplicate confirmation emails from two send paths
See it on your own jobs
Twenty minutes, your numbers, no slide deck. We’ll build one of your real buildings in front of you and send you the estimate link at the end — yours to keep either way.
or keep browsing features →