There's a brutal test for whether you actually own a small manufacturing business or whether the business owns you. Try to leave for two weeks. Just two.

For most small defense and aerospace contractors I talk to, the test is over before it starts. They can't. Not won't, can't. The shop will not run without them on the phone. And not because anything is broken. Because everything that matters lives in their head.

What this looks like in practice

A sick-call from a machinist comes in at 6 AM Monday. The owner is on a beach in Mexico. By the time they're done texting back and forth with the floor lead, the shift schedule is reworked, the Costpoint timesheet correction is queued for the controller, the daily kickoff brief to the floor is updated, and three other small fires are on hold waiting for the owner to come back. Vacation is over. It was over the moment the phone rang.

This is not a leadership problem. It is a knowledge architecture problem.

Why it happens to almost every owner

Small contractors grow by the President doing everything. The President is the operating system. They know which prime is sensitive about certs, which machinist is reliable on Mondays, which subcontractor cuts corners on the third revision, which engineer needs a heads-up before any change order. None of this is written down. It does not seem like knowledge until it is absent for a day, a week, or longer.

By the time the business hits 20 employees, the President has accumulated years of cross-system context: email threads, ERP entries, calendar patterns, compliance records, and supplier conversations. No single tool stores this information and most of it is not documented, even though the business runs on it.

Why typical fixes fall short

Standard operating procedures. Documents that do not get read or maintained. The exception is the rule, and exceptions are where the President's judgment lives.

Hire a #2. Years to transfer the knowledge. Most #2s leave before it is complete because they cannot do anything without checking with the President anyway, and that is not a job.

More software. Each tool sits in its own silo. The President is the integration layer. Adding a tenth system makes it worse, not better.

Process consultants. They produce a binder. The binder gathers dust.

What is actually needed

An ops layer that has the cross-system context the President has. Not a dashboard. A dashboard requires a human to read it and then act. Not a workflow tool. Workflow tools execute predefined paths and break on the exception. Not an iPaaS. iPaaS moves data between systems but does not make decisions.

What is needed is an agent that watches across email, scheduling, ERP, training records, the CMMC tracker, all of it, and starts handling the decisions the President would have made. The agent has the same context the President built up over five years. It just does not go on vacation.

What that looks like, concretely

6 AM Monday. A sick-call comes in. The agent reads the email, opens the schedule, checks who is certified to run that machinist's job. Sees that the next-best-fit person is already committed to a different job today and pulling them would create a worse schedule problem downstream. Notes that the controller is on PTO so the timesheet correction will need to route to the backup. Identifies the third-best-fit operator who has the cert and open hours. Drafts the swap, the Costpoint update, and the kickoff brief language. Pings the owner on their phone:

Carter called out. Recommend Lopez on GA-7, Patel stays on the original job. Costpoint update + kickoff line ready. Tap to approve.

The owner taps approve. Costpoint updates, the 7 AM kickoff goes out to the floor, the timesheet correction routes to the backup controller. The owner finishes their coffee, goes back to vacation.

That is the work. Seven systems crunched in 90 seconds, surfaced as one decision. The President used to be the thing that did it. Now they execute without digging around multiple systems for answers.

The vacation test as a benchmark

You will know you have a business when you can leave for two weeks and the operations do not degrade. Not "with planning." Not "if nothing major breaks." You leave. Things keep running. Things that need decisions get decided. You come back to a summary of what happened, not a backlog of what did not.

For most contractors I talk to, this feels impossible. It is not. It just requires extracting the cross-system context out of the President's head and into something else that can act on it.

That is the whole project.

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