OpsCom

Your officers know the job.
They should not have to learn another system to do it.

A task that takes ten minutes of police work can take an hour of software.

Lt. Hashmal sits between your people and the systems they are required to use. The officer says what needs to happen.

Hashmal does the file conversion, the uploads, the form fields, the transfers. The officer verifies and approves.

Request a 30-day evaluation

The arithmetic.

Overtime

is filling the gap. In May 2026, one of the largest sheriff's departments in the country directed deputies to finish reports inside their regular shifts rather than on overtime.

NBC4 Investigates, May 2026.

Sheriffs' offices, police departments, and training centers are all running the same arithmetic. You cannot hire your way out of it in this market. The hours have to come from somewhere else.

Why experienced officers are slow at this.

The problem is not skill. A twenty-year deputy knows the job better than any software will.

The problem is that the job now runs through a stack of systems: dispatch, records, jail, evidence, property, fleet, court. Each has its own interface, its own login, its own file requirements. Each gets replaced or upgraded on its own schedule. Training arrives once, at rollout, and then stops.

Officers say this themselves. In a 2025 nationwide survey, they reported not receiving adequate training on the technology they are issued, and described learning systems on their own or from younger colleagues.

Police1 What Cops Want survey, 2025. First-responder usability findings from NIST Public Safety Communications Research.

So the interface becomes the bottleneck, and the person paying for it is the officer at the end of a shift.

Today: officer must learn every systemSeven system boxes across the top: dispatch, records, jail, evidence, property, fleet, court. One officer circle at the bottom. Seven arrows from the officer up to each system.TODAYseven interfaces, seven ways to be slowDispatchRecordsJailEvidencePropertyFleetCourtOFFICERWith Hashmal: officer works through one layerSeven system boxes across the top. An amber Hashmal layer spans the middle. One officer circle at the bottom. One arrow from officer up to Hashmal. Seven arrows from Hashmal up to each system.WITH HASHMALone interface, one hand on the wheelDispatchRecordsJailEvidencePropertyFleetCourtHASHMALOFFICER

How it works.

  1. 01
    The officer states the task.

    In plain language. Not a form, not a menu path.

  2. 02
    Hashmal operates the systems.

    Within agency-approved permissions and defined credentials, it converts the file to the accepted format, navigates the approved interface, fills the fields, attaches what belongs, and transfers what needs transferring.

  3. 03
    Hashmal flags what it cannot resolve.

    Missing information, conflicting entries, anything requiring judgment.

  4. 04
    The officer verifies and approves.

    Nothing is submitted without a person. Every action is logged with its source.

Your systems remain the systems of record. Hashmal does not replace CAD, RMS, JMS, evidence, property, fleet, or court systems. It operates them, the way your officer would, and then hands the result back for approval.

The four-step sequenceFour nodes in sequence. Step one: the officer states the task. Step two: Hashmal operates the systems. Step three: Hashmal flags what it cannot resolve. Step four: the officer verifies and approves.01OFFICERStates the taskPlain language.02HASHMALOperates systemsApproved permissions.03HASHMALFlags the gapsMissing or conflicting.04OFFICERVerifies, approvesEvery action logged.
The four-step sequenceFour steps stacked. Officer states, Hashmal operates, Hashmal flags, officer verifies.01OFFICERStates the taskPlain language.02HASHMALOperates systemsApproved permissions.03HASHMALFlags the gapsMissing or conflicting.04OFFICERVerifies, approvesEvery action logged.

A randomized controlled trial published in 2024 found that AI narrative generation does not reduce report writing time. Hashmal operates on the task, not on the prose.

Journal of Experimental Criminology, 2024. Pre-registered RCT.

Sgt. Gabriel

Where the accuracy comes from.

Speed is only useful if the record holds up. Sgt. Gabriel checks the output before it goes anywhere: contradictions between the narrative and the underlying record, fields that cannot be traced to a source, missing attachments, clocks running out. Every element carries provenance, so your people can answer where each item came from and when.

The path a case file takesHorizontal flow of four stages: agency systems, manual assembly by the deputy, prosecutor intake review, then defense at motions and trial. The first two stages sit inside your building; the last two sit outside it. An amber checkpoint sits between manual assembly and prosecutor, labeled Gabriel checks here before the file leaves.INSIDE YOUR BUILDINGOUTSIDE ITAgency systemsCAD, RMS, videoManual assemblyend of shiftProsecutorintake reviewDefensemotions, trialGabriel checks hereon the case file, before it leavesfirst careful read today
The path a case file takesVertical flow of four stages: agency systems, manual assembly, then prosecutor and defense. Amber checkpoint between manual assembly and prosecutor labeled Gabriel checks here before the file leaves.Agency systemsCAD, RMS, videoINSIDEManual assemblyend of shiftINSIDEProsecutorintake reviewOUTSIDEDefensemotions, trialOUTSIDEGabriel checks hereon the case file, before it leavesfirst careful read today
What Sgt. Gabriel checksAbstract case file diagram. Seven horizontal rows, each an element of the case record. Four rows carry a cleared marker in cleared green; three rows carry a flagged marker in amber. To the right, a vertical Defensibility Index scale with the current file marker sitting low. Illustrative, not a product screen.Officer narrativeBody cameraAttachmentreferenced, missingTimestamp originRecording alignmentnarrative disagreesChain of custodyunsourced entryForfeiture clockDEFENSIBILITYINDEXthinCASE FILE

Illustrative, not a product screen.

Security and CJIS.

OpsCom is built to the CJIS Security Policy. Below is what that means in practice. CJIS compliance is assessed against each agency's own implementation, so we support your review with documentation and a named point of contact rather than asserting a status on your behalf.

Where your data lives

OpsCom runs in AWS GovCloud (US). Agency data stays inside US regions built for controlled government workloads. It does not leave that environment.

Credentials

OpsCom does not store agency credentials. Lt. Hashmal operates approved systems under authorization the agency controls and can revoke, and every action is attributable to the officer who approved it rather than to an anonymous service account.

Human approval

Nothing consequential is submitted without a person. Hashmal prepares, navigates, fills, and flags. An officer verifies and approves. That gate is not configurable away.

Audit trail

Every action is logged with its source system, the action taken, the approving officer, and the time. The agency can export the full log. Retention follows the agency's own policy and applicable law.

On officer data

Output is case-level and workflow-level. Access, retention, and use are controlled by the agency under its own policy. OpsCom is not built as an individual performance or discipline instrument, and the evaluation terms define exactly who sees what.

Technical reviewers: request the full data handling and CJIS documentation packet at hello@opscom.io.

How this rolls out.

Four phases. You can stop after any of them.

The four-phase deployment trackHorizontal rail with four markers. Phase one: demonstration, one session. Phase two: evaluation, thirty days, run under an MOU or as a paid engagement quoted to scope. Phase three: pre-deployment, three to six months. Phase four: full deployment, sized to the agency. Phases one and two render muted, phase three in raised navy, phase four in amber.PHASE 01DemonstrationOne sessionPHASE 02Evaluation30 days, MOU or quotedPHASE 03Pre-deployment3 to 6 monthsPHASE 04Full deploymentSized to your agency
The four-phase deployment trackVertical rail with four markers. Phases one and two muted; phase three raised navy; phase four amber.PHASE 01DemonstrationOne sessionPHASE 02Evaluation30 days, MOU or quotedPHASE 03Pre-deployment3 to 6 monthsPHASE 04Full deploymentSized to your agency
  1. 01
    Demonstration.

    A working session, not a slide deck. We show Lt. Hashmal operating on a workflow you recognise.

  2. 02
    Evaluation, thirty days.

    One workflow you select. We measure a baseline before anything runs, your personnel judge the result, and you receive the full findings either way.

    Most agencies run this at no charge under a short memorandum of understanding. The MOU sets out, in writing and before we begin, what the evaluation has to demonstrate. Your criteria, not ours. If we meet them, you take the result into your normal procurement process. If we do not, you owe nothing and you keep the baseline, the measured results, the issue log, and the workflow map.

    Where an agency would rather not set criteria in advance, we still run the evaluation as a paid engagement, quoted to scope. An evaluation without criteria is consulting, and we price it as consulting.

  3. 03
    Pre-deployment, three to six months.

    Scope widens from one workflow to the set your agency actually runs. We measure what your people use, what they do not, and where the time really goes.

  4. 04
    Full deployment.

    Sized to what the measurement showed.

On pricing across those phases

The pre-deployment period exists so that what you eventually buy matches what your agency uses. We would rather size a deployment correctly than sell you seats that sit idle. Scope and price are set from the measurement, not from a headcount estimate made before anyone had used it.

Your existing platforms remain the systems of record throughout. Nothing about this replaces CAD, RMS, JMS, evidence, property, fleet, or court systems.

How agencies buy OpsCom.

We are a registered federal contractor

OpsCom is registered in SAM.gov with an active UEI and CAGE code, and is eligible to receive federal awards and to be purchased with federal funds.

Most agencies do not need a formal solicitation to start

The demonstration carries no cost. The thirty-day evaluation runs at no charge under a short MOU that sets out what it has to demonstrate, agreed with you in advance. The MOU commits no agency to a purchase. It commits us to a standard, and it commits the agency only to taking the result into its own procurement process if that standard is met.

When an agency chooses to continue, the initial deployment is typically sized to a defined unit rather than to total sworn, which keeps the first purchase inside the small purchase threshold most jurisdictions set for direct departmental buys. We confirm your threshold with you rather than assume it.

Federal funds

Federal award purchases follow federal thresholds: minimal process at or below the micro-purchase threshold, and simplified procedures requiring quotes from more than one qualified source below the simplified acquisition threshold. Our registration supports either.

Piggyback access

Where an agency has competed a contract that permits piggyback use, we agree to that use so neighbouring agencies can buy under it without running their own solicitation.

Sole source

Where your counsel determines sole source documentation is required, we provide it on request, including the technical basis and the competitive landscape as we understand it.

What you receive at the end of an evaluation

The baseline, the measured results, the issue log, the workflow map, and a written proposal with scope, price, and start date, in a form your purchasing office can act on.

Standard terms: opscom.io/how-we-work

Registration details and documentation: hello@opscom.io

The evaluation

One workflow, selected by your agency. Thirty days.

The 30-day evaluation timelineHorizontal timeline with three marks. Day zero: baseline measured. Days one through twenty-nine: controlled use with human approval at every consequential action. Day thirty: readout with four artifacts.DAY 0Baseline measuredbefore any useDAYS 1 TO 29Controlled usehuman approval at every consequential actionDAY 30Readoutbaselinemeasured resultsissue logworkflow mapyours whether or not you continue
The 30-day evaluation timelineVertical timeline. Day zero baseline measured. Days one through twenty-nine controlled use. Day thirty readout with four artifacts.DAY 0Baseline measuredbefore any useDAYS 1 TO 29Controlled usehuman approval at everyconsequential actionDAY 30Readoutbaselinemeasured resultsissue logworkflow mapyours whether or not you continue
  • 01Baseline measured before any use
  • 02Your existing platforms remain systems of record
  • 03Defined users, permissions, and approval points
  • 04Human review of every consequential action
  • 05Complete activity and source audit trail
  • 06No purchase obligation and no automatic renewal
  • 07You may stop at any time

Run under a short MOU setting out the conversion criteria, agreed with you before the baseline is measured.

At the end you receive the baseline, the measured results, the issue log, and the workflow map, whether or not you continue with OpsCom.

What we measure

Handling time per task, steps requiring officer input, corrections and rework, and the share of that time falling outside regular shift hours. Your numbers, from your baseline. We publish no figure we did not measure at your agency.

We did not read about this problem.

Scott Hudson, co-founder and COO, is a former US police officer with DHS service.

DY Kim, co-founder and CEO, ran protective operations across five conflict zones with Presidential Security Service and UN close protection. He and Scott served together in Iraq.

Sang Dang, co-founder and CTO, built the contradiction engine and the CJIS-aligned runtime.

Backed by Hustle Fund and NEC X. Member of NVIDIA Inception.

Three ways in.

Training centers: ask about per-officer measurement across a training cycle.

Not the right person? Forward this, or tell us who owns records, digital evidence, dispatch workflow, or public safety technology at your agency.

hello@opscom.io