Monarch at $100M ARR: buy the team, not the product

You are deciding whether your first acquisition should buy a team that can run the next consumer-banking product line. Monarch's announcement is a clean example: on October 1, 2026, the company announced $100 million in annual recurring revenue and the acquisition of MBI, formerly HMBradley. It was Monarch's first acquisition. More than 1 million members were actively managing their finances on the platform.

The acquired team had spent about ten years building consumer-banking products and the supporting infrastructure behind them. The deal created Monarch Labs from the acquired team. The unit will build new financial products and services for Monarch members. Zach Bruhnke, who co-founded MBI and is its chief executive, will run Monarch Labs, with a focus on new products and growth areas. The financial terms were not disclosed.

Monarch bought operating range, not a logo

The deal is a capability buy: Monarch took a team that could run the next line, not a finished product to ship right away. A first acquisition is often a test of operating range, not a product gap. At a scale where the current product is already running, the next product line is a different kind of risk. You are not testing demand; you are testing whether you can staff, build, and support another product without losing the first.

If the target team can run the next line without a long integration, the deal buys operating range. If it cannot, the deal becomes an integration burden. Ask what the team will own, not what logo it adds.

The team-first test works in order

Monarch's team-first test: name the product line the target team will run; if it already owns the consumer-banking stack, buy the team; if not, keep building.

• Start with the next consumer-banking product you want to ship, not the target's name. Say what it does, who uses it, and what infrastructure it needs. Write the product, the member outcome, the required stack, and the launch window on one page. Include the data, permissions, and compliance work the product needs. A consumer-finance product is rarely just an interface; it may need account connections, transaction data, and a clear path to support. If those pieces are missing from your brief, the target cannot be judged fairly. If you cannot name the product line, you are buying a story. A first deal should answer a concrete operating question, not a vague ambition.
• Look for a team that has shipped the same kind of product, not just adjacent software. Ask what they built, who used it, and what systems they already run. The common mistake is to buy a product because it is on a roadmap and then discover the team cannot run it. Check the team's incentives, not only its resume. A team that built a product for a different customer may need a long reset. Ask how they handled support, edge cases, and the unglamorous parts of running a financial product. If the target's existing products do not match your next line, keep building.
• Do not scatter the team across your existing roadmap. Give them a named product line and a leader who can own it. Give the unit its own roadmap, budget, and hiring plan. If the acquired team must ask permission for every release, the next product line will move slowly because of your existing org. Make the mandate visible to the whole company, not hidden in a plan. A team that is absorbed into your current org chart rarely gets to run the next line. It gets assigned tasks, and the capability you bought fades.
• A first acquisition should not require you to bet the company on a new product. If the target's value depends on a large revenue multiple or a complex integration, slow down. The deal should be explainable in one sentence: you bought a team that can run a product line you already need. Set a review date before you close. Decide what evidence would show the team is running the next line, and what evidence would show you should stop. A first deal should teach you something, so the exit criteria matter as much as the entry. Write the product line, the stack, and the leader before you sign anything. If one of those is missing, the deal is not ready.