kyntralabs.Est. 2019
01Overview
In development — private beta coming

A workflow runtime for marketing campaigns.

Agora is a structured workflow runtime for marketing campaigns. Agencies and in-house brand teams define a reusable workflow once, then run live campaigns through it — with full visibility into who owns what, where it's stuck, and what changed.

02The problem

The work is cross-functional. Running it is invisible.

Marketing work happens in a graveyard of Google Docs, Slack threads, Asana boards, and Figma comments. Strategy writes a brief, Creative produces, Media plans, Legal reviews, Analytics measures — but the process of running it is invisible. Three things break, every time:

i.

Approvals drift.

Someone changed the audience after creative was already approved. Nobody knows — there's no source of truth and no change history.

ii.

Bottlenecks hide.

A section sat with Legal for 14 days. The PM found out at the status meeting.

iii.

Process doesn't compound.

Every campaign rebuilds its own scaffolding from scratch — same modules, same approvers, re-typed every time.

03How it solves it

Three layered concepts.

Define the workflow once, then run every campaign through it.

i.
Layer

Modules

Versioned form templates — "Campaign Brief," "Legal Review." Each owned by a team, with a typed field schema.

ii.
Layer

Blueprints

A workflow built from modules, with branching logic — if regulated industry → 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 — blocked, ready, in progress, review, complete — plus an assignee, an SLA, and answers.

Layered on top: change requests with field-level diffs, threaded chat per section, an activity audit log, SLA tracking that auto-flags breaches, and linked fields that pull from upstream sections — so a later module sees an earlier one's KPI targets without copy-paste.

04What's built

The product is real, and it maps to the problem.

Each capability closes one of the three gaps above:

  • Reusable, versioned Modules & Blueprints — process compounds instead of getting re-typed(→ process doesn't compound)
  • Change requests with field-level diffs + a full activity audit log — a real source of truth for what changed and who changed it(→ approvals drift)
  • SLA tracking that auto-flags breaches — bottlenecks surface the day they happen, not at the status meeting(→ bottlenecks hide)
  • Linked fields across sections — answers flow downstream automatically, no copy-paste
  • Three workflow views — Graph, Timeline, and Table — see the same campaign as a flow, a schedule, or a list
  • AI helpers — blueprint and module suggestions, plus draft generation, to get a workflow started fast

Plus the operational layer you'd expect: multi-workspace tenancy, per-team and per-workspace dashboards (cycle time, throughput, SLA-breach trend), per-section detail pages, integrated chat, a combined notifications/inbox/queue home, and admin controls for roles and invites.

05What stage it's at
Advanced prototype

Demo-ready and entering private beta. Built and shipping on a real cadence — not yet production-hardened, getting there fast.