Decide which enterprise features to build before moving upmarket

Help me decide which enterprise-readiness features to build before selling to larger customers. Current customers and target: [e.g. "SMB teams of 10-50, want to sell to 1,000+ employee companies"] Deals lost or stalled because of missing features: [deal names or sizes, and what was missing] What we already have: [e.g. Google login, basic roles, CSV export] Engineering capacity: [team size, quarters available] Pricing plan for enterprise: [what will be gated] Evaluate these enterprise requirements, plus any I add: - Identity: SAML/OIDC single sign-on, SCIM user provisioning, enforced MFA. - Access: custom roles, granular permissions, workspace or team hierarchy, domain capture. - Visibility: audit logs with export or SIEM streaming, admin usage reports. - Data: data retention settings, residency, bulk export, customer-managed keys. - Reliability and support: SLA, status page, premium support. - Procurement: SOC 2 report, security questionnaire answers, invoicing and PO billing, uptime history. Return: 1. A table: feature | why buyers require it (security, IT, procurement, legal) | revenue at stake from my lost deals | build effort (S/M/L) | buy or build option | priority. 2. A sequenced roadmap for the next 2-3 quarters, with the minimum version of each feature that unblocks deals. 3. Which features belong in the enterprise plan versus all plans (note that charging extra for SSO is common but draws criticism). 4. Non-product work that matters as much: security docs, contract terms, support coverage. 5. Signals that we are ready to go upmarket, and signals that we're building too early. Do not assume deal data I haven't given; mark it [ADD].