Camunda's platform story lands with engineers. It doesn't land with the CFOs approving the budget yet.

The Pitch: Where I'd Start

I'd start with exactly what I already built: a live battlecard against Appian, including a real answer to Appian's Gartner Leader placement against Camunda's own Visionary one. Read the battlecard →

That's the kind of system I'd keep running against competitors who move constantly.

The same instinct applies to the bigger narrative gap behind "agentic orchestration": it lands with the architects and engineers who understand it immediately, but not yet with the CFOs and boards approving the budget at $100M+ ARR. I'd interview the non-engineering buyers on recent closed-won deals, what language did they use internally to justify the investment, and turn that into a second narrative layer sitting alongside the technical story.

The SAP partnership gets the same treatment: an engineering integration usually outpaces the sales story built around it, and a focused co-sell package turns an existing integration into a repeatable land motion.

The Proof

Start with the Camunda vs. Appian battlecard I built from live research on both companies, the sharpest single proof point since it demonstrates the competitive-intelligence function itself. Beyond that: at FunnelEnvy, I owned the competitive intelligence program end to end, battlecards, win-loss analysis, and a defined update cadence briefed to sales. At Reform, I repositioned a developer-first SaaS platform into a category-specific product for a defined technical buyer: 34% lift in trial activation. At Cecure Intelligence, I moved from an individual-contributor sales role to Chief Revenue Officer within 12 months. I've also built and shipped 81 AI agent skills (34 published), daily proof of the comfort with AI tools this kind of work now takes.

Let's talk about Camunda.

If this is the right problem for you, I'd like to talk about it directly.