Everything from

Medium

8 resources from Medium we point founders to, and the questions each answers.

✍️ Essay
Free Beginner

Why we picked it Most founders either stop at two chats with friendly users or interview forever and never ship. Seaman, a UX researcher, gives you a concrete starting formula (begin at 5, add more for complex domains, multiply by personas) and a clear stop signal: when interviews start repeating and stop teaching you anything new, that is saturation and it is time to move. It reframes the real question from a magic number to noticing when you have stopped learning.

The Right Number of User Interviews

From Medium by Mitchel Seaman About a 10 minute read

  • Start around 5 interviews per persona and add more only if the domain is genuinely complex or the users vary a lot.
  • The point to stop is saturation: when new conversations mostly echo what you already heard, more interviews are wasted time.
  • There is no single correct number, so treat any count as a planning tool, not a target to hit before you are allowed to build.
Open medium.com →
Answers How many customer conversations should I do before I start building versus building a rough version to learn faster?
✍️ Essay
✓ Link checked Free Beginner

Why we picked it This is the rare piece that answers the exact question in its title instead of hedging on the generic in-house versus outsource debate. It lays out concrete signals for the switch (steady recurring revenue that can carry salaries, agency budget and deadline slippage, documentation and IP control slipping away) and suggests starting with a small 3 to 6 person core rather than replacing the agency overnight. Treat the revenue thresholds as a starting point to pressure-test against your own numbers, not a rule.

When Should Startups Stop Outsourcing and Build an In-House Team?

From Medium by AlterSquare About a 10 minute read

  • The trigger is usually money and control, not headcount: once recurring revenue reliably covers full-time salaries and you keep losing context to the agency, the math flips toward hiring.
  • Do not switch cold turkey. Bring in a small core (a senior developer or CTO first) and keep the agency on specialized or overflow work while you build capacity.
  • The hidden cost of staying outsourced too long is knowledge and IP control leaking out, so weigh that alongside the visible hourly rate.
Open altersquare.medium.com →
Answers When should I stop using an agency and hire my first in-house developer?
📄 Article
India Free Beginner

Why we picked it India does not have one launch button, so this is a useful starting point precisely because it shows ten real companies (Meesho, ShareChat, Dunzo, Redbus and more) reaching their first buyers through whatever channel actually sat where their users already were. Notice how few of them used a launch platform at all: WhatsApp groups, in-person workshops, travel agents, campus coupons, brand tie-ups. Read it as a menu of distribution moves to copy, not a formula.

How These 10 Indian Companies Got Their First 1000 Customers

From Medium by Harkirat Singh ~10 min read

  • Your first buyers come from the channel they already live in (WhatsApp groups, campuses, existing communities), not from a launch leaderboard.
  • Distribution in India is often physical and relationship-led (workshops, agents, partnerships), so plan for feet-on-ground reach, not just online posts.
  • Ten different companies used ten different first channels, which is the real lesson: pick the one channel that maps to your specific buyer and go deep.
Open medium.com →
Answers How do I launch in India where there's no single 'Product Hunt moment' that reaches Indian founders and buyers?
📄 Article
Free Beginner

Why we picked it This gives you a concrete cold email structure for the exact spot you are in: no case studies, so you lead by asking for feedback and offering early access instead of pitching. It names the customer you actually want first, the early adopter who will trade honest feedback for a first look, and shows how to write to them without pretending to have proof you do not have. Use the three part frame as a starting template, then make it sound like you.

The Anatomy of an Effective Cold Email for Early Adopters

From Medium by Mert Hilmi Iseri About a 10 minute read

  • Target early adopters first: they are willing to try unproven things and will share feedback that later becomes your case studies.
  • Frame the email as a request for feedback or early access, not a sales pitch, which removes the need for logos or traction.
  • Keep it short and specific, opening with something real about the recipient so it reads as a signal to the right person, not a blast.
Open medium.com →
Answers How do I cold email my first ten customers when I have no logos, no traction, and no case studies?
📄 Article
Free Beginner

Why we picked it This is written by a founder who actually ran three different communities on three different platforms and picked each one for a specific reason, not from a features chart. His two-question test (what are your users already comfortable with, and what kind of discussion do you need) maps directly onto the WhatsApp vs Slack vs Discord call. WhatsApp being his default for a low-friction group also lands well for an Indian audience where WhatsApp is where people already are.

Learnings from running communities on Slack, Discord and WhatsApp

From Medium by Adithya Narayanan About a 10 minute read

  • Pick on two things: what your users are already comfortable with, and what the content or discussion actually needs (channels, breakouts, threads).
  • WhatsApp wins when you need no fancy features and want the lowest friction for members; Slack and Discord earn their place only when the discussion structure demands it.
  • The platform is the easy part. Active curation, moderation, and recurring events are what keep a community alive, not the tool you chose.
Open medium.com →
Answers Should I build my community on WhatsApp, Slack, Discord, or Circle for early-stage founders in India?
📄 Article
India Free Beginner

Why we picked it India is the clearest live lab for the free product, hidden revenue layer question: UPI made payments free, so the money moved elsewhere. This piece walks through how apps you use daily actually earn, with local names like PhonePe (transaction fees plus cross selling financial products), CRED (revenue from brands), and PolicyBazaar (data partnerships). It is a grounded starting point for a founder building outside the big startup hubs who wants concrete Indian examples, not just Silicon Valley theory.

Fintech App Monetization Strategies: A Global Perspective with a Focus on the Indian Market

From Medium by Rakesh Bandi

  • The free UPI product is the acquisition layer, and cross selling loans, insurance, and investments is where the margin actually sits.
  • CRED earning from brands and PolicyBazaar from data partnerships show the revenue can be a completely different customer from the free user.
  • Use it as a map of options (subscription, transaction fees, cross sell, data), then dig into any one company's filings for the real numbers.
Open medium.com →
Answers My competitors give the product away and make money on something else. How do I find that hidden revenue layer?
✍️ Essay
✓ Link checked Free Beginner

Why we picked it When your product is half built, the temptation is to give it away and hope revenue comes later. Ash Rust argues the opposite: real money from your first handful of customers is the cleanest signal that you are solving a problem someone actually needs solved now. He walks through a concrete sequence (a free or near free first customer, then deliberately raising the price on customers four and five) so charging becomes a filter, not just a line of revenue.

Startup Sales: How to Charge your First 5 Customers

From Medium by Ash Rust ~8 min read

  • Charging early is a validation test: a customer who pays real money is telling you the problem is worth solving, in a way a polite yes never does.
  • Escalating the price on later customers (roughly 3x what feels comfortable) filters out people who merely like the idea but do not need it yet.
  • Extended low pricing and thin margins quietly hurt the business, so treat the first few deals as learning what people will actually pay, not a permanent discount.
Open ashrust.medium.com →
Answers How should I price my very first paying customers when I have no track record and the product is half-built?
📄 Article
Free Beginner

Why we picked it Every one-off custom feature you say yes to is margin you spend building something one customer wants and everyone else pays to maintain, and this is a working bootstrapped founder writing about how he actually decides. His rule is refreshingly blunt: if only one customer is asking, it is an edge case, and saying yes quietly turns a product company into an underpaid services shop. It is a practical starting point for building a filter, not a script to copy word for word.

How we avoid building the wrong product as a bootstrap startup

From Medium by Clement Bataille About a 7 minute read

  • If a single customer is the only one asking, treat it as an edge case and default to no, not yes.
  • Only entertain a custom build when the customer commits (for example a year) and the feature genuinely fits your product direction.
  • Limited resources are a feature: constraints force you to build only what serves the whole roadmap, which is what protects your margins.
Open medium.com →
Answers What are the most common ways bootstrapped founders accidentally kill their own margins?