Onebrief

1.1 Identity, product scope, and operating footprint

Onebrief presents itself as a command-decision platform built for military staffs rather than a generic enterprise collaboration app. Its homepage and Carahsoft partner page both describe a live, secure workflow environment that unifies planning, collaboration, maps, timelines, and briefings inside a single operational workspace, while the official ACC pilot release adds explicit API and cross-network deployment detail. That establishes the core business model—software sold into government planning workflows with implementation support—but not a clean public company profile on basics like headquarters, customer count, or revenue. Even the headquarters field is not fully settled in this evidence pack: QuantLogix profiles Onebrief as Honolulu-based, while one January 2026 trade article calls it Washington, D.C.-based, so later chapters should treat location as a live diligence item rather than inherited fact.[CO001, CO002, CO003, CO015, CO016]

1.2 Founder fit, leadership bench, and organizational scale

The strongest publicly verifiable founder signal is Grant Demaree's operator background: Business Insider reports that the cofounder and CEO is a former 101st Airborne officer and West Point graduate, which aligns with the company's military-planning thesis and likely helps with user empathy inside defense workflows. The clearest documented leadership expansion comes from the Series B announcement, which names David Wolf as VP of Engineering, Colten O'Malley as CISO, and Blake Lackey as Head of Sales, alongside a stated employee base of 100+ worldwide. That supports a view of functional bench-building across product, security, and go-to-market, but current headcount, board composition, and any 2025-2026 executive turnover remain largely private in the assigned source set, which keeps key-person dependence on Demaree materially relevant.[CO004, CO006, CO007]

1.3 Funding history, procurement momentum, and milestone quality

Public funding evidence shows three distinct phases: a Series B announcement that brought cumulative capital to $53 million, a June 2025 extension that lifted valuation to $1.1 billion, and a 2026 round that clearly pushed the company into Series D territory but is not consistently described across independent records. The cleanest current traction marker is procurement access rather than disclosed unit economics: Onebrief's September 2026 enterprise contract created a five-year Army ordering pathway and the company says its first task order executed within an hour, while the earlier ACC program shows branch-level rollout and integration work. The main caution is that public enthusiasm outpaces financial visibility: QuantLogix's current model estimate sits below the last disclosed round, and there is still no public revenue, ARR, customer-count, or cap-table-term disclosure to show whether the $2B-plus mark is supported by fundamentals or simply by strategic-demand momentum.[CO005, CO008, CO009, CO010, CO011, CO012, CO013, CO014]

1.4 Exhibits

2.1 Market boundary and substitutes

The assigned pool supports defining Onebrief's category as military operational planning, mission-command collaboration, and adjacent command decision-support workflows rather than a broad horizontal productivity or generic AI market. Onebrief's own platform and features pages consistently describe an integrated workspace where live operational data, plans, orders, maps, timelines, and briefs stay synchronized, while the Carahsoft listing frames the product as a secure government workflow environment for distributed teams operating in classified and unclassified settings. That makes the included spend logic more specific: planning software, staff-collaboration tooling, decision-support workflows, integrations, and deployment services that replace fragmented PowerPoint, Word, email, and file-based military planning. Excluded or only indirectly supported categories include pure office productivity suites, stand-alone intelligence analytics, weapons systems, and general IT infrastructure that may coexist with Onebrief but are not the directly evidenced buying job.[CM001, CM002, CM003, CM007]

2.2 Buyer, user, payer, and adoption path

Public evidence points to a multi-stakeholder defense-software sale in which users are planners and staffs, buyers are commands pursuing mission-command modernization, and payers are procurement offices or command budgets that can sponsor enterprise or pilot deployment. The ACC release shows a command-level adoption path: Onebrief won an operational-planning contract, planned rollout to all ACC staff directorates, and paired software with embedded onboarding to migrate existing work centers into the new workflow. The September 2026 Army contract expands that path from local program sponsorship to a broader department-wide procurement channel by allowing warranted contracting officers to issue orders under a five-year IDIQ. Those disclosures imply that adoption is not only a feature-led software decision; it depends on integration, implementation support, security posture, and a procurement route that lets commands buy without inventing a fresh contracting structure.[CM003, CM004, CM005, CM006]

2.3 Evidence-constrained sizing lenses

The pool does not disclose a clean TAM/SAM/SOM stack for Onebrief, so sizing must rely on multiple incomplete lenses instead of one asserted headline market number. One company-issued lens is broad: the 2025 unicorn-valuation release says defense tech exceeds $140 billion in annual spend and that military staff optimization could unlock more than $100 billion of Future Years Defense Program savings. Independent category-capital signals point in the same direction but measure something different: Business Insider cites McKinsey and PitchBook data showing capital flowing aggressively into defense technology, while AI Business Weekly describes the opportunity as mission-planning software needed by every command, unit, and headquarters. Those lenses are useful for valuation framing and market interest, but they do not isolate Onebrief's serviceable market because public evidence still lacks transparent pricing, seat counts, contract values, and customer concentration.[CM008, CM009, CM010, CM011, CM012, CM013, CM014]

2.4 Adoption drivers, constraints, and valuation relevance

The adoption case in the pool is driven by three recurring themes: operational speed, synchronized collaboration, and resilience in distributed or contested environments. Company and partner sources claim 75% time-and-resource reduction, 20x time savings, real-time updates across products, and support for classified and bandwidth-constrained operations; these claims explain why the buyer may tolerate a complex enterprise deployment if the software truly compresses planning cycles. The constraint is that these ROI figures are company-claimed rather than independently benchmarked in the assigned evidence, while the commercial envelope remains opaque because Onebrief does not publish pricing, contract minimums, customer counts, or retention metrics. As a result, the public market case is strongest on strategic relevance and procurement access, but much weaker on provable budget capture and revenue conversion, which is exactly why category enthusiasm can support premium valuation narratives faster than public operating evidence can validate them.[CM006, CM010, CM011, CM013, CM014, CM015]

2.5 Exhibits

3.1 Competitive frame and substitute set

The assigned pool supports a wide substitute set even though it does not provide a clean direct-peer benchmark pack. Onebrief's own materials and its Carahsoft partner page define the status quo as slide, document, email, and version-control churn rather than an incumbent single-purpose planning product. Independent sources then expand the field outward: QuantLogix explicitly lists Palantir, Anduril Lattice, and Govini as competitors, while AI Business Weekly places traditional primes such as Lockheed Martin, Raytheon, and Northrop Grumman in the same buying conversation. That makes the practical decision set broader than "Which planning app wins?" and closer to "Do we keep patching existing tools, build around current systems, or buy a planner-native command layer?"[CP002, CP006, CP007, CP008, CP009, CP016]

3.2 Where Onebrief appears differentiated

The strongest differentiation evidence in the pool is workflow-native depth rather than a published price edge. Onebrief describes a single workspace built from live, synchronized operational data, AI workflows, and interoperable APIs, and ACC's pilot language says the product augments an existing stack instead of replacing a single incumbent record system. Independent commentary reinforces that positioning: AI Business Weekly characterizes Palantir as strongest in data analytics and intelligence and Anduril in autonomous systems and sensors, which suggests those rivals attack adjacent decision layers rather than the exact same planning-centric job. The net effect is a differentiated "command workflow" posture, but one that is still defined more by capability narrative than by standardized third-party benchmarks.[CP001, CP003, CP007, CP008, CP014, CP016]

3.3 Distribution, switching costs, and pricing opacity

Distribution is where Onebrief has the clearest buyer-facing edge in this evidence set. The Army enterprise IDIQ and the first task order executed within an hour of award show a procurement path that is much more concrete than a generic venture software sales motion, and QuantLogix's federal-awards data points in the same direction. Switching costs also look meaningful because Onebrief repeatedly frames adoption around imports, interoperability, and augmentation of existing systems, which lowers initial deployment friction while still encouraging teams to move live planning work into its shared workspace. The biggest commercial weakness is that public pricing remains opaque: ToolMage says Onebrief runs a custom enterprise model, so outside buyers cannot benchmark list price, discounting, or realized contract economics from the public record alone.[CP002, CP004, CP005, CP010, CP015, CP016]

3.4 Durability and displacement risks

The moat case is credible but incomplete. Onebrief's planner-native feature set, classified-network posture, and direct contract vehicle help, and the company has raised enough capital to keep widening the product surface. At the same time, adjacent platforms, incumbent primes, and internal-build paths all remain viable ways to contest the account. The assigned pool offers category-level evidence that those competitors exist, but not enough neutral benchmarking to prove that Onebrief wins on realized cost, deployment speed, or long-run retention. That means the durability question currently rests on program momentum and workflow fit more than on audited proof that rivals cannot match the product or route-to-market.[CP004, CP008, CP009, CP011, CP012, CP013, CP014, CP016]

3.5 Exhibits

4.1 Revenue model and public traction

The clearest public monetization evidence is not list pricing but procurement structure. Onebrief disclosed in September 2026 that Army Contracting Command awarded a decentralized, single-award enterprise IDIQ that lets warranted contracting officers issue task and delivery orders directly for Onebrief planning capabilities, moving the company from prototype subcontractor status into a direct procurement path. A separate Air Combat Command release shows the business also sells into rollout programs that include onboarding and embedded support, while Interesting Engineering reported planning tasks compressing from roughly three hours to 30 to 40 minutes in Army experimentation. That combination supports a revenue model built around enterprise defense software adoption and follow-on task orders, but not a public view of realized revenue per command, user, or contract.[CI001, CI002, CI003, CI004, CI011, CI013, CI016]

4.2 Pricing, delivery costs, and unit economics

Public materials still stop short of disclosing price cards or unit economics. No reviewed source publishes seat pricing, command-level minimums, task-order dollar values, discounts, or realized expansion rates. Instead, the evidence shows the likely cost drivers: Onebrief says new capital is being used to expand engineering, infrastructure, AI, and support for 100,000 simultaneous collaborators, while product and ACC deployment pages describe bidirectional API work, document imports, embedded onboarding, and support across classified and unclassified environments. Those details suggest a business that mixes recurring software value with non-trivial implementation and support load, which means gross-margin potential depends on software scale outrunning services intensity and infrastructure spend, but public evidence is insufficient to measure that path.[CI004, CI009, CI010, CI012, CI013]

4.3 Capital adequacy and financing dependence

Funding disclosure is much stronger than operating disclosure. Onebrief's official June 2025 announcement and Business Insider's contemporaneous reporting support the $20 million Series C extension at a $1.1 billion valuation, and QuantLogix now lists a January 2026 Series D of $359.28 million with $303 million raised in total. That capital stack should reduce immediate financing pressure, but the public record still omits cash on hand, monthly burn, debt terms, and runway, so investors cannot test whether the 2026 balance sheet merely funds growth or is already committed to infrastructure, staffing, acquisition, or classified deployment demands. QuantLogix's lower $1.6 billion model price and steep secondary-price discount imply that private-market confidence may be less robust than the headline last-round mark.[CI005, CI006, CI007, CI008, CI012, CI015]

4.4 Financial verdict and diligence blockers

The positive financial read is that Onebrief has visible procurement momentum, referenceable defense-command adoption, and enough disclosed capital raises to keep scaling. The negative read is that nearly every underwriting variable that would convert those signals into a defensible revenue-quality or margin thesis is still private: revenue mix, contract values, renewal cohorts, customer concentration by dollars, software-versus-services gross margin, burn, runway, and debt obligations. As a result, public diligence can support a view that Onebrief is building a real enterprise-defense revenue engine, but it cannot support a clean judgment on revenue quality, capital efficiency, or the timing and terms of the next financing trigger.[CI007, CI008, CI012, CI014, CI015, CI016]

4.5 Exhibits

5.1 Planner-native workspace and product surface

Public materials consistently describe Onebrief as software that replaces fragmented PowerPoint, Word, email, and file-based military staff work with a single live workspace. The core operating idea is a shared structured data model built around reusable Cards, so the same underlying information can feed lists, timelines, maps, whiteboards, slides, and documents without manual copy-and-paste. That product surface matters because it defines Onebrief less as a point planning app and more as a system of record for staff products across echelons. The company and channel materials also make the AI layer concrete enough to underwrite a workflow claim: Onebrief says its AI uses plan context and doctrinal templates to draft and update plans, orders, and briefs rather than merely adding a generic chatbot beside static files.[CE001, CE002, CE003, CE004, CE015]

5.2 Deployment, integration, and control surfaces

The public product story is strongest where Onebrief ties collaboration to deployment and control mechanics. The official features page describes bidirectional APIs, imports from common office formats, and operation across classified, unclassified, and partner networks with disaster-recovery and regionalization claims. Carahsoft's reseller page reinforces the same positioning with a single-source-of-truth workflow, role-based permissions, structured audit history, and embedded support for adoption. Taken together, the evidence supports a credible integration-and-governance narrative for defense workflows, but it does not expose implementation timelines, uptime history, classification boundary details, or independent security attestations at the level a buyer would want for technical diligence.[CE006, CE007, CE008, CE010, CE014, CE016]

5.3 Maturity, differentiation, and technical risks

The clearest maturity signals in the assigned pool are operational and procurement-oriented rather than developer-facing. In 2026, public reporting tied Onebrief both to the Army's next-generation command-and-control effort and to an Army enterprise contract that moved the company from subcontractor to prime with a direct ordering path; QuantLogix also records a visible federal-award footprint, while company fundraising materials frame roadmap investment around scale, resilience, allied operations, and continuous wargaming. That combination supports a thesis of real deployment relevance and differentiated workflow fit for defense planning. The main technical underwriting gap is that these signals still sit beside thin independent proof on architecture performance, security accreditation specifics, public incident history, and community/developer signal, so the chapter can support product relevance better than it can support software-quality assurance.[CE005, CE009, CE010, CE011, CE012, CE013, CE016]

5.4 Exhibits

6.1 Defense organizations are the visible buyer, user, and payer base

The assigned evidence pool points to a concentrated customer base: U.S. military staffs and commands are the only clearly documented paying and using organizations. Salesforce Ventures says Onebrief is already in active use across the Joint Staff and major U.S. Combatant Commands, while a 2025 company funding release said adoption had reached four of seven geographic combatant commands. The buyer appears to be command-level defense organizations procuring collaboration and planning software for staff officers and planners, not decentralized line users. Public materials support strategic relevance, but they do not disclose customer counts, contract values, renewal cohorts, or commercial-sector mix.[CU001, CU002, CU003, CU004, CU014]

6.2 Named deployments show command-level traction, but proof quality varies

Named customer proof is strongest where the company ties product use to a specific command workflow. Air Mobility Command is the clearest example: independent coverage says the deployment entered its third consecutive fiscal year, expanded from headquarters to operational wings, and became the sole planning product for a 2026 conference workflow. Air Combat Command adds pilot-to-rollout evidence, including deployment across staff directorates and an onboarding effort embedded with users. The Army proof is more procurement-centric: a five-year enterprise contract and an immediate Army G4 task order show a direct buying path, but not yet the revenue or seat density behind it.[CU005, CU006, CU007, CU008, CU013]

6.3 Expansion logic is visible; retention and concentration economics are not

The public expansion motion is a land-and-expand pattern inside defense: pilot and onboarding activity at ACC, HQ-to-wing broadening at AMC, and a new enterprise contract vehicle with the Army. That is meaningful commercial progress, but it is not the same as durable recurring revenue. Business Insider reported that CEO Grant Demareee said “Almost all of the military's largest plans are built in our software” while declining to cite specific plans because of contractual constraints, which underscores how difficult breadth-of-use claims are to verify independently. Across this pool, named deployments are overwhelmingly U.S. defense accounts, so customer concentration and renewal dependence on a narrow buyer set remain material open questions.[CU009, CU010, CU011, CU012, CU014]

6.4 Exhibits

7.1 Security, accreditation, and assurance burden

Onebrief's own materials describe a platform already deployed across classified, unclassified, and partner networks, with an API that can run on SIPR, NIPR, and JWICS, while Carahsoft describes secure deployment and role-based controls for sensitive content. That is a real mitigation base, not slideware, and the company also says new capital is being used to harden the platform and keep it operational during cyberattacks. The risk is that a system positioned this deep inside mission-planning workflows inherits a much heavier assurance burden than ordinary enterprise SaaS, while public third-party evidence of accreditations, incident history, or model governance remains absent from the retained source set.[CR006, CR007, CR008, CR009, CR016]

7.2 Operational scaling and integration execution

The execution story is ambitious even by defense-software standards. January 2026 funding was tied to the Battle Road acquisition and to platform hardening, while the 2025 company release said the roadmap targets support for 100,000 simultaneous collaborators under adversarial conditions. At the same time, the ACC rollout required onboarding and embedded government-commercial teams throughout 2025, and the product strategy relies on AI-assisted workflows plus deep integration into existing command systems. That combination creates a clear operational risk: if integration, performance, or post-acquisition execution lags, the same features that power adoption can become the bottleneck that slows wider branch-level expansion.[CR005, CR006, CR010, CR011, CR015, CR016]

7.3 Government concentration and ecosystem dependence

The strongest proof points also define the concentration risk. Public evidence centers on the U.S. military: ACC rolled the platform to all staff directorates, the September 2026 Army enterprise IDIQ created a five-year department-wide procurement path, Sapphire describes a hybrid go-to-market motion reinforced by military relationships, and the StartEngine offering repeats the claim that Onebrief powers three of the Department of Defense's four most significant operational plans. These are valuable signals, but they point to one dominant customer complex, one procurement environment, and one mission domain. If budgets, priorities, or contracting pathways shift, a large share of both growth evidence and commercial leverage can move at once.[CR010, CR012, CR013, CR014]

7.4 Capital-markets risk and kill criteria

Public marketability evidence is materially weaker than product-adoption evidence. StartEngine makes explicit that the 2026 security was a membership interest rather than direct shares and that the exposure was speculative, illiquid, and capable of a total loss. Meanwhile, the retained 2025 sources show a rapid valuation reset from $650 million to $1.1 billion in roughly one quarter, while Business Insider also reports that management would not identify specific plans because of contractual constraints. The resulting investment risk is not that the product lacks demand; it is that public evidence does not yet let an outsider test whether contract concentration, unit economics, and assurance depth justify the pace of mark-up. That is the chapter's core kill criterion.[CR001, CR002, CR003, CR004]

7.5 Exhibits

8.1 Recommendation and entry discipline

The recommendation remains research-more rather than buy because the underwriting problem is now more about price discipline than product legitimacy. Onebrief has a credible wedge in military staff planning, and both company and third-party reporting point to bottom-up user pull, widening procurement access, and a push from collaboration software into AI-assisted planning and simulation. But the latest disclosed round reset the price to roughly $2.15B after a prior jump to $1.1B only months earlier, while the freshest external mark retained in this chapter sits materially below that level. That leaves enough evidence to stay engaged, but not enough to underwrite the round headline without access to private operating and capital-structure data.[CV001, CV002, CV003, CV007, CV010, CV012]

8.2 Valuation context and comparable signals

The public valuation case rests on platform ambition rather than disclosed economics. The bull story is straightforward: planner-native adoption, documented API and classified-network deployment claims, and a simulation expansion path could turn Onebrief from a workflow tool into a sticky command platform. The anti-thesis is equally straightforward: the adverse case points to roughly $19.1M of revenue against a $2.15B mark, which implies a triple-digit revenue multiple, while the current external price signals already clear below the last round. Comparable exit logic therefore depends less on a near-term IPO and more on Onebrief proving that procurement depth and product scope can outrun both slower federal sales cycles and larger-stack competition.[CV002, CV003, CV004, CV005, CV008, CV012, CV013, CV014]

8.3 Scenarios, diligence asks, and thesis-breaks

The scenario frame should anchor on observable marks rather than false precision. The bull case only holds if the Army-wide procurement path, product expansion into simulation, and command-level adoption signals convert into revenue quality that can close the gap between the last round and the current external marks. The base case assumes the company is strategically valuable but still over-earning its public headline until private diligence clarifies contract durability, margins, burn, and preferences. The bear case is a classic down-round setup: multiple compression, slower procurement conversion, and a platform ceiling imposed by a larger defense software stack. The key diligence asks are the 2026 cap-table terms, revenue bridge, cohort retention, burn/runway, and how much of the Jan. 2026 financing was true primary capital versus secondary liquidity.[CV003, CV004, CV006, CV010, CV011, CV012, CV013, CV014]

8.4 Exhibits