Bring someone on once. Every app knows their role.
Connected apps for companies that put people on shifts: training, scheduling, shared texting, site maps, shift reports and certificates. Built inside a working staffing company, for the people who do the work.
One door, one memory.
StaffLaunch is the door: identity, roles, training and the app catalog. StaffQuery is the memory: a typed, linked database every other app reads and writes.
The rest are focused tools that share both, so the company has one source of truth for every person, client and shift.
What it looks like for one person
Riley is a fictional new hire, and the screens are real apps seeded with demo data.
-
New hire
Signs in once and starts with the welcome guide
The New Hire role shows the docs library and the welcome guide. Everything else stays out of the way until Riley is ready for it.
-
Valet
Passes at 80% and the role is granted
A graded doc adds the Valet role on the spot. Schedulrama, Valetra and speedTPS appear on the dashboard with the right permissions already set inside each app. Nobody files a ticket.
-
On the schedule
Answers availability from a text
Each availability campaign goes out by text and email. Staff reply from a link on their phone, with no app to install, and coverage fills toward its target as they do.
-
Event night
Works from a map that stays current
Zones, cone lanes, flow arrows and runner posts live on a LogicLot map. When the lead edits it, every phone on the crew updates within a second. The shift closes out in speedTPS.
-
Lead and site manager
Sees more, in the same documents
Billing contacts and damage-claim rules sit in the same playbook, gated paragraph by paragraph. A promotion in StaffLaunch re-applies inside every app on the next launch.
The apps, by the job they do
The door and the memory
Filling shifts and reaching people
On site
Fleet
Records and running the company
Coming next, and not available yet: PactPad for contracts and PayRelay for payments. See the full roadmap.
Born in valet and events. Shaped for any company with shifts.
Tables, fields, roles, maps and documents are configured rather than coded, so the words change and the engine doesn’t.
| Industry | A person is a | A place is a | Work is a | Proof is a |
|---|---|---|---|---|
| Valet and events | Valet | Venue or residence | Event shift | Shift report |
| Healthcare | Clinician | Facility or unit | Per-diem shift | Credential |
| Construction | Tradesperson | Job site | Crew call | OSHA card |
| Security | Officer | Post | Patrol shift | Guard card |
| Live production | Crew member | Venue or stage | Call | Rigging cert |
| Hospitality | Associate | Property | Banquet | Service cert |
Who can see what, and who changed it.
- Launch tokens bound to one app
- Every launch is a signed token that lives 45 seconds and only works in the app it was minted for.
- Two-factor on email sign-ins
- TOTP on email sign-ins, Google sign-in, and optional password re-entry for sensitive apps.
- Visibility set per field
- Pay rates, gate codes and risk notes are admin-only, and the API needs an explicit flag to read them.
- A history on every value
- Every cell records which app wrote it and what it replaced. Every change is in the audit log.
Follow Riley through the whole suite.
The tour goes app by app, from first sign-in to site manager, with the connections between them.
Take the suite tour