ReadSearch

Research intelligence for people who cannot afford to miss it.

FounderPeter Salame
ProductReadSearch.ai
StagePre-seed
DateAugust 2026
The problem

The paper you needed was published last Tuesday.

Open access solved availability. It did not solve discoverability. Roughly three million research articles are published every year, and the number climbs annually.

Every sheet is a paper. One of them was written for you.

What it costs

Missing it is not neutral.

Clinician
A treatment plan that could have changed.

A physician finishing a full day of patients cannot track the literature relevant to their practice. The finding that would have informed a diagnosis goes unread.

Researcher
Months spent on a question already answered.

Duplicated effort is the quiet tax on every lab. Work published in a neighbouring field six months ago stays invisible until it is too late to matter.

Engineer & analyst
A decision made without the best evidence.

The method that halves your compute, the material that solves your failure mode, the model that outperforms yours. All published, none surfaced.

Why now

Three curves met this year.

Supply
Open access reached critical mass.

Free, machine readable, no gatekeeper.

Cost
Summarisation fell to fractions of a cent.

Dollars per paper two years ago.

Behaviour
Listening became a default habit.

Long form audio already fills the commute.

Now 72% margin at $3.99
The solution

ReadSearch pulls the three that matter. Every morning.

We read the world's research continuously, score every paper against the specific context of your work, and keep only what is genuinely relevant. A digest you can read in ten minutes, or a briefing you can listen to on the way in.

Everything else, you never have to see.

How it works

A pipeline, not a chatbot.

Eight sources, deduplicated by DOI with merge rather than drop, ranked by per-domain calibrated profiles, summarised once and shared.

What makes it defensible

One engine. Every field. No forks.

The architecture
Specialisation comes from configuration, not codepaths.

Recommendation behaviour is fully specified by per-domain profiles. Cardiology, condensed matter physics and macroeconomics run through the same ranked pipeline with different calibration. Adding a field is a data change, not an engineering project, so coverage compounds while cost does not.

Against the alternatives
Keyword alerts are noise. Vertical tools are one field deep.

Scholar alerts fire on string matches and get ignored within a month. Single-vertical products serve one audience and cannot cross the boundary where the most valuable findings usually sit. ReadSearch is broad and precise at once, which is only possible because the engine is parameterised.

Market

Everyone whose decisions depend on being current.

Active researchers
worldwide
Practising
physicians
R&D staff
in industry
Annual revenue
per user

Entry is bottom-up and consumer priced, which removes the procurement cycle entirely. Expansion runs upward into team seats, institutional licences and an API tier, where the same engine sells at materially higher price points. Population figures are working estimates, to be validated.

Business model

$3.99 a month.

Revenue from user one
Every signup is a paying signup.

No subsidised cohort, no conversion funnel to fix later, and no ambiguity about whether the product is worth paying for.

Shared compute
Generated once, served to many.

Summaries and audio are produced per topic-set and per paper, then served to everyone following those topics. Adding a user to an existing cluster costs close to nothing.

Expansion
Three paths already open.

Annual plans that cut payment fees and lift retention, team and institutional seats, and an API or alerts tier for embedded use.

Measured unit costs  ·  production, not estimates

Three units. Three drivers.

UnitCostWhat drives it
One carousel$0.0013Distinct papers. Cached forever, shared globally.
One episode$0.0275Distinct topic-sets × 30 days. Twenty-four hour cache.
One search parse$0.0010Queries per user.

Measured against 56 real cached carousels and a verified production episode build on 15 August 2026: 1,641 characters, 105 seconds. The episode figure replaces an earlier estimate that was 64% too high, because it carried an old text-to-speech rate we no longer use.

Unit economics  ·  per user per month at one thousand paying users
LinePer userBasis
Revenue$3.99Single tier, monthly
Payment processing($0.42)2.9% + $0.30, exact
Audio briefings($0.46)555 topic-sets × 30 days × $0.0275
AI summaries($0.15)~117k distinct carousels × $0.0013
Search parsing($0.02)~15 structured queries per user
Infrastructure($0.20)Itemises to $0.12. Pad retained.
Gross profit$2.7469% gross margin
Payment 10.4%Audio 11.5%AI 3.8%Search 0.5%Infra 5%Gross profit 69%
What the margin hinges on

One number moves everything: users per topic-set.

Optimistic  300 sets, 60% overlap
Central  555 sets, 30% overlap
Pessimistic  unique per user, no overlap
Stated plainly

Audio cost scales with distinct topic-sets, so clustering is the entire margin story. Today's ratio of 1.8 users per set comes from nine seeded accounts on a legacy nine-topic picker; the live taxonomy now exposes 144 followable leaves, so early diversity will run worse and push toward the downside row. The 30% overlap assumption is modelled, not measured. Even at the floor the business clears 53%, and annual billing removes most of the payment drag, which is the largest single cost at this ticket.

Lifetime value  ·  targets
Gross margin,
measured
Target lifetime,
months
Lifetime value
per user
Target CAC,
a 3× ratio

At a $3.99 ticket the acquisition channel has to be cheap by construction, so growth is built around organic and content-led distribution rather than paid performance. Annual billing is the primary margin lever: it removes most of the payment-fee drag, lifts retention, and pulls a year of cash forward per user.

Why we are building this

Somewhere in today's research is the paper that changes how you work. It exists. It is published. The odds you will ever see it get worse every year.

We are building the thing that puts it in front of you, while it can still make a difference.

FounderPeter Salame
Emailpetermsalame@outlook.com
ProductReadSearch.ai
Click or press →