Off Duty Ninja for Work Request a preview
People are policy

Take care of your people. They'll take care of you.

Off Duty Ninja for Work makes it easy for your people to use the time off they've earned. Our rules engine reads your leave policy alongside the law where your people work, including paid sick leave, and shows every hour before it's lost.

Request a previewPrototype. We send each preview one to one.
Dashboard · Hours at risk at year end · sample company
Dashboard showing 1,912.00 hours at risk at year end across four units, for 41 of 148 people.

One rules engine. All 50 states researched.

Your policy is only as good as the law behind it. The engine reads both, rule by rule, and tells you where they meet and where they may not.

Your policy, rule by rule

Earning, carryover, caps, cash-out and payout, each tied to the section of your policy it came from.

Federal and state law

Use-it-or-lose-it, caps, payout at separation and paid sick leave. We've researched all 50 states from their official sources and are adding them to the engine state by state.

Where you may not comply

When a rule in your policy may conflict with the law where your people work, we flag it and show the source. Your counsel decides.

Policy · Rules to review
Rules to review: four rules with their source, two up to date, one needing HR review, and a state paid sick leave rule being checked.

Every number shows its math.

Hours come from your own policy rules, with the section each one used. Nobody has to trust a guess.

Employees

Employees can see the effect of the time off request in real-time.

Before they send it, each person sees what the time off does to their balance and how many hours they would still lose at year end.

Request leave
Request leave screen: 32.00 hours requested, hours at risk drop from 32.46 to 0.46.
Supervisors

Approve in Slack, where they already work.

The request arrives with team coverage and hours at risk. One click opens the math behind it.

Slack · Off Duty Ninja app
Slack message with a leave request, Approve and Decline buttons, and the math panel opened.
HR

Test a policy change before anyone feels it.

Put your current and new policy side by side and see hours lost, people affected and anyone left worse off. Nothing changes until you confirm.

Compare policies
Policy comparison: raising the carryover limit from 40 to 80 hours cuts hours lost from 1,912.00 to 640.00.

Running in three steps

On Basic you set it up yourself. On Team and Enterprise we set it up with you. Your people keep working where they already do.

  1. Send your staff list

    A spreadsheet is enough. Connecting your HR system is optional on Team.

  2. Set your policy

    We load your leave policy with you and check the hours against your own records.

  3. People request, supervisors approve

    Employees request. Supervisors approve in Slack. HR sees the whole company.

Three plans. Pick by how you work.

Start small on Basic. Move to Team when you need your own policy, Slack approvals and payroll. Enterprise adds what larger organizations need.

Small teams

Basic

Up to 10 people
Expected March 2027

So simple you turn it on and set it up yourself. No help from us needed.

  • Turn it on and set it up yourself
  • Pick a policy from our library
  • Load your team
  • Hours-at-risk dashboard
  • Each person's math, line by line
  • Employee view and requests
Request a preview
Most teams

Team

Any size
Expected May 2027

Everything in Basic, set up around your own policy and tools.

  • Import, check and compare your own policy
  • Slack approvals and reminders
  • Approvals with more than one step
  • Payroll file sent automatically
  • Roles and a full activity log
  • Sign in with your company account
Request a preview
Larger organizations

Enterprise

Any size, many structures
Date to be announced

Everything in Team, plus the controls a larger organization needs.

  • Everything in Team
  • Reconcile leave with payroll
  • Accounts that follow your company directory
  • Full company sign-in controls
  • Forecasts by your own structure: units, cost centers, locations
Request a preview

Founding customers

Our first three Team customers get a much lower setup fee and a discount for their first 12 months, in return for feedback and a case study we write together. Open to employers of up to 500 people. Ask about it when you request your preview.

Add-ons we're exploring

Tell us which would help you most when you request your preview.

  • Running payroll for you, through a partner
  • Time and attendance
  • Employee onboarding
Compare every feature
FeatureBasicTeamEnterprise
PeopleUp to 10Any sizeAny size
Policy from our libraryYesYesYes
Your own policy, imported and checkedNoYesYes
Compare a current and new policyNoYesYes
Hours-at-risk dashboardYesYesYes
Each person's mathYesYesYes
Employee view with the effect shown firstYesYesYes
"Take the time" suggestionsYesYesYes
Slack approvals and remindersNoYesYes
Approvals with more than one stepNoYesYes
Payroll file sent automaticallyNoYesYes
Roles and activity logNoYesYes
Donate and cash out leave, where policy and law allowNoYesYes
Sign in with Microsoft, Google or SlackNoYesYes
Connect your HR systemNoOptionalYes
Reconcile leave with payrollNoNoYes
Accounts that follow your company directoryNoNoYes
Full company sign-in controlsNoNoYes
Forecasts by your own structureNoNoYes

Built for people's data

Leave records are personal. Your people trusted you with them, and we keep them that way. Here is exactly how, in terms your security team will recognize.

Each employer's data kept apart

Every record carries its company in every key, and every read and change names its company, with no default. A test of company separation runs on every build.

Sign-in hardened

Passwords of at least 12 characters, sessions that end after 8 hours, sign-in limited to 10 tries a minute, and form posts from other sites refused.

Strict browser protections

HTTPS forced for a year, framing blocked, and a content policy that allows no inline or outside scripts. Nothing loads from another site, and no reply with data is cached.

No AI on your people

The rules engine is plain code with no AI library, and nothing about a person is sent to an AI. The engine never runs in the browser.

No names in our logs

Log lines are event codes. Email addresses are stripped from any error text, and no log line carries a field about a person.

An activity log for HR

HR sees who did what, and when, on the Roles and activity page.

Patched on a clock

Dependencies are checked every week. Critical and high advisories are patched within 48 hours.

SOC 2 readiness

Each of these controls is mapped to the SOC 2 Trust Services Criteria for Security and Confidentiality, with an automated test that runs on every build. Quarterly access reviews and a written incident response plan cover the rest. This is readiness work. No SOC 2 report has been issued yet.

Ask Sensei

A question we haven't answered? Ask it here. A person replies by email within one business day.

We keep your question so we can reply. Nothing you send goes to an AI.

Questions HR asks first

Do we need an HR system to start?

No. A spreadsheet of your staff is enough. On Team you can connect your HR system later if you want it kept in sync.

Which chat apps does it work with?

Slack for now, with Microsoft Teams coming. Employees and HR can also use it in the browser.

Who sets up our policy?

On Basic, you do: pick a policy from our library and load your team, with no help needed. On Team and Enterprise, we do it with you and check the hours against your own records before anyone sees them.

See it with your own policy in mind.

Tell us a little about your team and we'll send you the preview video and demo, one to one.

Request a preview