CTA Shopify Digital Asset Store — Statement of Work

Date: December 15, 2025
Version: 1.0
Client: Consumer Technology Association (CTA)
Author: Brainforge AI

1. Overview

This Statement of Work defines Brainforge’s engagement to assess, troubleshoot, and redesign CTA’s digital asset sales infrastructure currently implemented through Shopify. The project addresses authentication loop issues, ownership ambiguity, and technical debt from a legacy Ruby implementation, while evaluating whether to optimize the current Shopify setup or migrate to a more appropriate platform (such as Stripe). Brainforge will deliver a comprehensive architecture assessment, platform evaluation, and implementation plan to reduce customer friction, clarify ownership, and potentially enable future use cases such as lead generation data delivery and CES sponsorship sales.

2. Objectives

Eliminate Customer Friction: Resolve authentication loops between Okta, Remembers (AMS), and Shopify causing download failures
Clarify System Ownership: Propose clear ownership model for digital asset sales infrastructure across marketing, market research, and IT
Evaluate Platform Fit: Determine whether Shopify is appropriate for CTA’s digital asset sales use case or if alternative platforms better serve needs
Reduce Technical Debt: Address Ruby codebase maintainability concerns and authentication wrapper complexity
Enable Future Use Cases: Design solution that can support lead generation data delivery, CES sponsorship sales, and member benefit fulfillment
Improve Visibility: Establish reporting and analytics for product performance, sales volume, and customer issues

3. Scope of Work

3.1 In-Scope

Discovery & Assessment (Phase 1)

Map current Shopify integration architecture (Okta authentication, Remembers data flow, Ruby codebase)
Document authentication flow and identify loop/failure points
Review Ruby codebase to understand authentication wrapper functionality and dependencies
Catalog complete product inventory in Shopify (reports, research, sponsorships, other digital assets)
Analyze sales volume, revenue, and customer demographics for past 24 months
Interview stakeholders across marketing, market research, and IT to understand ownership expectations
Review customer support tickets and Slack complaints related to Shopify issues
Assess New Zealand vendor relationship and ongoing obligations
Document integration with Marketing Cloud for fulfillment (if applicable)

Solutions Evaluation (Phase 2)

Evaluate “fix Shopify” scenario: Authentication improvements, Ruby code modernization, integration optimization
Evaluate Stripe-based solution leveraging Brainforge’s e-commerce expertise
Evaluate alternative digital asset platforms (Gumroad, SendOwl, Paddle, or custom portal)
Compare member vs. non-member pricing capabilities across platforms
Assess lead generation/data sharing use case fit for each option
Model migration complexity, timeline, and resource requirements for each scenario

Recommendations & Roadmap (Phase 3)

Deliver ROI analysis comparing fix vs. replace scenarios (TCO, operational efficiency, user experience)
Provide platform recommendation with clear rationale
Propose ownership model clarifying responsibilities across marketing, market research, IT
Document product catalog management workflow for chosen solution
Deliver migration roadmap with phases, data migration plan, and testing strategy
Identify quick wins achievable within 30 days regardless of platform decision

Implementation Support (Phase 4 - Optional)

Implement chosen solution (Shopify fixes OR new platform setup)
Configure authentication flow to integrate with Okta and Remembers
Migrate product catalog and historical customer data (if replacing Shopify)
Build or configure member vs. non-member pricing logic
Establish reporting dashboard for sales, product performance, and customer issues
Test end-to-end purchase and fulfillment flow
Support parallel system operation during migration (if applicable)
Transition ownership to appropriate CTA team with documentation and training

3.2 Out-of-Scope

Full platform implementation without separate Phase 4 approval
Marketing content creation or product descriptions
Pricing strategy or business model consultation beyond technical implementation
Email deliverability improvements (separate workstream)
Shopify theme design or brand customization
Ongoing managed services or long-term platform support
Integration with systems beyond Okta, Remembers, and Marketing Cloud
Membership pricing or tier strategy definition (CTA owns business logic, Brainforge implements technical rules)

4. Requirements & Inputs

Access & Permissions

Administrative access to Shopify store
Ruby codebase repository access
Authentication integration documentation (Okta, Remembers)
Customer support ticket data (Slack channel exports, ticketing system)
Product catalog details (pricing, member vs. non-member rules, fulfillment methods)

Documentation

Shopify contract and pricing details
New Zealand vendor contact and relationship history
Integration architecture diagrams (if available)
Member benefit policies related to digital asset pricing
Marketing Cloud fulfillment workflow documentation

Stakeholder Availability

Jay Heavner (IT): Technical deep dives on authentication and Ruby code (weekly)
Katherine Bayless (Data Operations): Strategic alignment and ownership discussions (bi-weekly)
Marketing team representative: Product catalog management, pricing rules, ownership expectations
Market research team representative: Product strategy, content requirements, sales reporting needs
Customer service representative: Common issues, ticket volume, customer feedback

Data & Metrics

Product catalog with current pricing (member and non-member)
Sales data for past 24 months (volume, revenue, customer segments)
Customer support ticket volume and issue categories
Authentication failure rates and error logs
CES sponsorship data stored in Shopify (September email reference)

5. Deliverables

Phase 1: Discovery & Assessment

Current State Assessment Report (12-15 pages)
- Architecture diagram showing Okta → Remembers → Shopify authentication flow
- Ruby codebase analysis with maintainability assessment
- Product catalog documentation
- Sales and customer analysis (volume, revenue, trends)
- Issue log with categorized customer complaints
- Ownership ambiguity assessment with stakeholder perspectives
Executive Summary (2-3 pages)
Open Questions Log requiring CTA input

Phase 2: Solutions Evaluation

Platform Comparison Matrix (4-5 scenarios across 8-10 criteria)
Fix Shopify Scenario: Technical specification for authentication improvements and Ruby modernization
Stripe Scenario: Reference architecture and implementation plan
Alternative Platforms: Feature and cost comparison
Migration Complexity Assessment for each scenario
Lead Generation Use Case Fit Analysis

Phase 3: Recommendations & Roadmap

Platform Recommendation with rationale tied to CTA priorities
ROI Analysis comparing scenarios (TCO, operational efficiency, user experience impact)
Ownership Model Proposal with RACI matrix for marketing, market research, IT
Quick Wins Report (2-4 initiatives achievable within 30 days)
Migration Roadmap with 3-phase approach (if replacing Shopify)
Risk Assessment and Mitigation Plan

Phase 4: Implementation Support (Optional)

Implemented platform with configured authentication and pricing logic
Product catalog migrated and validated
Member vs. non-member pricing rules configured and tested
Reporting dashboard operational (sales, products, customer issues)
End-to-end testing summary with documented test cases
Transition documentation for CTA ownership team
30-day post-launch support and optimization recommendations

6. Project Timeline

Phase 1: Discovery & Assessment (Weeks 1-2)

Week 1: Kickoff, access setup, architecture documentation, stakeholder interviews
Week 2: Ruby code analysis, data analysis, issue cataloging, draft report

Phase 2: Solutions Evaluation (Weeks 3-4)

Week 3: Shopify fix scenario scoping, Stripe architecture, alternative platform research
Week 4: Cost modeling, migration complexity assessment, use case fit analysis

Phase 3: Recommendations & Roadmap (Week 5)

Week 5: Final recommendations, ownership proposal, roadmap delivery, executive presentation

Phase 4: Implementation Support (Timeline TBD based on Phase 3 recommendations)

Shopify Optimization Track: 4-6 weeks (authentication fixes, Ruby modernization)
Platform Migration Track: 6-10 weeks (new platform setup, data migration, testing, parallel operation)
Timeline to be scoped separately following Phase 3 completion and leadership approval

Total Discovery Duration: 5 weeks (Phases 1-3)

7. Assumptions

Stakeholders from marketing, market research, IT, and customer service are available for interviews and ongoing questions
Administrative access to Shopify, Ruby codebase, and related systems provided within first week
Sales data and customer support ticket data are available and reasonably complete
New Zealand vendor can be contacted for knowledge transfer if needed
CTA is open to platform change if ROI justifies migration effort
Parallel system operation is acceptable during migration (if replacing Shopify) to minimize disruption
Authentication integration with Okta and Remembers is maintainable regardless of platform choice
Product catalog is relatively stable (< 50 SKUs) making migration feasible
CTA will designate clear owner for digital asset sales platform following Phase 3 recommendations

8. Risks

Risk	Impact	Mitigation
Ruby codebase more complex than expected	Medium	Allocate extra time in Phase 1 for code review; engage New Zealand vendor if critical knowledge gaps exist; consider full replacement over fix if complexity too high
Stakeholder disagreement on ownership model	High	Facilitate ownership workshops in Phase 3; escalate to executive leadership early; propose clear RACI with Katherine Bayless as arbiter
Sales volume too low to justify platform investment	Medium	Evaluate broader use cases (lead gen, sponsorships); consider lightweight solution if volume doesn’t justify complexity; document opportunity cost of ongoing friction
Authentication complexity spans multiple systems	High	Deeply analyze authentication flow in Phase 1; engage Jay Heavner as technical lead; consider whether broader Okta optimization (separate SOW) should be prerequisite
Migration disrupts active sales during transition	Medium	Plan parallel system operation; implement during low-volume period; provide customer communication plan; test extensively before cutover
Product catalog data quality issues	Low	Conduct data quality assessment early; plan cleanup as Phase 4 prerequisite; engage market research team for validation
New platform lacks member pricing capabilities	Medium	Validate member vs. non-member pricing as must-have requirement in Phase 2; ensure Remembers integration can pass membership status; consider custom logic if needed

9. Acceptance Criteria

Phase 1 Acceptance:

Architecture diagram validated by Jay Heavner as accurate
Ruby codebase analysis identifies specific maintainability concerns
Product catalog documented and validated by market research team
Sales analysis covers 24-month period with clear trends identified
Stakeholder ownership perspectives captured from marketing, market research, IT

Phase 2 Acceptance:

Minimum 3 platform scenarios evaluated with complete cost models
Migration complexity includes effort estimates and risk ratings
Lead generation use case fit assessed for top 2-3 options
Member vs. non-member pricing capability validated for each scenario

Phase 3 Acceptance:

Platform recommendation includes clear rationale tied to CTA business priorities and ROI
Ownership model proposal has stakeholder input and executive-ready presentation
Migration roadmap (if applicable) addresses data migration, testing, parallel operation
Quick wins are actionable with 30-day delivery commitment

Phase 4 Acceptance (if engaged):

Authentication flow functions correctly with < 1% failure rate
All products migrated with accurate pricing (member and non-member)
End-to-end purchase and fulfillment tested and validated
Reporting dashboard operational with key metrics tracked
CTA team trained on platform administration and product management
30-day post-launch period shows reduced customer complaints

10. Communication Plan

Regular Meetings:

Weekly Technical Working Session (45 min): Jay Heavner + Brainforge team
Bi-weekly Strategic Alignment (30 min): Katherine Bayless + Uttam Kumaran
Stakeholder Workshop (Phase 3): Marketing, market research, IT representatives for ownership discussion
Phase Gate Reviews (60 min): End of Phase 1, 2, 3 with Katherine, Jay, and relevant stakeholders

Async Communication:

Dedicated Slack channel for daily questions and updates
Shared workspace (Google Drive or equivalent) for documentation and deliverables
Weekly status email summarizing progress, blockers, and upcoming milestones

Escalation Path:

Ownership disputes escalated to Katherine Bayless
Technical blockers escalated to Jay Heavner
Timeline risks communicated within 24 hours of identification
Platform recommendation review with executive leadership before Phase 4 commitment

11. Open Questions

These questions were not fully addressed in discovery conversations and will be answered during Phase 1:

Product Catalog: What is the complete product inventory in Shopify? How many SKUs? What product categories?
Sales Volume: What are annual sales volumes and revenue broken down by product? What is the trend over past 24 months?
Customer Demographics: What percentage of purchases are from members vs. non-members? What member tiers purchase most frequently?
Vendor Relationship: Who is the New Zealand vendor contact? What is the current relationship status and ongoing obligations?
Ruby Codebase: Where is the Ruby code repository? What specific authentication wrapper functionality does it implement? What are the dependencies?
Data Flow Architecture: What specific data flows between Shopify, Okta, and Remembers? What authentication tokens or session data is exchanged?
CES Sponsorship Data: What CES sponsorship data is stored in Shopify (September email reference)? Is this an intended use case or accidental?
Lead Generation Use Case: What are the specific business requirements for using this platform for lead gen/badge scan delivery? Volume expectations?
Marketing Cloud Integration: Is there integration between Shopify and Marketing Cloud for fulfillment? If so, what is the workflow?
Member Pricing Logic: How are member vs. non-member prices differentiated? Is membership tier (gold, silver, etc.) relevant to pricing?
Support Ticket Volume: What is the volume of Shopify-related support tickets? What are the top 3-5 categories of customer issues?
Parallel System Tolerance: If migrating platforms, what is CTA’s appetite for running Shopify and new platform in parallel during transition?
Historical Data Requirements: If migrating, what historical customer and sales data must be preserved? What can be archived?
Current Shopify Costs: What is CTA paying for Shopify monthly? What plan/tier? Are there transaction fees?
Ownership Expectations: Who does each stakeholder group (marketing, market research, IT) believe should own this platform operationally?

12. Pricing

Pricing to be provided separately based on final scope confirmation following review of this SOW.

Estimated Ranges for Planning:

Phase 1-3 (Discovery, Evaluation, Recommendations): 5 weeks of engagement
Phase 4 (Implementation Support): Timeline and pricing dependent on Phase 3 recommendations
- Shopify optimization track: 4-6 weeks
- Platform migration track: 6-10 weeks

Brainforge will provide detailed pricing proposal following initial SOW review meeting.

13. Sign-Off

By signing below, both parties acknowledge understanding and agreement with the scope, deliverables, timeline, and approach outlined in this Statement of Work.

Client (CTA):

Name: ___________________________
Title: ___________________________
Date: ___________________________
Signature: _______________________

Brainforge AI:

Name: Uttam Kumaran
Title: Managing Lead
Date: December 15, 2025
Signature: _______________________

Appendix A: Key Stakeholders

Name	Role	Involvement
Jay Heavner	IT Lead / CTO	Technical lead for authentication and Ruby code, weekly working sessions
Katherine Bayless	Director of Data Operations	Strategic sponsor, ownership arbiter, bi-weekly alignment, executive liaison
[Marketing Lead]	Marketing Team	Shopify system owner, product catalog management, pricing strategy
[Market Research Lead]	Research Team	Content producer, product strategy, sales reporting requirements
[Customer Service Rep]	Support Team	Customer issues, support ticket analysis, user feedback

Appendix B: Platform Evaluation Criteria

Brainforge will assess platforms against these criteria in Phase 2:

Functional Criteria:

Authentication integration (Okta, Remembers)
Member vs. non-member pricing capabilities
Digital asset delivery and fulfillment
Product catalog management
Lead generation/data sharing use case fit
Reporting and analytics

Technical Criteria:

Integration complexity with existing CTA systems
Maintainability and technical debt
Security and compliance
Scalability for future growth
Mobile experience

Operational Criteria:

Total cost of ownership (licensing, transaction fees, maintenance)
Administrative ease for product management
Customer support requirements
Migration complexity and timeline
Vendor stability and support quality

User Experience Criteria:

Customer purchase flow friction
Authentication success rate
Download/fulfillment reliability
Mobile responsiveness
Member experience differentiation

Appendix C: Success Metrics

Brainforge will track these metrics during discovery to establish baseline and measure improvement:

Customer Experience Metrics:

Authentication failure rate during purchase flow
Support ticket volume (Shopify-related)
Average time to issue resolution
Customer complaint frequency (Slack mentions)
Purchase completion rate (cart to checkout)

Business Metrics:

Sales volume by product
Revenue by product and customer segment (member/non-member)
Average order value
Customer retention (repeat purchases)
Product catalog SKU count

Technical Metrics:

Authentication loop occurrences
Ruby codebase maintainability score
Integration complexity rating
System uptime and reliability

Operational Metrics:

Time to add new product (end-to-end)
Platform administration effort (hours/week)
Reporting accessibility and accuracy
Ownership clarity score (stakeholder survey)

Brainforge Knowledge

Explorer

SOW_CTA_Shopify_Digital_Asset_Store