Ask HN: PG's 'Do Things That Don't Scale' manual examples?

Article summary

The article discusses Paul Graham's essay 'Do Things That Don't Scale' and asks for examples of manually doing things that will later be automated. The essay mentions Stripe manually onboarding startups as an example. The goal is to understand how startups can apply this principle in their own businesses. By doing things that don't scale, startups can focus on solving real problems and iterate towards a scalable solution.

Main themes

• doing things that don't scale
• manual vs automated processes
• startup growth and iteration
• customer feedback and support
• scalability and efficiency
• lean startup principles

What commenters say

• Manually configuring user preferences can be more efficient than building a UI, especially in the early stages of a startup.
• Having an internal UI for configuring user preferences is essential for efficient customer support and feature management.
• Not having a preferences UI can provide an opportunity for customer feedback and control, but may also lead to inefficiencies and scalability issues.
• Using a simple JSON file or database to store configuration data can be a viable alternative to building a complex UI.
• Some startups have successfully used manual processes, such as manually signing up users or buying products after they are ordered, to test their business models and iterate towards a scalable solution.
• Automating tasks too early can lead to over-engineering and distract from more important tasks, while manual processes can provide valuable feedback and insights.
• The decision to automate or manualize tasks depends on the specific needs and goals of the startup, and there is no one-size-fits-all solution.
• Manual processes can be used to test hypotheses and validate business models, allowing startups to iterate and improve their products and services.