Skip to main content
A soft gate is a checkpoint that advises you to pause before scaling a motion that has not earned it. It shows the tradeoff and leaves the decision with the founder.

​
Before extracting a template

Learn from real conversations before turning a speculative message into a repeatable process. handoff templatize checks recorded sends before extracting a reusable template. Below its preflight threshold, it warns and asks whether to continue, defaulting to no. --force skips that confirmation.

​
Before handing off sales

handoff readiness rates you green, yellow or red, with next actions. It combines a self-assessment with ledger context, asking about demand, retention, discovery questions, the pitch and other readiness signals. It is guidance based on your answers, not independent proof of product-market fit. handoff first-ae assesses readiness for the first sales hire. See the CLI reference for each command’s options; not every readiness assessment has a force override.

​
Different from enforced checks

Soft gates advise. Enforced checks block. A soft gate is not a missing credential, trigger readiness failure, ICP rejection, suppression rule or sender cap. Those checks protect a specific execution path, and an override on a handoff command does not disable them. When warned, review the missing evidence and decide whether you have a reason to proceed. Being able to override is not a recommendation to increase volume.