Francis Brero, VP of AI Strategy at HG Insights, joins Ray Rike to unpack what it actually takes to move a established software company toward an AI first operating model. Francis founded MadKudu, which was acquired by HG Insights, and was given a mandate to infuse AI into both the product and the internal operating processes. The conversation covers how HG Insights defines AI first, how the company organized around it, who owns execution across the functional groups, and who is accountable for the return on those AI investments.
What Ray and Francis Covered
The buyer is becoming an agent. Francis rebuilt the product assumption from an analyst consuming a data file to an agent consuming data on demand. Shipping an MCP interface was the first build in his first three weeks, and it opened the door to every customer already standing up agentic go-to-market systems.
Velocity is the separator between legacy and AI native. An agentic software development lifecycle changed shipping pace, and Francis makes the case that bolting an engine onto a bicycle only gets you so far before you have to build the motorcycle.
Pricing has to be re-architected for agent discoverability. Unique, high value data assets get priced down so an agent will actually reach for them, commoditized assets absorb more of the price, and data delivered through MCP is leased for a single workflow rather than sold into the customer warehouse. Both changes alter the shape of gross margin.
The $5, $50, $500 decomposition test. Every job to be done gets broken into atomic tasks, and each task gets a price the business would pay to outsource it. Five dollar tasks get automated. Francis notes the hardest part is that most operators have never decomposed their own work that far.
Centralized ownership of AI ROI. Francis owns the leading indicator and the productivity gain, the functional leader still owns the lagging indicator, and the two present the business case jointly to the CFO and CEO. Centralization is also the control point that prevents engineering spend from exploding when everyone gets model access.
Two lessons learned. Operationally, he moved to second order process redesign before the organization understood first order automation, and had to reset to crawl, walk, run. On the product side, AI generated ten times more code and therefore more total defects, until he introduced adversarial review across different model families rather than same family self review.
If you are finding value in these conversations, please subscribe on your favorite podcast app, leave a five star rating, and connect with Ray Rike on LinkedIn to suggest future guests.
Podden och tillhörande omslagsbild på den här sidan tillhör
Ray Rike. Innehållet i podden är skapat av Ray Rike och inte av,
eller tillsammans med, Poddtoppen.
