AI Toolbox

Organize, find and export conversations across supported AI chat websites.

Freemium extension + subscriptions + lifetime licensesProductivity
Visit website
Reported revenue> $10,000Monthly revenue · Unspecified $More than 10,000 in trailing 30-day revenue; the July 2026 article was later corrected by the founder in its comments; exact financial window unspecified.Original disclosure
Business modelFreemium extension + subscriptions + lifetime licensesProductivity
Profile depthResearched profileProduct facts and editorial breakdown
Source checkedOct 20, 2026Observation date, not revenue cutoff

Business overview

Public positioning

Organize, find and export conversations across supported AI chat websites. The July 2026 first-person interview identifies Adi Leviim and Mohammad El-Esawi as the two builders and describes operation without contractors or investment at launch. This is a dated operating account, not a current audited staff count.

How it makes money

Free usage limits with per-platform Premium, an All Access lifetime bundle and team seats.

Business breakdown

Researched Oct 20, 2026

Source-linked product facts, followed by MRRTrace analysis of the customer problem, workflow, trade-offs and questions to test.

The customer problem

The official product places folders, search, saved prompts and export inside several AI chat websites. Editorial interpretation: the paid problem is recovering and reusing earlier work when a person changes tasks or assistants. Observe an actual lost-conversation episode before choosing features. Record what the user remembers, which site they search first and how much time they spend repeating an answer. That observation can reveal whether the smallest useful product is retrieval, organization or an export that fits another working tool.

Core workflow

  1. Install the extension and open a supported AI chat website using the existing service account.
  2. Organize conversations, search earlier messages or select a saved prompt relevant to the task.
  3. Export selected work and check that the resulting format supports the destination workflow.

What customers pay for

Editorial analysis: measure successful retrievals and useful exports per returning user, alongside the support time each paid customer requires. Separate monthly subscription renewals from new lifetime-license sales before projecting future support capacity. A burst of one-time purchases can finance development without demonstrating durable recurring demand. Compare a focused single-platform offer with a cross-platform bundle through actual adoption and repeat use. Do not assume that someone who installs on four sites obtains four times the value or will pay four times the price.

Distribution signals

Observed channels and entry points; their performance is not inferred.

  • Existing extension marketplace

    The founder interview describes the Chrome Web Store as an acquisition route and support-led improvements as part of that process. It does not independently isolate the causal effect of ratings or any single feature on sales.

    Evidence

Trade-offs

  • Editorial risk: embedding directly in a familiar interface can reduce setup effort while creating a continuing compatibility obligation. Budget representative checks after host updates before expanding into more platforms.
  • Editorial risk: an attractive lifetime offer converts a purchase today into a future service obligation. Test whether upgrade income and retained reserves can cover maintenance even during a slow sales month.

Open questions

  • Which retrieval or export task creates repeat value after the first organization session?
  • How much maintenance and support is required for each additional host platform?

A MRRTrace reading of public product material. Trade-offs and questions are editorial analysis.

Revenue evidence

Founder disclosure
> $10,000Monthly revenue · Unspecified $ · More than 10,000 in trailing 30-day revenue; the July 2026 article was later corrected by the founder in its comments; exact financial window unspecified.
Reporting period
More than 10,000 in trailing 30-day revenue; the July 2026 article was later corrected by the founder in its comments; exact financial window unspecified.
Figure as of
Not provided
Reporting method
Founder disclosure
Source checked
Oct 20, 2026
Source published
Jul 23, 2026

The interview headline and body label the result MRR, but Adi Leviim explicitly corrects this in the article comments: most revenue is one-time lifetime purchases and he tracks trailing 30-day revenue. Store the disclosed threshold as Monthly revenue, not recurring MRR. The correction has no exact visible date. Currency code and reporting cutoff are unspecified; this is unaudited historical income, not profit.

July 2026 founder interview and author metric correction
This historical disclosure is separate from any current Stripe connection shown on this page. MRRTrace has not audited the business. Revenue is not profit, and historical figures are not current earnings guarantees.

Official pricing shows $9.99/month or $99 lifetime for a module, $199 All Access lifetime, and team pricing from $12/seat/month billed annually with a two-seat minimum; dollar currency code unspecified.

The source page may change its prices, limits, or offer after the recorded check date.

What founders can learn

Editorial notes

Study a narrow organizational layer inside an established daily workflow, while budgeting for host-interface changes and lifetime-license support.

Before you build something similar

  • Host websites can change without notice and break extension behavior.
  • Local search and the product privacy policy do not imply every export or summary is processed entirely on the device.
  • Lifetime receipts finance ongoing maintenance; the reported infrastructure bill does not include all labor, tax or business expenses.

These are MRRTrace observations, not statements by the founder or proof of a repeatable outcome.

Source material

3 sources
  1. July 2026 founder interview and author metric correction Public source · Checked Oct 20, 2026
  2. Official product and workflow Public source · Checked Oct 20, 2026
  3. Official current pricing Public source · Checked Oct 20, 2026