Do I need an MSA for a small project?

For a one-off piece, the legal terms can live in a single combined agreement. If you expect more than one phase, an MSA saves you renegotiating confidentiality, IP and liability each time.

What's the difference between an SOW and a scope of work?

People use the terms loosely. 'Scope of work' usually means the description of the work itself; a statement of work is the full document that contains the scope plus deliverables, acceptance, schedule and price.

Who writes the statement of work?

Usually the engineering provider writes it and you review it. On Talent Badger the statement of work follows the proposal and sets the billing terms, with IP assignment built in.

What happens when the scope changes mid-project?

Agree a change order before the extra work starts: what changes, the cost and schedule impact, and written approval. It keeps surprises out of the invoice and the schedule.

When do I own the work?

Product-specific work is yours once it is paid for. The agreement should say so, and every Talent Badger specialist signs an IP assignment before work begins.

Where does the NDA fit?

Before you share confidential details, usually before the discovery call or the proposal. An NDA covers confidentiality only; the MSA later repeats those terms and adds IP, liability and payment terms for the actual work.

Straight Answers

Engineering Proposal vs Statement of Work vs MSA: What Each Document Does

A proposal recommends what to do and why, with options and a price for the first piece. A statement of work (SOW) is the binding scope for one piece of work: deliverables, acceptance criteria, milestones, schedule, price and billing terms. A master services agreement (MSA) holds the legal terms that apply to every SOW: confidentiality, IP ownership, liability and payment terms. You usually read the proposal, sign the MSA once, and then sign one SOW per phase.

Start a project Browse the bench

The proposal: the recommendation

Restates your problem in plain terms, so you can check it was understood.
Recommends an approach and a first piece of work, with alternatives where they exist.
Names who would do the work and what they have done before.
Lists the assumptions behind the price and the questions still open.
It is not a contract. Its job is to help you decide.

The statement of work: the binding scope

Deliverables as artifacts you can check: schematic and layout project, Gerbers, BOM, a tagged firmware release, a test report.
Acceptance criteria for each deliverable, and how long you have to accept or reject it.
Milestones, schedule and billing terms, plus what you will supply and when.
Written non-goals: what this piece of work will not do.
Hardware lines: parts and fabrication priced separately, review rounds stated as a number, and who pays for a respin.

The MSA: the legal terms for every SOW

Confidentiality, IP ownership, warranties, limitation of liability, payment terms, termination and dispute resolution.
Sign it once; each new phase is a new SOW under it, so you don't renegotiate legal terms every time scope changes.
A limitation of liability, often capped at the fees paid, and a carve-out for prototypes and modifications are normal in hardware engineering agreements.

IP and changes

Product-specific work transfers to you once it is paid for: schematics, PCB files, Gerbers, BOMs, firmware source, CAD, drawings and test records.
The engineer keeps their pre-existing tools, libraries and general know-how, and licenses you whatever is built into your deliverables.
Every change in scope gets a short change order: what changes, the cost and schedule impact, and who approved it. No change order, no change.

Red flags in each document

A proposal with one large program price, no assumptions and no smaller first step: the unknowns have been priced as if they were known.
A statement of work whose deliverables are activities ('support firmware development') instead of artifacts you can check at acceptance.
No acceptance criteria, or acceptance that happens automatically after a few days of silence with nothing to test against.
IP that transfers only at the end of the whole program, or not at all until a final payment you may never reach.
No change-order clause, which turns every scope question into a dispute over the invoice.
An agreement with unlimited liability on either side, which usually means nobody has read it carefully.

The order on Talent Badger

Brief or upload at talentbadger.com/start, then a discovery call if you want one.
An NDA first if you need one, then the written proposal with the first fixed piece.
The agreement and statement of work for that first piece, with billing terms set in the SOW. Nothing is billed until it is signed.

Common questions

Generally no. A proposal is a recommendation and an offer to agree terms. The statement of work and the agreement it sits under are what bind both sides.

Describe the project. Talk to an engineer. Get a written scope.