skip to content
← blog

my clients pay for my products

5 min read

there is a story shape in indie hacking that i have never fit into. you save some money, you quit, you give yourself twelve months, you build until something works or the money runs out.

i have never had that. i have client work. the client work pays for everything, including the products, and it is not going anywhere.

that is a constraint, and it is worth being specific about what it constrains, because it is not just “less time”.

what it actually costs

the hours are the wrong hours. i work a us clock at night. the product hours are whatever is left, and whatever is left is not my sharpest thinking. clients get the good hours because clients are the ones paying. that ordering is correct and it means my own work is built on the tail end of my attention.

momentum breaks. a client incident does not care that you were three hours into something. product work needs consecutive days and consecutive days are the exact thing an agency cannot promise you.

everything takes longer than the plan. not a little longer. multiples. i now assume a personal project takes three times my estimate and i am still wrong in the same direction.

what it buys

i never have to ship something for money. this is the big one and i think it is worth more than the time i lose.

if my products had to pay rent this month, i would have added things i do not believe in. an aggressive upsell. a paywall in front of the thing that makes the product good. an enterprise tier for a consumer app. every one of those is a decision made by a runway, not by a person thinking about the product.

pricing a screen time app at $1 a week only makes sense if you are not desperate. desperate charges $9.99 and dies slower.

i can wait. a product that takes two years to find its audience is allowed to take two years. nothing forces me to kill it at month nine.

i learn on somebody else’s problem and apply it to mine. the security auditing i do for clients is the same auditing that found the holes in my own launches. the infrastructure discipline is the same. the product work and the client work feed each other more than either feeds itself.

the trap i fell into anyway

thinking of the products as the real thing and the client work as the tax.

that framing is poison and i held it for a while. it makes you resent the thing paying your bills, and resentment shows up in the work, which threatens the thing paying your bills.

the honest version: the agency is the business. the products are a bet placed with the profits of a business that already works. if one of them turns into something bigger, great. if none of them do, i still have a business.

that reframe cost me nothing and changed how monday feels.

what i build differently because of this

nothing that needs an audience i do not have. anything social, anything requiring critical mass on day one, is out. i cannot manufacture a network from a spare six hours a week.

nothing with an ongoing operational cost i cannot ignore for a month. if a busy client month means the product goes untouched for four weeks, it has to survive that untouched. that rules out anything with heavy moderation or manual onboarding.

small, opinionated, and useful to me first. every product on this site is something i wanted. that is not a philosophy, it is a survival tactic. when the product has no users yet, being your own user is the only thing keeping you working on it.

if you are in the same position

do not wait for the runway. i think most people waiting to quit are waiting for permission, and the permission never arrives at the amount they picked.

build inside the constraint. it makes you pick smaller ideas, which are the ones a single person can finish anyway.