Status: SignaUnit is in private development; features marked Planned are not yet available. Everything else on these pages describes the v0.1 design.
SignaUnit sits between franchise HQ and owners. HQ publishes a few priorities with targets. Owners log progress, weigh in on drafts and share what’s working, which HQ can pass to other units. The rollup shows who is behind before the quarter is lost.
These docs describe what SignaUnit does and how it is designed. They are written for two audiences: people at franchisor headquarters (operations leaders, field consultants and admins) and franchise owners.
How to read these docs
SignaUnit is pre-launch. The pages describe the v0.1 design, the build planned for the first brands we work with. We use one convention throughout:
- Anything described without a badge is part of the v0.1 design.
- Anything marked Planned is beyond v0.1. It is on the roadmap but not committed to a date, and it is not yet available.
Where a page discusses a choice your brand makes (for example, how often owners are reminded, or whether peer comparisons are shown), the default is stated alongside the option.
The loop in one paragraph
HQ publishes a priority, such as “reply to 90% of new reviews within two days”. SignaUnit fans it out to the units in scope and gives each owner one batched notice. Owners acknowledge it with one tap and log progress in two taps or one sentence. On day 7, 30 and 60 after launch, follow-through check-ins run automatically, and units that stall go to the field consultant’s follow-up list. The rollup shows adoption next to KPI change against baseline, so HQ can answer two questions in one view: did they do it, and did it work?
Design principles
Two-way, not top-down. HQ sets the few priorities that matter. Owners shape them before they go out and share what’s working once they do. Notes stay private until the owner chooses to share one. Owners posting what’s working directly to peers in other units is Planned.
Three things, not thirty. An owner’s Today view shows at most three ranked priorities. Every priority carries HQ’s one-line “why it matters to your unit”.
Every priority ties to money. Each objective must name what it is for: lead response, conversion, profitability, a launch or a brand standard. If a priority can’t say which, it probably shouldn’t go out.
Outputs, not inputs. SignaUnit sets the result a unit is working toward, such as a response time or a launch date. It coaches the franchise owner on outcomes. It does not direct, assign or monitor work by franchisee employees, and owners decide who in their business sees what. See Roles and permissions.
On top of what you already run. SignaUnit is not a suite migration. Your CRM, POS, accounting and franchise tools stay where they are. SignaUnit holds the few priorities that matter this quarter, the follow-through, and the proof that they moved.
Calm and dependable. The iPhone app works offline, keeps you signed in after one Google sign-in, batches notifications and respects quiet hours. Voice is available but never required.
Where to start
- At headquarters? Start with Getting started (HQ), then Concepts and Publishing and fan-out.
- A franchise owner? Start with Getting started (franchise owner), then iOS app and voice.
- Reviewing security or legal posture? Read Security and data isolation and Roles and permissions.
All pages
Getting started (HQ)
Set up, invite owners and publish your first priority.
Start hereGetting started (franchise owner)
Accept your invite, see this week's priorities and update HQ.
Core conceptsConcepts: objectives, priorities, initiatives, versions, units, rollup
SignaUnit's vocabulary, from HQ to the unit.
Core conceptsPublishing and fan-out
How a priority goes from HQ draft to every unit in scope.
Core conceptsFollow-through check-ins (day 7/30/60)
How a priority stays alive after launch day.
Core conceptsAudits (offline, close the loop)
Offline scored audits whose findings become verified fixes.
Core conceptsKPI import (CSV, QuickBooks, operations connector)
Measure results from your own data, not only self-reports.
iOS appiOS app and voice commands
The iPhone app, five voice commands and their privacy rules.
iOS appOffline sync
Working without signal, and syncing safely after.
Trust and accessRoles and permissions
Who sees and does what, and why HQ works with owners, not staff.
Trust and accessSecurity and data isolation
How each brand's data stays separate.
Extend and connectCustomization & extensibility
A standard core, configured for your brand and connected to your tools.
Extend and connectIntegrations roadmap
What connects in v0.1, and what's planned.
ReferenceFAQ
Answers to common questions.