"Dedicated team" defined by what it does not promise
In short
In most software proposals, "dedicated team" promises only that some group of people is assigned to your account. It does not normally promise named individuals, a stated share of their week, exclusivity, or notice before someone is moved. Three artefacts make it verifiable: names in an annex, an allocation percentage, and a substitution notice period.
Key takeaways
- "Dedicated" is a statement of intent, not a commitment; on its own it binds a supplier to nothing checkable.
- The 3 artefacts that make it real: named individuals, an allocation percentage per person, and a notice period before substitution.
- Partial allocation is often the right answer — a specialist for 3 weeks beats a generalist for 3 months — but it has to be stated, not implied.
- A supplier that will not put an allocation number in writing is telling you the number is variable.
- Score staffing as artefacts present or absent, not as a rating out of 5 on how convincing the team slide looked.
The phrase means a supplier intends to keep a group of people pointed at your account. It is a statement of intent, and it is usually sincere. What it is not is a commitment anyone could be held to, because on its own it names nobody, quantifies nothing, and reserves every substitution right to the supplier.
That gap matters because both sides usually leave the conversation believing different things, and neither of them lied.
What the phrase usually commits to
Four things a buyer typically hears, against what the document underneath actually says.
| What a buyer hears | What the proposal commits to | The artefact that settles it |
|---|---|---|
| These specific engineers | A team matching a described seniority mix | Named individuals in an annex, with role and start date |
| Full time on our work | Availability across the engagement | A stated allocation percentage per named person |
| The same people throughout | The supplier's right to staff as it sees fit | 5 to 15 working days notice before any substitution |
| Nobody else's work in between | Nothing at all | An exclusivity statement, which is rare and priced accordingly |
None of the middle column is dishonest. A supplier promising specific humans for 9 months would be promising something it cannot control. The problem is that the ambiguity is commercially convenient in exactly one direction, and stays unresolved unless the buyer resolves it.
The three artefacts that make it verifiable
- Named individuals in an annex. Name, role, and the date each one joins. An annex can be revised by agreement; a slide with 3 anonymous avatars cannot be breached, because it never said anything.
- A stated allocation percentage. "60% for the first 8 weeks, 30% after" is a number you can check against standup attendance and commit history later. "Dedicated" is not.
- A notice period before substitution. Typically 5 to 15 working days, with a handover expectation attached. The point is not to prevent changes but to make them visible before they happen rather than in week 3.
All three are cheap to ask for and revealing to be refused. A supplier that builds with its own staff can produce them in a day; one that intends to subcontract will negotiate hardest on the first. That makes the request a diagnostic in its own right — the same signal that tells a builder from a reseller in one call.
When partial allocation is the right answer
There is a version of this where the buyer is wrong. Full-time allocation is not automatically better work. A payments specialist for 3 weeks is worth more than a generalist for 3 months, and demanding that every named person is on your account 5 days a week produces either an idle senior engineer or a junior relabelled as one.
Four shapes of partial allocation are legitimate, and each one should be said out loud rather than discovered.
- A specialist, briefly. Security review, data migration, one hard integration — deep involvement for a fixed window, then gone. Continuity buys nothing here.
- An architect or designer at a fraction. 2 days a week across the whole build usually beats 5 days for the first month and silence after it.
- A small internal build with a long tail. Ops tooling often needs a fractional presence for a long time rather than a full team briefly — see internal tools and ops.
- Maintenance of things already shipped. Every surface a supplier already runs consumes part of its week, the effect described in what maintaining our own demo builds taught us.
The uncomfortable part about ourselves: BuildspaceLabs is a small studio, and on most engagements the honest answer is a split allocation with named people rather than a bench sitting idle between projects. What we commit to is the artefact set above — who, what share, how much notice. A supplier claiming permanent full-time exclusivity at small scale is either much larger than it looks, or describing something that will quietly stop being true.
A stated 40% allocation is worth more than an implied 100%, because only one of them can be checked against reality in week 6.
How to score it without manufacturing noise
Staffing is a binary, not a rating. Either the annex names people, states allocations and sets a notice period, or it does not. Rating 3 suppliers out of 5 on "team quality" produces a number that feels rigorous and encodes only the reviewer's impression of a slide — the defect that makes five-point quality scales produce noise wherever they are used. Mark each artefact present or absent, and note what changed between proposal and signature.
This page defines the term. Detecting a breach once work has started needs a different observable — commit authorship against the annex — covered in the engineers who pitched are not the engineers committing. The surrounding decisions sit in deciding what to build and who builds it, inside the wider library.
Frequently asked questions
Short answers to the follow-ups this page tends to raise.
What does "dedicated team" mean in a software proposal?
It means the supplier intends to assign a group of people to your account for the duration, and nothing more precise. It does not imply named individuals, full-time allocation, or that the same people will be there in month 6. Those exist only if stated separately, so the useful response is to ask for names, an allocation percentage and a substitution notice period rather than argue about the phrase.
Is it reasonable to ask for engineers to be named in the contract?
Yes, and most suppliers who build with their own staff will agree. The normal shape is an annex listing names, roles and start dates, with a stated process for agreed changes rather than a promise that nobody moves. Refusal is not automatically bad faith — a supplier may not know in month 1 who is free in month 4 — but refusing to name anyone at any point is a different signal.
Is a part-time allocation a warning sign?
No, provided it is stated up front and the number is real. Specialists working briefly and architects working fractionally are both normal and often better value than full-time generalists. The warning sign is the mismatch: a proposal implying full attention and a delivery reality of 2 days a week, discovered by the buyer rather than disclosed by the supplier.
- procurement
- vendor selection
- engagement models
- staffing
The work behind this page
Builds from our portfolio that this page draws on.
Read next
- The engineers who pitched are not the engineers writing the codeAn impression that the team changed is unarguable and useless. Commit authorship against the names in the proposal is measurable, and it separates a legitimate rotation from a silent downgrade.diagnostic
- Everything is now a change requestArguing about whether a change request is fair goes nowhere. Sorting the last 10 into 3 buckets says whether the bid was underscoped, the scope grew, or nobody decided.diagnostic
- Finance sent it back again and did not say whyA second rejection with no stated reason is not obstruction. Ask which number would have to change for approval, and the reply identifies which of four defects you have.diagnostic
- The supplier you want cannot pass a policy written for someone elseProcurement policies rarely require a certificate universally. They require one when a condition is met, and four of those conditions can be changed by how the engagement is designed.diagnostic
- Total cost of ownership is a structure, not a numberA single total cost figure tells you nothing. The structure does: four phases, a fixed list of line items, filled in identically for every option you are comparing.definition
- It worked on five hundred documents and broke at fifty thousandNothing regressed when the corpus grew. A candidate budget that comfortably held the answer at 500 documents now competes against a hundred times as many near-neighbours, and k never moved.diagnostic
Working on something in this space?
Tell us where you are in a sentence or two. We'll tell you honestly whether we're the right team, and what a sensible first slice of the work looks like.
Start the conversation