This is the rollout plan for a group of locations. It is short because the product does most of the setup itself: a schedule upload creates every account, a new location inherits the group's settings, and the crew signs in from any phone. What takes thirty days is not the software, it is your people getting used to it one market at a time, so the plan is built around that.
Every milestone below is something the product does today. Nothing on this page depends on a feature that is still being built.
Before day one: what you need ready
- The list of locations, with each store's address and time zone.
- One leader per location who will own the pilot there: the person who posts the schedule and runs the shift.
- A schedule file or a photo of the printed schedule for each location. FlowState reads it, creates an account for every name on it, and shows the leader each person's temporary sign-in. A HotSchedules export works as is.
- Your brand color, if you want the app in your colors. FlowState builds the full light and dark palette from one color and checks it for readability.
- Who should see the whole group: the people who need every location's numbers, and whether each of them manages or only views.
Day 0: the group exists
An owner creates the organization and adds every location from inside the app. Each new location is created instantly and inherits the group's brand color, time zone and team starter password, so the eleventh store is set up the way the first one was. Group members are added with the access level you chose. Billing is one invoice for the group, not one per store.
Milestone: every location provisioned, every group member able to switch between locations without signing out.
Week 1: one pilot store, running a real shift
Pick the store with the leader who is most curious. That leader:
- Uploads the schedule. The crew now exists, each person with a temporary sign-in that the app makes them replace on first use.
- Names the stations to match the real floor, then builds the day's lineup by dragging names onto stations and taps once to notify everyone.
- Photographs the opening and closing lists on the wall. FlowState turns them into checklists, each assignable to a person with a due time.
- Sets the temperature rounds and the items checked on each, and adds the waste items the store actually throws away with what each costs.
The crew gets the app tour on their first sign-in, in English or Spanish, and clocks in, ticks checklists and logs temperatures from their own phones the same day. Wages, if entered, are visible only to owners and masked on shared devices.
Milestone: by the end of the week the pilot store has posted a lineup, completed its checklists, logged its temperature rounds and tracked a week of waste in dollars, and the leader has run one Weekly Huddle with the built-in scorecard, plays and queue.
Week 2: the pilot store settles, the second market prepares
The pilot leader keeps running shifts. This is the week small things get tuned: a checklist that needs a different due time, a station name, a temperature round that should run at a different hour, the break rules the store follows, including the stricter ones for employees under eighteen if timekeeping is on.
Meanwhile the leaders of the next market get the same schedule-upload walkthrough the pilot leader had, done on a call with the person who built the product, not with an onboarding specialist reading from a script.
Milestone: the pilot store's leader can set up the next store without help, and two more stores have their schedules uploaded.
Weeks 3 and 4: market by market
Each new location follows the week-one sequence: schedule upload, stations, checklists from a photo, temperature rounds, waste items. Because every location inherited the group's settings on day zero, there is nothing to configure twice.
People who work at two locations are linked once by a leader, so they see one merged schedule and switch stores with a toggle instead of a second account. Group members watch the whole group come online from the Multi-store view: every location's numbers side by side, and the org chart across all of them.
Milestone: every location live, every crew signed in, every leader running the daily lineup and the weekly huddle from the app.
Day 30: the review
A thirty-minute call with the group's owner and the market leaders, covering:
- Adoption, from the group's own data: lineups posted, checklists completed, temperature rounds logged, waste tracked, huddles run, per location.
- Money found: waste in dollars per store for the month, usually the fastest number that changes.
- Exports, so your bookkeeper and your inspector readiness are covered from day thirty: the payroll CSV for a pay period, the audit binder for a date range, and the security log for the group's IT reviewer.
- What to turn on next: the timeclock and payroll export if the group did not start with them, the geofence, shared kiosks, the AI assistant per store.
Milestone: the group is running on FlowState, has its first month of numbers, and knows what the next month is for.
Who does the work
Setup is self-serve by design, and every step above is something a leader does in minutes from a phone. What you get from us is direct access: the person on the walkthrough calls, on the day-30 review and on the security questionnaire is the operator who built the product and runs it in seven stores of his own. Support questions reach that same person at support@flowstateqsr.com.
What we ask of you
- A named leader per location who will actually run the pilot, not a manager who delegates it.
- Schedules uploaded within the first two days of each location's week.
- Honest feedback in the week-two tuning, especially about anything that felt slower on the app than on paper. That is the feedback that changes the product.
Pricing for groups is on the home page; past fifteen stores it is worked out with you. The security answers a procurement review needs are on the security overview, and the plain-language account of what happens to your data is on the trust page.