Preview: SignaUnit is in private development. All figures shown are sample data for illustration, not customer results.

SignaUnit, from Acutis Ignatius

Every franchise unit shares in what works.

Priorities from HQ. Proof from the field. Owners share what works at their unit, and still run their own business.

Tell us what you're rolling outSee the product

HQ rollup · Example Brand (fictional)

Reply to every review within two days

Version 2 · Day 30 of 60 · 48 units

Day 30 check-in
Adoption71%
Review response vs. baseline+18 pts
At risk9 unitsFlagged on the rollup
UnitRegionAdoptionKPI vs. baselineStatus
Unit 12North100%+24 ptsOn track
Unit 18North86%+15 ptsOn track
Unit 23South52%+3 ptsAt risk
Unit 31South40%−2 ptsAt risk
Unit 37East0%—Not started
Unit 44East94%+19 ptsOn track
Illustrative HQ rollup. Sample data.
For franchise owners

Three things this week, each with a reason.

Owners see at most three ranked priorities from HQ, each with why it matters.

  • Ranked. Do the first one first.
  • Two-way. Owners add notes and choose who sees them.
  • Readable status. Shape and label, not just color.
Status, shape and label
  • On track
  • At risk
  • Not started

Today · Unit 12, North

This week from HQ

  1. New customer greeting v2

    Updated by HQ. First visits that feel welcome come back.

    Not startedAcknowledge

  2. Reply to every review

    Day 30 check-in due Friday. Repeat customers read the replies.

    At risk

  3. Launch seasonal promo

    Live since Tuesday. Brings in new leads during the slow weeks.

    On track

Three things, not thirty.

Illustrative owner Today view. Sample data.
Check-ins on the web

A check-in takes one sentence.

Owners type a number on the web and press Log progress.

Day 7, 30 and 60 check-ins on iPhone, by tap or voice Planned

Planned

  1. Day 0Publish
  2. Day 7Check-in
  3. Day 30Check-in
  4. Day 60Final check-in
Check-in

Day 30 check-in · Unit 12

Reply to every review

Target: 90% answered within two days

  1. Day 7
  2. Day 30
  3. Day 60
You said“Log a 92 percent review-response rate for Unit 12.”

Log update for Review replies?

Review response rate92%
Illustrative iOS check-in. Sample data.

Scheduled

Once, weekly or monthly, set at publish.

Retry-safe

A dropped connection never double-counts.

Rolled up

Lands in HQ's view next to adoption.

After launch day

Rollouts don't fail at launch. They fail after.

After the webinar, follow-up depends on who remembers, and nobody can say if it worked.

  1. Built
  2. Announced
  3. Webinar
  4. Box checked
  5. Follow-through

And when one owner finds a better way, the other units rarely hear about it.

  • Adoption is invisible

    Nobody knows which units did it.

  • Stalls surface late

    Found on a site visit, too late.

  • Every ask looks equal

    No signal about what matters most.

How it works

One priority, from headquarters to every unit.

Did they do it, and did it work? One loop answers both, and carries owner know-how back.

  1. Publish

    HQ sets the target and the why. Owners comment, vote or test first Planned

  2. Fan out

    Pick regions, franchisees or units. One batched notice per owner Planned

  3. Check-ins

    Owners log progress on the web, on the cadence HQ set. Reminders by push, email and field consultant Planned

  4. Rollup

    Adoption next to KPI change, at-risk units flagged. What worked goes back out to peers Planned

The two-way loop between headquarters and franchise unitsHeadquarters at the top, franchise units at the bottom. On the right, priorities go out: 1 Publish, 2 Fan out. On the left, what works comes back: 3 Check-ins, 4 Rollup.HeadquartersFranchise unitsPriorities go out1 · Publish2 · Fan outWhat works comes back3 · Check-ins4 · Rollup
Edits after publishing ask owners to acknowledge. Publishing and fan-out.
Core v0.1 features

Built for the part after the webinar.

What v0.1 does today, and what is planned next.

Adoption and KPI change, side by side.

Tracked initiatives

Each priority tied to its KPI and result.

  • Adoption next to KPI change
  • Your own met / at-risk rules
  • Versioned, never silently edited

Scheduled follow-through

Follow-up on a cadence, not memory.

  • Once, weekly or monthly check-ins
  • At-risk units flagged
  • Day 7, 30 and 60 check-ins Planned
  • Follow-up lists for field consultants Planned

Offline audits Planned

Visits end in a verified fix.

  • Scored audits, no signal needed
  • Findings become owner actions
  • Photo proof, then verify

Owner-first iOS Planned

Three things, not thirty.

  • Ranked priorities on Today
  • Update in a tap or a sentence
  • Same sign-in as the web

Owner input and KPI import

KPI data in, owner notes shared on their terms.

  • CSV KPI import with preview
  • Owners choose who sees their notes
  • Comment, vote and test drafts Planned
  • Shared notes become peer tips Planned
  • QuickBooks and an operations connector Planned

Read the full design

Every concept, from versions to data isolation.

Open the docs
Customization and extensibility

Make it yours. Keep the tools you have.

A standard core, shaped by settings, beside the systems you already pay for.

Customization never weakens data isolation.

How SignaUnit fits your brandThree stacked layers. At the base, the standard SignaUnit core: priorities, follow-through and rollup. Above it, your configuration: metric types, checklists and targeting. At the top, dashed because they are planned, connectors to the tools you already use: franchise suite, POS and CRM.YOUR TOOLS · PLANNEDFranchise suitePOSCRMYOUR CONFIGURATIONMetric types · Checklists · TargetingSTANDARD CORE, EVERY BRANDPriorities · Follow-through · Rollup
Illustrative. Dashed items are planned.

One standard core

Priorities, follow-through and rollup.

Your metrics and checklists

Number, percent, currency, yes/no or checklist measures. Custom fields and audit templates Planned

Signed webhooks Planned

Events to your systems, signed and retried.

Scoped API Planned

Keys limited to the scopes you choose.

Plugins Planned

Approved by your HQ admin.

Fits the tools you use Planned

Franchise suite, POS, CRM and QuickBooks connectors.

Customization & extensibility · Integrations roadmap

iOS app Planned

Voice when it helps. Never required.

Planned for the iOS app: five voice actions, each just as quick by touch.

Confirm before every write

Spoken updates save only after a tap or a yes.

On-device speech

No audio stored or uploaded. Voice can be off.

Everything works by touch too. How voice will work.

Voice · five things Planned

Say it, see it, confirm it

  • You sayWhat matters today?A short brief of your top priorities.
  • You sayLog a 92 percent review-response rate for Unit 12.Records a check-in.Confirm first
  • You sayNote: seasonal promotion launched Tuesday.Adds a note.Confirm first
  • You sayAcknowledge the new customer-greeting standard.Acknowledges the current version.Confirm first
  • You sayHow am I doing on repeat customers?Reads back status and trend.
Example phrases; the unit and numbers are sample data.
Security and multi-tenancy

Every brand's data stays separate.

The database itself walls brands apart, and tests try to break through.

Tenant isolation at the databaseA request for Brand A reaches only Brand A's rows. Row-level security sits between Brand A and Brand B, and an attempt to cross it is blocked.Request · Brand ABrand ARow-level securityBrand BEach request sees one tenant

Isolated at the database

Row-level security, even if the app has a bug.

Cross-tenant leak tests

Cross-brand reads and writes must fail. Run on every pull request Planned

Key changes logged

Publishing, sharing and imports: who and when. Every change logged Planned

Owner-first

Owners decide who sees what.

No passwords

Google or an email magic link. SSO and SCIM Planned

Your content stays yours

Never used to train public models.

SignaUnit standardizes outcomes, not franchisee staff. Not legal advice. Security and data isolation · Roles and permissions

Get in touch

Tell us what you're rolling out

SignaUnit is in private development. Help shape it with us, starting on sample data.

  • What the priority was
  • Who it was for
  • How you'd know it worked
Email usRead the docs