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

Extend and connect

Integrations roadmap

What connects in v0.1, and what's planned.

On this page

SignaUnit sits on top of your existing tools. Integrations bring results in, so owners don’t retype them.

For how each HQ tailors SignaUnit (custom fields, checklists, objective types, webhooks, the scoped API and plugins), see Customization & extensibility.

In v0.1

Integration What it does
CSV KPI import HQ uploads unit-level metrics with column mapping and a dry-run preview. See KPI import.
CSV roster import Units, franchisees and regions, plus bulk owner invites
Google sign-in Continue with Google for HQ users and owners, the only sign-in method in v0.1
Email and push Owner invitations, batched notifications and escalations
Outbound webhooks Signed, retried and logged events (priority published, priority assigned, check-in recorded, audit closed, KPI updated) sent to your own systems. See Customization & extensibility.
Apple platform features On-device speech recognition and speech output

Next: the release after v0.1

  • QuickBooks, for unit-level revenue and margin measures behind profitability priorities. Planned
  • One field-service / operations connector, chosen with the first brands we work with, for conversion and customer follow-up measures. Planned
  • HQ single sign-on through SAML or OIDC, with SCIM for deprovisioning. Planned
  • More sign-in methods: email sign-in links, passkeys, Face ID unlock and Sign in with Apple, alongside Google sign-in. Planned
  • Scoped API with per-tenant API keys or OAuth clients. Planned
  • Weekly digest email for owners and HQ. Planned

Later, by value

These are listed in the order we expect them to matter most to franchise results. The order will be set with the first brands we work with.

  1. Lead sources and call tracking (for example web forms and call tracking) for speed-to-lead and response rate. This is the most direct measure of whether units are finding and converting leads. Planned

  2. Franchise and field CRMs (for example HubSpot, plus further operations systems) for conversion and customer follow-up. Planned

  3. Point of sale (for example Toast and Square) for sales and ticket measures in food and retail brands. Planned

  4. Financials and P&L uploads for unit profitability and early warning on units that are struggling. Planned

  5. Reviews (Google Business Profile) for review count, rating and response rate. Planned

  6. Franchise management suites such as FranConnect, through single sign-on links and deep links, so SignaUnit sits alongside the suite your owners already open. Planned

  7. Tenant-supplied unit economics uploads, only as files the franchisor provides. SignaUnit doesn’t scrape data. Planned

  8. Plugins: tenant-installed integrations that declare the scopes they need, approved by an HQ admin. See Customization & extensibility. Planned

Connectors are designed to work both ways: they pull KPIs in and push priority status out, so SignaUnit sits alongside your existing stack instead of replacing it.

Rules every connector follows

Every connector, now and later, follows the same rules:

  • Unit-level aggregates only. Connectors pull measures such as a unit’s average response time or close rate. They don’t import per-employee data, staff rosters, shift data or individual performance. Those are inputs that belong to the owner.
  • Credentials stay secret. OAuth tokens and API keys are held in a secrets manager, never stored in the database in plain text.
  • The source is always shown. Every imported value is labelled with where it came from.
  • Preview before trust. Mapping a connector to a priority’s metric includes a preview of the values it would produce.
  • Tenant-scoped. Connector data lands inside the tenant’s isolated space like everything else. See Security and data isolation.

Other planned capabilities

Beyond connectors, these are on the roadmap:

  • Answers from your approved content. Owners ask a question and get an answer drawn only from your approved material, with the source and how current it is. Planned
  • Drafted reminders, approved by a person before anything goes out. Planned
  • Regional adjustments to targets, with HQ approval. Planned
  • Multi-brand parents with several brands in one tenant. Planned
  • Deeper peer benchmarks. Planned
  • Light theme, iPad layout and Android (Android only if brands ask). Planned

Asking for an integration

If your brand depends on a system that isn’t listed, tell us what you’re rolling out. The first brands we work with help set the order of this list.