How the scoring works
The application asks fourteen questions. Nine of them carry a weight — budget, timeline, current revenue, decision authority, and five qualifying questions you can rewrite for your offer. The workflow sums the weights into a contact field called `application_score`.
A single if/else branch compares that score against a custom value. Clear it and the confirmation page renders the calendar. Miss it and the contact lands on a "not a fit yet" page with a self-serve offer, so an application that is not ready for a call is not simply discarded.
The pipeline is part of the product
Six stages: Applied, Qualified, Booked, Showed, Proposal, Won. Every stage move is driven by a workflow rather than by a human remembering, so the pipeline is trustworthy enough to forecast from on day one.
Disposition tags from the call feed back into the sequences: "not now" contacts go into a 90-day re-engagement, "no budget" contacts go to the self-serve path, and "won" contacts drop out of every marketing sequence automatically.
Pre-call homework raises the close rate
Three touches between booking and the call: a two-minute video about how the call runs, a one-page prep document, and a same-morning SMS. They are built, written and switched on by default — you can remove any of them, but they cost you nothing to leave in.