Built because the Tuesday email never got answered.
Jo Thomas spent five years running sales-development teams at B2B SaaS companies across Sydney. The pattern she kept seeing: a prospect replies on Tuesday at 10am with a real question — pricing, implementation, timeline. By Friday, nobody has followed up. By the following Tuesday, the deal is cold and the rep has no idea why.
The dead zone between replied and worked.
From 2015 to 2020, Jo ran SDR teams at two B2B SaaS companies in Sydney. In that time she watched the same operational failure repeat: inbound replies landing in shared inboxes, getting buried under new threads, then resurfacing weeks later when the prospect had long since gone elsewhere. It wasn't a motivation problem. The reps were busy. It was a structural one — the inbox is built for reading, not for queue management.
In 2019 she moved into a RevOps role and tried to solve it with CRM workflows, follow-up task sequences, and manual SDR triage. None of it held. The volume was unpredictable, the handoffs broke down, and the SDRs kept getting pulled onto other priorities. Seventy percent of the inbound replies that mattered went unworked past 72 hours. She could see the pipeline gap clearly — she just couldn't close it with the tools available.
By late 2020 she'd started sketching the product she wished had existed. Not an outbound sequence tool — there were dozens of those. Not a CRM add-on — the problem wasn't data capture, it was reply triage. The gap was specific: a replied-but-stalled thread needs detection, ICP scoring, and a warm follow-up draft before a human should have to touch it. She brought in Daniel Park, who'd spent four years building email automation infrastructure at a Sydney fintech, and they started building Enrola in early 2021.
We're bootstrapped and deliberate about it. Enrola does one thing — it works your dormant inbound reply queue. It is not an Apollo replacement, not an Outreach competitor, not a cold-email engine. We work the reply queue. That's the whole product.
Small team, deep focus
Former Head of SDR and then RevOps at two B2B SaaS companies in Sydney (2015–2020). Built Enrola after five years of watching high-intent replies go unworked because the inbox is a terrible triage system.
Spent four years building email automation infrastructure at a Sydney fintech before co-founding Enrola. Leads the reply-detection pipeline and the short-form NLP model that scores intent signals from email content.
Five years in sales ops and HubSpot/Salesforce implementation across a dozen mid-market B2B teams before joining Enrola. Owns the queue UI and the ICP configuration workflow — the parts SDRs and RevOps managers actually touch every day.
How we think about the product
We'd rather surface 5 high-ICP threads than 50 noise threads. A queue of 20 well-scored drafts that reps actually work beats a queue of 200 that they ignore. Quality of handoff is the metric that matters.
Enrola is not a sending tool. It writes the follow-up, your rep reviews it, your rep sends it from their own account. The relationship stays human. We're deliberate about that boundary — it's not a limitation, it's the product design.
We process email thread content to generate drafts. We do not train shared models on it, we do not share it across accounts, and we delete it when you cancel. This is a product constraint, not a marketing position — your prospect conversations are not our training data.