# Innerloop

> Read-and-acknowledge receipts and a feed every shift worker can reach, without a company email — what Workvivo starts selling at $20,000 a year.

Source page: https://saascode.ai/products/innerloop
Machine-readable record: https://saascode.ai/products/innerloop.md

One-time purchase · full source code · self-hosted by the buyer.

Price: $299 (one-time)

## How to read this document

Written for a model auditing this product on a buyer's behalf. Two labels
appear throughout and they mean different things:

- **measured** — produced by a script reading the product's own source tree
  or database at the stated date. The method is named beside each number.
- **stated** — written by the seller. True or not, it is a claim, and this
  document does not ask you to treat it as evidence.

The live demo is the strongest verification available from outside: it runs
the same source a buyer receives. Nothing to sign up for — the public side is
open, and the seeded credentials below get you into each role.

## What it is

Innerloop is a company-branded internal social network and communications hub, built mobile-first to reach the deskless and frontline majority — retail, healthcare, hospitality, manufacturing — as well as office staff.

## Live demo

Two doors into the same running instance, and the same source a buyer
receives. There is no account to create; the public side is open, and the
seeded credentials below sign you into each role.

- **Guided (recommended):** https://saascode.ai/demo/innerloop — our shell, with a role switcher and
  the credentials in the menu. Best for a person.
- **Direct:** https://innerloop.saascode.ai — the product on its own, no chrome.
  Best when you are relaying steps to someone, or fetching a page.

4 roles seeded on the demo (of the 6 the schema defines — the build data below counts them all). Credentials are published deliberately: these
are demo accounts on a public demo instance, and a reviewer who cannot get
in cannot verify anything.

- **Employee** (`member`) — `user@demo.com` / `demo123`
  The employee surfaces of the company app.
- **Editor** (`editor`) — `jordan.kim@demo.com` / `see the page`
  Writes and publishes what the company reads.
- **Company admin** (`org_admin`) — `org-admin@demo.com` / `demo123`
  Runs the company account and its people.
- **Platform admin** (`super_admin`) — `admin@demo.com` / `demo123`
  The backend: every organisation, across orgs.

Or open a role directly: https://saascode.ai/demo/innerloop?role={role}

## Measured build

*measured — each number names the method that produced it.*

- **roles: 6** — distinct roles accepted by the role CHECK constraint: admin, editor, member, org_admin, super_admin, viewer
- **tables: 78** — distinct CREATE TABLE statements across every applied migration
- **migrations: 85** — .sql files in supabase/migrations
- **page modules: 96** — files named page.tsx under src/app, excluding node_modules and .next
- **source lines: 141,438** — lines of code (comments and blank lines excluded) across 1032 TypeScript files (127,111) and 118 SQL files (14,327); node_modules and .next excluded
- **api route files: 248** — files named route.ts under src/app/api
- **http operations: 312** — exported HTTP method handlers across those files, de-duplicated per file, OPTIONS excluded as CORS preflight
- **schema graph: 78 tables, 141 relationships** — parsed from the applied migrations

A large number here is scope, not quality. It says the product models a
real domain rather than a CRUD skeleton; it says nothing about code
quality, duplication, test coverage or maintainability, and should not be
read as if it did.

Release: v1.0.0 · built 2026-07-23

## Complete capability inventory

19 capabilities. Each summary is *stated* — selected from the
product's own buyer documentation, or written by the seller where marked.

### Announcements & reach

- **Content announcements (targeted)** — Company announcements published by an administrator or communications staff, targeted to an audience, scheduled, and delivered across channels — in-app, web push, email, and SMS where a company opts into it.
- **Advanced reach analytics** — The part that makes internal communications defensible rather than hopeful.
- **SMS delivery tier (hard-gated)** *(seller-authored)* — Adds SMS as a delivery channel for announcements and tasks, for the workforce that has a phone number and no company email address. It is hard-gated to a tier because message costs are real and per-recipient.
- **Programmatic API + MCP (Connect)** *(seller-authored)* — Exposes announcements, tasks and audience operations as single workflow calls with a machine-readable bridge, so an HR system elsewhere can publish to the right segment without a person retyping it.
- **Web push (OneSignal)** *(seller-authored)* — Browser and device push notifications, so an urgent announcement reaches someone who is not sitting in the app. Push is the channel that makes a same-day message actually same-day.
- **Frontline tasks & must-reads** — Segment-targeted tasks delivered by push, with completion tracked to the same standard as acknowledgements — per employee, timestamped, and reportable.

### Feed, spaces & people

- **Social feed + reactions/comments** — An organization-scoped post stream with reactions and comments, targeted by team, location or role so a store associate is not reading head-office material.
- **Spaces (topic/team/location)** — Topic, team and location spaces that employees join and leave, each with its own posts. Space count is one of the things plans scale.
- **Recognition & kudos + points** — Peer-to-peer recognition with badges, and an optional points ledger with a leaderboard.
- **1:1 direct message** — One-to-one messaging on every tier. Group chat is a gated capability on the higher tiers.
- **Group chat** *(seller-authored)* — Multi-person conversations for a shift, a project or a location, alongside the one-to-one messaging that ships on every tier. It arrives on a higher tier — revenue the buyer can reserve for their own larger customers.
- **People directory + org chart** — Extended employee profiles with search, plus an org tree built from a recursive query with a depth cap.
- **SSO (Microsoft Entra)** *(seller-authored)* — Single sign-on against the company's existing identity provider, so employees arrive already authenticated and leavers lose access when their main account is disabled rather than whenever someone remembers.
- **Company branding (logo/color)** *(seller-authored)* — Per-organization logo and colour, so the app reads as the employer's own rather than as a third-party tool staff were told to install. On an internal product that is most of whether people open it.

### Learning, surveys & mobile

- **PWA-lite (install + offline read)** — Onboarding without a corporate email. Phone number, QR code or one-time code. An employee with no company address is not an edge case in a retail or hospitality workforce — they are most of it, and a product that requires an email to sign up has already excluded the people it is sold to reach.
- **Surveys / eNPS / polls** — Polls, pulse surveys and employee net promoter score, with a results dashboard.
- **Learning paths** — Assignable content — articles, videos, quizzes and acknowledgements — grouped into paths and tracked to completion.

### Other

- **Acknowledgement audit trail**
- **Named reusable audience segments**

## What each system gives the operator

*stated.*

- **Announcements & reach** — You can prove a policy reached the people it was written for.
- **Feed, spaces & people** — Frontline staff get a place to be part of the company, not only be managed by it.
- **Learning, surveys & mobile** — A new hire's first two weeks run the same way for everyone, on a phone.

## The problems it was built to solve

*stated — the seller's argument, given in full so you can judge it.*

### You can name the people who have not read the policy yet.

Internal communication is usually measured by what was sent. A notice goes to everyone, engagement is reported as a percentage, and the question that actually matters — did the twelve people this concerns see it — has no answer. It stays theoretical until something goes wrong on a shift and somebody asks whether the person had been told. At that point the honest answer is that a message was published, which is not the same thing, and everyone in the room knows it.

### A store associate reads what concerns their store, on their own phone.

Most internal tools are built for the head office and handed to the frontline afterwards. The result is a feed full of material about departments the reader has never met, arriving on a channel that assumes a company laptop and a work email address. Frontline staff stop opening it within a month, and the company concludes its people are disengaged rather than that it has been broadcasting to the wrong audience on the wrong device.

### Every new hire gets the same onboarding whether or not their manager is free.

Onboarding quality tracks manager availability, and nothing else. A hire who starts in a quiet week gets the tour, the context and the introductions; one who starts during a launch gets a laptop and good luck. The difference shows up months later as uneven ramp times and early attrition that gets attributed to fit. Nobody connects it back, because by then the two weeks that caused it are long forgotten by everyone except the person who lived them.

## What it takes to run it

*stated — external services the buyer supplies and pays for directly.*

- **Node host** (required) — No platform lock-in.
- **Supabase** (required) — Postgres with row-level security, applied by the shipped migration scripts.
- **A payment provider** (required) — Per-seat subscription quantity. Configured by the operator, not hardwired. A provider without native per-seat quantity falls back to a standard subscription.
- **Email provider** (required) — Announcements, digests and notifications.
- **Web push provider** (required) — The primary channel for deskless staff.
- **A job queue** (required) — Announcement fan-out runs in batches outside the publishing request. Without it large sends will not complete.
- **SMS provider** (optional) — Only if the SMS delivery tier is enabled.
- **Roster import** (included) — Employees load by CSV; per-organization credentials for it are stored encrypted.

## FAQ

**What exactly do I receive after purchase?**

The complete source repository behind the live demo — 141,438 lines across the application and its database, 78 tables defined by 85 migrations that the shipped scripts apply for you, plus the seed data, the demo accounts and the setup documentation. Not a subset and not a scaffold: the same code that runs the demo you just used.

**Is the live demo the same product whose source I receive?**

Yes. The Innerloop demo runs the delivered release (v1.0.0), and the build figures on this page are measured from that same source — not from a showcase build kept separately.

**Can I test every account role before buying?**

Yes — all 4 of them: Employee, Editor, Company admin, Platform admin. Each one is seeded in the live demo and reachable from the role board above, so you can inspect the product from the customer's side, the agent's side and the administrator's side before you decide.

**Is this a complete product or a starter template?**

Complete. 96 page modules and 312 HTTP operations, with authentication, roles, billing, an administration panel, background jobs and seeded demo data all wired and running. A template gives you the shape of an application; this is one you can deploy and start operating.

**Can I rebrand and modify it?**

Yes, without asking. The name, identity, copy, styling and code are yours to change. Rebranding and operating it as your own service is exactly what the licence is for.

**What does the licence allow?**

A perpetual, worldwide, non-exclusive, non-transferable licence to the product you bought and to every update released for it. The Standard licence covers one business — yours. If you deploy for clients, the Client licence covers up to five. You can modify it, rebrand it, deploy it and charge your own customers.

**Can I resell the source code?**

No. Reselling, redistributing, sublicensing or giving away the source itself is not permitted under either licence. You build and deliver products with it — the code stays with you.

**What services and ongoing costs are required?**

You bring your own accounts, so we never mark anything up and there is no ongoing cost to us beyond the purchase. Required: Node host, Supabase, A payment provider, Email provider, Web push provider, A job queue, Roster import. Optional: SMS provider. The table above says exactly what stops working without each one; most have usable free tiers at low volume.

**How difficult is deployment?**

Two ways, and most buyers use the first. The installer in your saascode dashboard walks it: you create free accounts at Vercel and Supabase, connect them, and it provisions the database, applies 85 migrations, seeds the data, deploys and verifies the result — you watch the steps go green. Or take the source and do it yourself with the shipped scripts and docs, which is the same sequence run by hand.

**What updates and support are included?**

Updates to that product for as long as we maintain it — no renewal fee and no expiry date on your access. Support covers download problems, defects in the code as shipped, questions about what the product does and how it is structured, and licence questions. It does not cover debugging your own modifications, building features for you, or setting up your hosting and third-party accounts.

**Why does a complete codebase cost $299?**

Because it was built once and is distributed many times. SaaSCode builds each product and ships the same finished release through the catalog, so the price reflects repeatable distribution — not a reduced codebase, an unfinished template, or what the same work would cost commissioned.

**Do I need to be a developer?**

No, for the normal path. You create free accounts at Vercel and Supabase, connect them to the installer in your saascode dashboard, and it does the deployment for you — provision, migrate, seed, deploy, verify. What it asks of you is creating two accounts and copying a token, not writing code. If you would rather deploy it yourself, or host it somewhere else, the full source and the scripts are yours to do that with. Running the product day to day needs no technical skill at all: that happens through its own interface, which is what the demo shows.

## Licence

The buyer receives the complete source and may deploy, modify and operate it
as their own SaaS, charging their own customers. The source itself is not
resold or redistributed: you build and deliver **with** it, you do not sell **it**.

## What this document cannot tell you

Stated plainly because a review that misses it is not a review:

- code quality, duplication, or architectural consistency
- test coverage
- query performance under load
- security posture beyond what the stack implies
- how maintainable it will be in a year

Scope is measurable from outside; implementation quality is not. Anyone
evaluating this should say so rather than infer quality from size.

## Written about it

- [Employee Communication Platforms 2026: A Buyer's Guide for Frontline and Deskless Workforces](https://saascode.ai/inside/employee-communication-platforms-2026-a-buyer-s-guide-for.md)
- [One Vendor in This Category Will Tell You the Price](https://saascode.ai/inside/innerloop-vs-blink-vs-viva-engage-employee-communications.md)
- [Innerloop: employee comms that reach shift workers without a company email](https://saascode.ai/inside/road-to-innerloop.md)

## Links

- Catalog page: https://saascode.ai/products/innerloop
- Product record: https://saascode.ai/inside/products/innerloop
- Live demo: https://innerloop.saascode.ai
- Every product: https://saascode.ai/llms.txt