Company profile · 3 min read
Alia: Evidence-backed coordination across the company’s tools
Alia connects context across email, Slack, project tools and code to surface misalignment, bring the right people together and follow work through resolution.
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
Published · Updated
Alia is an agentic coordination layer for companies where work is spread across Slack, email, project tools and code. It fits a cross-functional team that loses time to promises, blockers and decisions that live in different systems rather than in one obvious task list.
What it does
Alia’s current site shows an agent watching context across tools and noticing when a customer promise in email or a meeting conflicts with the state of a Jira issue or GitHub work. It brings the people into a shared room, attaches the evidence, nudges the next action and stays with the thread until the issue is resolved.
That is a different product from a generic project-management assistant. The value is in the cross-system mismatch: a customer-success person believes a feature is on track, an engineer has no branch or pull request, and the client call is approaching. Alia’s workflow is to surface the discrepancy, name the people who can resolve it and preserve the follow-up history.
The site also frames the product at three levels. An individual can ask what they owe or who they are blocking. A team can hand off an action without losing it. A company can see work drifting from top priorities. The buyer should decide which of those is the first measurable workflow; trying to coordinate the entire company on day one would make the evidence hard to interpret.
Founder context and tradeoffs
The Speedrun profile identifies Thomas Filshill as CEO, with prior experience scaling AI systems, and Livia Kuga, who describes coordinating Stone from its founding team to 15,000 people. Those backgrounds support the coordination thesis, but they do not prove that the agent can infer intent from every company’s tools.
Pricing is not public. The current path is a demo. A buyer should ask which systems Alia can read and write, what permissions it needs, how it handles conflicting evidence and how a user stops or corrects a nudge. An agent that posts into team channels can save time, but a wrong escalation can create more coordination work.
Editorial take
I would shortlist Alia for a team with a visible cross-functional failure mode—customer promises disappearing between sales, success and engineering. Start with one workflow, one evidence bundle and one definition of “resolved.” If the company cannot name the decision Alia owns, it is probably too early for a coordination layer.
Quick facts
| Field | Sourced detail |
|---|---|
| Product | Agentic cross-tool coordination, blocker detection and follow-through |
| Buyers | Cross-functional operating, customer-success and leadership teams |
| Public workflow | Context across email, Slack, Jira and GitHub; evidence-backed nudges |
| Pricing | Demo-led; no numeric price observed |
| Main gate | Tool permissions, evidence quality, escalation rules and resolution definition |
Sources checked
| Source | Checked |
|---|---|
| Speedrun profile | 2026-09-19 |
| Alia homepage | 2026-09-19 |
About the author
Cofounder of Lazyweb (a16z Speedrun). Previously grew subscriptions and built native ads at Duolingo. Writes First1000 (90,000+ subscribers).
I cofound Lazyweb and publish Mudpie. This is an owner-written publication, not an independent testing organization. Research notes distinguish observations, sourced reporting and editorial judgment.
First1000 ↗ · X ↗