You Don't Have an Operations Problem. You Have a Software Problem.

Most small defense and aerospace contractors I talk to think they have an operations problem. They don't. They have a software problem.

They run their business across twelve different applications. Each one was bought to solve one specific pain. Email for communication. Costpoint for accounting. ProShop or JobBOSS on the floor. SharePoint for documents. A separate portal for every prime customer. A different portal for every supplier. A CMMC tracker. A training records system. Calendly for scheduling. Teams or Slack for chat. Some flavor of CRM. Eight tabs open at any given moment.

None of these systems talk to each other. The integration layer is the human staring at the screen.

The thing software was supposed to do

Software is supposed to make work cheaper and faster. The pitch when you bought each tool was "this will save you time." And in isolation, each one did. The problem is what happens when you have twelve of them.

The cost is not the license fee. The cost is everything underneath the license fee.

Training. Every new hire has to learn twelve systems before they can do their actual job. The first three months are not productive work. They are software onboarding.

Switching tax. A normal task today touches four or five systems. Open a ticket from the prime, look up the contract in Costpoint, check the schedule in ProShop, update the SharePoint folder, log the change in the CMMC tracker. Five context switches. Each one is a small tax. Stack them across a hundred tasks per day across a twenty-person shop and you have a real number.

Reconciliation. Because the systems do not talk to each other, the same data lives in three places. Three places means three chances for it to drift out of sync. Now somebody's job is keeping them aligned.

Audit risk. When the evidence for a CMMC or AS9100 audit lives in twelve different systems, building the audit packet is a project. Not a query.

President dependency. The President is the only person who knows where everything is, who has logins for everything, and who can stitch the picture together. Which brings you right back to the vacation test.

The mistake everyone makes

When the software stack starts hurting, the natural reflex is to buy another tool. An iPaaS to integrate the systems. A "single pane of glass" dashboard. A workflow tool to automate the handoffs. A new ERP to consolidate everything onto one platform.

Each of these promises to solve the problem. Each one becomes the thirteenth system. Now there is one more login, one more vendor, one more set of training, one more contract to maintain.

The problem is not that you have the wrong twelve tools. The problem is that running operations through tools is the wrong abstraction.

What is actually needed

You don't need fewer systems. You need fewer humans inside the systems.

The right abstraction is to keep the systems where they are and put a single layer on top of them that traverses them on your team's behalf. Your machinist asks "what am I working on this morning, and is anything blocking me?" The layer answers, pulling from the schedule, the supplier status, and the training records in one response. Your controller asks "did the timesheet correction post for the Carter sick-call?" The layer confirms it across Costpoint and the kickoff log.

Nobody learned a new system. Nobody opened a new tab. The work happened.

Train people on work, not on tools

This is the part that actually matters for hiring.

When you hire a new operator, you should be training them on how the work gets done at your shop. Not on how to use Costpoint. Not on the SharePoint folder structure. Not on the prime's portal layout. Not on the CMMC tracker's checklist UI.

The agent handles the systems. The human handles the work.

Onboarding goes from three months to three weeks. The training material goes from a binder of click-paths to a description of the actual job. The new hire becomes useful faster, and the systems-knowledge stops being a moat that protects the President from ever leaving.

What that looks like, concretely

A 20-person aerospace composites shop in the mountain west. CMMC track, ITAR-controlled, eight active primes, three internal departments. Today they run on Costpoint, ProShop, SharePoint, GCC High email, four different prime portals, a CMMC compliance tracker, AS9100 quality records in a separate folder, and Teams.

After the agent layer is in place, the operator starting their morning shift opens one screen. They see what they're working on, what's blocked, what changed overnight, and what needs their attention before lunch. They never log into ProShop. They never open SharePoint. The agent did, on their behalf, and surfaced what mattered.

The compliance officer asks "give me the evidence for §3.1.20 for last quarter." The agent assembles it from the eight systems where the evidence actually lives, in minutes. Not weeks.

The President takes a vacation.

The test

You will know this is working when you can hire a new person without buying them twelve SaaS seats and expecting them to memorize all twelve before they are productive. You hire them. You teach them the job. The agent handles the rest.

That is the project.

Tentacle Ops is an operations agent built for CMMC-bound manufacturers. We are taking pilot customers in 2026. Learn more at tentacleops.ai.