Built for the ops team, by someone who ran one
Founded in Pittsburgh, PA in 2022. We build workflow orchestration for RevOps and BizOps teams who need their automations to keep working — not just run once and quietly break.
Why we built Orchestloom
Before starting Orchestloom, Liam Donovan was Head of Revenue Operations at a B2B SaaS company in Pittsburgh. His team managed lead routing, pipeline automation, and customer data sync across Salesforce, HubSpot, and five other tools — almost entirely through a mix of native CRM rules, Zapier zaps duct-taped together, and a shared Google Sheet that someone had to manually refresh every Monday morning.
The workflows worked — until they didn't. A step would fail silently at 2am. Leads would sit in a dead queue until someone noticed the CRM count was off. Engineering was helpful, but they had a product to ship; fixing a broken Salesforce webhook was never going to land in the next sprint.
The tools existed for simple triggers and single actions. What didn't exist was orchestration: multi-step workflows across systems that could survive failures, retry automatically, and alert the ops team when something genuinely broke. Not as an enterprise iPaaS. Not requiring a developer. Just a canvas an ops practitioner could build and own themselves.
That gap became Orchestloom. We launched in 2022, bootstrapped, from Pittsburgh's Strip District. We are not trying to replace engineering for complex custom integrations — that's not the problem we solve. We solve the problem of ops teams waiting in backlog queues to automate workflows they fully understand and just need a reliable way to run.
Liam Donovan
CEO & Co-Founder
Liam spent four years running Revenue Operations at growing B2B SaaS companies before co-founding Orchestloom in Pittsburgh in 2022. He's built lead-routing workflows from scratch, debugged silent CRM sync failures at 7am, and watched perfectly good automation projects die in sprint-planning backlogs because the engineering team was understaffed and the ops use case was low-priority.
He started Orchestloom because the tooling gap was real and expensive — not in dollars, but in data quality, team trust, and hours of manual reconciliation work that shouldn't exist.
Liam writes about workflow orchestration, RevOps, and operations infrastructure on the Orchestloom blog.
Our team in Pittsburgh, PA
100 Smithfield Street, Suite 800
Pittsburgh, PA 15222
[email protected] · +1 (412) 533-9908