Cluely Founder: Public Record and Company Timeline

The available first-party material does not let us responsibly name a Cluely founder or reconstruct the founders’ biographies. The company pages reviewed in August 2026 describe the product in detail, but they do not establish founder names, current executive titles, or historical roles. Search snippets and copied biographies cannot fill that gap.

Who founded Cluely?#

The reviewed source set does not provide enough evidence to identify Cluely’s founders by name.

That is the concise answer supported by the record available for this article. Cluely’s home page, pricing page, download page, mobile page, manifesto, undetectability page, and sitemap focus on the product. None of the reviewed material supplies a dated statement such as “founded by,” followed by names and roles.

This distinction matters because founder claims often travel without their original context. A search result may call someone a founder, cofounder, chief executive, or former executive. Those labels are not interchangeable.

A reliable founder record should establish three separate facts:

1. Identity: The person’s full name.
2. Historical role: The title held when the company began.
3. Current role: The title the person holds at the date of the source.

One source may establish only one of those facts. A current company biography could confirm a present title without proving an original role. An early announcement could identify the Cluely cofounders without showing who still works there.

The source should also have a visible publication date. An undated biography can change silently. A search snippet can preserve old wording after the underlying page changes. A copied profile can repeat another article’s mistake.

No dated Cluely founder interview was included in the reviewed materials. Without one, it would be speculation to attribute an origin story, division of responsibilities, or private motivation to any individual.

The defensible conclusion is narrow: Cluely publishes substantial product information, but the first-party pages reviewed here do not establish its founder history.

Cluely's founding timeline#

A complete Cluely timeline cannot be built from the reviewed pages, but the product’s public position in August 2026 can be documented.

A company timeline should begin with the earliest dated primary source. That might be an incorporation record, launch announcement, founder post, archived home page, or company newsroom entry. None of those founding documents appears in the source set available here.

What can be preserved is the public product record from August 2026.

August 2026: Cluely presents itself as a meeting assistant#

Cluely’s home page described an AI assistant for live calls. According to that page, it listens while a call happens, takes notes without a separate prompt, responds through a Cmd or Ctrl + Enter shortcut, and produces a recap with follow-up questions after the call.

The wording places meetings at the center of the product. The named integrations were Zoom, Slack, Webex, Microsoft Teams, and Google Meet.

That is a product-positioning milestone, not a founding milestone. It tells you how Cluely described itself at that date. It does not tell you when the company started or who occupied each early role.

August 2026: Desktop and mobile availability is documented#

Cluely’s download page listed a desktop application for macOS and Windows. It specified macOS 10.15 or later on Apple Silicon or Intel, along with Windows 11.

An App Store listing identified an iPhone application called “Cluely: AI Notetaker,” published by Cluely Inc. The listing classified it under Productivity and required iOS 17.0 or later.

These records support a distribution timeline. They do not establish a corporate founding date.

August 2026: Public pages remain meeting-led#

Cluely’s mobile page used the heading “AI meeting notes on the go.” It listed interviews alongside other situations such as coffee chats, lectures, therapy sessions, doctor visits, client calls, dinners, and notes to self.

The company’s sitemap listed 24 pages. None was a dedicated interview page or coding page. Its manifesto referred to sales calls, meetings, and negotiations. Its published comparison articles addressed Granola and Otter.

This wording matters for an interview shopper. It shows that interviews appeared as one use case within a broader meeting product. It does not show a dedicated technical-assessment workflow.

The dated Cluely product overview carries the checkable side-by-side product comparison. It is a better place for changing plan and feature details than a founder-history article.

What remains absent#

The reviewed record does not establish:

• A founding date.
• The names of the original founders.
• Historical titles held by those founders.
• Changes in executive responsibility.
• A dated launch sequence before August 2026.
• A founder account explaining why the company was created.

Those gaps should remain gaps until a primary source resolves them.

What the founders say Cluely does#

No founder statement was available, so the product description must come from Cluely’s company pages rather than from unnamed founders.

Attributing company copy to “the founders” would overstate the evidence. A home page represents the company’s published position. It does not necessarily reveal who wrote or approved each sentence.

Cluely’s current public description is consistent across the reviewed pages: it is a meeting assistant that listens during conversations, takes notes, uses call and screen context, provides shortcut-triggered answers, and creates post-call material.

Its undetectability page makes two direct claims:

“never joins your meetings, so there are no bots and no extra people on the guest list”

It also says the application:

“never shows up in shared screens, recordings, or external meeting tools”

Those are Cluely’s own statements. They should be quoted as such. They are not independent findings about what any named meeting or assessment platform can detect.

Cluely also publishes concrete transcription, response-time, and language specifications on its home page. Publishing measurable specifications is more useful than relying only on adjectives. This article does not independently validate those specifications.

For technical interviews, the documented omissions are more important than broad positioning:

• The reviewed pricing page did not use the words interview, coding, or assessment.
• The undetectability page named meeting products, not assessment platforms.
• No reviewed page named CoderPad, HackerRank, CodeSignal, or LeetCode.
• The pricing page referred to access to current AI models but did not identify models by name.
• Nothing reviewed described returning a compiling solution with a step-by-step explanation and time and space complexity for a problem displayed on screen.

That last point is a statement about the documentation. It is not a claim that the application could never support another workflow.

Cluely does document a useful after-call workflow. Its pages describe notes, a recap, and follow-up questions. A tool designed around a live coding problem serves a different job. You should compare the documented workflows rather than treating every assistant that can hear a call as interchangeable.

How to verify claims about a startup founder#

Start with dated primary records, then use full interviews and reputable reporting to resolve context.

Use this evidence order:

1. Official records and first-party announcements. Look for company filings, launch posts, newsroom announcements, and dated company biographies.
2. Full founder interviews. Prefer a complete recording or transcript over an edited clip.
3. Reputable reporting. Check whether the publication conducted original reporting or merely repeated a company statement.
4. Secondary profiles. Use them as leads, not final proof.
5. Search snippets and social summaries. Treat them as navigation aids only.

A small claim ledger prevents weak sources from turning into confident prose:

Publication dates need scrutiny. A page can display a recent update while retaining old claims. Record both the original publication date and the latest update date when available.

Archived pages help with silent changes. Save:

• The page title.
• The full URL.
• The capture date.
• The exact sentence supporting the claim.
• The person or organization publishing it.

Then trace citations backward. If one biography cites a news article, and that article cites another profile, neither is independent confirmation. Continue until you reach the original interview, announcement, or record.

Also separate direct quotation from paraphrase. Quotation marks mean the words appeared in the source. A paraphrase means the writer interpreted them. Third-party characterizations should be labelled clearly.

Founder profile versus product evaluation#

A founder biography does not establish whether a product fits your interview workflow.

A compelling origin story cannot tell you whether an application runs on your operating system, supports your task, or explains an answer you need to defend aloud. The reverse is also true. Sparse founder information does not prove that a product is poor.

Evaluate checkable product criteria separately:

• Application format: desktop application, browser tool, mobile application, or another form.
• Operating-system support: exact supported systems and minimum versions.
• Stated workflow: meetings, interviews, coding tasks, notes, or post-call follow-up.
• Input handling: audio, screen context, screenshots, or typed prompts.
• Output: notes, answers, code, explanations, complexity analysis, or follow-up questions.
• Named integrations: the specific meeting or assessment tools listed publicly.
• Model disclosure: whether the plan names the models you receive.
• Public documentation: whether limitations and requirements are available before purchase.
• Screen-sharing statement: what the product itself documents, without turning that statement into a claim about a platform’s private integrity systems.

Cluely’s documentation makes its meeting orientation clear. It also documents desktop and mobile availability and an after-call notes workflow. Its reviewed pages do not document a coding-problem workflow or name assessment platforms.

By contrast, Stealth Interview documents a macOS and Windows desktop application that reads a coding problem from a screenshot, returns a working solution, explains the steps, provides time and space complexity, and transcribes interviewer audio. That difference in documented purpose is more useful than a founder-profile comparison.

Use the Cluely overview for the sourced product comparison. For platform-specific research, consult the proctoring reference, which separates each platform’s own documentation from product claims. Neither page promises what a platform’s private systems will or will not detect.

Sources and unresolved questions#

The source record supports a product snapshot from August 2026, not a verified founder biography.

First-party materials reviewed:

1. Cluely home page, August 2026. Product positioning, live-call workflow, shortcuts, meeting integrations, and published performance specifications.
2. Cluely undetectability page, August 2026. Statements about joining meetings, shared screens, recordings, and external meeting tools.
3. Cluely download page, August 2026. macOS and Windows requirements.
4. Cluely mobile page, August 2026. Mobile positioning and the list of conversation contexts that includes interviews.
5. Cluely pricing page, August 2026. Plan structure and public model wording.
6. Cluely manifesto, August 2026. Positioning around sales calls, meetings, and negotiations.
7. Cluely sitemap, August 2026. The public page inventory reviewed for dedicated interview or coding pages.
8. Cluely blog pages, August 2026. Published comparisons involving meeting-note products.

Additional public listing reviewed:

9. App Store listing for “Cluely: AI Notetaker,” August 2026. Publisher name, category, and iOS requirement.

Unresolved questions include:

• Who were the original Cluely cofounders?
• What titles did they hold at formation?
• What titles do they hold now?
• When was the company founded?
• When did the first public product launch occur?
• Is there a complete, dated Cluely founder interview?
• Did the company’s positioning change before August 2026?
• Are earlier versions of the home page preserved in an archive?

No answer should be inferred from the product copy alone. Company roles can change. Product descriptions can change. A future first-party announcement or archived page may resolve the missing history, but it should be dated and checked before the Cluely company history is rewritten.