The Unread Pile — Edition No. 3

Saturday, 26 September 2026 · MumbaiEdition No. 325 posts · 1 flagged essay

Lead Feature · The essay you flagged

The AI Assistant is Finally Here. Notes from the Start of the Cycle

By Harsha Kumar, Partner, Lightspeed India · via LSIP Substack

The consumer AI-assistant cycle has finally started — because the technology finally works. After a year spent meeting founders building assistants, Harsha Kumar argues the no-brainer product was always the obvious one: not a chatbot that answers, but an assistant that acts. The market is behaving like she’s right. What follows are her notes on where the moats are and are not, which wedges work for India, and why the family — not the individual — may be the ideal customer.

A pen and notebook — notes from the start of the cycle — Field notes, not a thesis: a year of founder meetings distilled into one essay.

$50M→$2.5B

Instinct’s valuation sprint, Apr–Aug

~$1B

Town’s reported raise, nine months from prototype

100M

Messages Poke crossed in 3 months, Mar–Jun

Monthly users on Equal AI’s call screening in India

The market is behaving like a cycle has begun

Instinct repriced from a $50M round in April to a $2.5B valuation by August — without a public launch or even a price. Town is reportedly raising ~$1B. In India, M raised ₹102 Cr (~$12M) pre-product, and Equal AI reports a million monthly users on call screening alone. Every lab is in the race: a ChatGPT lifestyle app store, Gemini reading your Gmail and Photos, Meta AI inside WhatsApp, SpaceXAI’s Grok Bot, a new Siri on the way. The money is not debating whether assistants matter; it is fighting over who becomes the default.

The valuation sprint — assistant startups, 2026

Figures from Harsha Kumar’s essay. Poke: launched March, 100M messages by June, acquired in July.

Why 2015–17 failed — and why this time differs

The last cycle — Magic, GoButler, Fin, Facebook M — ran on a single bet: humans do the work while the software learns and takes over. It was a good story and a bad match for the technology. That era’s machine learning learned one narrow task from thousands of examples, while consumer requests were thousands of tasks with a handful of examples each. Automation covered the repetitive slice; humans kept the rest. So cost grew with every user, and the price exceeded what users would pay. This time the models can actually do the long tail of tasks, which flips the unit economics from “human-supported software” to “software-supported human” — or just software.

A shelf of old books — the previous cycle — The 2015 playbook, shelved: humans did the work while software promised to learn. It never did.

2015 vs 2025 — what broke, what changed

Diagram after Kumar’s 2015-vs-now framing.

“The ability to raise funds may in fact be a short-term moat.”— Harsha Kumar, on why Instinct is raising more than anyone to run the best model on everything

The two takeaways that reframe the product

Takeaway 1: human-assisted AI survives only at the ultra-premium end — executives who won’t spend time giving context, exclusive services like exotic destinations, impossible restaurant tables, front-row seats. For everyone else it’s AI over WhatsApp or a call with no human intervention. Human-in-the-loop becomes a premium feature, not a crutch. Takeaway 2: the personal-vs-professional assistant distinction collapses. One entry point, with data silos behind it — work vs personal, sales vs financial data. The assistant is singular; the contexts are many.

The economics are brutal and weird

The parts users love cost the most. Remembering everything means indexing every email and message as it arrives; being proactive means inference running in the background. Quality tracks model spend: the same product on a cheaper model is visibly worse. Founders are subsidising acquisition today, which puts viable consumer economics 1–2 years out. Instinct’s bet is explicit: raise more than anyone, run the best model on everything, let brand and habit set in before the bill comes due.

There is no data moat — except one

Your messages live in WhatsApp; a competitor can pull the same history in minutes. Raw data is not a moat. The only data moat is derived context — things the assistant learned on its own platform: that you hate aisle seats, how you write to your boss versus your spouse. The real moat is brand and habit, with a thin head start from ingesting everything within the first weeks.

The moat stack — what actually compounds

Diagram after Kumar: “The only data moat is derived context.”

The labs own the default — for now

Nine in ten consumers try their general assistant first; fewer than one in ten ChatGPT users ever visit another provider. The labs also set the price: ChatGPT costs $20 while a startup paying the same labs for hard tasks must charge $50. The window is that OpenAI’s agent features haven’t landed and it still doesn’t ask for the email/calendar access that makes an assistant useful — but, as Kumar notes, the window closes daily.

Speed matters more here than anywhere

Without moats, the assistant is a commodity, so the market is already behaving like one: valuations sprinting without a public launch, Poke crossing 100M messages between March and June and getting acquired in July. Churn’s quiet cause: people don’t know what to delegate — “one app per task” muscle memory runs deep. Onboarding that teaches delegation retains; proactive assistants that scan email and messages and prompt new tasks win. “A task not done is worse than a task not done well.” And a telling detail on engineering priorities: at least one leading assistant quietly put humans behind its purchase flows, because reliable browser automation was simply more expensive to run. Most of the engineering budget goes to keeping up.

Every channel is a trade-off

Messaging (iMessage/WhatsApp) is free reach but capped: no task list, no rich UI, and the platform writes the rules — Meta banned general-purpose AI chatbots on WhatsApp last October. Gmail is the only channel with a real API, but it selects for executives. Slack is work-only. Your own app has no ceiling — tasks, suggestions, relationship — but install friction is real, and asking for email/calendar access at signup loses about a third of users. And the surface everyone wants, the OS, belongs to Apple and Google.

Channel trade-offs — every surface gives something up

Diagram after Kumar’s channel analysis.

The wedge ladder — and why India starts with a phone call

Wedge choice decides everything. A restaurant-booking concierge is acquisition without retention — too low-frequency. An email/calendar wedge has frequency but selects only executives: a homemaker, student, shopkeeper, or nurse has little inbound email; their coordination runs on WhatsApp, calls, and errands. India’s special wedge is call screening: absurd spam-call volumes (numbers handed out at storefronts, UPI running over mobile numbers), unusually high NPS and frequency, selects everyone with a phone — not just inbox people — and lives in an app the platforms can’t switch off. From there: call-making → offline vendor discovery → staff delegation → the family as a unit. A family butler has natural lock-in and network effects, solves the delegation gap (a household generates tasks daily), and holds a dataset no digital platform has — the one place the data-moat argument reverses. One caveat: Bharat needs a far more guided, hand-held product — possibly a different interface paradigm, not a translated, stripped-down app. A real opportunity, but possibly a short-lived one.

A call center floor — the 1× baseline — The 1× baseline: human call centers — what call-screening AI replaces first.

The wedge ladder — from call screening to the family butler

The ladder after Kumar’s India wedge analysis. Dead ends: restaurant concierge (low frequency), email wedge (execs only).

A phone at night — the assistant lives where the calls are — The assistant lives where the calls are: messaging and voice, not the inbox.

Learnings

The cycle started because the tech finally works on the long tail of tasks — 2015’s human-in-the-loop bet was a technology mismatch, not a go-to-market failure.
Consumer AI economics run on subsidy today; viable unit economics are 1–2 years out, and fundraising is itself a short-term moat.
There is no raw-data moat. Derived context plus brand and habit is the whole game — and the labs own the default entry point.
Wedge > vision: low-frequency concierge dies, exec-only wedges cap out; in India, call screening is the rare wedge with frequency, NPS, and universal selection.

The takeaway — Kumar’s best guess at a venture-scale company: less “does everything for you” on day one, more a narrow high-frequency wedge that earns the right to expand, on a context layer that gets smarter about a household the longer it runs — with real thought about who it’s designed for. Notes, not a thesis.

Original: “The AI Assistant is Finally Here” — Harsha Kumar, LSIP · Companion: Lightspeed India’s updated AI-assistant market map (Sep 24 — founders wrote in with India names that had to be added)

In this edition

Lead feature
Why AI is booming but productivity isn’t
The productivity machine
Lenskart’s world model · The amplification gap
Moats
What counts as a moat now · The app-layer strikes back
Building
The two-person product · A snack catalog, built with Claude · Speed is a choice
Agents & memory
Jev & the memory problem
The automated creator
3Blue1Brown, fully automated · Bacterium → quantum fields · Notes from a clipper
Go-to-market
The bitter lesson of outbound · X-ray a company in 15 min
The human section
Signs you’re a generational outlier · Disgustingly self-disciplined
India
India Is Inevitable

The stack this week

Assistants: the cycle essay + updated market map
ROI: Chamath’s AI-ROI deep dive
Moats: Diamandis’ three survivors
Build: two people, taste, relentlessness
Create: Opus 5.5 → manim → Kokoro
India: CMF spins out, call screening

Previously in the pile

Lightspeed’s updated market map — published Sep 24 after Harsha’s essay drew founder write-ins, several building in India. The map is the visual companion to the lead feature.

The AI ROI debate

Essay · Deep dive

Why AI Is Booming, but Productivity Isn’t

Chamath Palihapitiya @chamath · Sep 25, 2026 · 316K views

In June Chamath declared vibe coding dead and said ROI-driven analysis of AI was about to go from nice-to-have to necessity. This is the follow-through: a full framework for what AI ROI actually is, and why it’s invisible in GDP numbers so far. His answer, in short — the tools are fine; the humans are the bottleneck.

Charts — measuring what AI actually returns — Measuring the return: spend is a rounding error, reorganisation is the whole game.

The arithmetic that reframes the debate

On the cost side, Ramp’s AI Index — tracking what 70,000+ US businesses spend on AI — finds the median company spends $12.50 per employee per month. Against an average employee cost of ~$8,500 a month, AI only has to make that person ~0.15% more productive to pay for itself: about three extra productive minutes a week. The token bill is close to a rounding error. The real costs are intangible: change management, re-training, the rest of the corporate machinery.

The ROI arithmetic — Ramp AI Index

After Chamath’s essay; spend data from Ramp’s AI Index (70,000+ US businesses).

Value is harder — so use productivity as a stand-in

At P&G, one person using AI produced product proposals as good as a two-person team without it. MIT economists showed automation pays when AI steps are grouped so a person checks the work once, not after every step. But here’s the catch: most of a corporate employee’s week goes to coordination, meetings, alignment, and process sign-offs — not producing work. What if humans are the bottleneck to AI ROI? If the saved minutes flow into another meeting or another week waiting on legal, the return is zero. AI may multiply output rather than add to it, so the best firms pull further away.

P&G: 1 person + AI = 2-person team output

MIT: check once, not after every step

Bottleneck: meetings > making

The experiment that settles it

A 2026 experiment with 515 startups gave every firm identical AI tools, training, and support — but a random half also saw how other firms reorganised work around AI. For the typical startup, revenue barely moved in either group. But almost all the gains came from the top 10% of firms, and the treatment group pulled furthest ahead — 1.9× the control group’s revenue. The tools were identical; what separated the leaders was how they rebuilt their work around them. AI lowers the cost of doing things, but does nothing about whether they were worth doing in the first place.

“Automation applied to an efficient operation magnifies the efficiency, and applied to an inefficient one magnifies the inefficiency.”— Bill Gates, 1995, quoted by Chamath

Chamath lines up the canon: Gates’ magnification rule, Musk’s five-step process (question every requirement → delete → simplify → speed up → only then automate — Musk said his biggest Tesla mistake was doing those steps backward), and Solow’s 1987 paradox: “You can see the computer age everywhere but in the productivity statistics.” Productivity grew ~1.5% a year from 1973–1995, then ~3.3% a year from 1995–2003 — once work was reorganised around the machines. We are in the 1987–1995 interregnum again, waiting on the reorganisation.

Learnings

AI’s break-even bar is absurdly low (0.15% productivity) — the spend was never the problem.
The gains concentrate: in a 515-startup experiment, nearly all ROI went to the top 10% — the firms that rebuilt workflows, not the ones with better tools.
Sequence matters: delete, simplify, speed up first; automate last. Musk learned it backward at Tesla.
History rhymes: the Solow paradox resolved only after a decade of reorganisation. We’re in that decade now.

The takeaway — Stop asking which model to buy. Ask what to delete, what to chain together, where a person still needs to check the work, and when a cheaper model is good enough. The ROI is in the reorganisation.

Original: Chamath’s X article · Deep dive: research.socialcapital.com/p/ai-roi

The productivity machine

Case study

Lenskart Got Faster Without Anyone Getting Faster

Ashwin Gopinath @ashwingop, CEO of Sentra · Sep 17

A $12B public company — Lenskart — got measurably faster across ten departments without a single employee getting faster. Ashwin’s team built a world model of the company from its own records: not faster individuals, but faster handoffs. The arithmetic is the point — the gains show up in the P&L, without the theatrics of token-maxxed leaderboards. It’s Chamath’s thesis in the wild: the company got more productive because the system changed, not the people.

The takeaway — Model the company, not the employee. The biggest AI wins are coordination wins.

Original: @ashwingop’s post + article

Essay · Founder psychology

The Amplification Gap

Nikunj Kothari @nikunj · Sep 24

Nikunj walked out of a meeting with an early-stage life-sciences founder with deep impostor syndrome — “was he talking about me?” Every early-stage founder tells him the same story. The essay is about the middle: people who are AI-curious but haven’t “fully gone off the deep end.” His argument: AI alone doesn’t amplify you anymore, because someone with AI can theoretically out-amplify you. The edge is agency — the “no fear” approach of constantly spinning up and not asking — combined with leaning hard on what you’re “out of distribution” at, and becoming 10× better at it using AI. Good product instincts still matter for generative ideas; the tools just raise the floor. “I feel like I need to rewire my brain, even though I am trying to do that actively.”

The amplification gap — same tools, different outcomes

After Nikunj’s essay: the tools are identical; agency is the multiplier.

Original: “the amplification gap” · His gloss: “This is the way..” — in any era

Moats

Essay · Strategy

What Counts as a Moat in the Age of AI?

Peter H. Diamandis @PeterDiamandis · Sep 25 · 101.8K views

A friend running a nine-figure AI services business has “no conviction” about his moat. So Diamandis went asking — Astro Teller, Steve Jurvetson, a training-data founder, Dave Blundin and Ramez Naam on the Moonshots podcast — and came back with an obituary and a shortlist. Buffett popularised the moat in the 1990s; AI collapses the time and effort that made moats work.

A speaker on stage — making the case for what survives — Making the case on stage: most of the old moat list doesn’t survive contact with AI.

The most valuable moat on earth is leaking

CUDA — NVIDIA’s moat of moats. Dave Blundin on the Aug 28 Moonshots episode: “Every AI researcher…” is working around it. Ramez Naam on Aug 4: “The CUDA moat is broken this year and next.” Jensen Huang saw it coming. Diamandis’ rule: your moat is only good until the next moat. Chips are the easy case — the same erosion hits P&G-style brand fortresses (Gillette’s playbook, copied by frontier models overnight) and SaaS (cloned by the models themselves). He cites the Coasean Singularity paper from MIT/Harvard: when transaction and coordination costs collapse, the firm itself gets unbundled.

The three moats that survive

After Diamandis: “The durable advantage is the metabolic rate of the organisation, and AI is the fastest way to raise it.”

The macro caveat

1999, the internet: the first owners rarely won — the second owners did. Diamandis’ closing drill is practical: entrepreneur — pitch your rate of reinvention, not your features; executive — audit your moat list and cross out what AI copies in ninety days; investor — underwrite management speed; student — learn faster than the tools change; parent — teach reinvention. “If AI could copy everything you’ve built in ninety days, what would you have left? Whatever your answer is, that’s your actual moat. Go widen it.”

Learnings

Patents, code, features, and distribution are off the moat list — AI copies all four in ~90 days.
The three survivors: speed of reinvention, capital velocity, brand.
Second owners won the internet; position for the second act, not the first hype cycle.

Original: Diamandis’ X article · Moonshots LIVE: moonshots.com/livestream

Counter-thesis

The Application Layer Strikes Back

Vijay Shekhar Sharma @vijayshekhar · Sep 25 · quoting Alex Mashrabov

“There’s a popular argument that foundation models will capture all the value in AI, leaving little for the application layer. Higgsfield is proving the opposite thesis.” The numbers: Higgsfield crossed $1B in annualised revenue and grew 20× since September 2025. The mechanism is the counter-thesis itself — better models expand what enterprises can achieve and thereby increase the value of applications embedded in their workflows. The foundation layer doesn’t eat the app layer; it fertilises it.

The opposite thesis — better models, more valuable apps

After Vijay Shekhar Sharma’s post quoting Higgsfield’s Alex Mashrabov.

The takeaway — If you’re building in the app layer, the foundation models are your tailwind, not your executioner — provided you’re embedded in a workflow, not floating above one.

Original: @vijayshekhar’s post

Building

Post · Team design

To Build a Cool Product Now, You Need Two People

signüll @signulll · Sep 16 · 345.5K views

“One dude with exceptional vision & taste who knows what should exist & can provide the right feedback loops for iteration. & one dude who is absolutely relentless about making it real no matter what. that’s it.” (He clarifies it wasn’t meant to be gendered.) The thread’s replies sharpen it: his first hire was a bad idea with lasting negative impact — the two-person rule is as much about who you don’t add. In the age of coding agents, headcount is a liability and taste is the scarcest input.

The two-person product team

Original: @signulll’s post

Build log

A Snack Catalog for Kids, Built with Claude in the Loop

Nikunj Kothari @nikunj · Sep 18

Obsessed with self-driving companies for over a year, tried a lot of products, none met the bar — so he built one himself with Claude in the loop. First experiment: nosugarforkids.com, a catalog of only healthy snacks for kids (“surprisingly this didn’t exist”), with chat for recommendations and a full-blown MCP/WebMCP so you can point your agent at it. His life philosophy is “everything in moderation” — but what kids intake matters supremely. The pattern is the story: taste identifies the gap, the agent builds the thing, MCP makes it agent-addressable from day one.

Product sense, visualized — Product sense, visualised: spot the missing catalog, ship it with an agent.

Original: @nikunj’s thread · nosugarforkids.com

Speed is a choice a16z @a16z · Sep 17
Two words from Patrick Collison’s catalog, republished as doctrine: speed isn’t a trait, it’s a decision. Pairs with Diamandis’ lead feature — the metabolic rate of the organisation is the moat.

“You’re right and I was wrong” Kavin @kavinbm · Sep 17
Push back on a frontier model and it folds — push back on the fold and it folds again. Underneath is next-word prediction, and “it’s so important not to forget that.” A one-line antidote to treating model agreement as validation.

Agents & memory

Article · Context engineering

Jev, and the Memory Problem in AI

Dhravya Shah @DhravyaShah · Sep 25 · “a great evening read”

Dhravya wrote up how TypesafeAI’s Jev can improve AI memory — walking through all the approaches “in quite detail, with a bunch of benchmarks and cool things in the middle.” It’s the engineering companion to this edition’s lead feature: Harsha Kumar says the only data moat is derived context — things the assistant learned on its own platform. Jev is the machinery for building exactly that: memory as a system, not a prompt trick.

The Jev memory system — The memory layer: what the assistant remembers is what it compounds.

Approaches to AI memory — the landscape Dhravya maps

Landscape after Dhravya Shah’s article; Edition No. 2 covered Jev’s beginner guide.

The takeaway — If derived context is the only data moat (see the lead feature), then memory architecture is moat architecture. Benchmark before you build.

Original: @DhravyaShah’s article post

Jev can WHAT? — the sponsored cameo Vladimir Bayandin @vovudebosh · Sep 23 · flagged: paid promotion
“It can take your website link, find people who need your product, email them and book the calls?” — reads as a paid placement for Explee’s Jev auto-GTM product ($30 free credit). Included for completeness; treat the claims as advertising, not evidence.

All self-improvement is attention management Prompter @PromptLLM · Sep 25
“All form of self improvement is just mastering where your attention goes.” Twenty-one words, filed under things worth re-reading monthly.

The automated creator

Demo · 312K views

The 90th-Percentile Educational YouTuber Is Fully Automated

Deedy @deedydas · Sep 24 · 5,362 likes · 5,232 bookmarks

Deedy generated an entire 3Blue1Brown-style video — eight minutes summarising the paper “Regularized Recursive Self Improvement of Agent Harnesses” — with Opus 5.5. The stack, which he didn’t even specify: manim for the visuals, Kokoro-82M for the voice, ffmpeg to compile. The model figured out the pipeline and generated it automatically. (He concedes the obvious: the real 3Blue1Brown is still better — but video is “far more approachable to any reader than actually reading.”)

The automated YouTuber — paper in, video out

Pipeline as described by Deedy; alphaxiv link card for the RRSI paper in the thread.

The takeaway — The creative stack is now: frontier model as director, open-source tools as crew. The scarce input is the source material worth adapting.

Original: @deedydas’ demo + thread

Demo

One Shot: Bacterium to Quantum Fields

Paras Chopra @paraschopra · Sep 24

“Claude 5.5 is crazy good with animations.” One prompt — a self-contained, aesthetically pleasing, scientifically accurate animation starting at a single bacterial cell, zooming through DNA, atoms, ending at quantum fields — produced a 1:47 video. It even added an original score. His thread shares the full prompt. Pair with Deedy’s piece above: the model is now a competent motion-graphics studio.

Original: @paraschopra’s post + prompt

Playbook

Notes from a Clipper Who Wanted You to Watch

Kaashvi Saxena @kaashvisaxena · Sep 22

“You’ve watched 100+ clips today. Here’s notes from a clipper who wanted you to.” Clipping in one line: taking long-form material and turning it into portable short-form stories that travel. The essay covers what changed (an organised distribution system, not just reposts), what’s eligible, what not to clip, the mechanism (feed behaviour), how brands ruin it, 7 questions to evaluate a clipper, Editor vs Network vs Agency, and how to start: one source asset, a licensed pilot, track retention/saves/shares. She runs ‘The Distribution Cafe’, an offline session IP.

The takeaway — Attention is manufactured at the clip layer now. If you make anything long-form, you need a clipping strategy — or someone else’s clips will define you.

Original: @kaashvisaxena’s article

Go-to-market

GTM lesson

The Bitter Lesson of Outbound: Fix TOFU, Not Conversion

Sajith Pai @sajithpai, Blume Ventures · Sep 18

“Improving TOFU is always better than improving conversion” — h/t Sam Blond on the Uncapped pod. More top-of-funnel beats a better-converting funnel. In the replies he adds the calibration note: pre-PMF GTM has to be more measured than post-PMF — the venture equivalent of “if you don’t have high loss rates, you’re not taking enough risk.”

Where to spend the marginal hour — TOFU vs conversion

Original: @sajithpai’s post

Framework · Heavily bookmarked

How to X-Ray a Company in 15 Minutes

Polymath Investor @polymathinvest1 · Sep 24 · 1,272 bookmarks

A carousel walkthrough for reading a company fast — the kind of post that earns 1,272 bookmarks because it’s a checklist you’ll reuse. The discipline: separate narrative from numbers, find the unit economics before the story, and check where the cash actually goes. Fifteen minutes, honestly applied, beats fifteen hours of vibes.

The X-ray checklist (abridged)

Read the cash flow before the narrative — stories are written, cash isn’t.
Find the unit economics: what does one more customer actually cost and return?
Check who gets paid first when things go wrong — the capital stack tells the truth.
Fifteen honest minutes > fifteen hours of vibes.

Original: @polymathinvest1’s carousel

The human section

Essay

The Signs You’re a Generational Outlier

Tim Denning @Tim_Denning · Sep 24 · 472 bookmarks

“Outliers are secret weirdos” — they live a life most people don’t understand. Denning, fascinated with outliers since Gladwell’s book, admits the uncomfortable thing: “I have probably become an outlier.” Six signs follow, and they’re worth reading straight — but the spine is the Three Extremes Rule (from Zach Pogrob, Aura’s founder): extreme focus (one thing), extreme timeline (one decade), extreme iteration (1% better every day). Trauma as an amplifier. A chip on the shoulder as fuel — “quiet rage” with a target. Obsession at the risk of looking like a maniac. Eccentricity as a feature, not a bug: non-linear careers, miniature trains, the strange stuff you do in the shadows.

A man looking out over the city — the outlier's view — The outlier’s view: one thing, one decade, 1% better every day.

Extreme focus — 1 thing

Extreme timeline — 1 decade

Extreme iteration — 1% daily

The takeaway — “If you want to spot the outlier in you, look for the strange stuff you do in the shadows.” The 10,000-hour rule is out; the three extremes are in.

Original: @Tim_Denning’s article

Essay · 3.3M views · 26.5K bookmarks

How to Become Disgustingly Self-Disciplined

Dan Koe @thedankoe · Sep 19

The most-bookmarked piece in this edition, by a mile. Koe’s system starts with a provocation: become so disgusted with where you are that you have no option but to win. The rocket analogy carries it — 85–90% of a rocket’s mass is fuel for launch. Launch fuel is motivation, pain, willpower, tactical stress. Cultivate disgust for the life you don’t want; spend a week observing society and let it work on you.

Dan Koe — the discipline essay — The most-saved piece in the pile: discipline as identity, not willpower.

Identity, not discipline

“You aren’t disciplined because you aren’t the person who doesn’t view it as discipline.” Identity change first (his examples: Elon, Arnold), then James Clear’s line: be more concerned with your current trajectory than your current results. Then the input/output equation — Input = everything you’re exposed to; Output = your decisions, actions, works — with four input rules: information diet, people, interrogate beliefs, active over passive consumption.

The four-part feedback loop — Skinner, via Koe

After Koe’s essay; the loop is from B.F. Skinner, applied to muscle-building and writing-business goals.

The takeaway — Don’t optimise willpower; redesign inputs and environment until the right behaviour is the lazy option.

Original: @thedankoe’s article

Look for anti-models, not role models Vivek @Vivek_Investor · Sep 18 · 17K likes
“This is what Taleb said: instead of looking for role models, look for anti-models. This applies to every aspect of life.” Quoting a gym-motivation meme — the uncles you don’t want to become, as a 10-minute timer. Via negativa, applied to the body.

Game theory explains the uncomfortable truth Dhruv kumar @Dhruvkumar16797 · Sep 20
“Why some people become successful while others stay average. The reason is uncomfortable.” Quoting Dan Koe’s “How to fix your entire life in 1 day” — a 53-minute video for the pile’s long tail.

India

Essay · 1.2M views · 3,146 bookmarks

India Is Inevitable

Carl Pei @getpeid · Sep 21

Every country that has manufactured consumer electronics at scale has eventually produced its own global champions — Japan did, Korea did, China did (Pei watched it over eight years living there). India is next: the world’s second-largest smartphone manufacturer, the largest youth population, one of the deepest software talent pools — but no global consumer-electronics brand of its own. Yet.

Carl Pei — India Is Inevitable — Eight years in China taught him the pattern. Now he’s betting it repeats in India.

R&D is the whole game

The how is R&D: the ability to design, engineer, and keep improving a product in-house — what separates a company that lasts from one that rides a moment. The cautionary tale is 2015: Indian brands sold close to half the smartphones in the country; one was briefly India’s best-selling brand, ahead of Samsung. Within two years foreign brands arrived with what the domestic ones lacked — real engineering. The locals were licensing off-the-shelf designs, changing the back cover, adding a logo. By 2025 they held under 1% of the market they once led. “The hard part comes later, when the window closes and only the product is left — the better-engineered phone wins.”

Pei makes R&D checkable — five questions: who engineers the structure (materials, thermals, durability); who selects camera sensors and builds the imaging pipeline; who writes and maintains the OS and commits to years of updates; who re-tunes and certifies antennas when the design changes; who works directly with suppliers to co-engineer displays, chipsets, camera modules. If the honest answer is “our manufacturing partner,” the brand is picking a phone, not engineering one — a ceiling.

The announcement — CMF spins out as a standalone Indian company

After Carl Pei’s essay. Manufacturing was step one (99% of phones sold in India are made in India); R&D is step two.

Ecosystems form around hard questions

Pei moved from Stockholm to Shenzhen in 2012; by 2020 Chinese suppliers were among the world’s biggest in OLED panels, camera modules, in-display fingerprint sensors. Policy alone didn’t do that — Chinese phone makers built engineering teams that refused the catalogue, and suppliers stopped being vendors and became engineering partners. Manufacturing was step one: 99% of phones sold in India are now made in India. Step two is R&D. India has the base, a market absorbing 150M+ smartphones a year, and a government aiming for a global export hub. What it lacked was the brand to drive engineering demand. The bet: 100M phones a year is the line between a brand and a platform — above it, you’re the reason the supply chain exists. “India will produce global consumer electronics companies. The only question is when.”

Learnings

Manufacturing without R&D is a ceiling — 2015’s Indian brands prove the window closes fast.
R&D is five checkable things, not a vibe: structure, imaging pipeline, OS, antennas, supplier co-engineering.
Ecosystems don’t follow policy; they follow engineering demand — suppliers become partners when brands refuse the catalogue.

Original: “India Is Inevitable” — Carl Pei