45 min

How to Make a Company AI-Native: Michael Batko on the Three Systems to Build First

Making a company AI-native starts with three systems, according to Michael Batko: a shared company AI brain that holds context, a skills library so one person's workflow becomes everyone's, and a command center that shows what's running and how well. Michael spent eight years as CEO of Startmate, often called the Y Combinator of Australia, before founding Hourglass AI, which builds these systems inside other businesses. He explains why he kept it a service business, which companies make the best clients, why behavior change is harder than the technology, and how he prices audits, builds and ongoing support.

AI adoptionAI-native operationsproductized servicesservices pricingfounder lessons

Guest

Michael Batko

Michael Batko

Founder, Hourglass AI

Michael Batko is the founder of Hourglass AI, which audits companies, builds AI systems for them and maintains those systems over time. Before that he spent eight to nine years as CEO of Startmate, often described as the Y Combinator of Australia, backing hundreds of startups. His earlier career included American Express, PwC and KPMG, followed by two startups, one of which went public and one of which was sold.

Key Takeaways

  • 1.Customer conversations come first; at Hourglass, clients pay for an audit so they share their real problems.
  • 2.Productize internally and sell as a service because clients want one trusted owner.
  • 3.The best-fit client is 20 to 100 people, founder-led and without an engineering team.
  • 4.Build three foundations first: a company AI brain, a shared skills library and a command center.
  • 5.Behavior change is harder than the technology, and clients need to arrive ready for change.
  • 6.Use a low flat-fee audit, a scoped build range and ongoing support; clients should own their AI bill.

Full Transcript

4:49
Michael Batko

The number one thing every founder should focus on is customers and customer conversations. At Hourglass we literally get paid to talk to customers, because we audit the company first.

6:30
Michael Batko

We build custom two or three times, productize it internally so we can deploy it easily, and still offer it as a service. They want one head on the chopping block.

10:22
Michael Batko

Our ideal client is 20 to 100 people with no engineering team. Usually founder-run, with a strong leadership team. Get the founder on board and you can transform the whole company within six months.

14:33
Michael Batko

The first thing we do for every client is create a company AI brain. It's ring-fenced so not everyone sees salary data, but it already has the client data and company tone of voice.

15:00
Michael Batko

A shared skills platform means one person builds a due diligence skill and the whole firm has it, as one global version.

18:06
Michael Batko

The hardest thing about AI transformation isn't the technology. It's behavior change. People do not want to change.

25:24
Michael Batko

A client call finishes, the transcript goes into our AI brain, and it drafts a follow-up with next steps. Within five minutes both people have an email from me.

28:54
Michael Batko

I hate persuading people to use AI. You can't help someone who doesn't want it. They have to come ready for the change.

33:57
Michael Batko

We've learned to give a range rather than a fixed fee, then run a scoping call before the build and reprice based on the features.

36:45
Michael Batko

We never own a client's AI bill. If we take it, nobody at the client cares how much they're spending, and you want that feedback loop.

Frequently Asked Questions

In an AI-native company, an AI assistant is the first stop for most work. It already holds the company's context and workflows, so people draft emails, documents and follow-ups through it instead of copying information between tools.

Michael starts every client with three foundations: context through a company AI brain with access controls; collaboration through a shared skills library; and a command center showing which agents are running, how they're used and how well they perform.

Companies with 20 to 100 people and no engineering team are a strong fit. They're usually founder-led, so decisions move fast. Smaller companies should build for themselves, while larger ones can become long IT transformation projects.

The hard part is behavior change, not technology. Many people are still judging AI on a bad experience from two or three years ago. The best results come from clients who arrive ready to change.

Michael splits pricing into a flat-fee audit, a build quoted as a range and confirmed after a scoping call, and a monthly retainer to maintain and improve what was built. Crediting the audit toward the build can shorten decision times.

The client, Michael says. If the vendor covers the AI bill, nobody at the client pays attention to spend and they lose the feedback loop. Clients should use their own AI subscriptions.