he first customer contract feels like a milestone, and it is, but it is also a trap dressed as a formality. The trap is treating it as a one-off, a document to get this single deal signed. In reality your first customer contract is a template. You will reuse it, with small changes, for the next fifty deals, which means every decision baked into it gets baked into your business. Getting it roughly right once is worth far more than getting this one deal done fast.
- 01
Scope and payment
What you deliver, what counts as done, and how and when you get paid.
- 02
Liability
The ceiling on what you can be made to pay if the deal goes badly.
- 03
Intellectual property
What the customer gets, and what stays yours.
- 04
Data and termination
Personal data, how either side gets out, notice and renewal.
- 05
Pushback
The clauses a bigger customer will want changed, and your red lines.
What you’re promising, and for how much
Scope and payment sound obvious and are where most disputes start. Be precise about what you are delivering, what counts as done, and what is out of scope, because “that wasn't included” is the most common argument in commercial work. Then the money: how much, when, what happens if they pay late, and whether the price can change.
What happens when something goes wrong
This is the part founders skip and lawyers care about. The limitation of liability clause sets the ceiling on what you can be made to pay if the deal goes badly, and it is the single most important number in the contract. Get it wrong and one unhappy customer becomes an existential problem. Get it right and a bad day stays a bad day rather than becoming a bad year.
Who owns what
If you are building or delivering anything, the contract needs to say clearly what the customer gets and what stays yours. Handing over ownership of your own underlying tools or IP by accident, through loose drafting, is a genuine risk, and it is invisible until it matters. The usual answer is that the customer gets a licence to use what you deliver, while you keep ownership of the underlying product, but that only holds if the contract says so.
Data and the boring-but-mandatory bits
If you touch personal data, and almost everyone does, the contract needs to deal with it properly, because the obligations are not optional. Alongside that sit termination (how either side gets out), and the quiet clauses on notice and renewal that decide whether the contract ends when you think it does.
The clauses your customer will push back on
Worth anticipating, because a bigger customer almost always will. They will want a higher or uncapped liability, broader warranties about what your product does, indemnities if something you supply causes them a problem, and often their own paper instead of yours. None of these are unreasonable to discuss. The point is to know in advance which you can live with and which you cannot, so a negotiation does not turn into a scramble. The first time a customer sends back a marked-up contract is not the moment to work out your own red lines.
The first time a customer sends back a marked-up contract is not the moment to work out your own red lines.
The point of doing this well once
Every one of these decisions becomes your default for future customers. Spend the effort on the template, and every subsequent deal is a quick tailoring job rather than a fresh negotiation from a shaky base. Skip it, and you are re-litigating the same risks with every new customer, on paper that was never built for the job.
The short version
Your first customer contract deserves more care than the deal itself, because it outlives the deal. Building that first solid, reusable version is one of the highest-value things you can do at this stage, and it is exactly the kind of work we take off founders' hands.