Quick Summary

Understanding request complexity helps you set realistic expectations for turnaround time and plan your queue effectively. Learn what makes requests simple, medium, or complex, with real examples.

What You'll Learn

• Simple request examples and turnaround
• Medium complexity requests
• Complex request examples
• Breaking down large projects
• Realistic turnaround expectations
• How to estimate complexity

Why Complexity Matters

Impact on Turnaround Time

• Simple Requests: 4-24 hours typical
• Medium Requests: 1-3 days typical
• Complex Requests: 3-7 days typical
• Very Complex: 7-14 days or more

Factors Affecting Complexity

• Scope: How much work is involved
• Technical Difficulty: Complexity of implementation
• Design Complexity: Custom vs template-based
• Dependencies: Integrations, third-party services
• Testing Required: Cross-browser, devices, scenarios
• Revisions: Iteration cycles needed

Simple Requests (4-24 hours)

Characteristics

• Single, focused task
• Clear requirements
• Minimal design decisions
• No complex functionality
• Quick to test
• Few dependencies

Simple Request Examples

Content Updates:

• Update text on existing page
• Replace images (same size/format)
• Add new blog post
• Update contact information
• Change button text or link

Minor Design Changes:

• Change color of element
• Adjust spacing or padding
• Update font size
• Change background color
• Swap logo or icon

Simple Fixes:

• Fix broken link
• Correct typo
• Adjust image alignment
• Fix mobile spacing issue
• Update copyright year

Basic Additions:

• Add social media icons
• Add email link
• Add simple button
• Add text block
• Add image to page

Simple Request Example

Title: Update Homepage Hero Headline

Description:
Please update the main headline on our homepage from "Welcome to Our Site" to "Transform Your Business with AI"

Location: Homepage, hero section, main headline

Access: [provided]

Expected Time: 15-30 minutes

Medium Complexity Requests (1-3 days)

Characteristics

• Multiple related tasks
• Some design work required
• Moderate functionality
• Requires testing
• May need clarification
• Some dependencies

Medium Request Examples

Page Updates:

• Redesign existing page section
• Add new section to page
• Update multiple pages with same changes
• Restructure page layout
• Add image gallery or slider

Form Work:

• Create custom contact form
• Add fields to existing form
• Set up form notifications
• Integrate form with email service
• Style form to match brand

Design Tasks:

• Design social media graphics set
• Create email template
• Design landing page mockup
• Create icon set
• Design banner ads

Functionality Additions:

• Add search functionality
• Implement filtering system
• Add user login
• Create custom post type
• Add booking calendar

Medium Request Example

Title: Add Product Filtering to Shop Page

Description:
Add filtering functionality to our Shopify shop page so customers can filter products by category, price range, and color.

Requirements:
- Filter by category (dropdown)
- Filter by price range (slider)
- Filter by color (color swatches)
- Results update without page reload
- Mobile-responsive design
- Match existing shop page style

References: Similar to https://example.com/shop

Access: [provided]

Expected Time: 2-3 days

Complex Requests (3-7 days)

Characteristics

• Significant scope
• Custom design required
• Complex functionality
• Multiple integrations
• Extensive testing needed
• Multiple dependencies
• Likely needs revisions

Complex Request Examples

Full Page Designs:

• Design and build new landing page
• Complete homepage redesign
• Design multi-page website
• Create custom page template
• Build interactive page

Custom Functionality:

• Build custom calculator tool
• Create product configurator
• Develop custom booking system
• Build member portal
• Create custom dashboard

E-commerce Work:

• Custom product page design
• Checkout flow customization
• Build custom cart functionality
• Product recommendation system
• Inventory management features

Integrations:

• CRM integration
• Payment gateway setup
• Email marketing integration
• API integration
• Third-party service connection

Complex Request Example

Title: Build Custom Product Configurator for Shopify Store

Description:
Create a custom product configurator that allows customers to customize products with multiple options and see real-time price updates and visual preview.

Requirements:
- 5 customization options (size, color, material, engraving, packaging)
- Real-time price calculation based on selections
- Visual preview updates as options selected
- Add to cart with all customizations
- Mobile-responsive
- Save configurations for later
- Email configuration to customer

Functionality:
- Step-by-step wizard interface
- Progress indicator
- Validation for required fields
- Summary page before adding to cart
- Integration with Shopify cart

Design:
- Modern, clean interface
- Match existing store theme
- Clear CTAs and navigation
- Reference: [attached mockup]

Access: [provided]

Expected Time: 5-7 days

Very Complex Requests (7-14+ days)

Characteristics

• Large scope
• Highly custom
• Multiple complex features
• Extensive integrations
• Significant testing
• Multiple revision cycles
• May need phased approach

Very Complex Examples

• Complete website redesign (10+ pages)
• Custom web application
• Multi-vendor marketplace
• Learning management system
• Complex booking/scheduling system
• Custom CRM or portal
• Advanced e-commerce features

Recommendation for Very Complex

Break Into Phases:

• Phase 1: Core functionality
• Phase 2: Additional features
• Phase 3: Integrations
• Phase 4: Polish and optimization

Benefits:

• Faster initial delivery
• Easier to test and iterate
• Can launch sooner
• More manageable scope
• Better results

Breaking Down Large Projects

Why Break Down Projects

• Faster Results: Get working features sooner
• Better Quality: Focus on one thing at a time
• Easier Testing: Test incrementally
• More Flexibility: Adjust based on feedback
• Less Risk: Smaller scope = less can go wrong

How to Break Down Projects

By Feature:

• Request 1: User registration
• Request 2: User profile
• Request 3: Dashboard
• Request 4: Settings page

By Page:

• Request 1: Homepage
• Request 2: About page
• Request 3: Services pages
• Request 4: Contact page

By Phase:

• Request 1: Design mockups
• Request 2: Build homepage
• Request 3: Build inner pages
• Request 4: Add functionality
• Request 5: Testing and fixes

By Priority:

• Request 1: Must-have features
• Request 2: Should-have features
• Request 3: Nice-to-have features

Example: E-commerce Site Redesign

❌ One Large Request:

"Redesign entire e-commerce site with new homepage, product pages, cart, checkout, and account pages"

Estimated time: 3-4 weeks

✅ Broken Into Phases:

Request 1: Design homepage mockup
Time: 2-3 days

Request 2: Build homepage from approved design
Time: 2-3 days

Request 3: Design product page template
Time: 2 days

Request 4: Build product page template
Time: 2-3 days

Request 5: Design cart and checkout flow
Time: 2-3 days

Request 6: Build cart and checkout
Time: 3-4 days

Request 7: Design account pages
Time: 2 days

Request 8: Build account pages
Time: 2-3 days

Total time: Same 3-4 weeks, but delivered incrementally

Setting Realistic Expectations

Turnaround Time Factors

What Affects Speed:

• Complexity: More complex = longer time
• Clarity: Clear requests = faster start
• Assets: All assets ready = no delays
• Revisions: More revisions = longer total time
• Queue: Your position in queue
• Team Availability: Current workload

Average Turnaround by Type

Managing Expectations

Communicate Deadlines:

• Mention if time-sensitive
• Provide context for urgency
• Ask for estimated completion
• Build in buffer time

Be Flexible:

• Understand estimates are estimates
• Complex work may take longer
• Quality takes time
• Revisions add time

Estimating Your Request Complexity

Self-Assessment Questions

Scope Questions:

• How many pages/sections affected?
• How many different tasks involved?
• Is this one focused task or multiple?

Design Questions:

• Using existing design or creating new?
• How much custom design needed?
• Do you have mockups or starting from scratch?

Technical Questions:

• Simple update or custom functionality?
• Any integrations required?
• How much testing needed?

Clarity Questions:

• Do you have all requirements defined?
• Are all assets ready?
• Any unknowns or decisions needed?

Complexity Scoring

Score each factor 1-3:

• Scope: 1=Single task, 2=Multiple tasks, 3=Large project
• Design: 1=Existing, 2=Minor custom, 3=Fully custom
• Technical: 1=Simple, 2=Moderate, 3=Complex
• Clarity: 1=Very clear, 2=Some unknowns, 3=Many unknowns

Total Score:

• 4-6 points = Simple (1 day or less)
• 7-9 points = Medium (1-3 days)
• 10-12 points = Complex (3-7 days)

Tips for Each Complexity Level

For Simple Requests

• Batch multiple simple requests together
• Use for quick wins and momentum
• Perfect for filling gaps in queue
• Great for urgent needs

For Medium Requests

• Provide clear requirements upfront
• Include all assets and references
• Plan for 1-2 revision rounds
• Good balance of value and speed

For Complex Requests

• Consider breaking into phases
• Expect multiple revision rounds
• Maintain close communication
• Plan for longer timeline
• Build in buffer time

Common Questions

Q: How do I know if my request is too complex?
A: If it would take a freelancer 40+ hours, consider breaking it down into smaller requests.

Q: Can I submit a complex request?
A: Yes, but breaking it down often leads to better results and faster initial delivery.

Q: What if I'm not sure about complexity?
A: Submit the request and your PM will advise if it should be broken down.

Q: Do complex requests cost more?
A: No, all requests are included in your subscription regardless of complexity.

Q: How can I speed up complex requests?
A: Provide complete requirements, all assets, clear references, and quick feedback.

Q: What's the most complex request you can handle?
A: We can handle very complex projects, but recommend breaking them into phases for best results.

Q: Should I always break down complex requests?
A: Not always, but it usually leads to faster initial delivery and better results.

Q: How do I estimate turnaround for my request?
A: Use the complexity guide above, or ask your PM for an estimate when submitting.

Need More Help?

Contact support@thrivepix.com or message your project manager