Traveling the world with Boomi Companion

In late March 2026, I (Jeremy Eastburn, Principal Developer Advocate) teamed up with Michael Bachman (Boomi's Head of Research, affectionately known as "Bachman") for a major undertaking: a 6-week, 50,000-mile world tour. We crossed 3 continents, traveling from the US to Sydney to Bangkok, to speak with dozens of customers, partners, and government agencies.

The primary mission of this fast-paced tour was to introduce our new open-source developer offering, Boomi Companion: a suite of Agent Skills designed to help anyone activate their data faster and accelerate time to value with the Boomi Platform.

Not one person we met with had ever seen Boomi Companion, and some had never even heard of Boomi. But across 30+ conversations, the same reactions kept surfacing in different rooms: "gamechanger," "extraordinary," "what we've all been dreaming about," "it lowers the barrier to entry."

This is the story of what happened in those rooms, and how Bachman and I came to the following realization: Boomi Companion is the most consequential thing we've seen in all our years at Boomi. It's the story of what we learned as customers watched their business problems turn into real, working solutions, prototyped in front of them, with their own eyes.

Boomi Companion, briefly

Before getting into what happened in those rooms, in case you haven't heard, here's the short overview of Boomi Companion.

Boomi Companion is an open-source suite of Agent Skills that enable your AI agents to work with the Boomi Enterprise Platform through natural language. Each skill bundles deep platform knowledge with the tools and prompts an AI agent needs to put that knowledge into action, translating plain-language requests into real work on your Boomi account.

Whether you're an experienced Boomi developer accelerating your workflow, a newcomer ramping up on the platform, or a practitioner whose work touches Boomi in another way, Boomi Companion is a knowledgeable partner that helps you move from idea to outcome faster.

For a deeper dive into the technical details, refer to Boomi Companion: Equipping the agents your teams already use.

Australia: the room around one table

Australia was where the road show really took shape. Across 10 days in Sydney and Melbourne, Bachman and I had more than 30 conversations: partner sessions, customer briefings, and executive whiteboards. The afternoon I kept coming back to was a Sydney partner-hosted session, where one of our trusted Boomi partners had brought several of their customers into a single room around one long table.

We walked through what Boomi Companion can do, then opened it up to the room: what would you actually want to build? Two moments came out of that one afternoon:

• Order-to-cash for a global medical devices customer: The first came from a global medical devices customer. The leader at the table asked, point-blank, whether Boomi Companion could build out a full order-to-cash solution, something they had been struggling to build. We said, "Let's try it!" 9 minutes later, a working prototype of a complex order-to-cash process was up on screen. The leader looked at it and exclaimed: "This is a gamechanger."

• Student scheduling for a Sydney university: The second moment came from a Sydney university customer at the same table. With the room, we co-prototyped a student scheduling solution, the kind of workflow that has to bridge professor schedules, enrollment systems, and student preferences. They liked what they saw enough to invite Bachman and me to their campus later that same day to walk their full team through the capabilities of Boomi Companion and how else we are innovating as a company.

Different verticals, different personas, similar reactions. Not to a slide deck, but to watching a customer's actual problem turn into a working prototype, in front of them, in real time.

The US leg: Houston and New York

Then we came back stateside. First Houston, then New York.

In Houston, we shared a main stage with 500 oil and gas professionals at an AI conference, then spent the rest of the day in private executive demos for global energy companies. The question that kept surfacing (sometimes asked directly, sometimes implied) was a sharp one: If I can build anything with Claude Code, why do I need the Boomi Platform?

It's a fair question, and the answer is what makes Boomi Companion meaningful. Boomi is the trusted underpinning and infrastructure for everything Boomi Companion builds via Claude Code (or any similar tool). You can look at the Platform, see and understand exactly what was created, audit it, change it, orchestrate it, and govern it. The output isn't buried in thousands of lines of opaque code. AI-built solutions land in a place you already trust to run them, backed by the design time and runtime architecture that Boomi customers have built their stack around for years.

A week later, I joined our Boomi account team in NYC for an afternoon with a major US healthcare system. It was an active RFP, so the room had a long list of questions about the Platform, and we had a high bar to clear. Then we showed Boomi Companion. Mid-demo, a director in the room paused, looked up, and said: "This is brilliant."

In a regulated, high-stakes environment, that word doesn't fall out of someone's mouth lightly. The bar in that room had been a real one. Boomi Companion had earned the rest of the conversation.

Malaysia: the cruise

The week in Kuala Lumpur was full of partner meetings, but the specific experience I want to walk through happened on a 4-hour lake cruise a short yet beautiful drive from the city. Telcowin, a trusted Boomi partner, had organized this half-day Cruise & Connect event, bringing together a room of Malaysian government agencies and prospective Boomi customers in the government province south of Kuala Lumpur, where the agencies and the people who run them live. Most of them had never heard of Boomi.

Bachman opened with a Boomi introduction framed around the importance of data activation. I followed with an explanation of Agent Skills and how we leveraged them to create Boomi Companion. Then, with no stable wifi on the boat, I played a pre-recorded version of our Houston oil and gas demo.

Frankly, it didn't land. Most in the room weren't native English speakers, nor were they oil and gas professionals, and we'd jumped from "you've never heard of Boomi" to "let me show you an advanced developer experience for Boomi" in one move. We hadn't yet made the value of Boomi or Boomi Companion clear.

Then we broke for lunch and split up across tables, asking each agency what problems they were trying to solve or what business outcomes they were seeking. At one of those tables, a real pain point surfaced: government agencies that weren't interconnected, citizens providing the same information over and over, and a need to share data between agencies only when the citizen consented.

We immediately pivoted. We connected my laptop to a coworker's cell phone hotspot, brought everyone back together, and reframed the demo around what we'd just heard. I read the prompt out loud—a meaty one, multiple processes, various services and endpoints, with event-driven architecture in the middle. Then we let Boomi Companion go.

For the next 20+ minutes, the room watched it work. Would the hotspot hold? Would Boomi Companion finish? It held. It finished. Then we asked Boomi Companion to generate the solution documentation in the local Bahasa Malaysia language.

When the documentation came up on screen in their language, around their problem, that was the moment. It clicked. We talked a lot about trust on that cruise. The room that had walked in not knowing what Boomi was had left seeing their own problem solved, in 26 minutes, in their language, with the cell signal flickering the whole time. Everything the day had built toward landed in that moment. The result? Real follow-up conversations that translated into real opportunities.

Telcowin captured it on their LinkedIn post: "On a boat, in 26 minutes. No big deal."

Bangkok: the multilingual unlock

The day after the cruise we hopped on a quick flight up to Bangkok for a partner training event. The pitch we walked in with was straightforward: Boomi Companion could be a knowledgeable sidekick for the kind of person who fields client questions about what Boomi can do (a business analyst, say) but who isn't necessarily a Boomi developer themselves.

We generated some solution documentation in both English and Thai. Then we had an idea: We asked Boomi Companion: "Explain Boomi to me in simple terms, but in the Thai language."

It did. We pulled someone from across the room who'd never heard of Boomi, asked them to read what Boomi Companion had produced in Thai, and then asked them to explain Boomi back to us. They could! A person who had walked into the room knowing nothing about Boomi was now describing it back to us, in their own language.

That moment generated an idea: what if Boomi Companion could build the integrations themselves bilingually: process step labels, profiles, documentation, all in the local language? In the iterations that followed, we tested it. It works in Thai. It works in Japanese. It works in Bahasa Malaysia. Even though the platform itself stays in English, the outcomes Boomi Companion produces for you can come out in the language of the audience you're working with.

That's a door we hadn't expected to walk through on this trip, but it was one of the most surprising and valuable lessons to come out of it. It's a door we plan to keep walking through.

Coming home

What surprised us most across each stop on our world tour of 5 cities and 2 trips around the equator was how eager and excited people were, not just to build with the Boomi platform, but to build more quickly and efficiently than they ever have before. Existing customers and partners who'd been building on the Platform for years saw Boomi Companion and immediately recognized the opportunity to accelerate.

We started every single meeting by asking the room what they actually wanted to get out of our time together. We'd write their needs on the whiteboard as they listed them. The thing that surprised us as we wrote down each item on the whiteboard was how often Boomi Companion already addressed those needs without us having to plan the demo around them: accelerated builds, design standards, naming conventions, governance audits across existing processes. The kinds of unglamorous work that take weeks of someone's time and that everyone wishes were already done.

Somewhere between Bangkok and home, that opening realization felt earned. After every meeting, every prototype, every flight, Bachman and I kept coming back to the same observation: this is the most consequential thing either of us has seen in all our years at Boomi.

Boomi Companion has created a whole new doorway into the Boomi Enterprise Platform: a fresh way to design, build, and run integrations that didn't exist a year ago.

Boomi Companion is live, open source, and ready to solve your next real-world problem. The next prototype is yours to build. Get started with Boomi Companion.

Acknowledgments

Boomi Companion v1 is the work of Chris Cappetta, Ben DeBoer, Shasta Hayes, and Claude. Thanks to the AI & Platform Center of Excellence for sponsoring the trip, to our Boomi APJ friends (Lisa Hills, Amanda Sattler, Caysey Jackman, Nogeeshik Haskell, Richard Yang, Tony Mann, Rob Warneford, Ayffus Gyamfi, Jim Fisher, and the whole team) for hosting us across the region, to our Southeast Asia colleagues (Greg McCreanor, Roy Wakim, and Rodney Koh) for support throughout the SE Asia leg, and to the customers and partners across the trip for their time, their questions, and their trust. Special thanks to Michael Bachman for being a great travel sidekick and for putting up with me across more miles, hours, days, and weeks than either of us probably planned for.