Enterprise readiness
What a large buyer asks for before it signs, which parts every App already has, and when the agent first offers the rest.
A large buyer asks for the same few things before it signs, and every App already has them. The agent raises them when the first enterprise Deal opens, and not before.
When it wakes
An idea-stage Startup needs none of this, so the agent stays quiet about it. The chapter wakes when a Deal opens for a buyer that asks for single sign-on, a security review or a yearly contract. At Leaseline, that is Harbor Residential in month 12.
What every App already has
| The buyer asks | What answers it |
|---|---|
| Single sign-on and directory sync | Tenant.requestSetup, then SSOConnection.activate and a Member Directory |
| Access for each of its people | Access Levels and a Persona each, set by the Customer's own admin |
| An audit trail | The audit log, exported to their warehouse |
| Its data back on demand | Collection.export of every Tenant record |
| An uptime promise | An uptime target and credit tiers on the Offer |
| A yearly contract at its own price | A custom Offer and a Quote |
The custom plan
To sell Harbor Residential a yearly plan at $24,000, the agent makes an Offer for that Customer alone and sends a Quote. Make a custom plan for one customer is the guide. Sending the Quote is a send action, so it waits on the founder when her approvals ask first for that class.
What it waits on
The security questionnaire and the data processing terms come from the Startup's Agreements and its controls. A buyer that asks for support access to stay off by default gets it: support access always needs their consent.
Next
Reference lists every key of the App definition.