Saurabh

SEGMENT, ALWAYS SEGMENT Most confounding business problems have the same root cause: you haven't segmented your customers. You look at the top-line number. It's flat, or weird, or inconsistent with what your gut tells you. You poke at it and you can't figure out why. The answer is almost always that you're staring at an average that's hiding two or three very different stories. A few places this shows up: 1. When your high-level metrics look wonky or divergent, break them out by segment. A flat retention curve often hides one cohort churning out violently and another expanding aggressively. A "meh" NPS usually has one segment of fanatics and one segment of detractors cancelling each other out. The average is a lie. The segments are the truth. 2. When your product is trying to be everything to everyone, you need to tailor it per segment. If your roadmap has SMB founders, mid-market IT buyers, and Fortune 500 procurement all fighting for features in the same backlog, that's three products in a trench coat pretending to be one. Pick the segment you're actually building for, and ship accordingly. 3. When your pricing or positioning feels wrong no matter where you set it, it's because one SKU or pitch is spanning segments with wildly different needs or willingness to pay. Enterprise will pay 10x what a startup will for the exact same thing. A single price point either leaves money on the table at the top or closes the door at the bottom. Segment the packaging. Segment the price. The pattern holds every time. Whenever a business problem is hard to reason about, break the population into segments and look again. Nine times out of ten, the fog lifts. Importantly, you don't need to use standard gender or demographic segments. You can build your own! (And AI is a superpower here). One of the best segmentations in real life was done by @davidweiden at TellMe Networks in the early 2000s. TellMe was selling phone automation software into financial services: a half-billion dollar market, and they had almost no traction. David built a custom segmentation framework called Rifle, which scored every prospect on five weighted criteria. Where the customer was in their buying cycle (engage before the RFP, not after). Whether their long-distance carrier was compatible with TellMe's deployment model. Three more criteria with explicit weightings, including negative scores that disqualified prospects outright. The whole company aligned on the scoring. Sales stopped chasing bad-fit accounts. Product stopped building features for customers who would never close. Marketing stopped spraying the market. Over two years, Rifle drove $20M in ARR inside the qualified segment and took TellMe from a loss to a profit. They literally would have failed without the segmentation. . Founders: when a metric confuses you, when your product feels scattered, when your sales pitch or pricing won't land, segment. Segment, always segment.

Foundry USA just mined 7 blocks in a row again on April 3rd. In 2026 alone, they’ve done this Four times. They even pulled off a 10-block streak back in 2023. Is this pure luck… or a structural advantage in Bitcoin mining? Let’s dig into the on-chain data. 👇 @basedlayer , @0xB10C , @PlebLab

HUGE moment for India 🇮🇳 27M devs building on @github in India 2M+ more joined in 2026 1 in 7 new devs are from India 7.5M contributions to open source AI projects on GitHub Behind India’s economic growth is a relentless community of devs. Grateful we got to celebrate on the ground with so many of them here in Bengaluru. A big thank you to this community for building with us all these years. ❤️

Where is the public roadmap for Bitcoin Core? Bitcoin is already a multi trillion dollar asset and will continue to rapidly grow. Where is the dev roadmap? What key bug fixes and features will be worked on over the next 5-10 years? One of the key communication issues with Bitcoin Core is that hodlers, investors, and node runners are not really aware of what's being worked on. Sure we can try to read the Bitcoin mailing list, can try to listen to the @bitcoinoptech podcast or read the newsletter, can occasionally attend local BitDevs meetups – but it's not easy to keep up with what's going on. For example, if you asked me right now, I'd say that Core devs are considering some major improvements like covenants. I remember hearing about Utreexo at a BitDevs meetup last year. But I have no sense about the roadmap for new potential features. I'm sure Core devs would say that having a roadmap is difficult due to Bitcoin's decentralized nature. That there are no individual decision makers, that it is governed by consensus. That a roadmap necessitates a timeline which necessitates dates which will be impossible to hold to. And so on. But hear me out – this is a trillion dollar asset class that is being adopted by governments and publicly traded companies. Yes, it is decentralized. But I think it should at least have a roadmap we can reference. A roadmap would help non-devs understand what is being worked on and what new features are being considered. A roadmap will give everyone plenty of time to argue. Artificial target dates may even help; by acting as "deadlines" they can accelerate arguments and discussions regarding controversial issues. For institutional Bitcoin adoption, a roadmap is critical so that no one is surprised about new controversial features. That's because no feature will really be "new" – it will have been in the roadmap for several years by the time it is adopted. Also important upgrades like quantum resistance would placate critics and substantially minimize this low probability, yet existential, risk. I asked GPT to help me make a sample Bitcoin Core roadmap for the next decade: 2025: Package relay & v3 transaction policy improvements 2026: AssumeUTXO and Utreexo integrated for faster node sync 2027: Fee market and mempool optimizations under heavy load 2028: Covenant soft fork (likely CTV or APO) enabling vaults and channel factories 2029: Lightning enhancements — PTLCs, splicing, multi-party channels 2030: Privacy upgrades — improved transaction relay, better wallet-level privacy 2031: Vault and smart custody adoption through covenant-based tooling 2032: Block size, fee dynamics, and scaling research; Taproot utilization maturity 2033: Quantum-resilient key research and optional hybrid signing schemes 2034: Formal verification and code hardening of consensus layer 2035: Quantum-resistant soft fork (if needed), long-term sustainability focus Of course these are just placeholder items and timelines. But even just seeing this rough roadmap gives me more confidence that the Bitcoin Core project has direction. If this was a real roadmap, we can now all spend years discussing and arguing about each item, with arguments reaching a crescendo as the target year approaches. What do you all think? Thank you for reading.