do things that dont scale examples
"Do things that don’t scale" is a concept popularized by startup guru Paul Graham. It means that in the early stages of a startup, you should focus on manual, hands-on efforts to acquire customers and build your product, even if those methods aren’t sustainable when your company grows large. The idea is to prioritize growth and deep customer understanding first, then automate or scale later.
Here are some classic examples of "do things that don’t scale":
- Manually Onboarding Users
- Personally guiding each new user through your product setup to ensure they get value.
- Example: Airbnb founders personally meeting hosts to help take professional photos of their listings.
- Hand-Editing Content or Listings
- Manually curating or creating content for your platform before automating content generation.
- Example: Early Wikipedia editors manually organizing pages.
- Direct Outreach and Relationship Building
- Sending personalized emails or making phone calls to potential customers or partners.
- Example: Early Dropbox founders emailed people who shared their files to acquire beta users.
- Providing Exceptional, White-Glove Customer Support
- Offering personalized, detailed support to your first customers to build loyalty and gather feedback.
- Example: Zappos famously provided outstanding customer service that went well beyond typical industry standards.
- Manual Quality Control
- Personally checking each product or service delivery to ensure quality.
- Example: Etsy sellers personally packaging and writing thank-you notes to customers.
- Customizing Product for Key Customers
- Making product modifications based on direct user requests to fit their needs exactly.
- Example: Early startup founders customizing software features for their first few customers.
- Hosting In-Person Events or Meetings
- Meeting with users or clients face-to-face to understand pain points and build trust.
- Example: Founders of a B2B startup conducting in-person demos and workshops with initial clients.
These strategies are labor-intensive and not viable at scale but help startups deeply understand their users, create a great product, and establish initial growth. Once the startup grows, processes and automation can replace these manual efforts.
Okay, let's brainstorm some classic "do things that don't scale" examples, categorized for clarity. This concept, popularized by Paul Graham of Y Combinator, is about prioritizing early customer acquisition and feedback through manual, often inefficient, processes that wouldn't be sustainable in the long run. It's about learning what works and building a foundation.
1. Direct & Personalized Customer Onboarding/Support:
- Manually Onboarding Every User: Instead of relying on automated tutorials or documentation, personally walk each new user through the product. This could involve a video call, screen sharing, or even in-person assistance (if feasible). You learn their pain points and what they actually need.
- Personalized Email Responses: Responding to every customer support email with a thoughtful, personalized answer, even if it takes significant time. Avoid canned responses as much as possible. Show genuine empathy and try to solve their unique problem.
- Proactive Outreach: Instead of waiting for users to complain, proactively reach out to them (especially early adopters) to ask how they're doing, what they like, and what they're struggling with.
- "Concierge" MVP: Instead of building a fully automated product, manually fulfill the core service. Imagine a food delivery app where you personally pick up the food and deliver it for the first few weeks. This validates the demand before you invest in the tech.
2. Manual Customer Acquisition & Outreach:
- Going Door-to-Door (Figuratively or Literally): For a local business, this could be physically visiting potential customers. For an online service, it could be individually reaching out to people who fit your target audience on social media, forums, or relevant online communities.
- Hand-Picking Early Adopters: Instead of launching to the masses, carefully select a small group of ideal customers and give them exclusive access, early discounts, or personalized attention.
- Attending Industry Events (even if they seem small): Actively networking and engaging in conversations, even if the immediate ROI isn't clear. Focus on building relationships and understanding the market.
- Writing Personalized Notes/Gifts: Sending handwritten thank-you notes or small, thoughtful gifts to early customers or influencers. This creates a lasting impression.
- Directly Sourcing Content: Instead of relying on user-generated content, initially create the content yourself (blog posts, tutorials, demos) to set the tone and quality.
3. Manual Product Development & Feedback:
- Building Features Based on Individual Customer Requests: Instead of prioritizing features based on a grand roadmap, prioritize the features that your most vocal early adopters are asking for. This ensures you're building something people actually want.
- Shadowing Users: Observing users as they interact with your product (or a prototype) to understand their behavior and identify pain points. Don't just ask them what they want; watch them.
- "Wizard of Oz" Testing: Creating the illusion of a fully automated feature, but manually fulfilling the back-end tasks. For example, an AI-powered recommendation engine that is actually being curated by a person.
- A/B Testing with Small Sample Sizes (Qualitative Focus): While statistically insignificant for large-scale decisions, running A/B tests with small groups of users and focusing on the qualitative feedback can be valuable for early product iteration. Understand why people prefer one option over another.
- Prototype First, Code Later: Before writing any code, create detailed prototypes (using tools like Figma, Balsamiq, or even paper) to test the user experience and gather feedback.
4. Operational Inefficiencies for Learning:
- Manually Processing Orders: Even if you plan for an automated system, begin by manually processing orders. This helps you deeply understand the entire fulfillment process, from order entry to shipping.
- Doing All the Sales Calls Yourself (as the Founder): Even if you plan to hire a sales team, the founder should initially handle all the sales calls. This provides invaluable insights into customer needs, objections, and the sales process.
- Tracking Everything Manually: Using spreadsheets or other manual methods to track key metrics like customer acquisition cost, churn rate, and revenue. This forces you to understand the data and how it's generated.
Why Do These Things?
- Deep Customer Understanding: It forces you to truly understand your customers' needs, pain points, and motivations.
- Rapid Iteration: You can quickly adapt your product based on direct feedback.
- Building a Strong Foundation: You create a loyal base of early adopters who will champion your product.
- Validation of Assumptions: You can test your assumptions about the market and your product before investing heavily in scaling.
- Differentiation: In a crowded market, personalized attention can be a significant differentiator.
Important Considerations:
- Know When to Scale: The goal isn't to always do things that don't scale. It's about using them strategically in the early stages. Once you've learned enough and validated your product, you need to start automating and scaling efficiently.
- Document Everything: Carefully document the processes you're using, the feedback you're receiving, and the decisions you're making. This will help you when it's time to scale.
- Focus on the Core Value: Make sure the things you're doing that don't scale are directly related to delivering the core value proposition to your customers. Don't waste time on things that don't move the needle.
In short, "doing things that don't scale" is a strategy, not a permanent state. It's about putting in the hard work upfront to build a solid foundation for future growth. Good luck!
"Do things that don't scale" is a concept popularized by Paul Graham, co-founder of Y Combinator, in his essay on startup growth. It refers to the idea that early-stage startups should focus on manual, resource-intensive, or non-scalable activities to learn about their customers, validate their product, and achieve initial growth before worrying about efficiency or automation. The goal is to prioritize speed, customer feedback, and traction over building perfect, scalable systems from the start.
Here are some examples of "doing things that don't scale" in the context of startups or small businesses:
1. Manually Onboarding Customers
- Instead of building an automated onboarding system, founders might personally reach out to early users, guide them through the product, and answer their questions one-on-one.
- Example: Airbnb founders manually helped early hosts take professional photos of their listings to improve the quality of the platform. This was time-consuming but helped build trust and attract more users.
2. Hand-Delivering Products or Services
- Physically delivering products or providing services yourself to understand customer pain points and logistics.
- Example: The founders of DoorDash initially delivered food orders themselves to test the demand for a food delivery service and learn about restaurant partnerships and customer needs before building a scalable delivery network.
3. Cold Emailing or Direct Outreach
- Personally sending cold emails, making phone calls, or meeting potential customers face-to-face to acquire early users.
- Example: Many B2B startups have founders cold-emailing or LinkedIn-messaging potential clients to secure their first few deals, even if it’s not an efficient long-term strategy.
4. Manually Curating Content or Inventory
- Instead of using algorithms or automated systems, manually selecting or creating content, products, or recommendations for users.
- Example: Early on, Pinterest founders manually curated pins and boards to ensure high-quality content for their initial users, which helped shape the platform's aesthetic and user experience.
5. Providing White-Glove Customer Support
- Offering highly personalized customer support to early users, even if it takes a lot of time, to build loyalty and gather feedback.
- Example: Stripe founders personally handled customer support inquiries in the early days, directly engaging with developers to solve their payment integration issues and improve the product.
6. Recruiting Users One-by-One
- Manually recruiting users or communities instead of relying on scalable marketing channels like ads.
- Example: Reddit’s founders created fake accounts and posted content themselves to simulate activity and attract real users to the platform in its early days.
7. Customizing Solutions for Early Clients
- Tailoring your product or service to meet the specific needs of your first few customers, even if it’s not a scalable approach.
- Example: Many SaaS startups build custom features or integrations for their first enterprise clients to secure a deal, even if those features might not be relevant to a broader audience.
8. Hosting In-Person Events or Meetups
- Organizing small, in-person events to build a community or gather direct feedback, even though it’s not an efficient way to scale.
- Example: Early fitness apps or local service startups often host meetups or workshops to engage with their initial user base and build word-of-mouth.
9. Manually Processing Transactions or Operations
- Handling backend operations by hand instead of automating them to save time and resources early on.
- Example: Groupon started by manually creating and emailing daily deals to subscribers before building an automated platform for merchants and customers.
10. Directly Asking for Feedback
- Personally reaching out to users via email, phone, or in-person interviews to understand their needs and improve the product.
- Example: Dropbox’s founder, Drew Houston, personally talked to early users and even watched them use the product to identify usability issues before scaling the team or marketing efforts.
Why Do Things That Don’t Scale?
- Customer Insights: Direct interaction helps you understand customer problems deeply.
- Validation: Non-scalable methods can prove whether there’s real demand for your product before investing in automation.
- Speed: Manual processes can be faster to implement than building complex systems.
- Relationships: Personal outreach builds strong relationships with early customers, turning them into advocates.
While these tactics are not sustainable in the long run, they are critical for getting a startup off the ground. Once you’ve achieved product-market fit and gained traction, you can invest in automation, scalability, and efficiency. The key takeaway is to prioritize learning and growth over perfection in the early stages.
💡 Try this comparison yourself:Compare AI models side-by-side on SNEOS
Analysis
This comparison demonstrates the different approaches each AI model takes when responding to the same prompt. Here are the key differences observed:
Response Characteristics
ChatGPT: Provides a direct response with 26 sentences.
Gemini: Provides a detailed response with 56 sentences.
Grok: Provides a detailed response with 42 sentences.
Key Takeaways
- Each model brings unique strengths to this type of query
- Response styles vary significantly between models
- Consider your specific use case when choosing between these models
Try This Comparison Yourself
Want to test these models with your own prompts? Visit SNEOS.com to compare AI responses side-by-side in real-time.
This comparison was generated using the SNEOS AI Comparison ToolPublished: October 03, 2025 | Models: ChatGPT, Gemini, Grok