Why you should charge your design partners
Free customers give you politeness. A paid contract gives you everything else.
I’m a big fan of Clarify (the autonomous CRM for startups). They run their entire PLG motion through their own product.
Every signup gets routed automatically — no manual triage, ever.
Freemail? An agent researches and finds their work contact info
Work email? An agent qualifies ICP fit and routes to the right rep based on product activity and credit usage
Personalized outreach goes out automatically. If they reply, a deal is created and updated with the conversation summary.
No manual work. No dropped leads.
Product-Led Geek readers get 5,000 free credits!
I see something often with early-stage founders: they land three or four promising logos by giving their product away because that desire to get some initial traction is so strong, and charging up front feels like it could cost them a deal, and then they wonder why nobody’s using it properly.
But ask a design partner who isn’t paying you to tell you what’s wrong with your product, and they’ll tell you it’s great. Ask one who is, and you’re much more likely to learn something useful. When someone has real financial stakes in the outcome, the dynamic shifts and the tone of the conversation changes. They’ll stop being so nice about it because they have more reason to tell you what’s broken.
Here’s why. “Free” feels like it makes the ask easier, and it does, but it comes with a catch. Free customers don’t complain because nothing is at stake for them - and worse, free terms don’t filter out the people who never had the problem in the first place. You end up with two silent groups that are hard to tell apart:
Good fit potential customers who care but won’t spend political capital on a freebie
Bad fit evaluators who are much less likely to buy
Unfortunately, silence is the worst signal you can get from an early customer, because it’s easily mistaken for satisfaction, and it robs you of the opportunity to learn.
A financial commitment fixes both of these: it screens out the people who never had the problem (bad fit), and it gives the ones who do a reason to be open, vocal, and blunt.
What produces the signal is an obligation to pay. In Inspired, Marty Cagan advocates for commitment but without any upfront charge and I agree. His objection to charging in advance is because it risks turning the relationship into something closer to a vendor/consulting contract, and you end up building a custom solution for whoever’s paying instead of a general product for the market you’re trying to serve.
That’s a definite risk, so a design partner contract should obligate payment aligned with your delivery cadence. Milestones defined as a feature list agreed on day one are the wrong instrument - you’d be locking down the roadmap before you’ve learnt anything, which is the opposite of what a design partner is for. Tie payment instead to the things that hold up as you learn: shipping to them on an agreed rhythm, hitting your response-time commitments, turning up to the review calls.
Here are the four key parts that a good design partner agreement needs:
How long it runs (sixty to a hundred and twenty days is a sensible window)
What triggers payment, and the discounted rate (50-80% off list is a reasonable range, due on your delivery of the agreed milestones)
What you owe them (access, an SLA, some input into the roadmap, maybe early-adopter recognition if appropriate)
What they owe you (a feedback cadence - a biweekly call is a reasonable default, a written testimonial by a fixed date, and case study rights if it goes well)
It’s important to include a clause that’s explicit that you’re building one general product, not a bespoke version for them. That’s what keeps a design partner a partner rather than a client with a support contract.
It should also include what happens at the end. Does the contract convert to list price? Renew at a (potentially lower) discount? End cleanly?
FWIW, none of this is counter to PLG: Design partners aren’t your growth motion. Your free tier or self-serve funnel is for a product that mostly works, aimed at broad adoption. It comes later. Design partners are for a product that doesn’t fully exist yet, aimed at a handful of companies helping you find out what the product should be.
If your design partners are larger companies, another dynamic is introduced. Purchase decisions need approval, so senior leaders and/or finance teams start to get involved. Your design partner users need to justify the cost internally. But despite the temptation to circumvent that with free access, the feedback you can get here can be most valuable. In my experience, customer contacts that are bracing for pushback from their peers go looking for the issues and gaps they’d previously been happy to brush aside, and they bring those to you.
The ideal outcome is feedback like “this is nearly there, but I can’t move forward because X is broken.”
At the end of the day, the commitment is what makes the relationship honest. If a prospective partner won’t sign something with a real financial consequence attached, they probably weren’t your real buyer to begin with.
So here’s what I recommend. Aim for three to five partners you have high confidence are your ICP (rather than twenty loose-fit), because you can’t service more than that properly and targeted depth is the point of these programs. Lead with the obligation, not the discount, when you pitch it. Be clear about your list price, then describe the arrangement and what you need from them in return. And when a partner isn’t delivering signal even though they’ve signed on the dotted line, end it early. The programme has a real cost, which is your time, and a signed contract with no engagement behind it is about as useful as a chocolate teapot.
Book a free 1:1 consultation call with me - I keep a handful of slots open each week for founders and product growth leaders to explore working together and get some free advice along the way. Book a call.
View the State of AI Search for Dev Tools 2026 benchmark report - 126,814 citation records across 1,075 representative tool-evaluation scenarios, 43 developer-tool categories, and five AI search platforms
View your free public Dev Tool AI Market Presence Report - 500+ dev tools across 47+ verticals and growing, all in the Dev Tool AI Search Landscape.
Sponsor this newsletter - Reach over 11,000 founders, leaders and operators working in product and growth at some of the world’s best tech companies including Paypal, Adobe, Canva, Miro, Amplitude, Google, Meta, Tailscale, Twilio and Salesforce.
Thanks again to our sponsor: Clarify
