Akkari — Investment Memo · Orange Collective

Thesis

Every customer interaction at every B2B company creates a long tail of operational work: a commitment made on a sales call, a bug surfaced in Slack, a security question asked for the third time, a fix that shipped but never got back to the customer, an expansion signal scattered across email and meeting notes. At an early-stage startup, this work lives in people's heads — until it doesn't.^[3]

Akkari captures every commitment, issue, request, and opportunity across the customer surface (Slack, calls, meetings, email, Discord, CRMs) and executes the actual work to close each loop — drafts the reply, files the ticket, schedules the meeting, opens the PR, sends the customer the update when the fix ships.^[2]^[3]

Recording work is not the same as doing it. Akkari is the AI execution layer that turns conversations into completed customer outcomes.

01
The wedge is execution, not transcription. A decade of GTM tooling — Gong, Chorus, Granola, Fireflies, Salesforce Einstein — produced excellent records of customer conversations. None of it does the work those conversations create. Akkari is the first product built around the assumption that an AI should not just summarize the call, it should finish the to-do list the call produced.
02
The founders have lived this problem at every scale. At OrderAhead (W11, acquired by Square), Jeff and Henry built the product and Michael built the GTM org — 30-person sales team, 2,500 contractors, thousands of merchants. They learned the same lesson three times: customers are won or lost in the follow-through, not in the pitch. At BLADE, Jeff and Henry scaled to $1.2B+ in monthly trading volume on the back of the same operational rigor.^[5]^[6]^[7]
03
The angel list is the validation. Fidji Simo (CEO, OpenAI Apps), Tony Xu (DoorDash), Eric Wu (Opendoor), Othman Laraki (Color), plus Liquid 2, Tuesday Capital, YC, and Orange Collective.^[2] Every name on the list ran the exact customer-operations problem at scale and chose to back the team building the solution.
04
P26 batch validation is happening in real time. Superlog, Limrun, Auxos, Superset, Sazabi, Standout, and Klaimee — some of the most credible teams in the P26 batch — are already design partners or queued to onboard.^[3] The pull is showing up simultaneously across founder-led sales, customer success, and PLG-to-enterprise conversion — which is exactly what you'd expect from a horizontal customer-ops layer.

Problem

Every customer interaction creates a long tail of operational work. At an early-stage startup, all of it lives in people's heads.

A customer reports a bug in Slack. A founder promises a pricing breakdown on a call. A prospect asks the same security question three times. An engineer ships the fix, but nobody tells the customer. A champion is ready to expand, but the blockers are scattered across email, Slack, Linear, and meeting notes.^[3]

At ten customers, the CEO holds it in their head. At fifty, it's a Notion doc and a few Slack channels. At a hundred, half the team is spending half their week on the operational work created by the other half — and customers are slipping through the cracks anyway.

The conventional response is to layer in more tooling: a CRM for accounts, a ticketing system for support, a call-recording tool for sales, a customer success platform for retention. Each surface has its own database, its own AI summary feature, and its own narrow notion of what "the customer" is. None of them close the loop on the actual work.

The reason the best teams win is not better product or better messaging. They win because they follow through faster, more consistently, and with better judgement than everyone else. That's what Akkari is making available off-the-shelf.^[3]

~10 calls/wk

When pre-sales breaks down

Per Akkari's onboarding guidance

~10 customers

When post-sales breaks down

Operational work stops fitting in your head

5+ surfaces

Where customer signal lives

Slack · email · calls · Discord · CRM · Linear

Why Now

For the first time, AI can do the work — not just describe it.

Two preconditions had to come true at once: companies needed a complete digital record of their customer work, and AI agents needed to be reliable enough to act on it.

The shift

Now · agentic execution

Doing the work

Akkari. Drafts the reply, files the bug, schedules the meeting, opens the PR, sends the customer the update when the fix ships. The job is no longer to read the summary — it's to review the action.

AI wasn't meant to just store context or summarize conversations. It should execute the work those conversations create.^[3] The model capability — Claude Sonnet 4.6 / Opus 4.7 (1M context), GPT-5, multi-step agentic tool use — finally lets a horizontal product reach across Slack, email, Linear, GitHub, and a CRM in a single coherent action. The substrate is finally there.

One of the most experienced founder teams I've come across. These guys really know GTM. I'll be following closely!

Sherwood Callaway^[3]

Founder & CEO · Sazabi (P26)

Proud to be customers! One of the fastest moving teams.

Muvaffak Onuş^[3]

Co-founder · Limrun (P26) — Akkari customer

Proud to be one of the early design partners. The guys are absolute beasts — extremely smart and experienced. Very excited to see their product grow.

Arseniy Shishaev^[3]

Co-founder · Superlog (P26) — Akkari design partner

Three preconditions converged in the same six-month window.

Complete digital record of customer work. Slack/Teams replaced email for internal coordination. Loom/Granola/Gong recorded the calls. Email APIs and webhooks turned every external touchpoint into structured data. For the first time, the entire customer surface — internal and external — is machine-readable. The data is sitting there, waiting to be acted on.

Agent reliability crossed the bar. A year ago, a multi-step agent that read a Slack thread, classified it as a bug, opened a Linear ticket with the right team and severity, and notified the customer when the PR merged — without a human in the loop — was a research demo. Today, on Claude Sonnet 4.6 / Opus 4.7 (1M context) and GPT-5, it's a production-grade workflow that the model can execute end-to-end with the right harness. Akkari's bet is that the harness is the product.

Builders feel the pain acutely now. Modern AI-native startups ship 5–10× faster than two years ago (the Sazabi thesis). The downstream effect: more shipped features → more customer commitments → more follow-ups → more operational work per founder-hour. The "outer loop" problem Sherwood Callaway named for observability has a customer-operations twin, and Akkari is the team building for it.

How It Works

Detect signal. Triage against account context. Execute the work.

Concrete loops Akkari closes today.

Pre-sales follow-through. Move a lead from a vague next step to a completed follow-up — the pricing breakdown promised on the call, the security questionnaire requested in email, the demo recording the prospect asked to share with their team — drafted, sent, and tracked.^[2]

Bug-report to merged PR. Convert bug reports and feature requests from Slack, calls, and emails into Linear tickets with the right team and severity. When the PR merges, Akkari notifies the right customers — automatically.^[2]

Onboarding unblocking. Turn onboarding blockers — missing API access, undocumented integrations, security review prerequisites — into queued action items routed to the right internal owner.

Quiet-churn early warning. Spot the silent signals — falling usage, missed check-ins, a champion gone quiet, a tonal shift in a thread — and trigger the save play before renewal becomes a fire drill.

Expansion play orchestration. Detect usage spikes and conversation signals indicating expansion readiness. Surface the open commitments, the unresolved blockers, and the buying signals into a single play the AE can run — or that Akkari can run with review.

Where signal comes from — and where action goes out

Integrations

SlackGmail / EmailCalls & meetingsDiscordLinearGitHubPostHogCRMsClaude Code / Cursor (MCP & CLI)REST API

Akkari is horizontal by design. Single-channel incumbents — a CRM AI, a ticketing AI, a meeting-notes AI — can only see one slice of the customer. Akkari sees the whole surface and closes loops across it.^[2]

The Long Arc

A living model of how a company actually operates.

Customer-operations execution is the wedge. The durable bet is the operational memory layer that compounds underneath it.

The wedge is execution today. The compound asset is the model of the customer.

Step one — close the loops. Akkari proves it can act reliably on every customer signal: commitments, blockers, bug reports, expansion triggers, churn signals. The product earns trust action-by-action; users escalate it from drafts-only to fully autonomous on the actions where it's earned the right.

Step two — build the operational memory. Every action, follow-through, and outcome compounds into a structured record of how this customer relationship actually works: who decides, what they care about, what blockers recur, what signal precedes expansion, what precedes churn. The system gets sharper customer by customer, week by week.

Step three — become predictive. Once you have a structured model of how customers operate, you can run it forward. Which deals will close. Which accounts are about to churn. Which expansion plays will land. Where the next handoff is going to break. Akkari's framing: a living model of how companies actually operate — and one that becomes predictive over time.^[3]

Akkari is our wedge towards building a living model of how companies actually operate — and one that becomes predictive over time.

— Akkari launch on Bookface^[3]

Market

Three concentric markets. Akkari has commercial signal in all three already.

Near term — YC P26 and AI-native startups. The densest concentration of the buyer is in the current YC batch: technical founders who feel the customer-operations pain acutely at 10–50 customers and have authority to switch tools in a day. Akkari is already embedded with Superlog, Limrun, Auxos, Superset, Sazabi, Standout, and Klaimee as design partners or queued to onboard.^[3]

Mid term — Seed-to-Series B B2B SaaS. Companies that have outgrown the founder-in-everyone's-DMs phase and are starting to lose deals and accounts to follow-through gaps. Hundred-engineer-or-less GTM orgs where a single VP-Sales or VP-CS can decide. The per-seat economics here are best — Akkari acts as an always-on operations layer across the entire customer team.

Long term — enterprise revenue operations and customer success. The category sitting between CRM (system of record) and meeting intelligence (system of capture) is system-of-execution. None of the incumbents own it. Salesforce, HubSpot, Gong, Outreach, Salesloft, Gainsight, Zendesk — every one of them has tried to add an "AI agent" surface. None of them ship execution across all channels because none of them sit across all the channels.

Competitive landscape

Four categories adjacent to Akkari. None of them execute across the full customer surface.

Each adjacent category has a structural limit. Akkari's horizontal, execution-first wedge is the answer to all four.

Akkari's positioning

Akkari is the horizontal AI execution layer for customer operations. CRMs hold the record. Meeting tools capture the conversation. Akkari is the system that closes every loop those records and conversations create — across every channel, for every customer, end-to-end.

Founder deep dive

Three founders. One prior YC company together. One $1B+ exchange. One thesis they earned the hard way.

The OrderAhead chapter (YC W11, founded 2012 → acquired by Square late 2016). Jeff and Henry founded OrderAhead in YC W11 — a mobile ordering and payments platform that scaled out of Palo Alto into SF, LA, Houston, Denver, Chicago, and New York and was acquired by Square in late 2016 to complement Caviar. Notably capital-efficient: $10.5M total raised from Marc Benioff, Eric Schmidt, Jerry Yang, Adam D'Angelo, SV Angel, August Capital, Matrix, Menlo, and Initialized.^[9] Michael joined as one of the first 10 employees in 2012 as an Account Executive — and rode the whole arc up to VP Sales & Operations, then stayed through the Square acquisition as Sales & Success Lead managing the merchant integration. At peak he was managing a 30-person GTM team and 2,500 contractors.^[4]^[5]^[6]^[7]

The lesson from OrderAhead — said in their own words. "At both companies, we learned that customers are won or lost in the follow-through that begins with the first conversation. The best teams do not win just because they have better product or better messaging. They win because they follow through faster, more consistently, and with better judgement than everyone else."^[3] This is not a thesis they read about. It's the lesson they extracted from building one of the YC alumni cohort's most operationally complex GTM organizations and watching dozens of competitors die because they couldn't keep up with their own commitments.

The BLADE chapter (2018–2023). Jeff and Henry started BLADE Holdings, a crypto derivatives exchange backed by Coinbase, SV Angel, Slow Ventures, Justin Kan, and Adam D'Angelo. They scaled to $1.2B+ in monthly trading volume — an environment where operational rigor and customer trust are literally the product. Jeff started his career as a credit derivatives trader at Morgan Stanley; the operational discipline of finance is in his bones.^[5]^[6]

Why this is the team for this problem. Most teams attacking customer ops have either GTM pedigree or technical pedigree — rarely both, almost never with prior operating experience at the same company. Jeff and Henry have shipped two companies together (one acquired, one $1B+ TVL). Michael has run the customer-ops function at every scale from 10 to thousands. They're not learning the problem; they're building the product they spent two companies wishing existed.

The angel list is a recommendation letter. Fidji Simo (CEO, OpenAI Apps), Tony Xu (DoorDash CEO), Eric Wu (Opendoor CEO), Othman Laraki (Color CEO), plus Liquid 2 and Tuesday Capital.^[2] Every name on the list ran the exact problem at massive scale: DoorDash on marketplace ops, Opendoor on transactional follow-through, Color on healthcare account management, OpenAI Apps on the next-generation execution layer. They're not investing in a deck; they're investing in the team they wish they'd had.

How they run the playbook. Tight design-partner cycle inside P26 — Superlog, Limrun, Auxos, Standout, Klaimee, Superset, Sazabi.^[3] Founders directly in the customer Slacks. Public, opinionated launch with a clean wedge-and-vision split. The same "follow through faster, more consistently" rigor they're selling, applied to their own GTM. The compounding starts at the founder loop.

Founders

Jeffrey Byun

Repeat FounderExited

Co-founder & CEO

2x YC founder (W11, P26). Previously co-founded OrderAhead (W11) — a mobile ordering platform that scaled to millions of users and thousands of merchants before being acquired by Square. Then founded BLADE Holdings, a crypto derivatives exchange backed by Coinbase, SV Angel, Slow Ventures, Justin Kan, and Adam D'Angelo, which reached $1.2B+ in monthly trading volume. Started his career trading credit derivatives at Morgan Stanley. MIT and University of Pennsylvania.

Henry A. Lee

Repeat FounderExited

Co-founder

Co-founded OrderAhead (W11) as CTO with Jeff — acquired by Square. Then CTO/co-founder at BLADE. Earlier engineer at Increo Solutions (acquired by Box). Stanford CS. Deep technical operator across two prior YC companies with Jeff.

Michael Moore

Repeat FounderExited

Co-founder

Joined OrderAhead in 2012 as one of the first 10 employees and grew with it through acquisition — Account Executive → Manager (Merchant Growth) → Head of Sales & Success → VP Sales & Operations → Sales & Success Lead at Square post-acquisition. Managed a 30-person GTM team and 2,500 contractors at peak. Later COO at PlayVision and VP of Operations at Sittercity. UNC Chapel Hill. Has lived the customer-operations problem from the inside at every scale.

Risks & mitigations

Risk

Execution accuracy — when an AI sends the wrong follow-up to a customer, the cost is a damaged relationship, not just a wasted token.

Mitigation

The team treats every action as either review-required or fully autonomous on a per-customer, per-action basis. Drafts vs. sends, files vs. resolves, alerts vs. acts. The product is built around the assumption that trust accrues action-by-action and is calibrated by the user — not granted up front. Founder pedigree at OrderAhead and BLADE (where customer follow-through was the whole business) means they understand the cost of getting this wrong better than anyone.

Risk

Slack, Linear, Notion, Salesforce, HubSpot, or another incumbent ships a native version of this and absorbs the market.

Mitigation

The wedge is horizontal-by-design: Akkari sits across Slack, calls, email, Discord, Linear, GitHub, PostHog, and CRMs simultaneously. Single-system incumbents can't credibly close the loop across the whole customer surface because each is locked to its own channel. The defensible product is the cross-channel memory and the act-on-the-customer execution layer — neither of which sits naturally inside a CRM or a ticketing tool.

Risk

ICP discipline — "customer operations" is broad. The pull is showing up in sales, success, support, and PLG conversion. Spreading thin is the obvious failure mode.

Mitigation

The team is running a disciplined design-partner motion across P26 (Superlog, Limrun, Auxos, Standout, Klaimee, Superset) with weekly check-ins. They're seeing pull across sales, success, and PLG and explicitly choosing to keep the surface horizontal during the wedge phase — because the operational pain is the same regardless of which team owns it. Tightening the ICP becomes a Series A problem; right now the discovery is the moat.

What we're watching

Conversion of design partners (Superlog, Limrun, Auxos, Standout, Klaimee, Superset) into paid contracts post Demo Day — and how fast the first non-YC paid logo arrives.
ICP focus — does the team lean further into one of (founder-led sales / customer success / PLG-to-enterprise conversion), or do they sustain the horizontal customer-ops wedge?
Where execution accuracy lands in production — false positives on commitments, sent-without-review actions, and how quickly the trust loop with customers tightens.
Whether the founders use Akkari's own operational memory layer to build a self-improving, predictive model of how their customers actually operate — the long-arc bet.

References