Make healthcare coverage instantly knowable.
Backwork builds Verity, a source-backed coverage intelligence layer for prior authorization, claim validation, denial prevention, and payer-policy monitoring.
Too much healthcare work still depends on hidden rules: payer portals, policy PDFs, CMS pages, and plan-specific instructions that change without making much noise.
Verity turns those rules into answers teams can check before an authorization request or claim goes sideways: what is covered, what documentation is needed, whether prior auth is required, and where the answer came from.
What we believe.
Payer rules should be computable. If a policy affects coverage, documentation, authorization, claims, or reimbursement, software should be able to read it.
Every answer needs evidence. Verity shows source policies, effective dates, last-verified dates, confidence, and the places where the evidence is incomplete.
The useful moment is before submission. Catch the missing document, stale policy, or authorization requirement before it turns into rework.
We stay at the rule level first. Verity is built for coverage-policy and code-level work, so early customers do not need to send PHI/ePHI to get value.
What we are building.
Verity takes payer policies and turns them into validation decisions that people can inspect and software can use. The web app, API, feeds, webhooks, and monitoring all use the same policy layer.
The product has five pieces: structured payer-policy data, a coverage and claim validation engine, API and feed access, an operator UI for lookup and QA, and policy-change monitoring.
We are starting with DME and sleep billing. A narrow set of answers people can trust is better than broad coverage that falls apart when someone audits it.
Who is building this.
Tyler Gibbs
Founder & Lead Engineer
Tyler started Backwork after watching revenue-cycle teams dig through payer sites, policy PDFs, and source documents to answer questions that should have been easy to check. Verity is the attempt to make that work faster, clearer, and less dependent on someone knowing where the right PDF is buried.
LinkedInMove coverage decisions upstream.
Send top codes, payers, states, and denial pain points. We'll map the coverage requirements, documents, policy sources, recent changes, and API-ready outputs.