Stanley Tang

Early-stage, pre-product-market fit founders should not manage engineers. I recently shared some takes on how early-stage engineering teams can over-manage themselves into a standstill (🔗 link below) * Hire for drive & nourish it, but don't "install" it: you can't manage someone into caring. In the 0-to-1 phase, passion for the problem is a prerequisite. * Reject BigCo Cargo-Culting: most “best practices” exist to reduce risk at scale, not to maximize speed under uncertainty. * Choose the "Node & Postgres" stack of management: boring, minimal, predictable. Just enough structure to ship, nothing more. The Caveat: This is a "wartime" framework for the 1–15 engineer stage. It is not designed to scale, because your goal is to survive long enough to need a different system.

30

3 Comments

This Abram Brown piece captures something I'm seeing everywhere: Tools like Claude Code are giving founders way more agency. For many, it's a reminder of the old days when they were ICs or running tiny companies. To be clear, this is not every founder. But those that were already hands on, in the weeds, in the codebase have just been handed Thor's Hammer.

35

5 Comments

The 4 layers of a scalable dispatch operation: Most companies think dispatch is just "answering calls." That's like saying running a restaurant is just "cooking food." Here's what actually separates good from great: Layer 1: CALLS Taking orders, fielding questions, and providing basic customer service Layer 2: COORDINATION  Matching drivers to jobs, managing schedules, and route optimization Layer 3: TRACKING Real-time updates, status monitoring, and problem flagging before they escalate Layer 4: REPORTING Data analysis, performance metrics, and identifying bottlenecks Most companies stop at Layer 1 and wonder why they can't scale. The truth? Each layer multiplies your capacity. Layer 1 gets you running. Layers 2-3 get you profitable. Layer 4 gets you scalable. If you're stuck doing everything yourself, you're missing layers 2 through 4. Want to see how we build this? Send me a DM. #ScalingOperations #FleetManagement #DispatchManagement

5

Most tech founders assume that building a strong product is enough. It isn’t. What Abhilash shared here is a pattern I keep seeing - smart builders, solid tech, but unclear on validation, positioning, and actual market readiness. The gap is rarely effort. It’s direction. 0to1 isn’t about teaching theory. It’s about forcing clarity: – Is your idea worth building? – Are you solving a real problem? – Can you sell it? Because a “good product” that doesn’t convert is just wasted time. Glad to see this shift. #StartupLessons #FounderJourney #TechFounders #BuildInPublic #StartupReality #ProductMarketFit #StartupGrowth #Entrepreneurship #0to1 #FounderLife #StartupIndia #SalesForFounders #IdeaValidation #EarlyStageStartups #B2BStartups

2

1 Comment

Technical founders fall in love with product. Then forget this important puzzle piece: Distribution. This is a huge problem. Here's a quote from a founder I spoke to recently: "Building isn't the problem, knowing the right thing to build is." He’s one of the smarter ones. He elaborated: "If we can't get to the right users, we can't get feedback. We can't move fast enough." Most businesses focus on their product. The latest feature. Shiny new UX. They create a "solution bubble" for themselves. In reality, they need more time in front of the right audience. I've fallen for the same trap before. I spent months tinkering with an app in my first business. I put my head up on "release day." Reality gave me a rude wake-up call. I didn't have the skill to drive people to my solution. I've been building that skill ever since. With my services. With my books. With partners. Distribution is more important than your product. Without a minimum viable distribution (MVD), your minimum viable product (MVP) will remain: minimum. No feedback. No iteration cycles. Slow product market fit. Traction, slimming along a gravel ground like a snail. Team focused on growth ask: "What channels do we prioritize?" "What events do we go to?" "Where do we engage?" "How many times?" When you have a minimum viable distribution plan, you’ll have: - the right message for the right channel. - product that reaches the right people. - a targeted approach to gain traction. In my latest letter, I wrote about how to develop a minimum viable distribution (MVD) plan for your team. It gives you a 12-month plan to reach the right people with your: • Top 3 events of the year • 1 platform to prioritize • 1 format to focus on • List of 50 partners With this, you'll stop being everywhere and only be in the right rooms. Read it in the comments below.

8

3 Comments

SaaS isn't dead. It's just being demoted. As users shift to multimodal, agentic workflows, most traditional SaaS products will persist mainly as dumb backends. Commoditized systems of record that agents read from and write to, not products users meaningfully interact with. To replace something like SAP with an agent-native system, you'd need to reproduce it as a modern data store. Most enterprises would rather just keep what they have. Same reason many fortune 500 companies still run mainframes. Easier and safer to just keep it. Of course, this only applies if the logic in a SaaS platform is super complex. If it's simple, then yes, it's dead.

36

6 Comments