Staff Augmentation

Embedded specialists on your direction. Time-and-materials billing. The structure when the scope is too uncertain to commit to up front, when your team is building alongside ours, or when headcount constraints leave hiring on the wrong side of the budget line.

What Staff Augmentation actually means.

Staff Augmentation engagements run against an Order Form — a short document executed under a Master Services Agreement. The MSA carries the heavy contractual terms (IP, warranty, termination boilerplate, confidentiality, dispute resolution); the Order Form names the specific resources, their direction, their duration, and their rate. Scope is held by the Client's project plan, not by the contract.

The contractual structure carries the risk differently than Project-Based. There's no fixed deliverable, so there's no fixed price. The Client carries scope risk — what gets built, how long it takes, how the work evolves week to week. Extense carries performance risk — the named resources show up, deliver competent work, meet the agreed performance standards. Termination is typically for convenience with short notice on either side; this is contracted flexibility, not contracted commitment.

Operationally, the resources embed in the Client's team. They attend Client standups, follow the Client's project plan, escalate through the Client's PM. Their work product becomes Client IP under MSA terms. The relationship looks much more like a temporary FTE than a vendor engagement — which is the point. Reporting is light: weekly timesheet against agreed hours, monthly utilization summary, quarterly performance review.

Staff Augmentation is the right shape when the scope is too uncertain or evolving to commit to up front, when the Client wants their team to learn through pair-work, or when headcount and hiring constraints make adding contractors the only available path. It's the wrong shape for bounded deliverables with fixed budgets — those belong in Project-Based — or for ongoing operations with SLA expectations — those belong in Managed Services.

The document.

A fuller version of the procurement instrument introduced on the Services overview. 5 pages, organized the way a procurement reader actually moves through an Extense Order Form — section by section.

Excerpt · Order Form v2.1 · 5 pages

Order Form #XX · under MSA-XXXX-XXXX

Order Form

The staffing instrument executed under your Master Services Agreement.

Page 1 / 5 — Resources & Direction

  • Resource Profile Named roles at named FTE allocation. Example: Senior DITA Information Architect (1.0 FTE) · Senior XML Engineer (0.5 FTE). Skills, seniority level, and specific tooling experience documented for each resource.
  • Direction Resources work to the Client's project plan, attend Client standups, and report to a named Client lead. No fixed deliverable; scope authority is held by the Client's PM, not by the Order Form.

Page 2 / 5 — Term & Rate

  • Term Effective date, minimum term, and extension/notice provisions. Typical range: 3–12 months minimum, extensible by additional Order Form or renewal. 30-day extension notice; 30-day termination for convenience by either party.
  • Rate Hourly rate by role and seniority. Typical range: $200–$300/hr for senior roles; $300–$450/hr for principal-level architects. Billed monthly in arrears against timesheet.

Page 3 / 5 — Reporting & Standards

  • Reporting Weekly timesheet at agreed utilization (typically 40 hr/week per 1.0 FTE). Monthly utilization summary with hours-by-task breakdown. Quarterly performance review with the Client lead.
  • Performance Standards Deliverable quality consistent with seniority level, adherence to Client's project plan and standards, timely communication, and meaningful contribution within the Resource Profile. Replacement provisions named for unsatisfactory performance.

Page 4 / 5 — Mechanics & Termination

  • Equipment & Access Resources supply their own development hardware unless otherwise agreed. Client provides system access, VPN credentials, badges, and any necessary equipment for on-site work. Security onboarding completed before billable hours begin.
  • Termination Either party may terminate for convenience with 30 days written notice. Rate stops on termination effective date; hours worked through termination are billable. For-cause termination by either party with cure period as specified in MSA.

Page 5 / 5 — MSA Reference

  • MSA Reference All terms not named in this Order Form (IP assignment, warranty, confidentiality, dispute resolution, indemnification) are governed by the parent MSA. Each Order Form is a standalone instrument under that framework; multiple Order Forms may run in parallel under one MSA.
1 / 5

How it runs.

  1. 01

    Order Form execution (Week 0)

    Resources named in the Order Form. MSA reference confirmed (or new MSA executed if first engagement). Start date, minimum term, and direction confirmed with Client's lead. Equipment and access provisioning kicked off.

  2. 02

    Onboarding (Week 1)

    Resources join Client standups, gain system access, meet stakeholders, and review the project plan they'll execute against. Weekly timesheet cadence starts. Security onboarding completed before billable hours begin.

  3. 03

    Embedded execution (Weeks 2 → minimum term)

    Resources work to Client's project plan under Client direction. Weekly timesheet against agreed utilization. Monthly utilization summary. Quarterly performance review with the Client lead.

  4. 04

    Extension or transition (Term end)

    Decision point. Order Form renews under the same MSA, terms revised in a new Order Form, or the engagement transitions to a different model — Project-Based for a defined deliverable, Managed Services for ongoing operations.

  5. 05

    Closeout (if not extended)

    Knowledge transfer to remaining Client team. Equipment and access deprovisioned. Final timesheet, final invoice. Order Form closed under MSA; MSA remains in force for future engagements.

What’s in scope, what’s out.

Out-of-scope items are typical defaults. Exact inclusions and exclusions are named in the SOW for each engagement.

Status Item Notes
In Named resources at the named FTE allocation The specific roles, seniorities, and utilization documented in the Order Form's Resource Profile.
In Work performed against Client's project plan and direction Scope authority held by the Client's PM; resources execute against Client priorities and standards.
In Weekly timesheet submission at agreed cadence Hours-by-task detail consistent with the agreed utilization target.
In Monthly utilization summary and quarterly performance review Standard reporting cadence for visibility and performance dialogue with the Client lead.
In Resource substitution upon mutual agreement Replacement with reasonable transition support if performance issues arise or Client circumstances change.
Out Fixed deliverables or acceptance criteria There is no contractual deliverable; scope authority is held by the Client's PM, not the Order Form. For fixed deliverables, see Project-Based.
Out Hours beyond contracted utilization Additional hours require an Order Form amendment. Sustained over-utilization signals the engagement should be re-scoped.
Out Project-management responsibilities Project planning, prioritization, and delivery management are normally held by the Client. Resources execute the plan; they don't author it.
Out Substitution of resources without mutual agreement Both Client and Extense have approval rights on resource changes. Substitutions follow a documented transition process.
Out Work product outside the Resource Profile's agreed role Senior architects don't get redirected to junior tasks; specialist resources don't get pulled into adjacent disciplines without agreement.

When you’d pick this.

  1. “We have the strategy. We need execution capacity.”

    Internal team owns the direction and the project plan. We supply senior specialists who work to your plan, on your timelines, against your standards. Best when you know the work but not the headcount.

  2. “Headcount freeze. We can't hire but we can contract.”

    Contract spend typically lives under a different budget line than FTE additions. An Order Form bridges what hiring can't — especially at fiscal-year boundaries or during reorgs when permanent headcount is locked.

  3. “We want our team to learn from yours.”

    Embedded specialists transfer practical knowledge through pair-work that classroom training and reference documentation don't. The learning is a deliverable too — just not a contractually-named one.

  4. “Scope is going to evolve. We need flexibility.”

    When the work is exploratory or the architecture is being discovered week-to-week, a fixed-scope SOW becomes a change-order treadmill. T&M staffing carries the uncertainty in the rate structure instead of the contractual structure.

When this is the wrong choice.

ANTI-PATTERN

Staff Augmentation for tightly-scoped deliverables.

When the scope is well-defined and the timeline is fixed, Staff Aug has no contractual cost ceiling — billing runs at hourly rates against whatever hours are actually worked. A fixed-fee SOW caps the cost and commits both sides to the scope. Project-Based is the right shape.

ANTI-PATTERN

Staff Augmentation without real Client direction.

Embedded resources need someone to embed under. If the Client's PM is overloaded, absent, or only nominally engaged, Staff Aug devolves into resources guessing what to work on. The Client carries scope risk — if that scope authority isn't real, the engagement drifts.

ANTI-PATTERN

Staff Augmentation as a long-term substitute for hiring.

When Staff Aug runs continuously for 18+ months, it's often signaling a hiring decision deferred too long. The right move is either to convert to FTE (with notice through the MSA) or to transition the work to Managed Services if it's operational in nature.

Recent engagements.

  1. A medical-device team during a year-long CCMS rollout.

    Order Form for one Senior DITA Information Architect (1.0 FTE) and one Senior XML Engineer (0.5 FTE) for 9 months under the Client's existing MSA. Resources embedded in the content engineering team, attending daily standups and reporting to the Client's technical lead. Knowledge transfer to two newly-hired FTEs in the final two months; engagement closed under the original Order Form's term.

  2. A defense contractor's exploratory S1000D architecture work.

    6-month Order Form for one Senior S1000D Architect during early-stage scope discovery. Scope was too uncertain for a fixed-fee SOW; Client wanted optionality on direction. Extended twice (3 months each) as the architecture firmed up. Converted to a fixed-fee Project SOW for the actual build work in month 13.

Anonymized for client confidentiality. Specific scope, contract details, and named outcomes available under appropriate NDA channels.

Related

Sample Content Assessment

Tell us the role you'd embed, the FTE allocation, and the duration you're considering. We'll return a representative Order Form with rate, term, direction, and reporting terms within three business days — ready for execution under your existing MSA, or with a stub MSA if you don't have one in place yet.

Submit a sample →