The launch is a few days behind us, the press has covered the product, the response has been generous. I want to write — while the moment is still close — about the part of last week I think is easiest to underread.
On May 7, at the inaugural Health Decode: The Makers Summit in New York, we unveiled Daily Command — pharma's first system of work for brand, marketing, and commercial teams. Seventy-five of the most senior brand and agency operators in the industry, leaders responsible between them for more than $40 billion in annual brand spend, co-built it over the past quarter and put their names on it publicly. We call them Makers.
That is, by itself, a lot of news. But the most consequential thing about the launch was not the product, and not even the people. It was the precedent.
For most of the past two decades, pharma commercial software has been built on a familiar set of assumptions. Vendors design against their own read of what brand teams need; development happens far from the brand marketer's day. Customer input arrives late, often after launch, often through formal channels that move slowly. The brand marketer, whose day the product is meant to support, has rarely been in the room where decisions about that day get made.
This was not a moral failure on the part of the category. It was a structural one. Building software with customers — on the build's actual cadence — is operationally hard. It requires customers willing to sit inside an unfinished product, and vendors willing to be visibly unfinished in front of them. It requires giving up the comfort of presenting a polished launch.
We gave up the polish. We did not regret it.
What "with" actually meant
The category already knows a version of co-creation that is not what we did. Advisory boards meet quarterly and offer reactions. Beta cohorts get assembled after the architecture is locked. Strategic input gets solicited late, polished into a slide, and presented back as proof that the customer was heard. None of that is wrong in itself. None of that is what built Daily Command.
Leading up to Health Decode, the seventy-five Makers were inside the product process. They wrote module specifications. They stress-tested working software in hundreds of hours of sessions. They argued with our engineers about which parts of their day they could not afford to slow down. They told us, in language the design team could act on, what the morning hour of a pharma brand marketer actually looks like, and what AI would need to do to be useful in it rather than become another window to manage.
None of the Makers was selected to be polite about the product. They were selected because they personally run the workflows Daily Command is designed to replace, and because their judgment, applied honestly, was the most useful constraint we could put on the build.
That is the difference between input and constraint. Input gets considered. A constraint gets honored. We treated their judgment as a constraint on what shipped.
Why this resets the floor
A vendor's promise that it listens to customers means little once the listening becomes table stakes. What matters is what shipped because of it — what was different in the launch build because of which conversation, with which customer, on which day. That is the standard the rest of the category should be measured against from here.
Brand teams who buy pharma commercial software now have a working example of what building with — not building for — looks like in practice. They have a license to ask for it from every vendor in their stack. The Maker construct is documented and the names are public; what changed in the build because of which Maker is a thing brand teams can now ask their vendors to show.
The same principle is built into the product itself. Daily Command ships with an open Marketplace, not a closed stack — API-first, partner-neutral. We do not pick winners; brand teams do. Closing the system would have been easier and, for a quarter or two, more profitable. It would also have meant treating customer judgment as a thing to be managed rather than honored.
What we are committing to
Daily Command is the first product we built this way. It will not be the last.
The Maker format is now part of how Doceree intends to develop product. When Daily Command enters closed beta with five flagship partners in June, the Makers stay in the room. When the full industry release lands on July 14 alongside the Marketplace launch partners, the operators who shaped the product will be present at every threshold — and the names attached to it will continue to be the names of people whose judgment shaped what shipped.
I would not tell you this approach is right for every product, every customer, or every vendor. I would tell you that for software meant to support the daily work of people whose job is changing under them faster than their tools are, building for them is no longer enough. Building with them is the floor.
We set out to build a product for pharma brand marketers. We ended up building it with them. That is the part of last week's launch I most want the industry to read carefully.
— Harshit Jain, MD Founder & Global CEO, Doceree