Skip to main content
EmergentEMERGENT
Emergent SolutionsKnowledge Base

Delivery Process

How we execute client projects from kickoff to completion.

Project Lifecycle

Discovery → Planning → Implementation → QA → Launch → Support

Phase 1: Discovery

Objectives

  • Understand client goals
  • Assess current state
  • Identify requirements
  • Scope the project

Activities

| Activity | Duration | Output | |----------|----------|--------| | Kickoff call | 1 hour | Meeting notes | | Stakeholder interviews | 2-4 hours | Requirements | | Technical audit | 4-8 hours | Audit findings | | Requirements synthesis | 2-4 hours | Requirements doc |

Deliverables

  • Discovery Summary - Findings and recommendations
  • Requirements Document - Detailed specifications
  • Project Scope - Agreed deliverables and timeline

Checkpoints

  • [ ] Client approves requirements document
  • [ ] Access to all necessary platforms confirmed
  • [ ] Technical contacts identified
  • [ ] Timeline agreed

Phase 2: Planning

Objectives

  • Design the solution
  • Create detailed specifications
  • Plan implementation approach

Activities

| Activity | Duration | Output | |----------|----------|--------| | Measurement planning | 4-8 hours | Measurement plan | | Data layer design | 4-8 hours | Data layer spec | | GTM architecture | 2-4 hours | Container design | | Implementation plan | 2-4 hours | Task breakdown |

Deliverables

  • Measurement Plan - KPIs, events, dimensions
  • Data Layer Specification - Schema and examples
  • Implementation Plan - Phased task list

Checkpoints

  • [ ] Client approves measurement plan
  • [ ] Developer reviews data layer spec
  • [ ] Implementation plan accepted

Phase 3: Implementation

Objectives

  • Build the solution
  • Configure tracking
  • Support data layer implementation

Workflow

Development → Internal Review → Client Review → Revisions → Approval

Sprint Structure

Week 1-2: Foundation

  • GTM container setup
  • GA4 configuration
  • Core event structure
  • Data layer support

Week 3-4: Build Out

  • Event implementation
  • Marketing pixel setup
  • E-commerce tracking
  • Custom dimensions

Week 5+: Refinement

  • Edge cases
  • Additional events
  • Integration testing
  • Documentation

Daily Practices

  • Update task status in project board
  • Log blockers immediately
  • Document decisions made
  • Test as you build

Checkpoints

  • [ ] Internal QA passed
  • [ ] Client staging review complete
  • [ ] All events firing correctly
  • [ ] Documentation drafted

Phase 4: Quality Assurance

Objectives

  • Verify implementation accuracy
  • Test across scenarios
  • Document findings
  • Fix issues

QA Checklist

Page View Tracking

  • [ ] All pages fire page_view event
  • [ ] Page parameters correct
  • [ ] No duplicate page views
  • [ ] Virtual page views work (SPAs)

Event Tracking

  • [ ] All planned events fire
  • [ ] Event parameters correct
  • [ ] Events fire at right moment
  • [ ] No duplicate events

E-commerce (if applicable)

  • [ ] Product impressions
  • [ ] Product clicks
  • [ ] Add to cart
  • [ ] Checkout steps
  • [ ] Purchase
  • [ ] Refunds

Cross-Platform

  • [ ] Desktop browsers
  • [ ] Mobile devices
  • [ ] Different user states
  • [ ] Consent scenarios

QA Report

Document findings in standard format:

| Issue | Severity | Steps to Reproduce | Expected | Actual | |-------|----------|-------------------|----------|--------| | Missing event | High | Click CTA on homepage | form_start fires | No event |

Checkpoints

  • [ ] QA complete with no critical issues
  • [ ] All issues resolved or documented
  • [ ] Client sign-off on QA

Phase 5: Launch

Pre-Launch

  • [ ] Production environment access
  • [ ] Deployment plan documented
  • [ ] Rollback plan prepared
  • [ ] Stakeholders notified

Launch Day

  1. Deploy to production
  2. Verify tracking immediately
  3. Check data in GA4/GTM
  4. Monitor for errors
  5. Confirm with client

Post-Launch

  • Monitor data for 24-48 hours
  • Check for anomalies
  • Validate conversion data
  • Document any issues

Checkpoints

  • [ ] Production deployment successful
  • [ ] Data flowing correctly
  • [ ] No critical errors
  • [ ] Client confirmation received

Phase 6: Handoff & Support

Documentation Handoff

Deliver final documentation:

  • Implementation summary
  • GTM inventory
  • Data layer documentation
  • Maintenance guide
  • Training materials

Training Session

Cover:

  • What was implemented
  • How to make common changes
  • How to troubleshoot issues
  • When to ask for help

Support Period

Typical 30-day support window:

  • Bug fixes for implementation issues
  • Clarification questions
  • Minor adjustments

Checkpoints

  • [ ] Documentation delivered
  • [ ] Training completed
  • [ ] Client comfortable with maintenance
  • [ ] Support period communicated

Quality Standards

Code Quality

  • Consistent naming conventions
  • Proper organization
  • Documented configurations
  • No unnecessary complexity

Documentation Quality

  • Clear and concise
  • Up to date
  • Actionable
  • Accessible to client

Communication Quality

  • Responsive (within 1 business day)
  • Proactive on blockers
  • Clear status updates
  • Professional tone

Previous: Onboarding Next: Client Communication