Skip to content
English
More support
Contact us
  • There are no suggestions because the search field is empty.

Planning Your Launch on RepSpark Flow

Planning a successful launch on RepSpark Flow requires thoughtful consideration of your users, clear communication, and the right rollout strategy for your organization. This guide walks you through the available launch options and best practices for transitioning your teams to the new platform.

How it works

RepSpark Flow offers flexible rollout options that let you control exactly how and when different users access the new platform. You can configure access at the role or division level, allowing for gradual adoption or immediate switchover based on your needs.

Before you start

You’ll need:

  • A migration specialist assigned to you

  • A documented launch date and critical business dates that might affect your launch

If you’re new to RepSpark Flow and have not engaged yet with your RepSpark migration specialist, reach out to your Account Manager or start here.

Rollout Options

RepSpark Flow provides three powerful features to customize your launch approach:

UI Toggle

What it does: Allows users to switch between RepSpark Legacy and Flow at their own pace

Configuration options:

  • Enable/disable at the role level

  • Enable/disable at the division level

  • Set time limits for toggle availability

Best for: Organizations wanting to ease the transition and reduce user anxiety about change

Default Version Control

What it does: Determines which version (Legacy or Flow) users see when they log in

Configuration options:

  • Set different defaults for different roles

  • Set different defaults for different divisions

  • Change defaults over time as adoption increases

Best for: Gradually shifting users to Flow without requiring individual action

Early Adopter Role

What it does: Allows you to granularly control which users you want on RepSpark Flow, without affecting your other users yet

How to use it:

  • Assign the Early Adopter role to selected users

  • Combine with Default Version settings for automatic Flow access

  • Perfect for pilot programs or phased rollouts

Best for: Testing with a controlled group before wider deployment

Understanding Your Users

Before choosing your rollout strategy, assess your different user groups and their readiness for change:

 

User Type

 

Typically includes

 

What do they need?

 

Power User

  • Sales reps who use RepSpark daily

  • Admins who manage configurations

  • Customer service teams handling orders

These users benefit from early access to familiarize themselves with the new interface and can help support others during the transition.

Casual User

  • Retailers who order occasionally

  • Sales reps who primarily use mobile

  • Users in roles with limited RepSpark interaction

These users may need more structured support and clear communication about changes.
Assessing Change Readiness

Consider these factors for each user group:

  • Technical comfort level

  • Frequency of RepSpark use

  • Historical response to platform changes

  • Available time for training

  • Business impact of learning curve

Understanding these factors helps you decide whether to use a gradual rollout with toggles or a faster transition with comprehensive training.

Phased Rollout Strategies

RepSpark Flow offers multiple rollout strategies to match your organization's needs. You can phase or group your users based on:

  • Division: often used for different brands or different regions

  • Role: often used to roll out to sales reps first, and then retailers after

  • User: often used to choose a select group of beta testers, regardless of role

And remember, your users will always have access to the New UI toggle that keeps both versions available for an extended period. Each approach offers different benefits—from contained risk and focused support to maximum user flexibility—allowing you to choose the strategy that best fits your organization's culture and change management needs. The right strategy depends on factors like your user base size, your capacity to support them through training, technical readiness, and tolerance for change.

Choose a rollout strategy that matches your organization's needs and culture:

By Division

How it works: Roll out Flow to one division at a time

Example timeline:

  • Week 1: West Coast division

  • Week 2: East Coast division

  • Week 3: International division

Benefits:

  • Contained impact if issues arise

  • Lessons learned improve subsequent rollouts

  • Regional teams can support each other

By Role

How it works: Transition users based on their role in the organization

Example timeline:

  • Week 1: Admins and customer service

  • Week 2: Inside sales teams

  • Week 3: Field sales reps

  • Week 4: Retailers

Benefits:

  • Training can be role-specific

  • Support resources focused on one group at a time

  • Natural progression from internal to external users

By Customer Segment

How it works: Enable Flow for specific customers or customer types

Example timeline:

  • Week 1: Top 10 enterprise accounts

  • Week 2: Mid-market accounts

  • Week 3: Small business accounts

  • Week 4: All remaining accounts

Benefits:

  • High-touch support for key accounts

  • Gather feedback from different use cases

  • Risk mitigation for revenue-critical customers

Gradual Toggle Transition

How it works: Keep both versions available for an extended period

Example approach:

  • Month 1: Toggle available, Legacy is default

  • Month 2: Toggle available, Flow is default for new users

  • Month 3: Toggle available, Flow is default for all

  • Month 4: Remove toggle, Flow only

Benefits:

  • Maximum flexibility for users

  • Reduces resistance to change

  • Natural adoption curve

Speak to your assigned migration specialist about your needs and we’ll help decide on the best migration rollout strategy for you.