About / Franklin
Franklin Christuraj
Value Engineer at Make (Celonis). I build agentic systems that survive contact with a real business: multi-agent orchestration, governance, and human-in-the-loop checkpoints. 600+ professionals trained across Embedded Build Sprints.

Nothing is a mistake. There's no win and no fail. There's only make.
Corita Kent
Nothing is a mistake
Experiment freely.
The first version is data, not a verdict.
No win, no fail
Run the code.
Slides teach vocabulary. Execution teaches judgment.
There's only make
Build to understand.
If I can't build it, I don't teach it.
Proof
600+ professionals trained across multiple regions. One workflow built in ~40 min typically saves 200+ hours/year per team.
The Build-With-Me Session Framework
Cut a support agent's failure rate from 30% to under 5% by routing every agent through one state layer with human-in-the-loop checkpoints on high-cost actions.
Multi-Agent Orchestration Patterns
Agent context prep dropped from ~15 min of manual gathering to a single tool call. 1,400+ notes and 3,000+ typed edges queryable through one MCP interface.
Ziksaka: A Knowledge Graph MCP Server
Journey
How I got here
I came up through automation and customer-facing product work, not a research lab. That matters. I've watched teams buy the demo, miss the operating model, and then blame the model when production rejects the fantasy.
At Make (Celonis) I sit at the intersection of agentic systems, enablement, process mining context, and real customer constraints. Through Frank About AI I write and teach the production reality layer most decks skip: governance, orchestration, shared state, and hard-coded human checkpoints. I build the trust layer. Then I show where it breaks, and where the CFO gets nervous.
Passion
What I won't stop caring about
Agents that survive contact with a real business. Not a slide. Not a weekend prototype. The boring, high-stakes layer: shared state, human-in-the-loop checkpoints, failure modes you can explain without jargon.
I also care about teaching by building. Embedded Build Sprints exist because watching someone else click through a dashboard changes almost nothing. Shipping inside your own guardrails does.
Expertise
Where I'm useful
- Multi-agent architecture with a single source of state
- Human-in-the-loop design where the cost of being wrong is real
- Agentic governance and audit-ready legibility
- Hands-on enablement (Embedded Build Sprints) for mid-market and enterprise teams
- Knowledge systems agents can query (MCP, typed graphs, SPARK-style conventions)