How Cor started
Mantas Aleks spent six weeks embedded with the customer success team at a Denver-based workflow automation company. Every Monday morning, reps dialed through a queue of 80 new customers. By noon, fewer than 30 had picked up. The other 50 silently stalled and fell off onboarding.
The frustrating part was not the volume. It was the pattern. The customers who did pick up almost always resolved their blockers in a single two-minute conversation. The ones who did not answer were the ones who churned. The difference was not complexity — it was a missed phone call.
Mantas had come from Gainsight, where he had seen this pattern at scale across dozens of SaaS companies. Voice was the only channel that reliably got new customers to articulate what was actually blocking them. And voice was too labor-intensive to use at scale — a CS rep can handle eight to ten calls in a morning; a company with 200 new customers a week needs twenty calls a day, minimum.
The first version of Cor was a basic outbound call scheduler wrapping Twilio with a simple decision tree. It deployed at two pilot SaaS companies. Activation completion rates improved by 18% in the first month — but customers pushed back on the rigid script when their questions fell outside the decision tree.
Cor rebuilt the conversation layer using a large language model fine-tuned on onboarding transcripts. The agent was named Obi. The focus narrowed: the first 30 days post-signup, the highest-churn window, nothing else. Akira Nishida joined to design the voice infrastructure. Femi Adeyemi built the friction signal scoring and playbook builder. Petra Kalinowski brought the beta program live with a cohort of Denver-area SaaS companies.
Beta results: 78% call completion rate, 22% reduction in 30-day churn, 120+ manual touchpoints saved per CS rep per week. Cor moved from two pilot accounts to a waiting list of teams across the United States.
Our mission
Make every new customer feel like your best CS rep called them personally.
That statement sounds simple. It is not. Your best CS rep remembers where a customer is in their onboarding, asks the right question at the right moment, hears the hesitation before the customer even articulates it, and knows when to escalate versus when to just answer the question and move on.
Obi is built to do exactly that — at the scale of your entire new-customer list, every week, without burning out your team or adding headcount. Cor does not replace customer success reps. Obi handles the 80 calls that never get answered so your reps can focus on the 20 conversations that actually move accounts.
We are a seed-stage company in Denver, LoDo — a team of four, building carefully and shipping with intention. We believe voice is the most human-first channel available to SaaS companies for early customer engagement, and we intend to prove it at scale.
Where we are
Cor is a seed-stage company based in Denver, LoDo. We are working with a waitlist of mid-market SaaS teams in the United States — typically companies with 5 to 30 customer success reps onboarding 50 to 500 new customers monthly. Our focus is the first 30 days post-signup, the highest-churn window for this segment. We are not yet taking enterprise contracts or pure self-serve signups.
If your team matches the profile, book a call to join the waitlist and we will follow up within one business day. We are selective about early customers because we build Obi's playbooks collaboratively — your onboarding transcripts and CS team's knowledge become part of what Obi learns.
Cor has raised a pre-seed round from Denver-area operators and angels who have direct experience in SaaS customer success. We plan a seed round later in 2026 once we reach 20 paying accounts with demonstrated retention impact.
How we think and build
Voice-first, not voice-only
Voice is the best channel for resolving activation friction — not the only one. Obi uses voice where it works and steps aside where it does not.
Friction is a signal, not a failure
A stuck customer is telling you something. Obi's job is to hear it, score it, and route that signal to the right person quickly enough to matter.
CS reps amplified, not replaced
We build Obi to expand what customer success teams can do, not to replace them. Every Obi escalation reaches a human rep who is already briefed and ready.
No robocall energy
We hold Obi to a higher standard than "did the call connect." If customers feel like they talked to a script, we failed. Completion rate is a means, not an end.