A command that buys its own gear
United States Special Operations Command is the only combatant command in the U.S. military that buys its own equipment. Every other combatant command writes a requirement and waits for a service to fund it. SOCOM writes the requirement, holds the money, runs the source selection, signs the contract, and fields the result. That one structural fact explains nearly everything about how technology is sold to SOCOM, and it is the reason a small engineering firm can reach a program office there in months rather than years.
Congress built it that way on purpose. The Nunn-Cohen Amendment to the FY1987 National Defense Authorization Act (Public Law 99-661) created the command, which was activated on 16 April 1987 at MacDill Air Force Base in Tampa. The authority now sits at 10 U.S.C. § 167, which makes the SOCOM commander responsible for the "development and acquisition of special operations-peculiar equipment and acquisition of special operations-peculiar material, supplies, and services." Congress followed the authority with money: Major Force Program 11, a defense budget program that belongs to SOCOM alone.
The line that governs everything is SOF-peculiar versus service-common. SOCOM pays for what is unique to special operations. The services pay for what everyone uses. A standard rifle cartridge is service-common. A suppressor built to a special operations requirement is SOF-peculiar. For software the same line applies and is easy to misread: a general-purpose enterprise mail system is service-common and SOCOM will not fund it, while a mission-planning application built around a special operations workflow is SOF-peculiar and SOCOM will. Before pitching anything, decide which side of that line the work sits on. Being on the wrong side is the most common reason a good idea gets a polite meeting and no follow-up.
Scale matters for expectation-setting. Special operations forces run roughly 70,000 military, civilian, and contractor personnel, about three percent of the Department's people, funded at roughly two percent of the Department's budget. Recent MFP-11 requests have run in the range of $14 billion to $16 billion a year. Most of that is operations and maintenance. Research, development, test and evaluation is on the order of a billion dollars, and procurement sits between them. So SOCOM is a small buyer by dollars and a fast buyer by culture. Firms that chase volume should go elsewhere. Firms that want a real user, a short decision chain, and a shot at fielding should pay attention.
Openness to a first-time small AI and data firm, by entry path
Editorial weighting from public sources and practitioner reading, illustrative rather than a measured statistic.
Who holds the money
Four layers decide what gets funded. The Assistant Secretary of Defense for Special Operations and Low-Intensity Conflict sits in the Pentagon and carries service-secretary-like responsibilities over the special operations enterprise under 10 U.S.C. § 138(b)(4), a role directed by Section 922 of the FY2017 NDAA and stood up in 2020. That office shapes policy and resource advocacy. It does not run source selections.
The acquisition arm is Special Operations Forces Acquisition, Technology and Logistics, at MacDill, led by SOCOM's Senior Acquisition Executive. Under it sit the program executive offices, the science and technology directorate, and the procurement directorate that actually signs contracts. This is where a vendor conversation becomes an award.
The components generate the requirements: Army Special Operations Command at Fort Bragg, Naval Special Warfare Command at Coronado, Air Force Special Operations Command at Hurlburt Field, Marine Forces Special Operations Command at Camp Lejeune, and Joint Special Operations Command. Each runs its own smaller contracting activity for local needs, which is a real and underused door for services work.
Finally, the theater special operations commands, including SOCEUR, SOCCENT, SOCPAC, SOCAFRICA, SOCSOUTH, SOCNORTH, and SOCKOR, hold operational demand and almost no money. They matter anyway. A theater command is usually where a user problem first appears, and a validated user problem is the raw material every program office needs. SOCOM also runs an Office of Small Business Programs, required of every component by 15 U.S.C. § 644(k), whose stated job is to help firms of our size find the way in. That office answers email.
The program offices and what each one buys
The program executive offices are where the technical requirement lives. Any firm selling AI, data, or cloud engineering should be able to name the office that owns its problem before the first conversation.
| Program executive office | Portfolio | Where AI and data work appears |
|---|---|---|
| PEO Fixed Wing | AC-130J gunships, MC-130J tankers, manned ISR aircraft and their mission systems | Fleet maintenance prediction, sensor and mission-system processing, software sustainment |
| PEO Rotary Wing | The MH-60, MH-47, and MH-6 fleets flown by Army special operations aviation | Usage-based maintenance, flight-data analytics, degraded-visual-environment perception |
| PEO Maritime | Combatant craft, dry and wet submersibles, undersea mobility | Navigation without satellite positioning, hull and propulsion health, mission planning |
| PEO SOF Warrior | Weapons, ammunition, visual augmentation, tactical combat casualty care, operator equipment | Inference on wearables and optics under tight power budgets, medical and human performance data |
| PEO Special Reconnaissance, Surveillance and Exploitation | ISR sensors, signals collection, biometrics, technical surveillance, exploitation | The densest machine learning demand in the command by a wide margin |
| PEO Digital Applications | Mission command software, the common operational picture, data services, operator-facing applications | The natural home for a software-first firm with no hardware to sell |
Two more organizations round it out. PEO Services buys services acquisition support across the command, which is the office to know for analytic and engineering labor rather than a product. The SOF Support Activity in Lexington, Kentucky, handles logistics, sustainment, and depot-level work for SOF-peculiar equipment, and it sits on a very large stream of maintenance and supply data.
SOFWERX and the front door in Ybor City
SOFWERX, in the Ybor City district of Tampa, is the command's public-facing innovation outreach arm. It is operated by DEFENSEWERX, a nonprofit, under a Partnership Intermediary Agreement with SOCOM authorized by 15 U.S.C. § 3715. That statute is the legal reason SOFWERX can talk to industry in ways a contracting officer cannot, and it is why the front door feels nothing like a federal procurement.
SOFWERX runs collaboration events, rapid prototyping events, technology sprints, and assessment events, and it publishes them openly. Most are unclassified. Registration is generally open to U.S. companies, and the barrier to entry is a written submission rather than a proposal volume. For a firm with no SOCOM history, this is the cheapest way to be in a room with the people who own the problem. Some events end in a prototype agreement. Many end in nothing except a name that is recognized the next time.
The failure mode is treating it as a sales channel. SOFWERX is not a contracting office. It is a filter and an introduction. The money is downstream in a program office, an SBIR contract, or an Other Transaction. Firms that arrive with a demo and no idea which program office would eventually own the capability get a friendly reception and no path.
The vehicles that carry the dollars
SOCOM's enterprise IT work runs through the Special Operations Forces Information Technology Enterprise Contracts, now in their third generation as SITEC III. Rather than one monolithic award, SITEC III is structured as separate streams covering enterprise operations and maintenance, the global service desk, engineering, and program support. If a firm wants to touch SOCOM's enterprise networks and the data on them, the SITEC primes are the practical doorway, and a well-scoped data engineering workshare under one of them is a legitimate first engagement.
On the sustainment side, Global Logistics Support Services covers supply and maintenance for SOF-peculiar equipment and is tied to the Lexington support activity. SOCOM also buys heavily off government-wide vehicles. A GSA Multiple Award Schedule holder or a NASA SEWP contractor can receive a SOCOM task order without ever holding a SOCOM-specific contract, which is the fastest path most small firms overlook.
Below the vehicles sit the small awards that make a firm an incumbent. The simplified acquisition threshold is $250,000 under FAR 2.101, and FAR Subpart 13.5 permits simplified procedures for commercial products and services up to $7.5 million, and up to $15 million for certain acquisitions supporting contingency and defense-against-attack purposes. The micro-purchase threshold is $10,000. A defined $150,000 engineering task, delivered cleanly, is worth more to a young relationship than a large proposal that never gets read. The command's science and technology directorate also maintains a standing broad agency announcement, which is a year-round path for a white paper on an unsolicited technical idea rather than a response to someone else's requirement.
SBIR, STTR, and the Phase III lever
SOCOM publishes SBIR and STTR solicitations through the DoD SBIR/STTR Innovation Portal inside the Department-wide announcement releases. Its volume is small next to the Air Force or the Navy. That cuts both ways: there are fewer solicitations to bid, and far fewer bidders on each one, against a program office that already wants the answer and has the authority to buy it.
On award sizes, the Small Business Administration publishes statutory guideline amounts that it adjusts annually for inflation, currently above $300,000 for Phase I and above $2 million for Phase II. Agencies set their own ceilings within those guidelines, and DoD components commonly award Phase I well below the guideline. Several components also run Direct to Phase II solicitations, where a firm that has already completed Phase I-equivalent work on its own funds may skip Phase I entirely. That pathway rewards firms that build before they bid.
The part most firms miss is Phase III. Under 15 U.S.C. § 638(r)(4), any federal agency may award a Phase III contract derived from SBIR or STTR work, sole source, at any dollar value, with no further competition and no expiration. For a command whose acquisition culture rewards speed, Phase III is often the shortest legal route from a working prototype to a funded program. A Phase I award at SOCOM is not a small research grant. It is the key that opens that door, and it should be pursued with the transition in view from the first page.
Other Transactions and the prototype-to-production path
10 U.S.C. § 4022 gives the Department prototype Other Transaction authority, and § 4022(f) allows a follow-on production contract or transaction without further competition when the prototype was competitively selected and successfully completed. SOCOM uses this authority both directly and through consortium-managed agreements. Consortium membership usually costs a modest annual fee and opens a stream of solicitations that never appear on SAM.gov, which is why firms that watch only SAM.gov conclude that nothing is happening.
Status matters here. A nontraditional defense contractor, defined at 10 U.S.C. § 3014 as an entity not currently performing a DoD contract subject to full cost accounting standards coverage, can trigger reduced cost-share requirements and makes an OT easier for the government to justify. Most small software and data firms qualify. Say so in writing when responding, because the contracting officer needs that fact on the record.
The data SOCOM holds
Understanding the data classes is what separates a credible technical pitch from a generic one. Full-motion video and imagery from manned and unmanned ISR platforms is the largest volume problem in the command, and the exploitation workforce that reviews it is small. Signals and technical collection sit under the reconnaissance and exploitation portfolio, along with biometrics and identity data. Rotary and fixed wing fleets generate maintenance and readiness data from aircraft flown hard, low, and at night, which produces exactly the failure signatures that usage-based maintenance models need. Logistics and supply data flows through the Lexington support activity. Training and simulation systems produce performance data across every component.
Then there is the human data. Preservation of the Force and Family, the command's human performance program, produces physical, psychological, and social performance data across the force. It is unclassified, it is messy, and it maps directly onto problems our engineers solve for civilian health and workforce customers.
SOCOM's stated direction for all of this is the hyper enabled operator: putting data, computing, and communications at the operator's edge so the decision cycle shortens where it matters. That concept is public, it is durable across leadership changes, and it is the frame a technical proposal should speak to. A design that assumes a reachback link to a cloud model does not survive contact with that requirement.
The practical point for a firm without clearances: much of the highest-value near-term AI work sits on unclassified logistics, maintenance, contracting, medical, and human performance data. That work is reachable at Secret or below, and some of it needs no clearance at all.
The security gates that decide who gets in the room
Access is the real filter at SOCOM, and it is worth being precise about which gate is which, because they are often confused.
Facility clearance. Holding classified information requires a facility clearance under the National Industrial Security Program Operating Manual, codified at 32 CFR Part 117 since 2021 and administered by the Defense Counterintelligence and Security Agency. A firm cannot request its own facility clearance. It must be sponsored by a cleared prime or a government activity with a classified requirement in hand. That sponsorship dependency is the hardest gate in the whole path, and it is the reason the subcontract route matters so much.
Personnel clearances. Individual clearances run through the SF-86 and are adjudicated against the national security adjudicative guidelines in Security Executive Agent Directive 4. Trusted Workforce 2.0 continuous vetting has replaced the old periodic reinvestigation model, which shortens the practical timeline for keeping cleared staff current.
Export control. A great deal of SOF-peculiar technical data is export controlled even when it is unclassified, under the ITAR at 22 CFR Parts 120 through 130 or the Export Administration Regulations at 15 CFR Parts 730 through 774. The Joint Certification Program, run by DLA Logistics Information Services under DoD Directive 5230.25, uses DD Form 2345 to certify a U.S. or Canadian contractor for access to militarily critical technical data. Our firm is JCP certified under CAGE 1AYQ0. It costs nothing but paperwork and it is the difference between reading a solicitation and reading the drawings behind it.
CUI and CMMC. Contracts carrying controlled unclassified information invoke DFARS 252.204-7012 and NIST SP 800-171. The Cybersecurity Maturity Model Certification program rule at 32 CFR Part 170 took effect on 16 December 2024, and the acquisition rule phases certification requirements into new contracts over a multi-year rollout. Any firm that expects to handle CUI should already be scoring itself against 800-171.
Cloud. The DoD Cloud Computing Security Requirements Guide sets impact levels. IL4 and IL5 cover controlled unclassified and national security system unclassified workloads and are available in the government regions of the major providers. IL6 covers Secret and lives in classified regions. Knowing which level your architecture targets, and saying it plainly, marks a proposal as written by someone who has deployed before.
Where a small engineering firm actually fits
SOCOM does not need another platform integrator. It needs specific engineering done well and fast, on problems that are too small for a large prime to care about and too technical for a staffing shop to deliver. Six shapes of work fit that description.
- Sensor and video exploitation. Detection, tracking, and change detection that reduce how much full-motion video a human has to watch.
- Readiness and maintenance analytics. Component-level failure prediction on aviation and maritime fleets, built from maintenance records that already exist.
- Mission planning and decision support. Operator-facing software that shortens a planning cycle, delivered as an application rather than a study.
- Data engineering under an incumbent. Pipelines, schemas, and governance work as a subcontractor to the prime that holds the enterprise IT vehicle.
- Model evaluation and assurance. Independent testing of a vendor's model against operationally representative data, an assignment agencies increasingly fund on its own.
- Edge inference under power constraints. Compressed models that run on the hardware an operator can actually carry, with no assumed network.
Our team builds in all six shapes. The bench holds named engineers, licensed professional engineers, and domain specialists, and it is led by a former professor in technology whose competitive machine learning record sits in the top 200 of a platform with more than 200,000 ranked participants, with seven cloud certifications and fifteen years of production system delivery for federal agencies across five consulting firms, three of them federal. We take work as a prime and as a subcontractor, and we scope small first engagements on purpose because that is how a real relationship starts.
The concrete first step
If a firm wants into SOCOM and is starting from nothing, the sequence below is the one that works. It is deliberately unglamorous, and none of it requires an introduction.
Entry sequence for a first-time SOCOM vendor
If only one step is possible this quarter, make it step four. A written response to a live notice puts a firm on the record with a contracting officer and a technical point of contact, creates a document the government can cite later, and costs a week. Most firms that never win at SOCOM never wrote anything down.
Bottom line
SOCOM is the most accessible large technology buyer in the Department of Defense for a small engineering firm, and the reason is structural rather than cultural. The command owns its requirements, its budget line, and its contracts, so the distance between the person with the problem and the person with the money is short. The gates that matter are access gates, not size gates: registration, export-control certification, and eventually sponsorship for a facility clearance. Firms that clear those gates and put credible engineering in writing get in. Firms that wait for an introduction do not.
Frequently asked questions
Congress gave it that authority in the Nunn-Cohen Amendment to the FY1987 NDAA, now codified at 10 U.S.C. § 167, and backed it with its own budget program, Major Force Program 11. SOCOM funds what is special-operations-peculiar; the military services fund what is common to everyone.
Not to start. A meaningful share of the command's near-term data work sits on unclassified logistics, maintenance, medical, and human performance data. A facility clearance is required to hold classified information, and it cannot be self-requested: a cleared prime or a government activity with a classified requirement must sponsor it under 32 CFR Part 117.
It is SOCOM's innovation outreach arm in Tampa, operated by a nonprofit under a Partnership Intermediary Agreement authorized by 15 U.S.C. § 3715. It publishes collaboration events, technology sprints, and assessment events that are generally open to U.S. companies. It introduces and filters; the funding decision happens in a program office afterward.
SBA's statutory guideline amounts, adjusted annually for inflation, currently exceed $300,000 for Phase I and $2 million for Phase II, and DoD components often award Phase I below the guideline. The larger value is Phase III: under 15 U.S.C. § 638(r)(4) an agency may award follow-on work sole source, at any dollar value, with no expiration.
PEO Digital Applications for operator-facing software and data services, and PEO Special Reconnaissance, Surveillance and Exploitation for sensor, signals, and imagery machine learning. PEO Services is the office to know for engineering and analytic labor rather than a product.