NYPD paid detail management

every paid detail, proven and paid.

One platform to request coverage, verify the officer was there, approve the hours, and pay everyone to the cent, with an audit trail a city can trust.

Built on AWS GovCloud · us-gov-west-1 · encrypted · tenant-isolated

Five app screens: Home, Schedule, Clock In, Earnings, Profile
For agencies

Approvals without the paperwork

Every detail arrives pre-verified. Review hours, adjust with a reason, approve. The ledger and audit export write themselves.

For businesses

Coverage in minutes

Ask for where, when, how many, and what qualification. Get a quote before you commit and an invoice that matches it.

For officers

See only work you qualify for

Accept with one tap, check in on site, and get paid on a weekly batch. No double bookings, no disputes about hours.

One minute explainer

presence is proven, not claimed.

The server draws the geofence, measures the distance, rejects mocked GPS and stale timestamps, then discards the coordinates. What remains is a verdict you can audit, never a location you have to protect.

Geofence ring with the officer's position verified inside

see it run on your program.

A 20 minute walkthrough with demo accounts for officer, business, and administrator.

Product

six steps. one system of record.

This is the flow the app and backend run today. The state names are the real ones.

01 · REQUEST
shift · OPEN

A business asks for coverage

Where, when, headcount, and required qualification. A quote and a prepay hold land before anyone commits.

02 · ACCEPT
assignment · ACCEPTED

Only eligible officers see it

Eligibility, availability, and qualification are checked on the server. One officer per slot. No double booking.

03 · CHECK-IN
assignment · CHECKED_IN

Presence is proven, not claimed

The server draws the geofence, measures distance, rejects mocked GPS and stale timestamps. Coordinates are discarded after the verdict.

Geofence verification
04 · APPROVE
completion · APPROVED

A human signs off

An administrator reviews hours, adjusts billed time with a reason, and approves. The original check-out is never overwritten.

05 · LEDGER
financial record · balanced

Balanced to the cent

Business charge, admin fee, and officer payout are computed in integer cents and must sum. Every record stores the rate and fee that applied.

Ledger showing charge, fee, and payout
06 · AUDIT
export · READY

Written down forever

Hash-chained events per shift, actor identity hidden from non-admin readers, exports locked in write-once storage for seven years.

Worked example · one officer · 8 hours · $45/h · 10% fee
Business charge$360.00
Admin fee$36.00
Officer payout$324.00
Security

Government cloud

AWS GovCloud, us-gov-west-1. Customer-managed encryption keys, tenant isolation on every record, no cross-partition calls.

Privacy

No location retention

Only the verdict, distance, and accuracy are stored. Raw coordinates never touch the database or the logs.

Roles

Five, enforced by the API

Officer, Business Admin, Agency Admin, Finance, Auditor. Each route allows exactly the roles it should.

want the technical walkthrough?

Business

a fee on every verified hour.

A platform fee on every approved detail. Revenue scales with hours worked, not seats sold.

Platform revenue / month $72,000 $864,000 per year
Gross billed$720,000
Paid to officers$648,000
Shifts / month2,000

fee + payout = gross, to the cent.

Model a program
2,000
8.0 h
$45
10.0%

Defaults are the platform's constants: $45.00/h and 1,000 bps. Volume is a modelling assumption, not reported traction.

Who pays

The business

Property managers, venues, and city agencies prepay a hold at request time and are invoiced on approval.

Who benefits

The officer and the agency

Officers see only work they qualify for and get paid on a weekly batch. Agencies get approvals, ledgers, and audits without staff hours.

Why we win

Compliance is the moat

Verified presence, role-redacted audit trails, and GovCloud residency are hard to retrofit. They are in the data model from day one.

bring us your program's numbers.

We will model it with you on a call.

Investors

fund the platform that proves the detail.

We are raising to move from a working pilot to a production GovCloud deployment and our first agency contracts.

  • Built. Mobile app for officers, businesses, and administrators. Backend with the full request-to-payout flow and an audit export pipeline.
  • Specified. A production PRD targeting AWS GovCloud: Cognito, API Gateway, Lambda, DynamoDB, S3 Object Lock, all in us-gov-west-1.
  • Next. Payment provider integration, agency identity federation, and the first live tenant.
Use of funds
  • Production infrastructure. GovCloud deployment, security review, and audit tooling.
  • Payments. Prepay capture, invoicing, and weekly officer payouts through a licensed provider.
  • Go to market. First agency and business accounts in New York City.
Request the deck and a live demo

Demo accounts are available for officer, business, and administrator roles.

Model

Usage-based

A fee on every approved hour. No per-seat licensing to negotiate, no adoption cliff.

Defensibility

Compliance first

Government cloud, verified presence, and tamper-evident audit are the product, not a checklist added later.

Expansion

Every city with paid details

The workflow is the same wherever off-duty officers work private details. New York is the first market, not the only one.