Questions
Tech & SaaS
The things people actually want to know before starting one of these — money, time, and the parts nobody mentions. 10 researched blueprints sit behind this category.
You can get to a first paying customer without writing code, using no-code builders or by assembling existing tools. What you cannot outsource is knowing the problem better than anyone else. The risky version is paying a developer to build your full vision before a single person has agreed to pay. Sell the outcome manually first, by hand if necessary, then automate the part that is proven.
Price against what the customer currently spends on the problem, in money or in hours, rather than against your costs. Starting too low is the more common mistake: it attracts the most demanding customers, makes support unaffordable, and raising prices later is harder than starting higher. Charge from the first customer. Free users teach you very little.
It happens, and it kills products whose only advantage was that the feature did not exist yet. You survive it by serving a specific group deeply enough that a generic free version does not fit them, and by owning the relationship rather than the feature. If your entire business is one feature a large platform could add in a sprint, treat that as a warning before you build, not after.
Not to start, and raising too early usually costs more than it provides. Funding makes sense when something already works and money buys speed. Before that, it buys a longer runway to build the wrong thing. Small software businesses that charge from day one learn faster than funded ones, because the feedback is money rather than encouragement.
Longer than most founders plan for, because software income builds slowly and then compounds. The first customers are the hardest and the slowest. Judge progress by whether customers keep paying after the first month rather than by signups. Do not set a date by which this must replace your salary; set an amount of time you can afford to spend finding out.
By finding people already complaining about the problem and solving it for them personally, before the product is ready. Communities, forums and support threads are full of stated demand. Early users forgive a rough product; they do not forgive a product that solves nothing. One person paying beats a hundred signups who never log in again.