What you get4 things, handed over
- A process that runs itself and keeps a record
- Bots that read the portals so nobody has to
- A model that drafts, and a human gate where judgement belongs
- A trail of who decided what
Where the human sits, and how the cutover is decided. Machine work runs left to right — read the sources, extract, draft — and stops dead at the gate, which is a person approving an output before it becomes a commitment. Underneath, the old process runs in parallel against the same inputs, and the two record sets are compared. The parallel run is what decides the cutover, not the deadline: nobody switches on faith, and the comparison is the evidence that they do not have to.
How it runsautomate5 steps · 2 decisions
Watch the process as it is
The spreadsheet, the email chain, the person who remembers the exception. All of it counts.
Draw the line
Mechanical work moves to the machine. Judgement stays with a person.
DecisionWhat must a human still approve? Getting this wrong is how automation loses trust.
Build the smallest thing
The narrowest change that removes the manual step, not the platform someone could imagine.
Run both in parallel
Old process and new one together until the records match. Nobody switches on faith.
DecisionCut over, or go back and fix it. The parallel run decides, not the deadline.
Hand over the keys
Source, documentation, and deploy control. You should be able to fire me without losing the system.
What this covers6 areas, and where each one bites
- Human gatesEvery output a machine produces stops at a person before it becomes a commitment. Automation that hides its reasoning gets switched off the first time it is wrong.
- Audit trailWho decided what, when, on what input. By default, not as a feature someone remembers to enable.
- Parallel runOld process and new one against the same inputs until the records agree. The comparison decides the cutover.
- Portal readingBots watch the federal, state and subcontracting boards daily, so no opportunity depends on someone remembering to look.
- Data lineageA number in a report is only useful if someone can trace it back. Sources and transforms written down, not implied.
- The keysSource, documentation and deploy control in your account. You should be able to fire me without losing the system.
Models draft and bots read. Neither signs anything. Every commitment on a machine-produced output carries a human name, and the trail records whose.
The opinion behind it
Automation that hides its reasoning gets switched off the first time it is wrong. Record who decided what, and it survives.
What holds this workstandards we know, not certifications we hold
- Human sign-offNo machine output leaves as a commitment without a person approving it. This is a design rule, not a setting.Every output
- Audit trailInput, decision, decider and time recorded by default, in a form an auditor can read.Every run
- Parallel runThe new path and the old one against the same inputs until the records match. No cutover on faith.Before cutover
- Your existing stackBuilt into the tools you already pay for, wherever that is possible, rather than one more subscription.Where it can be
Where it stopsan empty row is work this firm does not take
What that covers
- Workflow automationThe spreadsheet-and-email process that eats a day a week, turned into something that runs itself.
- Data pipelinesPipelines and reporting where you can trace every number back to where it came from.
- AI-assisted draftingPut AI on the repetitive reading and drafting, with a human signing the result.
Capacity
The machines are the capacity. Bots read every portal daily, models take the first pass at anything document-heavy, and what arrives at a person is already sorted — which is how one engineer covers ground that would otherwise need a desk of people.
What does not scale is the deciding, and it is not meant to. The gate is the product.
How the work gets doneevery engagement, every page
Bots read the portals
SAM, the state portals and the subcontracting boards, every day, so no opportunity depends on someone remembering to look.
Models do the first pass
The reading, the mapping and the first draft of document-heavy work, where a machine is fast and tireless.
A person decides and signs
Every judgement call, every commitment and every signature is human, and the record says who.
One engineer, fixed scope
You get the person you evaluated, on a scope agreed before the work starts, and no invented follow-on.
How you can hire mescope is agreed first; price is a conversation — the scope sheet
On retainer
A senior quality lead a few days a month, holding the program and reachable when something goes sideways.
Fixed scope
A defined look at one problem, a defined amount of time, a written answer. No obligation after.
By the hour
An hour with someone who has built the thing you are asking about. Straight answers, no deck.
Start a conversationStraight answer, no deck. What it takes to start.
One standard, more than one verbwhy these are four sheets and not four firms
- NQA-1NQA-1 — Build: we write toNQA-1 — Prove: we write toNQA-1 — Automate: does not applyNQA-1 — Win: does not apply
- 10 CFR 50 App. B10 CFR 50 App. B — Build: we write to10 CFR 50 App. B — Prove: we write to10 CFR 50 App. B — Automate: does not apply10 CFR 50 App. B — Win: we write to
- ISO 9001ISO 9001 — Build: we write toISO 9001 — Prove: we write toISO 9001 — Automate: does not applyISO 9001 — Win: does not apply
- CMMC Level 2CMMC Level 2 — Build: we write toCMMC Level 2 — Prove: we write toCMMC Level 2 — Automate: does not applyCMMC Level 2 — Win: we write to
- NIST SP 800-171NIST SP 800-171 — Build: we write toNIST SP 800-171 — Prove: we write toNIST SP 800-171 — Automate: we write toNIST SP 800-171 — Win: does not apply
- WCAG 2.1 AAWCAG 2.1 AA — Build: does not applyWCAG 2.1 AA — Prove: we write toWCAG 2.1 AA — Automate: does not applyWCAG 2.1 AA — Win: we write to
- Section 508Section 508 — Build: does not applySection 508 — Prove: we write toSection 508 — Automate: does not applySection 508 — Win: we write to
- FARFAR — Build: does not applyFAR — Prove: does not applyFAR — Automate: does not applyFAR — Win: we write to
- Audit trailAudit trail — Build: we write toAudit trail — Prove: we write toAudit trail — Automate: we write toAudit trail — Win: we write to
Audit trailThe one line that crosses all four. Every practice here ends in a record of who decided what, because none of the others survive without it.