kyntralabs.Est. 2019
01Case study

A workflow runtime for marketing campaigns.

Nobody has ever been late to market because the email was hard to build. They're late because Legal had a question on day nine and nobody noticed until day fourteen.

Agora is a structured workflow runtime for the cross-functional work behind a campaign. Define the process once, then run every campaign through it.

02What you can buy

The shelf is not empty.

Asana. Workfront. Wrike. Monday. A Jira board somebody swears is working. A dozen vendors sell project management, and most marketing teams already pay for two of them.

So the honest starting question was never whether I could build one. It was why buying one hadn't solved it.

03What it misses

They model tasks. Not the process.

Four things break the same way on every campaign, regardless of which tool the team is paying for.

i.

Process never compounds.

A campaign brief is a form somebody re-types every quarter. Nothing versions it, so an improvement made in March is gone by June. The team gets better and the process doesn't.

ii.

Branching is a checklist item.

Regulated product means Legal, plus a disclosures step. In a generic tool that's a box somebody remembers to tick, which is a polite way of saying it depends on who's paying attention.

iii.

History stops at the task.

Who changed the audience after creative was approved? A task tool can tell you the card moved to Done. It cannot tell you the answer inside it changed, or who changed it, or when.

iv.

Bottlenecks surface late.

A section sat with Legal for fourteen days. In most stacks the place that gets discovered is the status meeting, which is nine days later than anybody needed to know.

04The hypothesis

Make the process the artifact.

If the workflow itself were a versioned, branching, auditable object rather than a document and a task list, would campaign work stop drifting? Three layers to find out.

i.
Layer

Modules

Versioned form templates. Campaign Brief, Legal Review. Each owned by a team, each with a typed field schema, each improvable in a way that sticks.

ii.
Layer

Blueprints

A workflow assembled from modules, with real branching. If regulated industry, then Regulatory Disclosures. The reusable definition you run campaigns through.

iii.
Layer

Initiatives

A live instance of a blueprint. Every step becomes a section with its own state, an assignee, an SLA, and answers. The definition and the running thing are separate objects, which is the entire trick.

05What I built

What I built to test it.

  • Change requests with field-level diffs and an append-only activity log, so every answer has a history and an author
  • SLA tracking that flags a breach the day it happens rather than at the status meeting
  • Linked fields across sections, so a later module reads an earlier one's answers without copy-paste
  • Three views of the same campaign — flow, timeline, and table — because different roles need different shapes
  • Multi-workspace tenancy, per-team dashboards, roles and invites
06The verdict

What it actually taught me.

Daedalus had somewhere to stand. It lives on top of Marketing Cloud, so the data model, the objects, and the permissions were already settled. I was building a lens over a system that already existed.

Agora had none of that. No host platform, no schema to inherit, no conventions to borrow. Every concept had to be invented first and then defended. That's what made the real lesson expensive enough to stick.

Ship the smallest thing that runs, then let use tell you what comes next.

Build against a feature list and you'll burn out somewhere around item nine, holding a half-working application and a backlog of things you were certain you needed. Start with a genuine MVP and iterate, and you end up with the tool you actually needed, which is almost never the one you spec'd. The list you write on day one is a guess. The list that real use hands you is evidence.

On the buy question, since that's the whole reason the lab exists: I went back and looked again. Nothing on the shelf does this. Versioned modules, branching approval paths, field-level history on every answer, an SLA on every step. The project management tools model tasks. Agora models the process. That gap is still open, and it's the closest thing to a verdict I have.