New: answer a few questions and AI writes your project scope, ready to post.

IT staffing & engagement models

Fixed-scope projects

The vendor delivers an agreed result, on an agreed timeline, for an agreed price.

  • Engagement model
  • Typical engagement: 2–6 weeks

Overview

In a fixed-scope project you describe what you need, usually in an RFP, and the vendor commits to deliver it for a set price. It is common for implementations, migrations, apps and audits.

It gives budget certainty and puts delivery risk on the vendor, but only if the scope is clear. Vague requirements lead to change requests, disputes or quietly cut corners, so a short paid discovery phase first is often the best money you'll spend.

How it works

  1. 1

    Discovery

    Clarify requirements, risks and assumptions.

  2. 2

    Statement of work

    Scope, deliverables, milestones and acceptance criteria.

  3. 3

    Delivery

    Run by the vendor, with regular demos and reports.

  4. 4

    Acceptance

    You test against the agreed criteria, then pay the milestone.

Is it right for you?

Best for

  • Projects you can describe clearly
  • Fixed budgets and approved business cases
  • Comparing vendors like for like in an RFP

Think twice if…

  • The work is exploratory or changes fast
  • You can't commit people to make decisions quickly

Typical engagements

  1. Paid discovery2–6 weeks
  2. Implementation or migration3–9 months
  3. Warranty period4–12 weeks

Typical ranges, not quotes. Scope, data and team size move them most.

Roles commonly staffed

  • Vendor project manager
  • Your product owner
  • Solution architect
Browse available talent

Questions to ask a provider

  1. 1Which assumptions is your price based on?
  2. 2How are change requests priced?
  3. 3What are the acceptance criteria for each milestone?
  4. 4What warranty and support follow go-live?

Ready to staff up?

Browse people available now, or post a request and let vendors come to you.