Scaling Business Operations

Scaling from 50 to 100 employees almost killed our company. Until we discovered a simple org structure that unlocked $100M+ in annual revenue. In my 10+ years of experience as a founder, one of the biggest challenges I faced in scaling was bridging the organizational gap between startup and enterprise. We hit that wall at around 100~ employees. What worked beautifully with a small team suddenly became our biggest obstacle to growth. The problem was our functional org structure: Engineers reporting to engineering, product to product, business to business. This created a complex dependency web: • Planning took weeks • No clear ownership  • Business threw Jira tickets over the fence and prayed for them to get completed • Engineers didn’t understand priorities and worked on problems that didn’t align with customer needs That was when I studied Amazon's Single-Threaded Owner (STO) model, in which dedicated GMs run independent business units with their own cross-functional teams and manage P&L It looked great for Amazon's scale but felt impossible for growing companies like ours. These 2 critical barriers made it impractical for our scale: 1. Engineering Squad Requirements: True STO demands complete engineering teams (including managers) reporting to a single owner. At our size, we couldn't justify full engineering squads for each business unit. To make it work, we would have to quadruple our engineering headcount. 2. P&L Owner Complexity: STO leaders need unicorn-level skills: deep business acumen and P&L management experience. Not only are these leaders rare and expensive, but requiring all these skills in one person would have limited our talent pool and slowed our ability to launch new initiatives. What we needed was a model that captured STO's focus and accountability but worked for our size and growth needs. That's when we created Mission-Aligned Teams (MATs), a hybrid model that changed our execution (for good) Key principles: • Each team owns a specific mission (e.g., improving customer service, optimizing payment flow) • Teams are cross-functional and self-sufficient,  • Leaders can be anyone (engineer, PM, marketer) who's good at execution • People still report functionally for career development • Leaders focus on execution, not people management The results exceeded our highest expectations: New MAT leads launched new products, each generating $5-10M in revenue within a year with under 10 person teams. Planning became streamlined. Ownership became clear. But it's NOT for everyone (like STO wasn’t for us) If you're under 50 people, the overhead probably isn't worth it. If you're Amazon-scale, pure STO might be better. MAT works best in the messy middle: when you're too big for everyone to be in one room but too small for a full enterprise structure. image courtesy of Manu Cornet ------ If you liked this, follow me Henry Shi as I share insights from my journey of building and scaling a  $1B/year business.

The New York Times profiled a start-up with 28 employees serving nearly 50 million users. That company is us. The traditional startup playbook: raise massive funding, hire hundreds of employees, and worry about profitability "later." But there's another way. Everyone at Gamma could fit in a small restaurant. We're not just surviving—we've been profitable for 15+ consecutive months, with revenue growing month over month, and lifetime negative net burn (we have more money in the bank than we've raised). This isn't an accident. We've deliberately designed our organization to maximize impact per person. Instead of creating specialist silos, we hire versatile generalists who can solve problems across domains. Rather than building management hierarchies, we find player-coaches who both lead and execute. Our team leverages AI tools throughout our workflow - Claude for data analysis, Cursor for coding efficiency, NotebookLM for customer research synthesis. These aren't just productivity hacks; they're force multipliers. Examples: — When our growth PM needed better analytics, he didn't file a ticket with a data team—he built a self-serve system that anyone can use without SQL knowledge. — When our marketing lead needed to understand our customers better, she fed thousands of interactions into an LLM and created actionable personas that now guide our entire strategy. — When our design team needs to test a hypothesis, we create a rapid prototype and show it to our power users. What we're seeing isn't just about "doing more with less." It's about fundamentally changing what's possible per person. The most valuable employees aren't specialists who excel in narrow domains - they're resourceful problem-solvers who continuously expand their capabilities. This approach creates remarkable resilience. Since everyone understands multiple functions, we don't have single points of failure when someone leaves or moves to another project. If you're building today, the question isn't how quickly you can scale headcount … it's how much impact you can create with the smallest possible team. The future belongs to tiny teams of extraordinary people.

🚨 Why Farmers Stay Poor: Are Finance Models Designed to Fail Them? It’s not the weather. It’s not the soil. It’s the system. For decades, financial models in agriculture have appeared to support farmers, yet poverty persists like a crop that won’t die. But why? Because the system is designed to finance the input, not the impact. Farmers are given loans to buy seeds and fertilizer only to sell low and borrow again. This is not empowerment. It’s a financial treadmill. Here’s the uncomfortable truth: > Most agricultural finance schemes were designed for lenders to manage risk not for farmers to build wealth < Three systemic design flaws that keep farmers trapped: 1. Short-term loans for long-term crops: Cash crops like coffee, banana, or avocado need patient capital. But most agri-loans are seasonal, forcing early harvests and losses. 2. Collateral bias: Land titles or assets are demanded, excluding women and youth who ironically are the ones farming most. 3. Profit blindness: No financing model asks: Will this farmer actually make money from this season? It assumes yield = success. But yield doesn’t pay school fees. Profits do. We don’t need more credit. We need credit designed for context. So what’s the solution? 📌 Agri-finance products co-designed with farmer groups. 📌 Flexible repayment systems linked to harvest cycles, not calendar months. 📌 Data-informed risk scoring using real-time climate and market data. 📌 Incentives for banks to finance regenerative and value-adding models, not just inputs. In 2025, agricultural finance must go beyond transactions to build transformation. If you're building a new finance product, running an agri-startup, or investing in food systems and you’re not thinking about this you’re building on sand. Let’s create capital that liberates, not entraps. National Agricultural Research Organisation - NARO FAO M-Omulimisa Enimiro Uganda Avotein Farms Limited Amabanda Uganda Limited Emata Shambapro AgriLink Uganda AgriProFocus Uganda Solidaridad East and Central Africa AGRA Are you curious on how I can redesign your agri-finance approach to actually build farmer wealth? Let’s connect. #Agribusiness #Agrifinance #InclusiveFinance #UgandaAgriculture #Agritech #SmallholderFarmers #Agripreneurs #AgriPolicy #FintechForFarmers #TheAgrithinkersTimes #AgriWealthStrategies #ClimateSmartFinance

This is the exact framework that helped many founders grow companies and exit with more than 50% ownership 95% of startups raise money at the wrong time. They either raise too early and dilute unnecessarily, or wait too long and run out of cash. After working with 100’s of founders, here's the exact roadmap that separates winners from casualties Stage 1: Bootstrap Phase (₹0 - ₹50L Revenue) ⤷ Focus entirely on product-market fit ⤷ Keep burn rate under ₹2L monthly ⤷ Validate unit economics with first 50 customers ⤷ Don't even think about external funding yet ⤷ Use personal savings, family money, or revenue to grow ⤷ Hire only essential team members (2-5 people max) Stage 2: Revenue-Based Debt (₹50L - ₹2Cr Revenue) ⤷ You have proven PMF and positive unit economics ⤷ Monthly revenue growth of 15%+ for 6 consecutive months ⤷ CAC payback period under 12 months ⤷ Customer retention above 85% ⤷ This is where debt financing makes perfect sense ⤷ Raise 6-12 months of runway to accelerate growth ⤷ Use funds for marketing, not team expansion Stage 3: Growth Equity (₹2Cr - ₹10Cr Revenue) ⤷ Strong unit economics with LTV/CAC ratio of 3:1 or better ⤷ Clear path to ₹50Cr+ revenue within 3 years ⤷ Market size of ₹1000Cr+ that you can capture ⤷ Need significant capital for market expansion or R&D ⤷ Team of 25+ people with proven leadership ⤷ Only raise if you can 3x revenue within 18 months Stage 4: Scale Funding (₹10Cr+ Revenue) ⤷ Approaching or at profitability ⤷ International expansion opportunities ⤷ Acquisitions or new product lines ⤷ Series B/C rounds make sense here ⤷ You're competing for market leadership When NOT to Raise Money ⤷ You haven't proven product-market fit ⤷ Burn rate exceeds 50% of monthly revenue ⤷ Customer acquisition is broken ⤷ You're raising to extend runway without growth plan ⤷ Market size is unclear or too small ⤷ You can achieve next milestone with existing cash + revenue The Hard Truths ⤷ 80% of companies never need equity funding ⤷ Most successful companies are profitable by ₹5Cr revenue ⤷ Raising too early kills more startups than not raising at all ⤷ Debt is almost always better than equity if you qualify ⤷ Every funding round should 5x your valuation within 2 years Note: These figures are based on my experience and may vary across industries and markets. Use this as a framework, not absolute rules. Decision Framework Bootstrap → Build until ₹50L revenue with strong unit economics Debt → Scale from ₹50L to ₹2Cr while maintaining profitability path Equity → Only when you need ₹5Cr+ for rapid market capture The companies that follow this roadmap keep 60-80% ownership at exit. The ones that raise too early end up with 10-15%. Which path are you on? #startups #funding #bootstrap #debtfinancing #growth

Bridging the "Manufacturing Valley of Death." If you're building a hardware startup, you already know: prototyping is hard, but scaling to production is where most ventures die. After helping dozens of hardware founders, I've seen one stage consistently kill great products: the transition from prototype to mass production. Why is this stage so so so brutal? You’re stuck in manufacturing no-man’s-land: ✅ Too big for prototype shops (their unit costs explode beyond 100 units). ✅ Too small for traditional contract manufacturers (they want 10,000+ units). ✅ Facing a 5–10x cost jump for tooling, molds, and compliance testing. ✅ Every delay cascades—supply chain hiccups, redesigns, and cash burn pile up fast. 1 day becomes 1 week becomes 1 month and so on... This is the "Valley of Death"—where startups hemorrhage money, time, and morale before reaching real customers. How to Survive (and Even Thrive, maybe): 1️⃣ Find a "Bridge" Manufacturer Look for CMs specializing in low-to-mid volume (500–10k units) with soft tooling or modular assembly. 2️⃣ Use Hybrid Prototyping Combine 3D printing, CNC, and hand assembly to defer expensive tooling until you validate demand. 3️⃣ Secure Flexible Funding Crowdfunding, pre-orders, or strategic investors who understand hardware’s scaling risks. 4️⃣ Design for Manufacturing (DFM) EARLY Involve manufacturing experts before your first prototype to avoid costly redesigns later. 5️⃣ Expect (and Budget For) Delays Assume your first production run will have 30% higher costs and 2x the timeline you planned. The Bottom Line: Crossing the hardware "Valley of Death" requires planning, partnerships, and patience. The startups that survive are the ones who: Treat scaling as a core risk (not an afterthought). Raise more capital than they think they’ll need (because they will). Build relationships with manufacturers before they’re desperate. If you’re in this phase now—keep pushing. The other side is worth it. What is your best tip for surviving the manufacturing valley of death? #Manufacturing #Electronics #Nearshoring #ContractManufacturing

Hospitality keeps talking about growth like it’s a mystery. It isn’t. Growth comes from systems. And nobody proved that louder than Conrad Hilton. Most people think Hilton won because he had hotels. Wrong. He won because he built a machine. He walked into a small Texas town in 1919 to buy a bank. The deal fell apart. He bought a hotel instead. Total accident. But what he did next wasn’t an accident at all. While everyone else was busy fighting the daily fires of hospitality Hilton was studying the patterns behind the fires. He wasn’t trying to run hotels. He was trying to design a system that could run hotels without him. That mindset shift is the single most underrated move in hospitality history. He documented everything. How guests were greeted. How the lobby should feel. How staff behaved. What consistency looked like at scale. He made the experience predictable which made the brand trustworthy which made the brand scalable. Back then nobody understood brand standards. Hilton invented the operating system before the industry even had language for it. And then he made his real power move. He built a centralized reservation network long before anyone believed global demand could be captured. Everyone else was hoping for bookings. Hilton was building pipelines. That’s why he became global. That’s why his competitors stayed local. Now here’s where I want leadership to lean in. If Hilton built what he built in 1919, with zero tech zero data, and zero AI what’s your excuse today? Why are your service standards not documented by every department? Why does your brand voice change every time someone new touches your social channels? Why is your guest experience dependent on personalities instead of systems? Why does your culture collapse every time the GM takes a week off? Why is your marketing still reactive instead of automated intentional and measurable? Why are you still rebuilding instead of replicating? Why do you keep saying you want scale but your systems can’t survive without you? Be honest about this. If the entire operation depends on you, you don’t own a brand you own a very stressful job. Hilton didn’t win because he worked harder. He won because he worked on the business not in it. He built a structure that grew even when he wasn’t in the room. That’s what leaders need to do right now. Especially when AI is about to widen the gap between brands that operate on instinct and brands that operate on systems. Your future growth won’t come from more hustle. It’ll come from designing a machine that prints consistency culture and revenue whether you’re on property or not. That was true in 1919. It’s even truer today. --- If you like the way I look at the world of hospitality, let’s chat: scott@mrscotteddy.com

Scale Fast or Stay Focused? The Hardest $10M+ Decision No One Talks About. At $1M, your priority is survival. At $10M, your priority is efficiency. At $50M+, your priority is expansion—or is it? The biggest mistake scale-ups make? Chasing expansion before the foundation is ready. Here’s how elite founders decide whether to scale fast or double down on what’s working. 📌 When to Stay Focused (Double Down on What Works) ↳ Your core business is growing profitably (expansion isn’t a Band-Aid for weak margins). ↳ You have unrealised growth potential in your existing market (expanding could be a distraction). ↳ You haven’t maximised operational efficiency (expansion will only magnify inefficiencies). ↳ Your team isn’t ready—scaling problems get worse at scale. 💡 Example: Amazon spent years perfecting e-commerce logistics before launching AWS. Mistake: Many startups chase expansion before their first market is fully tapped. They dilute their efforts instead of dominating a niche first. 📌 When to Expand (Take the Risk and Go Big) ↳ Your existing growth curve is flattening (you’ve maxed out your core market). ↳ You have repeatable, scalable acquisition systems that don’t depend on the founder. ↳ You’ve built cash reserves—growth burns capital fast. ↳ You can maintain strong execution while expanding (your leadership team isn’t stretched too thin). 💡 Example: Uber expanded into Uber Eats and freight once ridesharing reached scale. Mistake: Expanding too early without market dominance leads to disjointed strategy and operational strain. 📌 The Expansion vs. Focus Test  Ask yourself: 1️⃣ If we focus, can we still 10x in this market? 2️⃣ If we expand, can we execute at the same quality level? 3️⃣ What happens if we wait another 12 months before expanding? What’s your take—scale fast or stay focused? Drop your thoughts below! Making this decision in your company? Let’s talk. I help founders and leadership teams navigate scale-up strategy with clarity. DM me. 🚀 ♻️ Share this with someone who deserves to hear it.  👉 Follow Ben Botes for more insights on Leadership, Scale-ups and Impact Investment.

One CEO told me directly: “Klaus, you’re spending too much money.” The result: Another year of legacy, highly customized and disjointed ERP systems. Every executive decision carries invisible weight. The trade-offs are rarely discussed in the boardroom presentation. Here’s one that still keeps me up: You’re leading IT for a growing MedTech company. Years of acquisitions have left you with multiple ERP systems that don’t talk to each other. Manual workarounds everywhere. Excel spreadsheets bridging the gaps. Your teams are burning out maintaining systems that should have been retired five years ago. You build the business case. You show the operational cost, the untapped efficiency opportunities, the quality risk, the competitive disadvantage. You present the path forward. The CFO looks at the budget. The CEO looks at the timeline. “We can’t afford the disruption right now. The complexity is too high. You’re spending too much money.” So you manage the legacy systems for another year. And another. You watch competitors move faster because their technology actually works. You see talented people leave because they’re tired of 12-14 hour workdays and fighting broken tools. I’ve been in this position multiple times. Here’s what 15 years in executive IT positions has taught me: The cost of doing nothing always exceeds the cost of doing something. You just pay for it differently. Instead of a planned investment with a timeline and an ROI, you pay in operational inefficiency, quality incidents, lost talent, and missed market opportunities. My recommendation after doing this across the US, Europe, APAC, and Latin America: Treat ERP strategy like you treat capital equipment decisions. You wouldn’t run manufacturing on machines from three different acquisitions that can’t communicate. You wouldn’t tell your operations or quality teams to make do with duct tape and spreadsheets. Yet we do exactly that with enterprise systems and wonder why digital transformation fails. Stop asking “Can we afford this?” Start asking “Can we afford to keep operating like we are currently?” and "Which decisions do we need to make to support the commercial growth plans that we have?" Because the gap between what your systems can do and what your business needs to do is growing every quarter. Your competitors are closing that gap. Your best people are leaving to join companies that have. In regulated industries like MedTech, your ERP system is more than just software. It’s your quality system, your compliance framework, your operational backbone. When it breaks, everything breaks. Have you been there? How do you make the case for necessary technology investment when the C-suite sees complexity and cost instead of capability and competitive advantage? #GlobalLeadership #ExecutiveDecisions #ERPStrategy #DigitalTransformation #MedTech #ITLeadership #FractionalCIO

𝗪𝗵𝘆 𝗱𝗼 𝘀𝗼 𝗺𝗮𝗻𝘆 𝗘𝗥𝗣 𝗺𝗶𝗴𝗿𝗮𝘁𝗶𝗼𝗻𝘀 𝗳𝗮𝗶𝗹? 𝗕𝗲𝗰𝗮𝘂𝘀𝗲 𝗰𝗼𝗺𝗽𝗮𝗻𝗶𝗲𝘀 𝘁𝗿𝗲𝗮𝘁 𝗶𝘁 𝗹𝗶𝗸𝗲 𝗮 𝘀𝗶𝗺𝗽𝗹𝗲 𝘀𝗼𝗳𝘁𝘄𝗮𝗿𝗲 𝗽𝗮𝘁𝗰𝗵, not the business transformation it truly is. Listening to my network, there seems to be a rush to complete ERP migrations, as fast as possible, with SAP S/4HANA plans driving most of it. But an ERP system is more than just an IT upgrade. It’s a chance to redesign how your business operates and build a solution architecture that supports agility and innovation. While necessary, these migrations often become redundant without proper alignment to business goals. Something, I've seen happen! Here some get rights to consider: ◉ 𝗔𝗹𝗶𝗴𝗻 𝗯𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗮𝗻𝗱 𝘁𝗲𝗰𝗵 𝗴𝗼𝗮𝗹𝘀 Ensure that IT and business leaders are on the same page. ERP systems serve broader business objectives, such as innovation, improving procurement strategies, and enhancing supplier relationships. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗼𝘂𝘁𝗰𝗼𝗺𝗲𝘀, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝘁𝗼𝗼𝗹𝘀. Instead of getting caught up in the technology itself, be clear about the business benefits you'd like to achieve. New ERP functionality can be of support to achieve goals like efficiency, cost reduction, and agility. ◉ 𝗦𝗶𝗺𝗽𝗹𝗶𝗳𝘆 𝘄𝗼𝗿𝗸𝗳𝗹𝗼𝘄𝘀 𝗮𝗻𝗱 𝗽𝗿𝗼𝗰𝗲𝘀𝘀𝗲𝘀 𝗲𝗻𝗱-𝘁𝗼-𝗲𝗻𝗱 Don't just migrate complex, outdated processes but streamline them end-to-end. Reevaluate processes for efficiency and desired outcomes. ◉ 𝗜𝗻𝘃𝗲𝘀𝘁 𝗶𝗻 𝗰𝗵𝗮𝗻𝗴𝗲 𝗺𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗶𝗻 𝘁𝗿𝗮𝗶𝗻𝗶𝗻𝗴 ERP migrations often fail due to poor user adoption. Beyond training, invest in communication & ongoing support showing the value and relevance of the system to users. ◉ 𝗜𝗻𝘃𝗼𝗹𝘃𝗲 𝗰𝗿𝗼𝘀𝘀-𝗳𝘂𝗻𝗰𝘁𝗶𝗼𝗻𝗮𝗹 𝘁𝗲𝗮𝗺𝘀 ERP impacts every area of the business, so cross-team collaboration is essential. Involve stakeholders from finance, procurement, IT, and operations ensures the system meets everyone’s needs. ◉ 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝗱𝗮𝘁𝗮 𝗾𝘂𝗮𝗹𝗶𝘁𝘆 - 𝘄𝗶𝘁𝗵𝗼𝘂𝘁 𝗰𝗼𝗺𝗽𝗿𝗼𝗺𝗶𝘀𝗲 An ERP system is only as good as the data it processes. Ensure that data is clean, consistent, and reliable before migration. Dirty or incomplete data is one of the biggest challenges post-go-live. ◉ 𝗣𝗿𝗶𝗼𝗿𝗶𝘁𝗶𝘀𝗲 𝗦𝘆𝘀𝘁𝗲𝗺 𝗳𝗹𝗲𝘅𝗶𝗯𝗶𝗹𝗶𝘁𝘆 𝗮𝗻𝗱 𝗖𝗼𝗺𝗽𝗼𝘀𝗮𝗯𝗶𝗹𝗶𝘁𝘆 Choose an architecture which allows for future-proofing and integration of new features, scalability and integration. Business models evolve, and your ERP must evolve with them." ◉ 𝗦𝗲𝘁 𝗿𝗲𝗮𝗹𝗶𝘀𝘁𝗶𝗰 𝘁𝗶𝗺𝗲𝗹𝗶𝗻𝗲𝘀 - 𝗶𝘁'𝘀 𝗻𝗼𝘁 𝗴𝗼𝗶𝗻𝗴 𝘁𝗼 𝗯𝗲 𝗾𝘂𝗶𝗰𝗸 𝗶𝗳 𝘁𝗿𝗮𝗻𝘀𝗳𝗼𝗿𝗺𝗮𝘁𝗶𝘃𝗲 Don’t rush an implementation. ERP migrations are complex and require time to integrate properly. A phased approach allows for troubleshooting and mitigates a risk for failure. ❓Any other "get rights" i missed and you would add from your experience. #erp #businesstransformation #migration #sap4hana

 “Just send an email.” It looks like a one-liner: await sendEmail(to, subject, body); But in production, that line explodes into a full subsystem. Here’s what you actually end up building 👇 1. Reliability - never send inline Sending directly inside a request works… until latency spikes or the provider times out. You decouple it using a queue (Kafka, SQS, or RabbitMQ) -> a background worker processes sends. Each message gets a unique message_id for idempotency, retries use exponential backoff, and you persist status = pending/sent/failed. 2. Deliverability - “sent” != “delivered” Your API logs “200 OK,” but user didn't get it. You need webhooks from SES/SendGrid to capture delivered, bounced, or spam events. Those callbacks update your DB, mark bad addresses inactive, and feed a delivery analytics dashboard so you actually know what happened. 3 Spam filters & domain reputation You can write the best emails, and still end up in spam if you skip the basics: Set up SPF, DKIM, and DMARC. Warm up new domains gradually (start with low send volume). Use a dedicated sending domain (e.g., mailer.myapp.com) and separate IPs for transactional vs marketing. Without this, your whole app’s communication pipeline can get blacklisted overnight. 4 Personalization at scale You’re not just sending static HTML. Each email has dynamic placeholders ({{user.name}}, {{order.id}}), localized text, and sometimes attachments. You pre-render templates (Liquid/MJML), cache HTML in Redis, and bulk fetch user data to avoid DB thrash. At high volume, even template rendering becomes a performance bottleneck. 5 Observability & throttling At scale, email providers rate-limit you. You’ll need token-bucket throttling, multiple provider fallbacks, and metrics (Prometheus/Grafana) for latency and bounce trends. When one region hits its SES quota, your system should automatically failover to another provider without losing events. That “forgot password” email that lands in 2 seconds? It’s backed by queues, workers, webhooks, templates, cryptographic signatures, and deliverability tuning.