All teardowns
Teardown · 9 min

Cluely, under the microscope: viral, then what?

Almost no AI product has bought more attention for less money than Cluely. A suspension, a dropout story, a "cheat on everything" tagline, and an a16z Series A turned two founders into the most-talked-about consumer AI startup of the cycle. The marketing was a masterclass. The question we kept asking is the one the marketing was built to keep you from asking: what is actually under there?

We took Cluely into the Lab — the GPU overlay, the real-time assistance, the soft pivot to "meeting assistant" — and looked at it the way we'd look at any product a founder asked us to build. Here's where it's clever, where it settled, and how we'd rebuild it into something with a reason to exist in two years.

CluelyReal-time AI overlayTeardown · 9 min
01 · The premise

Cluely started life as Interview Coder: a tool that watched a coding-interview screen and fed answers back through an overlay invisible to the interviewer. After the founders were suspended and dropped out of Columbia, they reincorporated as Cluely, raised around $5.3M within weeks, and later took a reported $15M Series A from a16z. The product generalized: real-time assistance for sales calls, interviews, exams, and meetings, rendered through a GPU-level overlay (DirectX on Windows, Metal on macOS) that doesn't appear in Zoom, Meet, or Teams screen-shares.

We picked it because it's the purest example of a pattern we're asked about constantly: a product that goes viral on positioning, raises on momentum, and then has to answer whether there's a durable product underneath the moment.

02 · What they got right

The growth engine is the product, and it worked. Turning a suspension into a "cheat on everything" campaign generated national coverage and a flood of sign-ups for a fraction of normal CAC. Founders pay us to think about distribution; Cluely solved distribution before it solved much else, and that ordering is not always wrong.

The core technical insight is also real. The invisible overlay — assistance that lives on top of any app and stays out of the screen-share — is a genuinely useful primitive. Real-time, context-aware help during a live conversation is a category, not a gimmick. And the soft pivot toward "meeting assistant" shows the team can read the room when the original framing starts costing them enterprise trust.

If the question is "can two people manufacture attention and a usable demo," the answer is clearly yes.

03 · Where they settled

Here's where the trade-offs land — and most of them land on trust.

It's a thin wrapper, and thin wrappers get absorbed

Strip the overlay and the core is a prompt over a frontier model. Reviewers describe it as another AI chat wrapper whose main differentiation is persistence across a call. The structural risk: the platforms it sits on top of are shipping the same capability natively. Once ChatGPT-style "listening mode" is built into the assistant people already pay for, a standalone overlay has to justify a second subscription. That's a hard sell.

Invisible-by-design is a trust liability, not just a feature

The thing that makes Cluely useful in an interview is the thing that makes it radioactive in enterprise: software explicitly engineered to be undetectable by the other party. That forecloses the highest-value market (sanctioned, in-the-open sales coaching and support) at the exact moment the team is trying to pivot toward it.

Always-on friction

Users report the global keyboard shortcuts interfere with other apps and can't be turned off cleanly, so leaving it running outside a meeting is actively annoying. A product that's irritating when idle doesn't earn a permanent slot on anyone's machine.

No defensible memory layer

Real-time suggestion without durable, structured recall across conversations means there's nothing compounding. The moat in this category is the accumulated context, not the overlay — and that's the part Cluely under-built.

04 · The rebuild

We'd keep the overlay primitive and the real-time instinct, and rebuild everything around trust and defensibility. The goal: a product that wins the sanctioned market and compounds over time, instead of one that wins a news cycle.

1. Flip invisible to consent-aware

Default to a visible, disclosed assistant for the enterprise market, with a clear "assistance active" state. You trade the interview-cheating use case (a liability) for the sales-and-support market (a business).

2. Build the memory layer that's missing

Every call writes structured notes, entities, and outcomes to a per-user / per-account store. Suggestion quality compounds as the system learns the rep, the deal, and the customer. That's the moat.

3. Route models by job

Job in the loopCandidate modelEst. latencyEst. cost / 1k turnsWhy
Live "next question" promptsSmall / fast tier~0.4–0.9s~$1–$3Must feel instant in-call
Post-call synthesis / summaryMid frontier~2–4s~$8–$18Quality; latency irrelevant
Rare deep research / objectionTop frontier~3–6s~$30–$55Only when the rep asks

Planning-stage estimates, not a benchmark. A real-time product can't afford to route every suggestion through a slow, expensive model. Tiering is where in-call responsiveness and margin both come from.

4. Make it pleasant when idle

Configurable, scoped shortcuts; a real "off" state; no hijacking of other apps. Earn the permanent install.

05 · The 6-week plan

What we'd cut, and how we'd ship it.

Week 1

Repositioning & scope

Lock the sanctioned use case (sales / support coaching), cut the cheating-adjacent surface that blocks enterprise.

Week 2

Consent-aware overlay

Rebuild the overlay with a visible active state and clean idle behavior.

Weeks 3–4

Memory layer

Structured per-account store, write-back from each call, retrieval into the live context assembler.

Week 4

Model routing

Fast tier in-call, frontier post-call, per the table.

Week 5

Post-call analytics

Summaries, action items, CRM sync — the part that makes it a system of record, not a toy.

Week 6

Eval & polish

Suggestion-quality eval set, latency budget enforced, ship.

06 · The verdict

Twelve months out, we'd bet the overlay category survives and Cluely-the-overlay doesn't — at least not as a standalone consumer subscription. The capability gets absorbed into the assistants people already pay for, and the brand's viral, edgy origin becomes a liability in the enterprise market that's actually willing to pay.

The team clearly has the distribution instinct most founders lack. If they spend the runway building the consent-aware, memory-backed version — and let go of the use case that made them famous — there's a real company here. If they keep optimizing for the next viral moment, they're renting attention they can't keep.

Viral is a start. It is not a moat.

FAQ

Because Cluely is designed to be invisible to other call participants, using it in sanctioned settings is a policy question, not just a technical one — and it's exactly why the product struggles to win enterprise trust.

At its core it's a prompt over a frontier model delivered through an overlay. The overlay is the real innovation; the assistance itself is increasingly replicable by the platforms it runs on.

Native "listening mode" in the assistants users already pay for. A standalone overlay has to justify a second subscription against a free, built-in alternative.

A compounding memory layer — structured recall across every conversation — plus a consent-aware design that opens the enterprise market. Suggestion alone doesn't compound.