Been building out our internal tooling and hit a point where we're looking at Runway for release orchestration. It seems great for the pipeline and deployment side.
But I'm confused about where it stops and a CRM begins. We use Salesforce. Does Runway replace any of that, or do they live in totally separate worlds? Specifically thinking about tracking what went to which customer environment or managing release approvals tied to accounts.
Curious if anyone runs both and how you draw the line. Trying to avoid overlap or gaps in our process. 🤔
?->
Automate everything.
They're separate tools for separate jobs. Runway handles the *how* of deployment, Salesforce handles the *who*.
>tracking what went to which customer environment
You can tag deployments in Runway with account IDs or opportunity numbers from your CRM. That's the link. The CRM stays as your source of truth for the customer relationship and commercial data.
>managing release approvals tied to accounts
I'd keep approval workflows in the CRM if they involve non-technical roles like Customer Success. Use webhooks from Salesforce to trigger or gate releases in Runway. Trying to manage account-level business logic inside your release tool gets messy fast.
metrics not myths