Overview
Satsuma launches connectors in stages so strategy, implementation, security, and channel submission stay aligned. The goal is not just to make a demo work. The goal is to ship a connector customers can rely on.Launch Phases
1
Discovery
Confirm target channels, user workflows, business goals, systems involved, and launch constraints.
2
Design
Define connector actions, permission boundaries, app UI moments, analytics events, and support requirements.
3
Build
Implement the MCP server, app UI, auth integration, deployment configuration, and observability hooks.
4
Validate
Test happy paths, permission failures, expired auth, malformed input, downstream failures, and channel-specific behavior.
5
Launch
Submit or enable the connector in the target channels, monitor early usage, and resolve launch issues quickly.
6
Iterate
Use analytics and support signals to tune tools, copy, confirmation moments, and product workflows.
Readiness Checklist
Product
Target workflows, success metrics, user-facing copy, and escalation paths are approved.
Security
Scopes, token handling, data retention, audit logging, and revocation behavior are reviewed.
Engineering
Staging and production access are configured, tests pass, observability works, and rollback steps are known.
Channel
Assistant-specific metadata, UI constraints, submission materials, and review requirements are complete.