Every xTech competition — xTechSearch, xTech|Inversion, xTech|Edge Strike, xTech|Phantum — starts the same way: a short concept white paper, usually capped at four pages, plus a pre-recorded pitch video in some cycles. It is the single highest-leverage document you will write, because it is the gate to the pitch round, the finalist stipend, and the SBIR proposal invitation that follows. Most rejections are not bad technology; they are papers that answered the wrong question.
Reviewers score three things: technical merit, relevance to the stated Army need, and commercialization / transition potential. Write to those three explicitly.
Open by restating the specific capability gap from the competition announcement, then name your solution in one sentence a program manager could repeat. Do not open with your company history. The evaluator needs to know within 30 seconds that you understood the problem and have a credible answer.
This is where papers win or die. Assertions lose; data wins. Show a bench result, a TRL claim you can defend, a prototype photo, a prior test, a customer pilot. If you are responding to a Direct-to-Phase-II-style track, your feasibility evidence must come from commercial or internally funded work — not prior government SBIR effort.
The four-page trap: reviewers read dozens of papers in a sitting. Front-load your differentiator in the first paragraph. If your unfair advantage is buried on page three, it does not exist.
See if you qualify for an Ansys eval The MVP playbook →State plainly why the Army cannot already buy this, and why the incumbent or the obvious alternative falls short. Then give a crisp technical approach: the key innovation, the risks you see, and how you would retire them. Reviewers reward teams that name their own risks — it reads as competence, not weakness.
End on the path to a program of record and a dual-use market. Name the likely Army user, the PEO or DEVCOM center that would care, and the commercial customers who validate demand. Winners connect prize money to a real acquisition on-ramp, usually a Phase I Army SBIR proposal.
Respect the page limit exactly — over-length papers are commonly disqualified without review. Use headings that mirror the scoring criteria so evaluators can find each point. Kill jargon a smart non-specialist could not parse. Submit through the official portal well before the deadline; the xTechSearch site lists the active competition and its window. A clean, evidence-first four pages beats a dense ten-page thesis every time.
Three failures recur. First, the paper describes a technology the team is proud of but never connects it to the specific Army need in the announcement — interesting, but irrelevant. Second, feasibility is asserted rather than shown, so the reviewer has no reason to believe the claim. Third, the transition section is a wish (“the DoD is a huge market”) instead of a plan naming a real user and buyer. Fix those three and you clear most of the field. Have someone outside your company read a printed copy cold and tell you, in one sentence, what you do and why the Army should care — if they cannot, neither can a tired evaluator on paper number forty.
Official sources: xTechSearch competitions · Army SBIR|STTR Program. Figures change; confirm on the official page before relying on them.
