Owner: Client Intake Manager Camille · Department: client services

Requirements Template — Client Digital Talent

Process Flow

graph TD
  S0["2."]
  S1["### Secondary capabilities (nice-to-have"]
  S0 --> S1
  S2["2."]
  S1 --> S2
  S3["### Out of scope"]
  S2 --> S3
  S4["2."]
  S3 --> S4
  S5["2."]
  S4 --> S5
  S6["### Acceptance criteria"]
  S5 --> S6
  S7["2."]
  S6 --> S7
  S8["## 9. Constraints and Dependencies"]
  S7 --> S8
  S9["2."]
  S8 --> S9
  S10["2."]
  S9 --> S10

Requirements Template — Client Digital Talent

Owner: Client Intake Manager (Camille) Usage: Fill in one copy per client engagement during the requirements gathering step

1. Client Information

Field Value
Client name
Contact person
Contact email / phone
Industry
Company size (employees)
Referral source
Intake date

2. Business Context

What does the client's business do?

Describe the client's core business in 2-3 sentences.

What problem are they trying to solve?

What pain point, inefficiency, or gap does the client want the digital talent to address?

What is the current process?

How is this work done today? Manual, partially automated, outsourced, not done at all?

Who are the end users?

Who will interact with the digital talent? Internal staff, external customers, both? How many users approximately?

3. Desired Capabilities

Primary capabilities (must-have)

List the core things the digital talent must be able to do.

Secondary capabilities (nice-to-have)

List additional capabilities that would add value but are not essential.

Out of scope

Explicitly list things the digital talent will NOT do.

4. Target Platform

Field Value
Deployment environment (e.g., web app, Slack, Teams, email, API, standalone)
Client tech stack (relevant platforms, tools, languages)
Hosting preference (client-hosted, cloud, Talent Factory-managed)
Security requirements (data sensitivity, compliance needs, access controls)

5. Integration Needs

Systems to integrate with

List external systems, APIs, databases, or platforms the digital talent must connect to.

System Purpose Access method

Data sources

What data does the digital talent need access to? Where does it live?

Authentication requirements

How will the digital talent authenticate with external systems?

6. Timeline

Field Value
Desired start date
Desired delivery date
Hard deadline? (yes/no — if yes, explain why)
Phased delivery acceptable? (yes/no — if yes, what are the phases?)

7. Budget

Field Value
Budget range
Payment terms preference (upfront, milestone-based, monthly)
Ongoing maintenance expected? (yes/no)
Maintenance budget (if applicable)

8. Success Criteria

How will the client measure success?

Define specific, measurable outcomes that indicate the digital talent is working.

Acceptance criteria

What specific tests or demonstrations will the client use to accept delivery?

9. Constraints and Dependencies

Client-side dependencies

What does the client need to provide for the project to succeed? (access, data, approvals, subject-matter expertise)

Known constraints

Technical limitations, regulatory requirements, vendor lock-ins, or other constraints.

10. Additional Notes

Any other context, preferences, or concerns raised by the client.

Completion Checklist

  • Sections 1-4 fully populated (no blanks)
  • At least 1 primary capability defined
  • Target platform identified
  • Timeline and budget discussed (even if ranges)
  • Success criteria defined by the client
  • Out-of-scope items explicitly listed
  • All TBD items have a follow-up date assigned