Requirement Blocks

Requirement blocks define the scope and time estimates for each work type in a quote. Each block captures detailed information and provides a t-shirt size estimate.

​

What are requirement blocks?

Requirements are separate scopes for each type of work:

• One block per work type
• Independent scope and estimates
• Team members assigned per requirement
• Tracked separately through completion

​

Requirement types

​

Design

For visual and UX work:

• UI/UX design
• Visual assets
• Brand identity
• Marketing materials
• Prototypes

Key fields:

• Design goal
• Design types (can select multiple)
• Target audience
• Reference links
• Brand guidelines availability
• Timeline

​

Development

For code and functionality:

• New features
• Enhancements
• Bug fixes
• Integrations
• Performance optimization

Key fields:

• Development goal
• Work type
• Current behavior (for fixes/enhancements)
• Expected outcome
• Relevant links
• Technical constraints
• Timeline

​

Completing requirements

​

Step 1: Review the brief

Assigned team members review:

• Client’s goal and description
• Requirement-specific details
• Any attachments or references
• Timeline expectations

​

Step 2: Add detailed scope

Click Edit Scope to provide:

• Detailed breakdown of work
• Technical approach (for development)
• Design direction (for design)
• Deliverables list
• Any assumptions or dependencies

Scope editor features:

• Rich text formatting
• AI generation assistance
• Save as draft
• Preview before completing

​

Step 3: Choose t-shirt size

Select appropriate size based on effort: Time ranges for each size:

XS - Very Small

• Minimum: 15 minutes
• Average: 22.5 minutes
• Maximum: 30 minutes
• Example: Update button color, fix typo

S - Small

• Minimum: 60 minutes
• Average: 90 minutes
• Maximum: 120 minutes
• Example: Fix validation bug, add new button

M - Medium

• Minimum: 180 minutes (3 hours)
• Average: 270 minutes (4.5 hours)
• Maximum: 360 minutes (6 hours)
• Example: New form with validation, product filter feature

L - Large

• Minimum: 480 minutes (8 hours)
• Average: 720 minutes (12 hours)
• Maximum: 960 minutes (16 hours)
• Example: Complex checkout flow, multi-step wizard

XL - Very Large

• Minimum: 1440 minutes (24 hours)
• Average: 1920 minutes (32 hours)
• Maximum: 2400 minutes (40 hours)
• Example: Custom integration, complex dashboard

XXL - Extra Large

• Minimum: 2400 minutes (40 hours)
• Average: 4800 minutes (80 hours)
• Maximum: 7200 minutes (120 hours)
• Example: Full platform build, major redesign

​

Step 4: Confirm accuracy

Before marking complete:

• Review scope is clear and complete
• T-shirt size is appropriate
• All details are accurate
• Click Confirm to acknowledge

​

Step 5: Mark complete

Once confirmed:

• Requirement marked complete
• Auto-moves to next requirement (if any)
• When all complete → quote goes to “awaiting_csm_review”

​

The 80/20 split

​

How it works

Each estimate is split:

• 80% - Core work (initial subtask)
• 20% - Feedback budget (for fixes)

Example - M size Development (270 minutes average):

• Feedback budget: 60 minutes (20% = 54 min, rounded up to 1 hour)
• Development subtask: 210 minutes (3.5 hours)

​

Exception: XS tasks

XS tasks have no split:

• All time goes to core work
• No feedback budget reserved
• Assumed too small for meaningful QA

​

Using the feedback budget

The 20% budget is used when:

• Design needs client feedback changes
• Internal QA finds issues
• External QA requests changes

Fix subtasks are estimated using this budget:

• “Client Design Feedback” subtask
• “Internal QA Fixes” subtask
• “External QA Fixes” subtask

​

Requirement status

Requirements progress through completion:

• Start as incomplete when quote is created
• Marked complete when scope and estimate provided
• Can be edited anytime (marks incomplete again)

When all requirements are complete, the quote moves to awaiting CSM review status.

​

Editing requirements

​

Before completion

Full editing available:

• Scope content
• T-shirt size
• Brief details

​

After completion

Can still edit, but:

• Marks requirement as incomplete
• Quote returns to “in_progress”
• Must re-complete to progress
• CSM/client review reset

​

Best practices

​

Sizing guidelines

​

Scope writing

​

Common sizing mistakes

​

Undersizing

Mistake: Selecting S for work that’s actually M Impact:

• Insufficient time allocated
• Work goes over budget
• Profitability suffers

Solution: Size for realistic effort, not ideal scenario

​

Oversizing

Mistake: Selecting XL for work that’s actually L Impact:

• Quote appears expensive
• Client may reject
• Leaves budget unused

Solution: Be honest about effort - padding creates other problems

​

Not considering iterations

Mistake: Sizing only for initial build, forgetting feedback loops Impact:

• Budget consumed by fixes
• No time for revisions

Solution: The 80/20 split handles this - size the full work

​

Multiple requirements

​

When to use multiple

Use multiple requirement blocks when:

• Work requires multiple work types (design + development)
• Separating phases (design first, then development)
• Different team members estimate different parts

​

How they work together

Each requirement:

• Estimated independently
• Can be completed in any order
• All must complete before quote approval
• Convert to separate task requirements

Example: New feature quote

• Design requirement: L size (12 hours) - UI/UX for new feature
• Development requirement: XL size (32 hours) - Build the feature
• Total: 44 hours estimated

​

Next steps