Work the case.
The report writes itself.
The OR co-pilot for surgical device reps. Cards, plans, live capture, continuity.
A new rep should never cost you a surgeon.
When a rep leaves, their knowledge leaves too. The new rep walks in blind, faults the surgeon once — sometimes that's all it takes.
RepOS makes that knowledge transferable. The next rep walks in already knowing.
Face ID and you're in.
Your book stays locked. Face ID in, auto-lock when idle.
The day, on one screen.
Cases, lunches, coverage, credential clock. One tap deep.
What you carry. Who you cover.
Lines by company. Facilities. One-tap backup — your book stays yours.
Never hunt for an expiration again.
Itemize once. RepOS tracks the soonest per platform and warns you 60 days out.
Everything he wants, before he asks.
Per surgeon, per procedure. Recorded once. Recalled every case.
"I didn't even have to ask — my rep made sure it was on the table."
The whole case, before you walk in.
The plan builds itself from his card. Plan B, plan C, the failsafe — each with its checklist. Whatever happens, you have a plan.
The spine, level by level.
Plan the construct pre-op — screws, cages, per level. Tap any level to update it live during the case.
Tap when it happens. That's the whole job.
Tap-to-stamp times and counters. Durations compute themselves. No paper, no 8pm recall.
Already written by the time you're at the car.
Mirrors your Salesforce form, field for field, in its order. Most fields fill themselves. Copy, paste, done.
Knowledge that survives the roster.
Cards shared across the team. You choose what's visible. No rep walks in blind.
A thinking partner, on tap.
Fast answers, grounded in your own cards. Ideas the night before.
OR decisions belong to the rep and surgeon. AI is a resource — take it with a grain of salt.
Built for the whole day, not just the case.
Your day, with real statuses
Schedule and calendar with statuses that mean something: Current, Moved up, Delayed, Rescheduled, Canceled, Completed, On time. Tap to change; everything stays in sync.
Preference cards with teeth
Hard rules, systems, sizes, positioning, loaner tools — and what each surgeon actually uses you for. The card is the source; the plan reads it.
What I carry
Define your companies and product lines once. Case plans stage that procedure's tools, sizing, trays, imaging and biologics as a checklist — you verify instead of retype.
Case history, per surgeon
Every past case on file: procedure, date, hospital, system. Import your real history; it stays on your device.
Live case and close-out
Stamp the moments as they happen. Four toggles at closure — aborted, revision, complaint, billable — and a complaint triggers its own follow-up.
The report, field for field
Mirrors the Salesforce case form exactly. Most fields fill themselves from the plan and the live case. One tap to copy.
Notifications that earn their place
Tomorrow's cases, credential expirations, complaint follow-ups, preference-card gaps — in the app and in the iOS Notification Center. You choose which.
Colleagues and coverage
Share a surgeon profile with a colleague who's covering — per share, hospital-credentialed only, expiring with the coverage. No rep walks in blind.
Ask AI, grounded in your cards
Answers from your own preference data, not the internet. Attach fluoro, CT or MRI for a structured read. OR decisions stay with the rep and surgeon.
Works without signal
Lose reception in the OR and nothing stops. Notes queue on the device and sync when you're back.
Credential brain
RepOS tracks your soonest expiration per platform. Nothing lapses quietly.
Your book. Your team's library.
Reps keep their own cards. Distributor teams get a shared library that survives the roster.
The surgeon knowledge that walks out when a rep does.
Most teams keep surgeon preferences in a shared notes doc. It rots, nobody knows what's current, and the new rep walks in blind. RepOS gives every rep their own book — and gives the team a library that survives the roster.
The rep's book
Personal preference cards, plans, and case history. Theirs, on their phone. That's why they actually keep it current.
The team library
Reps publish the cards the team needs. Coverage, onboarding, and a rep's exit stop costing you a surgeon.
Beside your billing platform, not instead of it
RepOS lives on the surgeon side of the case. Inventory, POs, and billing stay where they are.
Built for a regulated room.
No PHI, by design
RepOS runs on cases, preferences, and equipment — not patients. No patient identifiers, ever. The report excludes them on purpose.
Locked down today
Face ID sign-in. Auto-lock when idle. Data on your device. Credentials in the iOS Keychain — not web storage.
The team track
Team accounts are built toward encryption at rest and in transit, audit logging, and SSO — and because RepOS holds no PHI, a team deployment never needs a BAA to start.
Straight answer: RepOS captures no patient identifiers anywhere in the app, is not a system of record for protected health information, and won't claim certifications before they're earned. Teams evaluating a deployment — ask us where the roadmap stands.
Currently in field testing.
In field testing with working reps. Want in? Send your role and lines. Running a team? Use the pilot link above.
Request TestFlight access