Features
Everything a store launch needs, and nothing it doesn't
FranchiseLaunch models one process — getting a signed location open on schedule. That narrowness is the point: the launch process is built in rather than something you configure and maintain.
One master checklist, reused every time
Your company's launch process should be one thing, not twenty copies that drifted apart. Build the master checklist once — steps, order, owners, departments — and every new store launch starts from it.
- Define phases and tasks once, in the order your team actually works
- Set the owning role and required approver per task, so a new launch arrives pre-assigned
- Create a launch from the master in seconds, or build a one-off checklist for something unusual
- Improve the master as you learn, and every launch created afterwards inherits it
Department approvals that actually hold
An approval that can be skipped isn't an approval. Mark a task as needing Legal, Accounts, or Operations sign-off and it cannot close until that department grants it.
- Route to a department, not a named person — approvals survive leave and role changes
- The task is structurally blocked until sign-off, rather than relying on a status field nobody enforces
- Partial approvals are modelled properly: approved subject to a recorded condition that still has to close
- Every decision is written to the activity trail with an author and a timestamp
- Reviewers get one queue of everything waiting on their department, across every store
One dashboard for every store
The question an operations head asks every week is "which stores are at risk." That should take one glance, not twenty tabs.
- Every active launch with its opening date, percent complete, and open task count
- Stores falling behind are flagged automatically rather than discovered in a status call
- Drill from the portfolio view into a single store's checklist without losing context
- No dashboard to build, no view to maintain, nothing to break when a status is renamed
A mobile app your site teams will use
The people who know whether a task is done are standing in the store. The app is built for exactly that person and nothing else.
- Open the app, see your next task — no navigation, no project picker
- Update status, comment, and request approval in a few taps
- Works for contractors and site staff who will never open a laptop tool
- Available on iOS and Android; new companies create their account from the app
Photo evidence attached to the work
"Signage is up" in a WhatsApp thread and a timestamped photo on the task are not the same claim. Only one of them survives a dispute six weeks later.
- Attach photos to a task directly from the phone that took them
- Evidence sits with the task, so an approver reviews without asking for it
- Snagging walkthroughs produce a punch list with pictures against each open item
- Handover and completion states are backed by something you can look at
Franchise partners see progress, not chaos
Store owners want to know how their launch is going. Giving them a read-only view removes a recurring stream of status questions from your team's day.
- Store Viewer accounts are read-only and scoped to a single location
- They see their own store's real progress in real time — never any other store's
- Always free, and they never count toward your plan's member limit
- No training required; it's the same app, in a simpler mode
Notifications that reach the right person
A due date only matters if it reaches someone. Assignment, approval requests, and blockers all push to the person who has to act.
- Push notification the moment a task is assigned or an approval is requested
- Reviewers are notified per department, so cover works when someone's away
- Blocked and at-risk tasks surface to admins rather than waiting to be noticed
A full activity trail
When a launch slips, the postmortem should be a lookup, not three people's conflicting memory of a chat thread.
- Every status change, comment, and approval is timestamped and attributed
- Read a launch's whole history as one timeline rather than per-task fragments
- See when a task was assigned, when it was first flagged at risk, and how often its date moved
- The record protects approvers as much as it protects the launch team
Coming from another tool?
Most teams arrive here from a spreadsheet, a general project management tool, or a full franchise management suite. We've written up where each one fits and where it stops.
Feature questions
How is a master checklist different from a template?
A template is copied and then forgotten — improvements you make later don't reach launches already running, and after twenty stores you have twenty diverging copies. A master checklist is the canonical definition of your process, and every launch is created from it, so there's one answer to "what is our launch process" rather than twenty.
What does a department approval actually block?
The task cannot move to done until the required department grants approval. It's not a status field that someone is trusted not to change — the completion is blocked. Approvals can also be partial: approved subject to a recorded condition, which itself has to be closed out before the task completes.
Do franchise partners cost extra?
No. Store Viewer accounts are read-only, scoped to one location, free on every plan, and excluded from your member limit — so partner visibility never changes what you pay.
Can contractors and site staff use it without training?
That's what the mobile app is designed for. Someone assigned a task opens the app and sees that task — no project picker, no board navigation. They update status, add a photo, and request approval in a few taps.
What happens when an opening date moves?
Task dates are anchored to the launch date, so moving a store's opening moves its plan with it rather than leaving a mix of dates reflecting the old plan and the new one.
Ready to run your next launch without the spreadsheet?
New here? Create your company's account from the app — live on iOS and Android.