Grant Demaree Turned a Three-Month Planning Lag Into Onebrief

The first draft of Onebrief was not code. It was a complaint, sharpened by consequences. In 2014, Grant Demaree was a young Army officer in Liberia with Joint Task Force United Assistance, part of the American response to Ebola. The virus kept changing its address. The planning process did not. By the time decisions traveled through briefings, documents, approvals, and updates, parts of the plan could be roughly three months behind the outbreak.

A treatment unit might be planned for a place where the need had already moved. Demaree changed how Ebola data was reported across the country and sketched an early software idea on a napkin. His frustration was not with a lack of intelligence or effort. It was with the machinery around both. Smart people were spending expensive attention moving facts between files.

The scene supplied the central argument of his later career: a military staff is a decision engine, yet much of its time disappears into document maintenance. Word files and PowerPoint slides are good at freezing an answer. A crisis is impolite enough to keep moving.

Two majors, three task forces, one recurring irritation

Demaree graduated from West Point in 2013 after studying Nuclear Engineering and International Relations. The pairing feels almost too neat in retrospect: systems and power, equations and institutions. He spent five years as an Army officer. After Liberia came service with joint task forces connected to the counter-ISIS campaign in Iraq, including assignments in Baghdad. Across commands, he kept seeing versions of the same friction. Plans lived in separate products. Changes had to be copied. Coordination depended on meetings, memory, and the heroic patience of staff officers.

He left the Army in 2018. Sensible advice pointed toward graduate school or an established company. He instead chose the less upholstered path and began researching a startup. The important word is researching. Demaree and software engineer Rafa Pereira did not treat military experience as permission to skip discovery. They made more than 200 calls across the hierarchy, from junior officers to senior commanders. Then they arranged 19 planning exercises where military volunteers gave up Saturdays to test prototypes against fictional scenarios.

Those Saturdays are more revealing than a pitch deck. Onebrief had no classified access, no large contract, and little reason for a customer to be patient. So the founders built a lawful proving ground. The scenarios were invented; the workflow pain was real. Every awkward click and broken assumption could be observed before the software entered an operational network.

The laptop in the secure room

Enterprise software often begins with an invitation to a sandbox. Defense software can begin with a request to bring a specially prepared commercial laptop into a sensitive compartmented information facility. Onebrief worked through the approvals. The machine went in. The software supported planning around a major Pacific exercise and a contingency involving a major adversary. An inelegant workaround became evidence.

The first meaningful contract was not designed to produce a handsome margin. Demaree has explained that Onebrief expected to lose money. The value lay elsewhere: a facilities clearance, sponsors for operational networks, credibility, and continued contact with users. Even from a weak negotiating position, the company protected three things. The government would cover the prime contractor’s fee. Onebrief could speak directly with its users. Its intellectual property remained its own.

There is a small business lesson hiding inside the bureaucracy. Revenue is only one thing an early customer can pay you with. Access, trust, feedback, and a contract that leaves the product intact can be worth more.

A plan should behave like data

Onebrief’s product decision was to stop treating a plan as a stack of finished documents. Information becomes structured, reusable building blocks in a shared workspace. A change to one item can appear wherever that item is used. Maps, cards, lists, timelines, and briefings draw from the same underlying material. Version control becomes a property of the system rather than a meeting topic.

This sounds ordinary to anyone raised on collaborative consumer software. In a headquarters, it changes the arithmetic of attention. Staff can spend less time reconciling slides and more time considering options. Different echelons can work from a synchronized picture. The product is deployed across unclassified, secret, top-secret, and coalition networks, places where security and intermittent connectivity are not decorative requirements.

Demaree frames the sale in outcomes: decision speed, decision quality, and staff efficiency. “What Onebrief is selling is less software for your staff and more a promise to make your staff’s KPIs better,” he said in a 2025 interview. The sentence is useful because it removes the romance of features. A button matters only if work changes on the other side of it.

The company’s customer-success folklore offers a sharper test. During a major planning event, a technical problem threatened the young company. Team members coordinated across time zones and deployed a repair overnight. The customer woke, returned to work, and never saw the scramble. It is the sort of anecdote founders enjoy telling once the danger has acquired a safe historical distance. Its point is less theatrical: consequential software is judged when its maker would prefer not to be awake.

From shared plans to digital wind tunnels

Onebrief entered Y Combinator’s Summer 2021 batch. By late 2024, it reported $53 million in capital raised after a year of fourfold revenue growth. A $50 million Series C followed in early 2025, then a $20 million extension that valued the company at $1.1 billion. In January 2026, Onebrief closed a $200 million Series D at a $2.15 billion post-money valuation, led by Battery Ventures and Sapphire Ventures with participation from Salesforce Ventures, General Catalyst, and Insight Partners.

The financing arrived with an acquisition. Battle Road Digital makes wargaming and simulation software. Demaree compared its role to the wind tunnel built by the Wright brothers after they doubted the era’s lift and drag tables. A wind tunnel lets an engineer test a wing before risking a pilot. Wargaming lets a commander expose a plan to simulated friction before reality sends an invoice.

The comparison says something about Onebrief’s aspiration. The company no longer wants merely to help people write and coordinate plans. It wants planning, simulation, and live decision support to sit in one environment, with AI assisting the flow between them. Battle Road’s integration is intended to support more domains, cloud deployments across military networks, and eventually AI self-play. The plan becomes less like a file and more like a living model that can be tested.

The early shift

For someone building a company around speed, Demaree keeps an unfashionably early clock. He has said he wakes around 5 a.m., exercises, then protects a stretch of quiet work. Bedtime is around nine. He describes himself as energized in the morning and less useful at night. No mythology, just capacity planning applied to a person.

His recommended reading is similarly operational. He points to Jen Pahlka’s writing at Eating Policy for a model of government in which culture shapes implementation. Policy may announce an intention; hiring and incentives decide how it lands. It is an observant choice for a founder whose customers contain brilliant people, rigid procedures, and consequences that do not wait for tidy organizational change.

In 2026, Hawaii’s Entrepreneur Awards recognized Demaree and Onebrief with Deal of the Year. Forbes later placed him at No. 153 on its Veteran 250. The company is headquartered in Honolulu, near the Indo-Pacific commands that make the region central to its work. Demaree has argued publicly that the Asia-Pacific deserves far greater strategic weight. His product thesis and geopolitical view meet at the same word: time.

That line softens the standard founder story. Demaree did not leave service because the experience meant little. He left because it meant enough to keep working on one of its stubborn problems. Onebrief grew from the belief that military staffs could be smaller, faster, more integrated, and more resilient. The phrase the company favors is “superhuman military command,” grand language attached to a practical inventory: shared data, fewer duplicate updates, software that works offline, and plans that can survive contact with change.

The stealable idea is quieter. When a vital institution moves slowly, begin by locating the unit of friction. In Liberia, it was not a shortage of slides. It was the assumption that a plan should live inside one. Demaree’s napkin sketch asked software to keep pace with events. More than a decade later, the question is still running ahead.