DEV Community: Christian Ruiz

The Startup Freelance Contract: 5 Clauses That Save You From Getting Burned

Christian Ruiz — Sun, 04 Oct 2026 07:19:59 +0000

You land a contract with a promising startup. Two weeks in, the founder says: "Hey, we'd love you to also handle the landing page copy." Three weeks in: "We're raising — would you take part of your fee as equity?" Then the budget runs dry and the project is cancelled with 40% of your work unpaid.

Generic freelance contract templates don't cover any of this. They assume a stable client with a stable scope and a stable budget — the exact opposite of an early-stage startup. If you work with startups, your contract needs to be built for startup-shaped risk. Here are the five clauses that matter most.

1. Equity compensation terms

Startups love offering equity instead of cash. It's a legitimate option — but only if the terms are concrete. A contract that says "contractor may receive equity" is worthless. Your contract should specify:

The exact number of options or the percentage of the company, not a vague "fair share"
Vesting schedule (e.g. 4 years, 1-year cliff) and when the clock starts
Exercise price and what happens on acquisition or termination
That equity is in addition to, not instead of, a baseline cash rate

If a founder can't put numbers on the equity, treat the offer as marketing, not compensation.

2. Scope fluidity clause

At a startup, the ask changes weekly. The fix isn't to ban changes — it's to make them cost something. A scope clause for startups should include a small buffer of included revisions (say, two rounds), then require a change order for anything beyond. New feature? New page? That's a change order. This clause is what lets you say "yes" without resentment.

3. Startup-appropriate IP terms

Investors will ask the startup about IP ownership, and the startup will ask you to sign over everything you create. That's usually fine — but the clause should (a) cover only work product, not your pre-existing tools and frameworks, and (b) state that payment is a condition of the IP transfer. No payment, no transfer. That last sentence is the one that keeps invoices honest.

4. Milestone payment structure

Startup cash flow is lumpy. The fix is milestone-based payments sized to the work, not a single balloon payment at the end:

Upfront deposit (30–50%) before work starts
Milestone payments tied to deliverables you control, with clear acceptance criteria
Short payment terms (Net 7–14, not Net 30–60) — startups can pay fast when they want to
A late-fee or pause-work clause that triggers automatically

Milestones protect you twice: you get paid as you go, and you always know exactly how much of the project is done.

5. Fair cancellation terms

Startups pivot, run out of runway, or get acquired — and the project ends. A fair cancellation clause pays you for work completed to the cancellation date, includes a kill fee or minimum engagement, and releases you from the non-compete and exclusivity obligations. It should also say what happens to IP for work you weren't paid for (spoiler: it stays yours).

The goal of a startup freelance contract isn't to be aggressive — it's to be specific. Specificity is what turns a friendly handshake into a relationship that survives the first pivot.

Don't draft this from memory

The Startup Freelance Contract Pack ($7) puts all five of these clauses — and the ones that support them — into a professional contract you can edit and reuse. Equity terms, scope fluidity, IP, milestone payments, and fair cancellation, all written for the startup world, in PDF and editable DOCX.

One contract that knows the difference between a startup and a corporation will save you more than $7 the first time a founder asks you to "just also do the QA."

This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.

How to Price Your Freelance Work When Your Client Is a Startup

Christian Ruiz — Sun, 04 Oct 2026 07:19:47 +0000

Pricing is the hardest part of freelancing, and startups make it harder. They need quality work but they're counting every dollar. They'll compare your rate to "what we'd pay a full-time hire" while ignoring that you come without equity, benefits, or a desk. So how do you land on a number that works?

Start with your floor, not your ceiling

Before you negotiate with anyone, know your minimum viable rate. This is the number where taking the work is still worth it — not your dream rate, but the one where you're not losing money or sanity. Calculate it using our freelance pricing calculator or use this formula:

Your floor rate = (Desired annual income ÷ 52 weeks) ÷ billable hours per week × experience multiplier

If you want $100K/year working 30 billable hours/week with 5 years of experience: ($100,000 ÷ 52) ÷ 30 × 1.3 = roughly $83/hour. That's your floor. Anything below that and you'd be better off with a salaried job.

Add the startup premium

Working with startups carries extra overhead that corporate clients don't:

Context switching: You're not just designing or coding — you're learning their domain, their customers, and their product from scratch, often with poor documentation
Payment risk: Startups have higher non-payment and late-payment rates than established companies
Scope volatility: What you sign up for in January is rarely what you deliver in March
Relationship management: Founders are often first-time clients who've never managed contractors

A healthy startup premium is 10–25% above your normal rate. If you'd charge an agency $100/hour, charge a seed-stage startup $110–125/hour.

Offer startup-friendly structures

The number isn't the only lever. Startups care about cash flow, and you can use that to your advantage:

Project-based pricing: Quote a flat fee with clear deliverables. Startups love predictable costs, and you can build the startup premium into the project price without having the hourly rate conversation.
Retainer with a discount: Offer a 10–15% discount for a 3-month retainer commitment. You get income stability; they get a better rate. Both win.
Milestone payments: Break a $10K project into four $2.5K payments. Easier on their cash flow, lower risk for you, and no awkward end-of-project invoice.
Mixed cash-equity deals: If the startup is interesting and you believe in it, consider 70–80% cash + 20–30% equity. But only after you've verified the equity is real (see our post on equity vs cash).

Red flags on pricing calls

When a startup client pushes back hard on your rate, pay attention to how they push back:

"We can't afford that right now, but once we raise…" → They're asking you to finance their company. Unless the equity is real and documented, pass.
"Our other freelancers charge half that" → Either you're overpriced for the market, or they're hiring juniors and expecting senior output. Ask to see the work of those other freelancers before you adjust.
"We'll make it up to you on the next project" → No they won't. The first project sets the relationship anchor. If they can't pay fairly now, they never will.

The real test: are you excited?

Money matters, but so does the work. If the startup is building something genuinely interesting and the team is sharp, it's okay to price at the lower end of your range. Interesting projects build your portfolio, grow your network, and open doors to better-paying work. Just make sure the contract protects you (see our Startup Freelance Contract Pack for the clauses that matter).

At the end of the day, the right price is the one where you'd still feel good about the work on a Friday afternoon — even if the founder just asked for "one more small revision."

This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.

Scope Creep Survival Guide: How to Handle It Without Losing the Client

Christian Ruiz — Sun, 04 Oct 2026 07:19:38 +0000

Scope creep is the #1 complaint in freelancing, and it's especially bad with startups. Founders are optimists — they genuinely believe "just one more small thing" won't take long. And sometimes it doesn't. But over a 3-month engagement, those small things add up to weeks of unpaid work. Here's how to handle it.

Why scope creep happens with startups (it's not malice)

Most startup scope creep isn't deliberate exploitation. It happens because:

The founder is learning what they need in real time — they genuinely didn't know they'd need a dashboard when they hired you for the website
There's no "product manager" filtering requests — you're hearing every idea directly from the founder
Startups operate on speed, and "just do it" feels faster than "let me write a change order"
The contract is vague about what's included, so everything feels like it could be included

Understanding this changes the conversation from "you're taking advantage of me" to "we need a process for this" — which is much easier to have.

Strategy 1: Build scope fluidity into the contract upfront

The best time to handle scope creep is before it happens. Your contract should include a scope fluidity clause that:

Defines what IS included (the initial scope in Exhibit A)
Includes a small revision buffer — say, two rounds of feedback and minor adjustments per deliverable
Specifies that anything beyond the buffer requires a written change order with an associated fee
Makes it clear that change orders require mutual agreement — you're not obligated to accept every addition

The Startup Freelance Contract Pack includes this clause pre-written. When a founder asks for something new, you reference the clause — not as a "gotcha," but as the process you both agreed to.

Strategy 2: Say yes with a price tag, not no with a reason

The worst response to scope creep is: "That's not in the contract." It feels confrontational and shuts down momentum. Instead, try:

"I'd love to add that. It's outside the initial scope, so here's what the addition would look like — about X hours at our rate, or Y as a flat add-on. Want me to write up a quick change order?"

This reframes the conversation: you're not refusing the work, you're providing a clear path to get it done. Founders respect this — they make cost-benefit decisions all day, and they understand that more work costs more money.

Strategy 3: Track and name the extras

When a founder asks for something small and you decide to do it without a change order (yes, sometimes you should), name it. Send a quick note:

"Just wrapped up the extra animation you mentioned — no charge for this one. I've logged it so we both know what's included versus the original scope."

This does three things: it builds goodwill, it prevents the "but you did the other thing for free" precedent from expanding indefinitely, and it subtly reminds the founder that scope is being tracked.

Strategy 4: Know when scope creep is actually a good thing

Not all scope creep is bad. Sometimes a founder asks for something that genuinely makes the project better — and doing it positions you for more work, a longer engagement, or a strong referral. The question isn't "is this in scope?" but "does doing this serve my interests?"

A good rule of thumb: if the extra work is small (under an hour), makes the deliverable better, and builds goodwill with a client you want to keep, just do it. Just make sure you tell them you're doing it (see Strategy 3).

Strategy 5: Walk away when it's systemic

If a client repeatedly ignores the scope process, treats change orders as suggestions, and expects unlimited revisions, the problem isn't scope creep — it's a bad client. No contract clause can fix a client who doesn't respect boundaries. Finish the current milestone, get paid, and politely decline the next engagement. Your time is worth more than managing someone else's inability to plan.

This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.

Equity vs Cash: When Should a Freelancer Accept Startup Stock?

Christian Ruiz — Sun, 04 Oct 2026 07:18:47 +0000

You send a proposal for $12,000. The founder replies: "Would you consider taking part of this as equity? We're early but the upside is massive." It's the most common startup negotiation tactic — and one of the hardest to evaluate objectively. Here's how to think about it.

The math: most startup equity is worth $0

Let's be blunt. Roughly 90% of startups fail. Of the 10% that survive, most don't generate meaningful exits for anyone below the C-suite. The expected value of startup equity for a freelancer, on average, rounds to zero. Don't let outlier stories (the designer who got 1% of Airbnb) override the base rate.

This doesn't mean "never take equity." It means treat equity as a lottery ticket, not a paycheck. Your cash compensation should cover your bills. Equity is for the upside — and you should only take it when the upside is plausible.

The framework: 4 questions to ask before taking equity

Is the equity in addition to a fair cash rate?

If the founder is offering equity instead of paying your normal rate, it's a hard no. Equity should be layered on top of a baseline cash rate that works for you. A reasonable split: 70–85% cash, 15–30% equity. If they can't pay at least 70% of your rate in cash, they can't afford you — and they probably can't afford to build the company either.

Do they have real funding or traction?

Equity in a company with $2M in funding, paying customers, and a clear path to revenue is very different from equity in an idea-stage company with no customers and a founder who's "bootstrapping" (translation: has no money). Look for:

Actual revenue (not "we're pre-revenue but the pipeline is strong")
Institutional funding from a known investor (not a friends-and-family round)
Customer traction you can verify (product in market, real users, not "we have 500 waitlist signups")

Equity in a company that checks all three boxes is worth considering. Equity in a company that checks none is a volunteer gig with extra paperwork.

What exactly are they offering — and is it in writing?

"Some equity" is not an offer. Neither is "we'll figure out the details later." A real equity offer includes:

Number of shares or options — or a specific percentage of the company
Fully diluted percentage (what you actually own after all outstanding options/convertibles are counted)
Vesting schedule (standard is 4 years with a 1-year cliff)
Exercise price (for options) and what happens if you leave
All of this in a signed stock option agreement or restricted stock purchase agreement

If the founder can't or won't put numbers on paper immediately, the equity is a negotiation tactic, not a real offer.

Would you invest your own cash in this company?

Taking equity instead of cash is equivalent to investing your fee into the company. If you wouldn't write a check for $3,000 to invest in this startup, don't accept $3,000 worth of equity instead of cash. The bar should be the same.

What to put in the contract

If you decide to take equity, your freelance contract needs explicit equity compensation terms. The Startup Freelance Contract Pack includes a full equity section that covers:

Number of shares/options and vesting schedule
What happens to unvested equity if the engagement ends
Information rights (so you can actually track what your equity is worth)
Tax treatment (and who's responsible for filing 83(b) elections)
A deadline for the startup to deliver formal equity documentation

Don't start the work until the equity section is filled in and signed.

The bottom line

Equity can be life-changing — but only in the rare cases where the startup succeeds, the terms are fair, and you hold enough to matter. Treat it as a bonus, not a substitute for cash. And if a founder gets defensive when you ask specific questions about equity terms, that's a signal about how they'll handle every other difficult conversation in your engagement.

This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.

The Freelancer's IP Guide: What You Keep, What They Get, and Why It Matters

Christian Ruiz — Sun, 04 Oct 2026 07:18:34 +0000

Intellectual property clauses are the most dangerous part of any freelance contract — and the most misunderstood. Sign the wrong IP clause and you could lose the right to use your own code libraries, design templates, or even display the work in your portfolio. Here's what you need to know.

The three buckets of IP in a freelance engagement

Every piece of work you produce falls into one of three categories:

Work Product (the client gets this)

This is what the client hired you to create: the design files, the codebase, the copy, the brand assets. In most contracts, you assign ownership of the Work Product to the client — and that's usually fine. The key protection: IP assignment should be conditional on full payment. No payment = no transfer. This single sentence in your contract prevents the most common startup horror story: delivering the work and never getting paid while the startup uses your output to raise money.

Background IP (you keep this)

These are the tools, frameworks, templates, code libraries, design systems, and methodologies you developed before the engagement — and that you'll use again after it. Background IP is yours, and the contract should say so explicitly. Without this clause, a client could argue that your reusable React component library is now theirs because it was used in their project.

A strong Background IP clause says something like: "Freelancer retains all rights to pre-existing materials, tools, frameworks, and methodologies. To the extent Background IP is incorporated into Work Product, Client receives a non-exclusive, perpetual license to use it — but Freelancer retains ownership."

Portfolio Rights (you need these)

Can you show the work you did? Put it on your website? Mention the client's name? Many freelancers assume the answer is yes. Many contracts say no — or, more commonly, say nothing, which is just as bad when a founder decides they don't want their pre-launch product design on your Dribbble.

A portfolio rights clause should say:

You can display the work in your portfolio after the product launches publicly (or after X months if it never launches)
You won't disclose the client's confidential information
For pre-launch startups, you'll defer portfolio display until their public launch (with a reasonable deadline — say, 12 months)

If a startup refuses to include portfolio rights, ask why. If the reason is legitimate competitive sensitivity, negotiate a delayed display. If the reason is "we don't want anyone to know we used freelancers," that's a red flag about how they'll treat you generally.

The open-source question

If you use open-source components in the client's work, make sure your contract doesn't inadvertently require you to open-source the client's proprietary code. A simple clause: "Freelancer may use open-source components in delivering Services, provided such use does not impose licensing obligations on Client's proprietary code." This protects both of you.

What happens when the engagement ends badly

If the startup runs out of money, cancels the project, or refuses to pay: who owns the work you did? Without a clear IP clause, the answer is legally messy. With one, it's straightforward: if they haven't paid, they don't own it. The IP stays with you until payment clears.

This is why "payment is a condition of IP transfer" is the most important sentence in your contract. Don't remove it, no matter how much the founder says "our lawyer needs clean IP assignment for the investor." Clean IP assignment is fine — after clean payment.

When to get a real lawyer

This guide covers the basics, but IP law varies by jurisdiction and by the type of work. If the engagement is large ($10K+), involves patentable work, or crosses international borders, spend the money on a real IP lawyer. A few hundred dollars of legal review upfront is cheap compared to an IP dispute later.

For most startup freelance work, though, a well-written contract with clear IP terms — like the one in the Startup Freelance Contract Pack — gets you 90% of the protection you need. The remaining 10% is having the confidence to push back when a founder asks you to sign away more than is fair.

This post originally appeared on Freelancer Kit, where you can find the Startup Freelance Contract Pack — contract templates built for freelancers who work with startups.