BusinessJuly 2025·5 min read

Equity, Retainers, and Project Fees: How Technical Partnerships Actually Get Structured

Most founders have no framework for how to compensate a technical partner. Here's how these engagements actually get structured — and the questions you should ask before signing anything.

Z

Zeidex Editorial

zeidex.com

📋PROJECT FEEFixed scopeLow risk🔄RETAINEROngoing workPredictable📈EQUITYLong-term betAligned incentiveALIGN STRUCTURE WITH RISK APPETITE + TIMELINE

One of the most common questions founders ask us at Zeidex is: "How does this work financially?" It's the right question to ask, and the honest answer is more nuanced than most vendors will tell you.

Technical partnership structures fall into a few categories, and each has different implications for your cash flow, your cap table, and your long-term relationship with the partner.

The retainer model

The most common structure for ongoing technical partnerships: you pay a monthly or quarterly fee for a defined scope of work — a certain team size, a certain commitment of hours, a certain set of deliverables. Retainers are predictable for both sides and allow for the kind of deep embedding that makes technical partnerships effective.

The risk for founders: retainer relationships can become expensive if the scope isn't managed carefully, and they can create a dependency if the transition to in-house isn't planned from the start.

The project model

A fixed scope, fixed fee engagement for a specific deliverable — typically an MVP or a defined feature set. You pay for the output, not the time. This structure is good for defined projects with clear requirements and acceptance criteria.

The risk: scope changes are expensive in project models. The incentive for the vendor is to deliver exactly the spec, not to challenge the spec. Make sure your partner is willing to push back on what's being built.

The equity-plus-reduced-fee model

Some technical studios, particularly in the venture studio model, take a small equity stake in lieu of a portion of their fee. This aligns incentives — the studio has skin in the game and is genuinely motivated by the startup's success. At Zeidex, we work with founders on custom structures based on their stage and needs.

The risk: equity arrangements should be approached carefully. Make sure the vesting schedule, cliff, and dilution protections are clearly defined. Get a lawyer to review any equity arrangement before you sign.

What to ask before signing anything

What does success look like, and how is it defined in the contract? Vague deliverables create expensive disputes.

Who owns the code? You should own the IP. Full stop. If a vendor is building your product on your dime, you should own what's built. Make sure this is explicit.

What's the offboarding plan? A good technical partner should have a clear plan for transitioning knowledge and code to your team or a new partner. If there's no offboarding plan, you don't have a partner — you have a dependency.

What happens if the engagement isn't working? There should be a termination clause with reasonable notice periods on both sides. If a partner locks you in with harsh penalties for early termination, that's a signal about the relationship you're entering.

We're happy to talk through structure at Zeidex — no commitment required. The right deal is one that both sides genuinely want to honor.

Ready to build
your company?

Start the Conversation