A subcontracted developer only knows what is written down. If the functional spec does not answer these five questions without a meeting, the spec is not ready:
What is the end client trying to achieve?
What is in scope, and what is out?
How does each user role move through the system?
How will every requirement be tested?
Who approves changes?
Consultancies and implementation partners regularly bring 724SOFTWARE in as a white-label or subcontract delivery partner. These engagements usually start with one engineer and scale as funded scope grows. The guidance below comes from receiving these specs and building from them.
TL;DR
A subcontracted developer cannot overhear discovery meetings, so the functional spec has to carry everything they would otherwise pick up there: business goal, scope boundaries, roles, data, and sign-off owner.
Every functional requirement needs pass/fail acceptance criteria. "User-friendly" is not a requirement.
The SOW sets commercial boundaries and the spec sets build boundaries. Change control connects the two.
Run a definition of ready checklist before sprint one, not after the first missed demo.
About the Author: This guide is written by 724SOFTWARE, a Vietnam software team of 200+ professionals (58% senior-level) with delivery experience across 10+ countries. The team works as a subcontract delivery partner for software consultancies and implementation partners.
What is a functional spec document, and how does it differ from an SOW or SRS?
The first job is to be clear about which document holds what. A functional spec document describes what the system must do from the user's point of view: behaviours, rules, inputs and outputs. It is not the contract, and it is not the technical design.
Document | Owner | Answers | Typical gap in subcontracting
|
|---|---|---|---|
Statement of work | Partner and end client | What is paid for, timeline, deliverables | Written for the buyer, too vague to build from |
Functional spec / functional requirements document | Partner's BA or consultant | What the system does, per role and workflow | Assumes the reader attended discovery |
Software requirements specification | Partner or architect | Functional and non-functional requirements, interfaces, constraints | Often skipped on smaller builds |
Technical design | Developer or architect | How it will be built | Started before the spec is stable |
Many consultancies already have a scope of work template for their end client. The functional spec sits underneath that document and translates commercial scope into behaviour a developer can build.
What sections belong in a functional specification template for subcontracted work?
Once you know which document carries the build detail, the next question is what it must contain for a reader outside your company.
Think of it as a relay handover. The next runner can only run with the baton actually in their hand. Anything your consultant learned in workshops but never wrote down does not exist for the subcontracted developer. They have no hallway conversations, no client lunches and no account history to fall back on.
Section | What it must include
|
|---|---|
Business context | End client's problem, success measure, why now |
Scope | In scope, explicitly out of scope, deferred items |
Roles and permissions | Each role and what it can see and change |
Workflows | Step-by-step flows, including error and exception paths |
Functional requirements | Numbered, one behaviour each, with acceptance criteria |
Data and integrations | Entities, field rules, API contracts, source of truth per record |
Non-functional constraints | Performance expectations, devices, accessibility, data residency |
Environments and access | Repositories, test environments, sample data, credential process |
Sign-off | Named approver for questions, demos and changes |
Your end client may run a platform such as Dynamics 365 Business Central or Odoo. In that case, the data section should state which behaviour is standard platform functionality and which is custom.
In 724SOFTWARE's experience, the out-of-scope list is the section most often missing. It is also the one that prevents the most disputes later. Every deferred item written down removes one "I assumed that was included" conversation.
What do strong acceptance criteria examples look like?
A requirements table is only as useful as its test conditions. An acceptance criterion is a pass/fail condition that the developer, the tester and the end client would all judge the same way.
Weak | Testable (example thresholds)
|
|---|---|
The invoice screen should be fast | The invoice list loads the first 50 records within 2 seconds on the staging dataset |
Users can approve orders | An Approver can approve orders up to their assigned limit. Above that limit, Approve is disabled and the order routes to the Finance Manager |
Handle errors gracefully | On a payment API timeout, the order stays Pending, the user sees "Payment not confirmed," and the system retries once after 60 seconds |
A short functional spec example for one requirement:
FR-014: Partial refund
Role: Customer Service Agent
Rule: A refund cannot exceed the captured amount minus prior refunds.
Acceptance: Given an order of 100 with 30 already refunded, when the agent enters 80, then the system blocks the refund and shows the remaining refundable amount (70).
The Given/When/Then format matters because it forces the writer to state the starting condition. Unstated starting conditions are where most "it works on my machine" disagreements begin.
How should the spec connect to the statement of work and change control?
Even a precise spec drifts if nothing governs how it changes, and in our experience this is where subcontract disputes usually start. The statement of work defines what is paid for, and the functional spec defines what is built. Change control is the bridge between them.
Scope creep is a well-documented problem in project delivery. The common mechanism is a requirement added verbally without updating either document.
Four practical rules close that gap:
Version the spec. Reference the version number in the SOW or work order.
Use one change owner. Route every change through one named person at the implementation partner, never directly from the end client to the developer.
Record impact first. Write down the effort, timeline and affected requirements before work starts.
Treat developer questions as spec defects. Answer them in the document, not only in chat.
ISO 27001:2022 Annex A Control 8.32 covers change management, which means changes are controlled rather than applied ad hoc. A delivery partner aligned with that standard should already work this way, so check for it during selection.
What belongs on a definition of ready checklist before sprint one?
With change control in place, the final gate is deciding the spec is ready to build from. A definition of ready checklist is a shared yes/no test that each requirement must pass before development starts.
[ ] Business goal and success measure stated in one paragraph
[ ] Out-of-scope list agreed by the end client
[ ] Every requirement numbered, with Given/When/Then criteria
[ ] API contracts or integration samples available, with a client-side owner
[ ] Test environment and anonymised or synthetic sample data provisioned
[ ] Repository and ticketing access granted, with NDA and security onboarding complete
[ ] Named approver with an agreed response window
[ ] Spec version referenced in the work order
In 724SOFTWARE's delivery practice, engineers use Gemini and NotebookLM for requirements synthesis and spec review. The aim is to surface gaps in the spec before sprint one rather than during it. The BA still owns the spec, but the review shortens the list of questions that would otherwise surface mid-sprint.
Author's opinion: A partner who builds against a spec that fails this checklist is moving the cost of ambiguity into rework. When comparing top staff augmentation companies, ask each one to review a sample spec and return their questions. The quality of those questions tells you more than a capability deck.
Frequently Asked Questions
Who writes the functional spec in a subcontract arrangement?
The implementation partner writes it, because it owns the end-client relationship and the discovery output. The developer reviews it and returns questions before estimating.
How long should a functional spec be?
It should be long enough that a developer with no discovery access can build and test every requirement. Complete acceptance criteria matter more than page count.
Is a software requirements specification the same as a functional spec?
Not quite. An SRS usually adds non-functional requirements, interfaces and constraints. A functional spec focuses on system behaviour.
Can the developer start before the spec is finished?
Yes, but only on requirements that pass the definition of ready. Everything else stays in the backlog until it does.
Should the subcontracted developer talk to the end client directly?
Only if the partner agrees. In white-label work, questions route through the partner so scope decisions stay with one owner.
What should a subcontract partner ask for before starting?
The spec, environments, access, a named approver and the change process. A vendor who asks for none of these is a warning sign.
About 724SOFTWARE
724SOFTWARE is an offshore IT company in Vietnam with 200+ professionals, 58% of them senior-level. It works as a long-term technology partner through dedicated teams, embedded staff augmentation and ODC models.
Implementation partners commonly start with one senior engineer validated against a live sprint, then scale up to 50+ pre-vetted engineers within 2 to 4 weeks as funded scope grows.
Delivery is GDPR compliant and aligned with ISO 9001 and ISO 27001:2022. Every onboarding includes security and NDA setup. The Follow-the-Sun model commits to <10 minute incident response time, and billing is based on actual working hours.
As a selected Anthropic partner in Vietnam, 724SOFTWARE trains its engineers to use Claude Code in day-to-day delivery work.
If a funded project is waiting on delivery capacity, bring your current spec to a scoping conversation with 724SOFTWARE at https://724software.com.vn/.
