See what is waiting, running, blocked, approved, and done.
Operations shows the live work: automations, approvals, owners, dashboards, goals, and exceptions. When a job fails or a decision is waiting, the team sees what happened and who needs to act.
Live workflows + approvals
Every automation is visible, every job has a status, and approvals happen before risky changes go live.
Goals tied to work
Goals, owners, and metrics stay linked to the campaigns, tests, workflows, and tasks that move them.
Charts tied to the live work
Charts and reports stay connected to the launch, customer, order, approval, or workflow they explain.
Attribution that holds up
Channels and tests are tied back to orders, spend, and revenue where the data is available.
Decisions with context
Every decision shows the work behind it: the numbers, source files, approvals, and next step.
First-party data when needed
Tracking, connections, reconciliation, and visualization can run inside the same workflow instead of becoming a separate data project.
| Task | Similar tools | Lyberty |
|---|---|---|
| Workflow automation | n8n / Zapier / Retool ($1-3k/mo) | included |
| Project & OKRs | Asana + Linear + Notion ($30-60/seat) | included |
| Dashboards & BI | Looker + GA4 ($3-8k/mo) | included |
| Attribution / analytics | Northbeam + Triple Whale ($1-3k/mo) | included |
| Data pipelines | Fivetran + Segment + GTM ($2-6k/mo) | first-party capable |
| Past decisions | Notion + Glean ($30-50/seat) | included |
A live work queue for what is running, blocked, and waiting.
Orders · approvals · jobs · automations
Zapier · Retool · Workato gives you the tool. Lyberty ties it to the rest of the business.
Under the hood
Every automation can see the order, customer, approval, and rule it touches.
Not scripts in a vacuum
Each step checks the right guardrails. Each result is recorded against the right order, customer, campaign, or finance line. When a run ends, you get evidence you can inspect and share.
This is not a nicer Zapier. It is a way to run the workflow and keep the approval, result, and evidence attached.
One keyboard shortcut for the work people keep asking about.
⌘K
The plan should show what shipped, what slipped, and why.
Not a deck · not a spreadsheet
Every objective links to the work that moves it, the tests that challenged it, and the numbers that prove it. "How are we doing on Q2?" should not require a screenshot update.
When something slips, you see it the day it slipped — not in the QBR three weeks later.
Notion · Asana · Linear roadmaps gives you the tool. Lyberty ties it to the rest of the business.
Under the hood
When Lyberty suggests a next move, you can see why.
Not another chat box
Blended CAC ran 4.2x LTV over 30 days. Cohort decay confirmed in the revenue readout. Suggested by the workflow, approved by Nia.
Three wins in sequence used the same follow-up pattern. The team saved it as a reusable playbook.
Churn signal appeared in cohort c_3. Decision: hold until July and collect more data.
Experiment B confirmed the issue. Step 4 was rewritten. Dropoff fell 38%.
Every decision leaves a trail. Every hypothesis keeps its evidence. Every suggestion points back to the test and the number behind it. The next person can see what the team already tried.
What matters is simple: when the same question comes up again, the team can see the last answer, the proof, and the next action.
Glean · ChatGPT Enterprise · your wiki gives you the tool. Lyberty ties it to the rest of the business.
Under the hood
The surface is just the view.
All six surfaces share the same record. Adopt one, and the others are already reading from what you wrote — no sync, no export, no reconcile.