Keep trust surfaces concrete while the product is still early.
Formal SLAs would be theater right now. The credible version is simpler: be explicit about beta status, security and data handling posture, current limits, and how to get help when the first workflow matters.
Beta product
ActionPlane is in a narrow-rollout stage and should be evaluated through one concrete workflow first.
Simulation or sandbox first
Salesforce starts in simulation when possible, while other connectors start in vendor or customer sandboxes.
Direct support path
The support model is founder-led, explicit, and optimized for early evaluators rather than enterprise theater.
Operational security posture
Data handling, credential storage, connector boundaries, and what stays visible on the governed run should be explicit.
Known product boundaries
The current connector matrix, workflow scope, and evaluation gaps should be visible before a buyer asks.
Clear escalation path
Evaluators need to know who responds, how fast the team engages, and what information helps resolve issues.
Production discipline
The first live workflow should stay intentionally narrow until the proof chain has earned trust.
The first production lane should still feel like an observed experiment.
Show the workflow safely
Use a seeded sample or vendor developer environment before a customer tenant is involved.
Prove one sandbox workflow
Keep the connector scope narrow: one identity, one object set, and one high-value change path.
Go live under operator visibility
The first production motion should still route through approvals, evidence, and explicit connector health.
Security and data handling
Explain what data ActionPlane stores, what stays in the customer environment, and how connector credentials are handled.
Known limitations
Show the current connector, simulation, and rollout limits directly instead of hiding them behind marketing copy.