CuspAI
Use case 01 · Rahul Sharma, Bengaluru

One person, four interests,one working answer.

The whole journey, start to finish — what Rahul types, what CuspAI shows him, and what he had built by Sunday.

4
topics typed
1
open per day
9
items kept
1
weekend to ship
AI toolsEmerging techModel releasesIndian AI fundingPrices in ₹Audio verdictsRefusal ListAI toolsEmerging techModel releasesIndian AI fundingPrices in ₹Audio verdictsRefusal List
01Signing up

Rahul picks what he actually cares about.

Rahul Sharma, 29, builds product at a Bengaluru fintech. On his first screen he does not choose a plan or a persona. He types what he follows — AI tools, emerging tech, model releases, funding in Indian AI — straight into the chat bar.

No checkboxes, no twenty-question onboarding. CuspAI reads the sentence, shows him the topics it heard, and lets him strike out the ones it got wrong.

  • Setup: under 60 seconds
  • Topics: 4 typed, 0 chosen from a list
CuspAI's first screen: “What do you want to keep up with?”, with the field and interest topics offered as chips and four already picked.
The first screen. Your field and your interests, picked in one pass — and every item CuspAI later shows names which of them it came from.
02The first open

What lands is people and tools, not volume.

Next morning Rahul opens CuspAI once. He gets the leading people worth reading on those four topics, the tools that shipped something real, and one line on what each is actually good for — plus what it costs in rupees.

Anything that only made noise is missing on purpose. If a tool paid us and still failed, it goes on the Refusal List with the reason attached.

  • Reads: 1 per day
  • Items: 9 kept, 214 dropped
The CuspAI reading surface: the topics being read across the top, then four items for the day, each with its source, its read time and the reason it surfaced.
The surface after sign-in. The day is dated and counted — four items, each naming its source, its length and the reason it reached you.
03The chat box

"Build me a website — what should I use?"

The chat box is always there. Rahul asks a loose question and CuspAI does not answer it blindly: it rewrites his prompt with the context a good answer needs — his stack, his budget, whether he wants to host it himself — and shows him that better prompt before it runs.

He edits one word, sends it, and gets a shortlist of four tools in the order he should try them, with what each will cost him per month.

  • Prompt rewritten: 1 tap
  • Answer: 4 tools, ranked, ₹0–₹1,29,000/yr
A stack CuspAI built from a one-line ask, split into a free track and a paid track, each tool showing its role, its cost and why it earned the slot.
The answer to one typed line. A free track and a paid track for the same outcome, every tool carrying its role, its cost and the reason it's there.
04The week after

He ships the site and keeps the loop.

Rahul builds the site over a weekend using the top two tools on that list. On Wednesday, CuspAI tells him one of them shipped a change that affects his setup — and what to do about it in two sentences.

When he is walking, he plays the audio version of the same thing. Same verdicts, no extra tab.

  • Time to ship: 1 weekend
  • Tabs open: 3
A single CuspAI item opened: headline, source, read time, the reason it surfaced, then a condensed read of the argument.
One item, opened. The reason it reached you stays attached to the piece — and once it's read, CuspAI doesn't show it to you again.

Your version of Rahul's week starts here.

Tell us what you follow. We'll tell you what's worth your evening.

Or read how it works first.