The Right Person for the Work You Can't Afford to Get Wrong

You've probably hired someone for a piece of work like this before — compliance documentation, a grant application, operational knowledge that needed to get captured somewhere. Someone who seemed qualified. Whose samples looked solid. Who turned in something that looked complete until it didn't.

The compliance document that wouldn't survive an assessor's first questions. The grant application that was technically accurate but never made the case. The operational knowledge that was supposed to get documented and didn't, because the person who held it retired and the filing cabinet is still full of things nobody opens.

The cost of getting this work wrong isn't usually immediate. It surfaces later — in a failed audit, a rejected application, a critical process that nobody on staff knows how to run anymore. By then the window has closed, the deadline has passed, or the person who knew is gone.

There are three specific problems Broadaxe Digital is built to solve.

If you need compliance documentation that will hold up

CMMC 2.0 Phase 1 is active. If you're a defense contractor pursuing DoD work, self-assessments are now a condition of contract award. Phase 2 — mandatory third-party certification for Level 2 — arrives November 2026. Contractors who arrive at that window without a defensible System Security Plan don't face a difficult assessment. They face contract loss.

Defensible means specific. A System Security Plan that describes controls in general terms — "we use firewalls," "access is restricted to authorized users" — will not survive a C3PAO assessment. Every control narrative needs to name the specific implementation: the systems, the roles, the policy references, the evidence an assessor can locate and verify. That specificity requires someone who understands what the control is actually asking for — not just what it says.

I've held a TS/SCI CI Poly clearance. I've operated the networks these controls describe. I've been inside the security architectures that SSPs are supposed to document. When I write a NIST 800-171 control narrative, I'm writing from operational experience — not from a framework summary and a template.

The same depth applies to HIPAA documentation, network architecture documents, SOPs, runbooks, technical guides, white papers, and the full range of documentation that organizations need to be compliant, assessable, and operational. If the document will be read by an auditor, a certification body, or a regulator, it needs to be written by someone who understands what they're looking for.

If you're pursuing broadband funding and the window is open now

West Virginia's BEAD Final Proposal was approved in November 2025. $546 million is allocated for 142 deployment projects. Construction begins this year. If you're an ISP, electric cooperative, municipality, or nonprofit pursuing any part of that funding — or the state-level programs, USDA ReConnect, ARC, or EDA programs running alongside it — the application is a compliance document and a persuasion document at the same time. Both have to work.

Most grant applications that lose don't lose because the project was bad. They lose because the narrative didn't make the case. The needs assessment cited state statistics instead of local data. The capacity statement described the organization's history instead of its operational readiness. The community benefit was aspirational instead of concrete. Reviewers score what's on the page, not what was intended.

I live in Marion County. Every county in West Virginia sits in the Appalachian Regional Commission footprint. The communities this funding is designed to reach are the communities I'm in. The cultural fluency, local specificity, and operational knowledge of the WV funding landscape that these applications require isn't something I researched. It's where I am. No out-of-state firm can replicate that.

A BEAD subgrant narrative runs 30–60 pages and follows a mandatory 11-section scaffold. I know what each section is being scored on and I write to that standard — not to the general direction of the requirements.

If your operational knowledge lives in one or two people's heads

Nearly half of U.S. small business owners are 55 or older. Only 30% of family-owned businesses survive into the second generation. The operational knowledge that defines most organizations — the processes that work, the relationships that matter, the decisions that only make sense if you know the history — lives in one or two people's heads and has never been captured anywhere a system can find it.

This is the most common and least visible risk in small business. It surfaces when the person who knows leaves, retires, or is simply unavailable when the question comes up. By then it's too late to build the system that should have been built earlier.

I build AI skill libraries — structured, retrievable knowledge systems that encode operational knowledge in a form that's actually usable by the people who need it. Not a SharePoint folder. Not a document repository. A working system built specifically for the processes, decisions, and expertise that define how your organization operates. The methodology I use is the same one that runs Broadaxe Digital's own operation — which means the proof of concept is available to anyone who wants to see it in action before they commission one.

For rural West Virginia businesses coming online with broadband this year: this is the moment to build. The organizations that establish this infrastructure in 2026 will have it when the next key person transition happens. The ones that don't will be rebuilding from memory.

Grant writing gets you the infrastructure. Documentation makes it legible and defensible. Knowledge management makes it productive from day one. For organizations in rural WV navigating all three at once, that's not three separate engagements. It's one conversation.

Why Broadaxe and not someone else

Three honest answers.

Domain depth. Twenty years in military communications, classified intelligence systems, enterprise IT security, telecom, and cloud infrastructure. That background is not a résumé item — it's the reason every deliverable I produce is accurate at a level that someone who only researched the topic can't match.

Local presence. Marion County. Appalachian Regional Commission footprint. WV BEAD funding landscape. The geographic and cultural specificity that matters in grant writing and rural knowledge management work isn't available from a distance.

The structure of how I work. Hard cap at three concurrent clients. Twenty billable hours a week. Async-first communication. Every project scoped before it starts, with explicit deliverables and explicit exclusions. Every scope addition requires a written change order. These constraints exist because they produce better work — not commitments spread thin, but a smaller number of commitments done to the standard they deserve. Every client gets the same depth, the same quality gate, the same person, start to finish.

Let's talk about your project

The first step is an email or a scoping conversation — your choice. You tell me what you're working on, what the stakes are, and what the deadline looks like. I'll tell you directly whether it's a fit and what the engagement would look like.

I hold a hard cap of three clients. I don't commit to work I can't deliver at the standard it deserves. If your project isn't the right fit for what I do, I'll say so and tell you what kind of support would actually serve your needs.

Use the contact form at broadaxedigital.com

Broadaxe Digital · Monongah, Marion County, West Virginia · "Docs and grants for the infrastructure age."