NDAs and SOWs for a Two-Person Studio (Without the Corporate Tooling)

TL;DR A two-person design-and-dev studio only signs a handful of things with clients: a mutual NDA before the pitch, a statement of work per project, and occasionally an IP assignment. You don’t need contract-lifecycle software or a legal team to handle any of it. A reusable SOW template and an e-signature tool that both partners can send from covers the whole job.

You are two people. One designs, one builds, and between you that is the entire company. The work is real and the clients are real, but the operation is small enough that “the legal department” is whoever last read a contract carefully.

That setup is fine. The paperwork a two-person studio actually deals with is short and repetitive, and once you understand the three documents that do most of the work, you can stop treating every new client’s PDF as a puzzle. This article is for the freelance duo running a design or development studio who want to sign client contracts properly without adopting tools built for a 200-person firm.

What paperwork does a small studio actually sign?

Strip away the intimidating stuff and a client engagement usually involves three documents:

A non-disclosure agreement, signed before the client shows you anything sensitive.
A statement of work, which defines the project itself: what you’ll deliver, by when, for how much.
Occasionally an intellectual property assignment, confirming the client owns the finished deliverables once they’ve paid in full.

Repeat clients sometimes add a fourth: a master services agreement (MSA) that sets the standing terms once, so each new project only needs a short SOW instead of a full contract. That’s it. There is no fifth secret document that “real” agencies use and you don’t. A two-person studio and a 200-person firm sign the same kinds of documents; the big firm just signs far more of them.

The rest of this piece walks through each of the three, plus the MSA, with the specific things a designer-and-developer team should watch for.

The NDA: read the definition and the term

Most NDAs land in your inbox from the client’s side, and they’re usually short. The temptation is to skim and sign so you can get to the interesting part. Two clauses are worth actually reading.

First, the definition of confidential information. This clause decides what you’re forbidden to repeat or reuse. A reasonable NDA scopes it to the client’s genuine secrets: unreleased products, internal pricing, customer data, roadmap. An overbroad one defines “confidential information” as basically everything you’ll ever see, which can restrict your ability to show the work in your portfolio later. If the definition is that wide, ask for a carve-out covering the general skills you use on any job, plus any non-confidential final work you’re allowed to display.

Second, the term. Some NDAs bind you for a fixed period after the project ends, commonly two years. Others run indefinitely for trade secrets. Both are normal. What you want to avoid is agreeing to an indefinite blanket obligation on ordinary project details, which is unenforceable in spirit and a headache in practice.

There’s a wrinkle specific to a two-person studio: if you and your partner are separate legal people, the NDA has to let you share the client’s confidential information with each other to do the work. Most templates handle this with a clause permitting disclosure to employees and contractors who need to know and are bound by the same terms. Check that it’s there. If you occasionally bring in a third contractor, that clause matters even more.

One-way versus mutual is the other decision. A one-way NDA puts the confidentiality obligation only on you. A mutual NDA covers both sides. Push for mutual when you can, because you also have things worth protecting, including your pricing and the work you haven’t publicly launched. A mutual NDA does it with a single document, which is less to track.

The SOW: the document that actually protects you

The NDA is mostly for the client’s benefit. The statement of work is the one that covers you. It’s the one document most worth getting right, because it’s what you point to when a client says “I thought that was included.”

A statement of work for a design or development project should pin down six things:

The scope and deliverables, written concretely enough that both sides read them the same way, such as “five-page marketing site, responsive, built in [framework], with a contact form wired to [service].”
What’s explicitly out of scope. This line prevents more disputes than any other. Copywriting, ongoing hosting, third-party plugin licenses, and post-launch support all belong here, so none of them get assumed into the price.
A timeline with milestones tied to client actions too, so a slow round of feedback doesn’t turn into your missed deadline.
Payment terms mapped to those milestones: a deposit up front and a due date for the final amount, with the rest scheduled in between. A third to start is a common opening for a small studio, with the remaining two-thirds due at an agreed milestone and on final delivery.
A revision limit that says how many rounds are included and what an extra one costs. “Unlimited revisions” is how a two-week project becomes a two-month one.
Who owns what, and when. Ownership of the final deliverables should pass to the client once they’ve paid in full, and the SOW should say who keeps the editable source files. That one sentence often removes the need for a separate IP assignment.

You don’t need a lawyer to draft one of these from scratch every time. Build one solid SOW template that covers the six items above, then change the scope and the numbers for each project. That template is the single most useful piece of paperwork a studio can own.

When do you need an MSA on top of the SOW?

For a one-off project, a single well-written SOW is enough. It can carry its own general terms (liability, confidentiality, governing law) and stand alone.

The MSA earns its place once a client comes back. A master services agreement sets the standing terms once: how disputes are handled, liability caps, payment defaults, IP ownership, confidentiality. After that, each new project is a short SOW that references the MSA and only spells out the scope and price for that specific job. For a studio that lands repeat work, this turns the second and third projects with a client into a one-page signature instead of a fresh contract negotiation.

If most of your work is one-and-done, skip the MSA and keep your terms inside the SOW. Adding an MSA you’ll only ever use once is more structure than a two-person studio needs.

Both partners need to be able to sign

There’s a small operational thing that trips up two-person studios. If only one of you can send documents for signature, every NDA and SOW goes out under that person’s name and account, even when the designer is running the project and the developer is offline that week.

That’s a problem for two reasons. Practically, it creates a bottleneck: the client is waiting on a signature and the one person with an account is asleep in another timezone. Legally, it muddies the audit trail, because the record shows a single sender for documents that two different people actually managed.

The fix is for each partner to have their own signing account so sent documents stay attributable to whoever ran the deal. On per-user pricing this is where the math starts to hurt, because a second seat is a second monthly bill for a tool you each touch a few times a month. On a flat-rate plan, the second account is free, which removes the temptation to share one login to save money. (We wrote a whole piece on why per-seat pricing punishes two-person teams if that’s the situation you’re in.)

How do you actually get an NDA or SOW signed?

Printing, signing, scanning, and emailing a PDF back is still how a surprising number of small studios do this. It works, and it’s also slower than it needs to be and leaves you with a flat scan that proves very little if anyone ever questions it.

Electronic signatures solve both. An e-signed NDA or statement of work is legally binding under the ESIGN Act in the US and eIDAS in the EU, the same as a wet signature. The part that matters for a contract is the audit trail: a proper e-signature tool records who signed and when, along with the IP address it came from, and seals the document so later edits are detectable. That record is worth far more than a scanned signature if a scope dispute ever gets serious.

The practical flow for a studio: upload the SOW, drop signature and date fields where they go, send it to the client, and get notified when it’s signed. Both you and your partner sign from your own accounts, the client signs from theirs, and everyone gets the completed copy. No printer involved.

What you can safely skip

The e-signature and contract market is full of tools built for legal departments: contract-lifecycle management platforms, clause libraries, automated redlining, approval-routing workflows, quote-to-cash systems. They’re genuinely useful at a company with a legal team and hundreds of contracts in flight.

At two people signing a few documents a month, that machinery is overhead you’ll pay for and never use. You need somewhere to store your NDA and SOW templates, a way for both partners to send documents for signature, and an audit trail that holds up. That’s the whole list.

If your studio grows into needing routed approvals, CRM-connected proposals, or automated document generation at volume, tools like DocuSign or PandaDoc are built for exactly that, and there’s no shame in graduating to them. Most two-person studios never reach that point.

Where HoloSign fits

We built HoloSign for teams this size. It’s $19/month for unlimited users and unlimited documents, so both partners get their own account, their own audit trail, and full access to upload, place fields, send, and track, with no per-seat math. The free plan covers 5 documents per month with every feature included and no credit card, which is enough to run a light month or test whether it fits your flow.

Every account includes drag-and-drop field placement, multi-party signing so the client and both partners can sign the same document, audit trails with SHA-256 verification, and compliance with the ESIGN Act and eIDAS. For a studio whose signing needs are an NDA at the start of a relationship and an SOW at the start of each project, that’s the shape of tool that fits: enough to be legally solid, not so much that you’re paying for a legal department you don’t have.

FAQ

What documents does a freelance designer and developer need to sign with clients?

Three cover almost everything: a mutual NDA before you see anything confidential, a statement of work (SOW) that defines scope and payment for each project, and sometimes an IP assignment confirming the client owns the final deliverables once they’ve paid. Repeat clients often add a master services agreement so you don’t renegotiate terms every project.

What is the difference between an NDA and a statement of work?

An NDA controls confidential information: what you can’t repeat or reuse, and for how long. A statement of work controls the job itself: deliverables, timeline, price, revision limits, and what happens if the project changes. The NDA keeps the client’s information under wraps, while the SOW is what safeguards your scope and your invoice. Most projects need both.

Should a two-person studio use a mutual or one-way NDA?

Push for a mutual NDA when you can. As a design-and-dev studio you also share things worth protecting, such as your pricing and the unreleased work in your portfolio. A mutual NDA covers both directions with one document. If a client insists on a one-way NDA where only you carry obligations, read the confidentiality definition and term length carefully before signing.

Do both partners in a two-person studio need their own e-signature account?

If both partners send documents for signature, yes. Sharing one login muddies the audit trail, because every request looks like it came from the same person. Separate accounts keep each partner’s sent documents attributable. On a flat-rate plan, adding the second partner costs nothing extra, so there’s no reason to share a seat.

Is an e-signed NDA or SOW legally binding?

Yes. Electronic signatures on NDAs and statements of work are legally binding in the US under the ESIGN Act and in the EU under the eIDAS regulation, the same as ink. What matters is that the tool keeps a tamper-evident audit trail of who signed and when, and the address it came from. Keep the signed copy somewhere both partners can reach it, not in one person’s inbox.