Two-track MSAs: one Master Services Agreement, two kinds of work.

The problem with single-track MSAs

A standard Master Services Agreement assumes one shape of work: a defined scope, a defined fee, a defined timeline. The Statement of Work describes what the consultant will deliver. The consultant delivers. The client pays. Both sides understand the deal.

This works for engagements that are actually one shape of work. It breaks the moment a real consulting relationship matures. The client wants the original deliverable plus a question answered next Tuesday plus an introduction to a vendor plus a quick review of something the team produced. Each of these is real work; none of it fits the original SOW. The consultant either does the work for free (eating the value) or initiates a new SOW for every ad hoc ask (eating the relationship) or stops doing the ad hoc work (eating the trust).

The fix is structural, not negotiated. The MSA should anticipate both kinds of work up front and provide a clean billing path for each.

The two tracks

Track A: productized service deliverables. Scope is defined in advance through phased Statements of Work. The deliverable is named. The fee is fixed (or capped) per phase. Acceptance criteria are written into the SOW. The work either passes acceptance or it doesn't. Examples: a website build, a specific integration, a regulatory filing, a custom audit, an onboarding package.

Track B: ad hoc senior hours. Scope is undefined in advance. The client requests time as needed. The fee is billed hourly at a documented rate. Acceptance is implicit (the client either keeps engaging or stops). Examples: questions answered during normal business hours, periodic reviews of work the team produced, vendor introductions, strategic consultations, debugging or troubleshooting.

The single MSA covers both tracks. Each track has its own billing flow and acceptance pattern. The relationship survives transitions between tracks (a productized deployment that finishes leaves Track A but the client may continue under Track B; a Track B relationship that expands into a defined deliverable spins up a Track A SOW).

The language that makes it work

Three sections of the MSA carry the structure.

Section 1.3 (Two-Track Scope). This section declares that the Agreement governs both Track A (defined SOW deliverables) and Track B (ad hoc senior hours). The two tracks are administered separately. Termination of one track does not terminate the other or the Agreement itself.

Section 2 (Compensation). This section breaks out compensation by track. Track A: fees per phase, payment terms, late-payment language. Track B: hourly rate, minimum increment (typically 15 minutes), monthly billing cycle, retainer credit if applicable.

Section 3 (Term and Termination). Termination provisions explicitly preserve the multi-track structure. The Agreement, Track A SOWs, and Track B all have independent termination mechanics. The client can pause Track A while continuing Track B, or vice versa, without renegotiating the underlying Agreement.

Why this beats the alternatives

Versus single-track plus change orders. Change orders are the conventional fix for scope creep. They work for true scope changes (the client wants something fundamentally different than the original SOW) but fail for ongoing ad hoc work. A consultant doesn't issue a change order for "answer my email about the vendor decision"; the friction is too high. So the ad hoc work either happens free or doesn't happen at all.

Versus separate retainer agreement. A separate retainer agreement covering ad hoc work means two contracts, two invoices, two sets of legal language to manage. Most clients (and consultants) consolidate this into one agreement once they realize how much extra paperwork they're carrying.

Versus per-engagement hourly billing. Some consultants try to bill everything hourly to handle the multi-shape problem. This works for some consulting relationships but loses the productized-service positioning entirely. A firm selling a $25K productized deployment cannot bill it hourly without compromising the package's defined-scope value.

The two-track MSA is the structure that lets a consultancy sell both productized services AND maintain ad hoc senior-hours relationships, under one document.

The staged-SOW convention as a partner pattern

Two-track MSAs work best when the Track A side uses staged SOWs rather than single-phase SOWs. The structure: Phase 0 (discovery) → Phase 1 (deployment or first delivery) → Phase 2 (optional follow-on) → and so on. Each phase is its own SOW under the same MSA. The fee for each subsequent phase gets locked at the end of the prior phase, based on real findings, not pre-discovery estimation.

This serves two needs. It lets the consultant price discovery low (because they don't know the deployment fee yet) without underpricing the deployment. It lets the client commit to a small first step without committing to the whole engagement. Both sides have an off-ramp at every phase boundary.

Termination language for staged SOWs: terminating one SOW does not terminate the Agreement, the other SOWs in the same engagement, or Track B. The client can decline to execute Phase 2 after Phase 0 delivers without ending the relationship.

Productized service IP carve-out

For consultancies offering productized services (the same deliverable to multiple clients, customized per engagement), the MSA needs one more piece: an IP carve-out that distinguishes the canonical package from the deployed instance.

The canonical package is the consultancy's Background IP. The deployed instance and any client-specific customization is the client's property. The consultancy retains the right to use lessons learned, anonymized telemetry, and pattern abstractions to refine the canonical package and deploy it to future clients. The consultancy explicitly cannot share client-specific configurations, data, or content with any other client.

Without this carve-out, the consultancy either gives away the canonical package every time it deploys (eating its own IP) or refuses to let clients customize (eating the value of the service). The carve-out threads the needle.

When NOT to use two-track

A single-track MSA is the right choice when:

• The engagement is genuinely one shape of work and won't expand. A one-off audit. A regulatory filing. A defined-scope build.
• The client explicitly does not want an ongoing relationship. Some legal and accounting engagements are scoped this way deliberately.
• The consultant doesn't want to take ad hoc work and prefers the friction of "issue a new SOW every time."

For everyone else (which is most actual consulting relationships once they mature), the two-track MSA is the default that should ship first, with a single-track exception flag for the engagements that truly don't need it.

How Rarefied Earth thinks about this work

The firm's MSA template went from single-track to two-track-default in May 2026 after observing that every active engagement was hitting the change-order friction. The cost of the more sophisticated MSA is one round of attorney review. The savings is hours per month of contract administration friction.

For consultants debating whether to invest in the more sophisticated structure: the value is not in the document itself. The value is in the discipline of separating productized deliverables from ad hoc work at the contractual level, which forces the consultancy to think clearly about what it is actually selling.

Claims to verify before publication

• The "Section 1.3, Section 2, Section 3" structure matches actual MSA conventions (verify against published templates and standard contract law sources).
• Staged-SOW pricing patterns (verify against industry practice and any published consultancy contract guidance).
• IP carve-out language is legally sound across jurisdictions where the consultancy might operate.
• Termination language for staged SOWs actually holds up if tested.
• Specific examples of consultancies running two-track structures publicly (find one or two named references for credibility).

Audience and positioning notes

Same audience as article 2 (pre-formation engagements). Could ship as a paired piece. Reaches solo consultants and prospects evaluating RE's productized services. Lower fit for the construction-tech primary audience but high defensibility from recent pre-formation and active client contract work.

Estimated effort to v1

Four to six hours. Should be reviewed by RE's contract attorney before publication to make sure the legal claims are defensible. Pair with article 2 in publication sequence ("contract structures for consulting" mini-series).