We landed a $4,000/mo client before we had a product. The last 6 months have been hell.
Last year, we were just two founders with a Figma prototype and a landing page. We reached out to a mid-sized logistics company to do some "customer discovery." They loved the mockups so much they said, "Can you build this for us? We'll pay you $4,000/month to start immediately."
We had zero code written. But we couldn't say no to $48k a year, so we said yes and promised a launch date 60 days out.
That was the start of the worst six months of my life. We didn't just have to build the software; we had to build the entire infrastructure of a legitimate company overnight. We had to scramble to set up SOC2-compliant hosting, write a 20-page legal contract, set up billing systems that could handle enterprise invoices, and build a custom dashboard from scratch in a fraction of the time it actually took.
Because we were rushing, we shipped bugs constantly. Every week, the client would call us furious because a core feature had broken or a report was generating incorrect data. We were working 80-hour weeks just to keep our heads above water and prevent them from firing us. We were essentially held hostage by our own customer.
We survived, and the client is still with us, but the product is held together with duct tape. We spent so much time building custom workarounds for this one client that the core product has zero scalability.
For founders who have experienced this: How do you say "yes" to early revenue without letting the client dictate a timeline you can't actually meet?
Do you ask for a much longer implementation timeline? Do you charge a massive "setup fee" to buy yourself runway? I need to figure out how to set boundaries before we accidentally land another client we can't handle.
Replies
John, I'd charge the setup fee, but not mainly for runway. a decent chunk upfront makes the client treat the timeline as a shared plan rather than your promise, and it gives you a reason to write down exactly what's in scope for launch and what comes after. the duct tape is the real cost here, so I'd also agree in writing which requests become core product and which ones they pay extra for. is the client still asking for custom bits every month?