Anthony Olivier has spent much of his working life on the part of a product people consult when something has become confusing. The help system. The user guide. The instructions that make an expensive purchase useful. It is a peculiar corner of software in which to build a career: everyone wants the answer, and almost nobody arrives in a celebratory mood.
He founded MadCap Software in 2005 to serve the people who write those answers. Before that came eHelp and Macromedia, businesses connected to RoboHelp and the software demonstration tool that became Captivate. Across those changes, Olivier kept returning to technical communication. While products acquired new owners and new names, somebody still had to explain how they worked.
Now his public writing is occupied by a related problem. AI can make information cheaper to produce. Companies must still decide which information deserves to survive, who will maintain it, and what should happen when an answer is wrong. For Olivier, that question arrives with years of documentation work attached. The filing cabinet has learned to talk. Its contents require attention.
The opportunity after the acquisition
In October 2003, Macromedia announced an agreement to acquire San Diego-based eHelp in a transaction valued at approximately $65 million. The attraction included two different kinds of assistance: RoboHelp, for creating help systems, and RoboDemo, for demonstrating software. Olivier was part of the management team continuing with the business. It was a transaction involving products already built around helping people understand other products.
The corporate sequence matters because MadCap emerged from the opening that followed. Macromedia’s interest in Flash-based demonstrations left technical authoring with a less central place in its strategy. Olivier saw room to start again with XML-based technology. MadCap’s founding team included developers with experience at eHelp. They brought familiarity with the work and an opportunity to build a new authoring system.
There is an appealingly practical quality to this origin. The customer’s problem had survived the acquisition. Writers still needed tools. A company could organize itself around that continuing demand. MadCap’s bet was that technical authoring merited its own sustained attention, even when another company’s priorities lay elsewhere.
“This has been now what we live and breathe, technical authoring.”
Anthony Olivier, 2023
His earlier roles also placed him across the boundary between explanation and instruction. At Macromedia, he served as a general manager with product strategy responsibilities covering help, eLearning and multimedia. Those areas would later reappear in MadCap’s expanding portfolio. The apparent niche contained several neighboring businesses.
A place for the people who write the instructions
By April 2013, MadCap had given its customers somewhere rather more sociable than a help window to meet. The first MadWorld conference took place at San Diego’s Hard Rock Hotel. It offered 40 training sessions and 24 professional speakers, with networking spread over more than two days. Technical communication had acquired a venue accustomed to rather different kinds of headliners.
The useful detail was the hospitality suite. Attendees could bring questions, workflow problems and even their own projects to people who knew the tools. One solo technical writer settled in with a laptop and a succession of questions for a MadCap support expert. For someone accustomed to solving documentation problems alone, a room full of available expertise was a substantial attraction.
That combination of serious work and deliberate sociability suited a community whose output is so often encountered without its authors present. In 2014, Jennifer White’s comic introduction of MadCap personnel included Olivier among its targets. A CEO at a customer conference can reasonably expect applause. Being teased is a useful variation.
A decade after the first gathering, Olivier welcomed attendees to MadWorld’s tenth-anniversary event at the same hotel. Jean-François Ameye announced AI integration in MadCap Central. The program included product developments and sessions for the people using them. Familiar faces and a familiar setting were meeting a new set of software questions.
There is a business logic in making room for those conversations. An author’s difficult project can reveal something that a feature list conceals. A demonstration explains what software can do; a customer with a stubborn problem explains what it still needs to do. A conference can accommodate both, preferably before the evening drinks.
Buying room for customers to grow
Olivier’s expansion strategy has repeatedly involved adding another route through the work. In 2015, MadCap acquired Doc-To-Help from GrapeCity. It brought an established option for people authoring in Microsoft Word, complementing Flare’s approach. The purchase covered the product’s assets, including its code, intellectual property and customer relationships.
That choice is revealing. Building a software business can tempt a founder to treat one workflow as the natural destination for everyone. Acquiring a Word-based product acknowledged the installed habits of another group of writers. Their starting point mattered. A useful portfolio could include different ways of producing and publishing content.
For years, MadCap grew as a bootstrapped business. In January 2022, it announced a majority-growth investment from Battery Ventures. Morad Elhafed and Roland Anderson joined the board. Olivier described a business supported by organic growth and financial discipline, now taking on an investor to help with its next stage.
Olivier later described the partnership as a learning experience, with Battery helping recruit executives and identify acquisition opportunities. The change involved the company’s capacity to grow as well as the capital available to it. A founder accustomed to building within existing resources had acquired another set of people to help plan the business.
In February 2023, MadCap acquired IXIASOFT, adding a component content management system based on DITA, a standard for structured information. The distinction can sound forbiddingly technical. Its business implication is straightforward: some organizations need tighter rules, more control and a different system for managing large collections of content.
Olivier framed the acquisition around changing customer needs. A team that starts with one authoring approach may later require more structure as its work expands. Providing a route between those environments gives the vendor another chance to serve the customer. It also makes expansion less dependent on persuading everyone to remain in the same product forever.
Xyleme, acquired later in 2023, extended that logic into learning content management. Training teams and documentation teams can carry related information in separate systems. Bringing their tools into the same portfolio created an opportunity to connect the work. The instruction explaining a product and the lesson teaching it need a way to remain in agreement.
Olivier’s stated ambition was to connect enterprise content across those boundaries. Xyleme’s then-CEO, David Walters, pointed to the complementary focus of the two businesses, including content reuse and publishing to multiple channels. The acquisition made the coordination problem part of MadCap’s own product responsibilities.
The manual acquires a new reader
By 2026, Olivier was making a pointed argument about the abundance of AI-generated material. He described a customer dismantling more than 11,000 training courses accumulated over a decade. In his telling, the collection had become a burden. Quantity had outrun the organization’s ability to keep its knowledge useful.
The example gives his argument a tangible shape. A course carries an obligation to know whether it is current. So does a support article or an onboarding guide. Producing another version adds something to the maintenance queue. AI can accelerate the arrival of those obligations along with the arrival of the words.
A conceptual view of Olivier’s argument for governed knowledge.
His proposed discipline starts with ownership and validation. Someone must carry responsibility for the information an organization makes available. In that view, the author remains central even as the tools for producing and retrieving text change. The expertise that distinguishes a company must stay connected to the material circulating under its name.
His writing on enterprise AI infrastructure extends that responsibility into distribution. MadCap positions SyndicateAI as a governed delivery layer connecting content systems with the places information is consumed. The concern is what reaches a portal, an application or an AI assistant after the writing and approval work has happened.
For Olivier, the unit of ambition has widened. A help authoring tool assists the writer. A delivery system must also account for the many destinations that depend on the writer’s work. The company’s history describes an expanding perimeter around the same essential transaction: somebody needs information that another person can stand behind.
Tomorrow comes with the software
Olivier also argues against casually building knowledge infrastructure in-house. The enduring expense, he says, lies in maintaining integrations, permissions, support and the system itself. He allows for exceptions where the capability truly differentiates a business and the organization can support it over time. His commercial interest is explicit: MadCap sells this infrastructure.
“Build what only you can build. Buy the rest.”
Anthony Olivier, 2026
The argument fits a career spent serving the work that continues after the exciting part. The product ships; the instructions need updating. The acquisition closes; customers need a path forward. The new AI system answers a question; someone needs to know whether it has the current information.
Olivier’s place on the University of North Texas Technical Communication Advisory Board provides another connection to the people entering that profession. MadCap’s tools are taught in educational settings as well as used at work. The audience has included experienced authors and students preparing to become them.
Across that span, his business has kept finding further consequences of a simple obligation: explain the thing properly, then keep the explanation useful. It is an occupation with limited scope for a final victory lap. Somewhere, a product has changed. Somebody will have to update the instructions.