If xTech and SBIR are the front doors, DEVCOM is often the building behind them. The Army Combat Capabilities Development Command — renamed from CCDC (Combat Capabilities Development Command) in 2019 — is the Army's principal science, research and engineering command. Understanding it tells you who actually evaluates your submission and where your technology transitions.
DEVCOM is a subordinate command of Army Futures Command. It runs a network of centers and laboratories, each owning a technical domain — ground vehicles, aviation and missiles, armaments, C5ISR (command, control, communications, computers, cyber, intelligence, surveillance and reconnaissance), soldier systems, chemical-biological defense, and the Army Research Laboratory (ARL) doing foundational science. Collectively these are the Army's deep technical bench.
The engineers inside these centers are the people who write SBIR topics and frequently sit on xTech evaluation and pitch panels. When a topic says the Army needs a lighter power source or a better autonomy stack, a specific DEVCOM center usually authored that need. Reading which center owns a topic tells you who your real customer and future technical point of contact (TPOC) will be.
Name change, same people: CCDC was renamed DEVCOM in 2019. You will still see “CCDC” on older documents and center names. They are the same organization — do not treat them as two different buyers.
See if you qualify for an Ansys eval The MVP playbook →DEVCOM centers buy and collaborate through several instruments. SBIR/STTR is the most common on-ramp for small companies — funded R&D tied to a specific center's need. xTech prize competitions surface new vendors and hand winners a fast lane into SBIR. CRADAs (Cooperative Research and Development Agreements) let a company and a lab share people, facilities and IP without money changing hands. Larger efforts flow through OTAs (Other Transaction Agreements) and traditional contracts, often via a consortium.
Start by identifying which center owns your technology domain, then track that center's SBIR topics on the Army SBIR|STTR site and its challenges on xTechSearch. When you win, the relationship with that center's engineers — not the prize check — is the real asset, because they are the internal champions who can pull your technology toward a program of record. Show up at their industry days, ask which problems keep them up at night, and map your roadmap to their gaps.
Once you know the centers, Army solicitations become far more legible. A topic's title, keywords, and background section reveal which center wrote it and, often, which program office is waiting downstream. That tells you three things at once: who evaluates your proposal, who your future technical point of contact will be, and where the transition dollars eventually live. Founders who skip this step write generic proposals to an anonymous government; founders who do it write to a named engineer with a named problem.
A single well-run SBIR effort with one DEVCOM center rarely ends there. Deliver well and the same engineers surface new topics, introduce you to sister centers working adjacent problems, and vouch for you when a program office is deciding whether to bet on a small company. The command is large, but the technical communities inside it are small and reputational — which means your track record travels. Treat your first center relationship as the seed of a portfolio, not a one-off grant.
Official sources: Army SBIR|STTR Program · xTechSearch. Figures change; confirm on the official page before relying on them.
