Aug. 14, 2026

The Future of AI Software Factories- OpenCLAW, Agent Orchestration & The Intelligence Age with Mark Smith [MVP]

The Future of AI Software Factories- OpenCLAW, Agent Orchestration & The Intelligence Age with Mark Smith [MVP]
The Future of AI Software Factories- OpenCLAW, Agent Orchestration & The Intelligence Age with Mark Smith [MVP]
M365 FM Podcast
The Future of AI Software Factories- OpenCLAW, Agent Orchestration & The Intelligence Age with Mark Smith [MVP]

Key Takeaways

  • Mark Smith [MVP] discusses the evolution of software development from traditional low-code platforms to advanced AI-first software factories.
  • The AI software factory model utilizes specialized, autonomous AI agents representing various DevOps roles to design, build, test, and maintain applications.
  • Context engineering and multi-model architectures are becoming increasingly vital as developers move beyond basic prompt engineering and single-vendor lock-in.
  • Autonomous systems leverage 'Ralph Loops' and dedicated observer agents like Ruru to enable self-healing and continuous improvement overnight.
  • Enterprise data sovereignty, security requirements, and local infrastructure play critical roles in determining whether to use cloud-native AI models like Microsoft's.
  • Institutional memory, maintained through structured wikis and documentation, is essential for giving AI development teams the persistent context they need.

What happens when AI stops being just a tool and becomes the team that designs, builds, tests, secures, documents, deploys, and even maintains your software?In this episode of the M365 FM Podcast, Mirko Peters speaks with Mark Smith [MVP], widely known as NZ365Guy, about the transition from traditional Microsoft development toward AI-first software engineering. Mark brings decades of experience across Microsoft technologies, Dynamics 365, Power Platform, Copilot, AI platforms, consulting, training, podcasting, and software development.The conversation goes far beyond Microsoft Copilot. Mark explains how he is building his own AI software factory with specialized autonomous agents, why he uses OpenCLAW as an AI harness, how multiple AI models can work together, why context engineering is becoming more important than basic prompt engineering, and what developers and IT professionals should learn to prepare for the Intelligence Age.

FROM MICROSOFT TRAINING TO THE AI ERA
Mark's journey into the Microsoft ecosystem started around 30 years ago. What began with an interest in learning web design eventually led him into IT training, Microsoft infrastructure, networking, management, Dynamics CRM, Power Platform, Copilot, and AI.He recalls the early days of the web, when technologies such as HTML and CSS were still relatively new to many organizations and Microsoft NT4 was becoming increasingly important. Over seven years, Mark progressed from selling technical training to delivering courses himself and eventually becoming general manager of the company.That experience created the foundation for a career that would continuously evolve alongside Microsoft's technology stack.

FROM DYNAMICS CRM TO POWER PLATFORM AND AI
Mark describes how his Microsoft journey moved from early Microsoft CRM into Dynamics 365 and later Power Platform. He was attracted to CRM not simply as a sales system, but as a platform that could be used to create many different kinds of business applications.Power Platform continued that evolution through low-code development. But Mark believes the next transition is significantly larger.AI is changing the interface between humans and software development itself. Instead of spending hours navigating configuration screens and traditional user interfaces, developers increasingly have the ability to communicate their desired outcomes through prompts, APIs, MCP interfaces, command-line tools, and AI agents.For Mark, this represents a fundamental shift away from traditional low-code development toward AI-first software creation.

THE MOMENT GENERATIVE AI CHANGED EVERYTHING
Mark began exploring AI years before ChatGPT, particularly around machine learning and Microsoft's Cognitive Services. However, the arrival of ChatGPT in November 2022 made the scale of the coming transformation much clearer.Another important moment came when he experimented with early Copilot capabilities inside Power Platform. During a Microsoft MVP session, he was able to prompt an application into existence while the technology was being demonstrated.That experience reinforced an idea that would increasingly shape his work: software creation was becoming conversational.

WHY MARK EXPANDED BEYOND THE MICROSOFT AI ECOSYSTEM
Although Mark has spent decades working with Microsoft technology, his current AI environment is deliberately multi-model.He discusses his experience with OpenAI, Anthropic, Microsoft models, Chinese AI models, European models, and other providers. Rather than designing systems around one vendor, he wants the ability to select the best model for a particular task.This approach reduces dependency on any single AI provider and allows the underlying models to change without rebuilding the entire system.The model becomes a replaceable component rather than the center of the architecture.

TRUST, DATA SOVEREIGNTY AND MICROSOFT AI
The discussion also explores why Microsoft's ecosystem remains important for enterprise AI.For regulated organizations, the location where AI inference happens can matter significantly. Data sovereignty, compliance requirements, infrastructure location, and third-party model providers can all affect whether an AI architecture is acceptable.Mark explains that he is developing software where Microsoft's own models and infrastructure can provide an important trust advantage. Organizations that already trust Microsoft's cloud environment may prefer AI workloads that remain within that ecosystem.This becomes particularly important in countries and industries where data cannot easily leave a specific jurisdiction.

WHAT IS AN AI SOFTWARE FACTORY?
One of the central topics of the episode is Mark's concept of an AI software factory.Traditionally, software projects require multiple specialized roles: requirements analysts, architects, developers, engineering managers, testers, security specialists, documentation teams, and release managers.Mark asked a different question:What happens if each of those roles becomes an AI agent?His current environment contains a team of specialized agents that represent different responsibilities within a DevOps-style software lifecycle.Instead of one general-purpose AI trying to perform every task, each agent operates within defined boundaries and responsibilities.

SPECIALIZED AI AGENTS IN THE DEVELOPMENT PROCESS
Mark describes several agents within his software factory.A requirements-focused agent gathers and structures requirements. An architecture agent researches and designs the technical solution. Development agents write code. Other agents handle verification, security, documentation, releases, maintenance, and orchestration.The agents are intentionally restricted.A developer agent, for example, should not simply declare that its own work is correct. Verification is performed separately. This introduces checks and balances similar to those found in mature human software engineering organizations.The result is an agentic development pipeline where work moves between specialized AI roles rather than relying on one large prompt.

RESEARCH BEFORE ARCHITECTURE
Another important principle is forcing agents to research before making architectural decisions.Mark does not want his agents relying on potentially outdated assumptions. His architecture processes therefore include awareness of the current date and research into current approaches before technical decisions are made.The objective is to answer a specific question:If we were building this system from scratch today, what would the architecture look like?This is particularly important in AI, where models, APIs, frameworks, security recommendations, and development patterns can change extremely quickly.

RALPH LOOPS AND AUTONOMOUS DEVELOPMENT
Autonomy becomes much more powerful when agents are capable of continuing work instead of stopping whenever they encounter a problem.Mark discusses his use of Ralph Loops, where agents continue working toward a defined goal until the issue has been resolved.This allows development activity to continue overnight.An agent can write code, encounter a verification failure, receive feedback, correct the implementation, run through the process again, and continue progressing without requiring Mark to manually intervene at every step.However, safeguards are necessary. Mark also implements mechanisms that stop agents when they repeatedly fail, preventing uncontrolled loops from consuming infrastructure resources indefinitely.

AN AI ENGINEERING MANAGER
The individual agents are coordinated through an orchestration layer.Mark describes Tara, his engineering manager agent, as the interface into the DevOps team. Tara coordinates the work between agents and ensures that tasks move through the appropriate stages.Rather than manually communicating with every development agent, Mark can interact with the orchestrator.This creates an architecture that resembles a real engineering organization: specialists perform defined tasks while an engineering manager coordinates the overall workflow.

SELF-HEALING AND SELF-IMPROVING SOFTWARE SYSTEMS
The software factory does not only build software. Mark is also experimenting with systems that monitor and improve themselves.He describes Ruru, an observer that operates outside the primary OpenCLAW environment.Ruru monitors infrastructure health, API availability, resource consumption, and other operational signals. When an issue is detected and verified, it can create a ticket automatically.The development orchestration system then discovers that ticket and moves it through the development lifecycle.In some situations, this means a problem can occur overnight, be detected automatically, enter the engineering workflow, and potentially be resolved before Mark starts work the following morning.This leads toward an important AI engineering concept: recursive self-improvement.

WHY MEMORY MATTERS FOR AUTONOMOUS AGENTS
Agent autonomy is not simply about giving an AI permission to execute tasks.Memory becomes critical.Mark discusses the need to distinguish between short-term, medium-term, and long-term memory. Agents need enough persistent context to understand what was created months earlier and why particular decisions were made.Documentation therefore serves a different purpose in an AI software factory.The wiki is not only written for humans. It becomes institutional memory for the AI development organization.Agents can refer back to previous architectural decisions, implementations, and documentation when making future changes.

Become a supporter of this podcast: https://www.spreaker.com/podcast/m365-fm-modern-work-security-and-productivity-with-microsoft-365--6704921/support.

🚀 Want to be part of m365.fm?

Then stop just listening… and start showing up.

👉 Connect with me on LinkedIn and let’s make something happen:

  • 🎙️ Be a podcast guest and share your story
  • 🎧 Host your own episode (yes, seriously)
  • 💡 Pitch topics the community actually wants to hear
  • 🌍 Build your personal brand in the Microsoft 365 space

This isn’t just a podcast — it’s a platform for people who take action.

🔥 Most people wait. The best ones don’t.

👉 Connect with me on LinkedIn and send me a message:
"I want in"

Let’s build something awesome 👊

Frequently Asked Questions

What is an AI software factory?

An AI software factory is a development approach where specialized autonomous agents take on specific DevOps roles—such as requirements gathering, architecture, development, testing, and maintenance—to build software collaboratively.

Why is Mark Smith [MVP] using a multi-model AI approach?

Mark utilizes a multi-model setup across OpenAI, Anthropic, Microsoft, and other global providers to select the best model for each specific task and reduce dependency on any single AI vendor.

How do Ralph Loops work in autonomous development?

Ralph Loops allow AI agents to continuously work toward a defined goal by writing code, running verification, handling errors, and correcting implementations without requiring manual human intervention at every step.

Why are data sovereignty and trust important for enterprise AI?

Regulated organizations must comply with strict data residency laws and security frameworks, making the location where AI inference happens—such as trusted Microsoft Azure infrastructure—a critical architectural decision.

1
00:00:00,000 --> 00:00:04,440
You're welcome everybody to another episode of the M665FM podcast.

2
00:00:04,440 --> 00:00:09,000
The podcast where we look on speakers Microsoft professional

3
00:00:09,000 --> 00:00:12,920
architects, consultiles, developers, IT leaders and decision makers.

4
00:00:12,920 --> 00:00:20,440
And yeah, we try to learn directly from every people in the Microsoft and from the Microsoft technologies.

5
00:00:20,440 --> 00:00:27,760
The days guest, I think it's someone who not really meets an interaction in the Microsoft community.

6
00:00:27,760 --> 00:00:37,440
And my guest is Mark Smith also known as the NZ 365 guy has been a Microsoft MVP for 15 years or over 15 years.

7
00:00:37,440 --> 00:00:54,880
Microsoft certified, okay, certified China founder of global based out of the Microsoft press book Microsoft 65 co palette adoption creator of the global success for 90 days mentoring challenge in the host of the.

8
00:00:54,880 --> 00:01:02,840
Yeah, over podcast, I think you have renamed it from the intelligent age podcast to Microsoft innovation podcast.

9
00:01:02,840 --> 00:01:21,680
Well, yeah, with more than 800 episodes and published since 2017 over the years, Mark has held thousands of professional worlds understand Microsoft technologies from dynamics 365 and power platform to today's rapidly evolving world of AI co palette in.

10
00:01:21,680 --> 00:01:37,080
Yeah, intelligent agents recently his focus has shift to one of the most exciting areas enterprise AI AI software factories and open claw where multi AI agent color,

11
00:01:37,080 --> 00:01:44,560
to design build and test to live a software ways called fundamental change how organizing create digital solutions.

12
00:01:44,560 --> 00:01:47,960
Yeah, welcome Mark. It's still amazing to have you here.

13
00:01:47,960 --> 00:01:50,880
Thank you. Thank you. It's a pleasure to be here.

14
00:01:50,880 --> 00:01:57,360
Yeah, so we've let the size normally you are the host.

15
00:01:57,360 --> 00:02:08,160
So, Mark, can you a little bit tell us how you how you become a part of the Microsoft ecosystem.

16
00:02:08,160 --> 00:02:19,040
Yeah, that's interesting. That started 30 years ago. So a long time ago, I was working for a company at the time that.

17
00:02:19,040 --> 00:02:26,480
Was involved in IT training. It was a company called New Horizons, which was headquartered in California.

18
00:02:26,480 --> 00:02:34,000
And I joined a company at that time that had the New Zealand franchise of that IT company.

19
00:02:34,000 --> 00:02:39,640
And I joined it because I wanted to learn web design.

20
00:02:39,640 --> 00:02:46,880
It was my goal. I had the company I was working for, which was in the medical industry at the time.

21
00:02:46,880 --> 00:02:53,040
I decided that we needed a website and started down that path. And back then,

22
00:02:53,040 --> 00:03:02,240
if you didn't have a super light as in from a file size on your website, you got criticized severely from the market.

23
00:03:02,240 --> 00:03:10,520
And so, you know, that was HTML, CSS back then you had to learn the whole everything and building sites.

24
00:03:10,520 --> 00:03:22,200
And so, this company advertised that they had a web design course that you could do over the course of a week, a full intensive, you know, six hour a day type web design course.

25
00:03:22,200 --> 00:03:27,800
And remember, this is at the the birjing of the internet. Back then, you know, Google wasn't even a thing.

26
00:03:27,800 --> 00:03:36,640
It was the search engines were were ultra vista and how was the other one as in.

27
00:03:36,640 --> 00:03:45,080
Fireball and you know, yeah, really, really old tech back then. And that was the start for me.

28
00:03:45,080 --> 00:03:51,840
And I joined, sorry, I signed up to do this course and then they told me that the course didn't exist.

29
00:03:51,840 --> 00:03:56,000
That they were aspirational and wanting to teach the course.

30
00:03:56,000 --> 00:03:59,080
And so from that, I joined the company.

31
00:03:59,080 --> 00:04:06,040
And as a salesperson of the training, and I sold the first 12 seats as a 12 seat classroom,

32
00:04:06,040 --> 00:04:10,800
I sold the first 12 seats and we didn't still didn't have a trainer.

33
00:04:10,800 --> 00:04:15,280
And so then they put me on train, the trainer out of the US at the work through the night.

34
00:04:15,280 --> 00:04:17,960
I learnt the web design course as the trainer.

35
00:04:17,960 --> 00:04:23,800
And then the next week, I delivered to the 12 students, individual students that I'd sold onto the course.

36
00:04:23,800 --> 00:04:25,600
So, and that was the start of it.

37
00:04:25,600 --> 00:04:34,400
And that was my start into IT at the time, really big, the big thing to get was that was.

38
00:04:34,400 --> 00:04:38,600
You know, by that, at that point, no value was switching over to Microsoft,

39
00:04:38,600 --> 00:04:41,480
been the big player in network operating systems.

40
00:04:41,480 --> 00:04:47,360
NT4 is what I started on from a tech perspective.

41
00:04:47,360 --> 00:04:51,640
And I was just immersed in it then for seven years.

42
00:04:51,640 --> 00:04:57,000
I taught courses on, I ended up teaching like a five day course on internet working,

43
00:04:57,000 --> 00:05:01,000
which covered everything around how packets move across the network,

44
00:05:01,000 --> 00:05:09,240
how they function down the OSIRM, which basically means how they get from your screen to the other side of the world.

45
00:05:09,240 --> 00:05:14,840
What's all the routes, you know, what is DNS, what is all the things that make the network infrastructure work.

46
00:05:14,840 --> 00:05:19,560
And that was, you know, my journey, I mean, I got exposed massively to Microsoft tech.

47
00:05:19,560 --> 00:05:23,360
At the time, I also bought some micro systems into the company,

48
00:05:23,360 --> 00:05:28,680
and I want a big contract for delivering all the Sun Microsoft system, system training.

49
00:05:28,680 --> 00:05:35,600
By that point, I'd moved into management and I became the general manager of the company over that seven years

50
00:05:35,600 --> 00:05:39,360
from starting off as the salesperson to getting into that position.

51
00:05:39,360 --> 00:05:43,640
And really, you know, I've been with Microsoft ever since.

52
00:05:43,640 --> 00:05:50,240
Yeah, you have worked across dynamics, power platform, corporate, corporate AI.

53
00:05:50,240 --> 00:05:57,040
How has your, your own career evolved alongside the Microsoft transformation?

54
00:05:57,040 --> 00:06:06,320
So it was, I, at this training company, our CRM was built on Fox Pro.

55
00:06:06,320 --> 00:06:11,480
Now, just to give you an idea, that means it was, it was never designed to use a mouse on it.

56
00:06:11,480 --> 00:06:17,920
It was designed to use keyboard shortcuts and, and key combinations.

57
00:06:17,920 --> 00:06:22,320
It was, it was designed pre-email.

58
00:06:22,320 --> 00:06:24,880
So you think there wasn't even an email address field?

59
00:06:24,880 --> 00:06:30,400
Well, not pre-email. It was never designed for email because email wasn't even a mainstream kind of construct.

60
00:06:30,400 --> 00:06:32,240
Then everything was phones.

61
00:06:32,240 --> 00:06:38,360
It was all around calling people, getting people on the phone and, and, you know,

62
00:06:38,360 --> 00:06:42,480
our draw card was, you offered a one day free training.

63
00:06:42,480 --> 00:06:45,120
And you've got to remember, this is the, the start of all tech.

64
00:06:45,120 --> 00:06:48,400
It was a start of using word in XR on PowerPoint.

65
00:06:48,400 --> 00:06:52,000
Now, I mean, our most popular course was exalt training.

66
00:06:52,000 --> 00:06:56,320
A two day, a two day exalt training course was the most popular course.

67
00:06:56,320 --> 00:07:03,600
But, you know, we, I was looking for a CRM that was a bit more modern.

68
00:07:03,600 --> 00:07:10,560
And the, the, the company, the pairing company, a new horizons wanted to go with the product called sales logic,

69
00:07:10,560 --> 00:07:11,560
back then.

70
00:07:11,560 --> 00:07:15,560
And Microsoft had just bought out MSCRM.

71
00:07:15,560 --> 00:07:22,520
And it started as MSCRM 1.0 in 2003. It started 2003.

72
00:07:22,520 --> 00:07:27,360
And by November 2003, it was MSCRM 1.2.

73
00:07:27,360 --> 00:07:32,480
And, and then they skipped too entirely and went to three.

74
00:07:32,480 --> 00:07:35,200
And that's when the dynamics name started to kick into play.

75
00:07:35,200 --> 00:07:42,760
And that was because they had bought other more ERP related products into the suite and that bazaar suite.

76
00:07:42,760 --> 00:07:46,040
And, you know, I got to say, I just fell in love with the tech.

77
00:07:46,040 --> 00:07:51,480
And for me, it wasn't about like a saw beyond the vision beyond CRM systems,

78
00:07:51,480 --> 00:07:54,240
which is to be able to build any type of system.

79
00:07:54,240 --> 00:08:02,240
And really, that was the original low code system that, that I touched from a Microsoft perspective.

80
00:08:02,240 --> 00:08:05,600
And you think SharePoint was only just coming out around the same time.

81
00:08:05,600 --> 00:08:12,720
It was, you know, very new SharePoint and content management systems at that time.

82
00:08:12,720 --> 00:08:14,680
They were all brand new things as well.

83
00:08:14,680 --> 00:08:16,760
I mean, our mobile phones were brand new.

84
00:08:16,760 --> 00:08:22,920
Like, you know, it was, it was a big deal to be able to get the web browser to work on your mobile phone back then.

85
00:08:22,920 --> 00:08:27,000
And so, yeah, it's been a long journey in tech.

86
00:08:27,000 --> 00:08:36,520
And so I've ridden the, the dynamic CRM and then Dynamics 365 journey right up to 10 years ago.

87
00:08:36,520 --> 00:08:40,360
But over 10 years ago, now Power Platform kicked in.

88
00:08:40,360 --> 00:08:51,440
And so, rode that journey and, but you know, one thing I've always observed about the smart people at work inside Microsoft.

89
00:08:51,440 --> 00:08:56,840
They always move to where the money where Microsoft is investing the money.

90
00:08:56,840 --> 00:08:59,720
And if you've just watched this space for a little while,

91
00:08:59,720 --> 00:09:03,560
then not really investing it in Dynamics 365,

92
00:09:03,560 --> 00:09:06,680
then not really investing in the Power Platform.

93
00:09:06,680 --> 00:09:10,920
And I might get some hate from that, but read the writing on the wall.

94
00:09:10,920 --> 00:09:17,000
Look at the people that have left Microsoft in recent times and look at the product teams that they've been involved in.

95
00:09:17,000 --> 00:09:21,680
The day of low code has been superseded by AI.

96
00:09:21,680 --> 00:09:27,760
And that, I can do a lot more with a lot deeper technical functionality and technical ability.

97
00:09:27,760 --> 00:09:30,560
And I low code just slows me down.

98
00:09:30,560 --> 00:09:35,360
A UX, that's, or UI, sorry, that's in the way slows me down.

99
00:09:35,360 --> 00:09:38,320
I'd much rather be at a COI level.

100
00:09:38,320 --> 00:09:43,480
I'd much rather be at a prompt level, MCP API level,

101
00:09:43,480 --> 00:09:51,320
to drive the results that I want, then spend hours wasted on configuration screens to try and make the software perform.

102
00:09:51,320 --> 00:09:53,280
How I wanted to perform.

103
00:09:53,280 --> 00:09:55,360
Yeah.

104
00:09:55,360 --> 00:10:03,400
What was, how you, one was the moment you realized I would fundamentally change software development.

105
00:10:03,400 --> 00:10:09,280
I mean, the day,

106
00:10:09,280 --> 00:10:14,160
ChatGBT became a thing in November 2022,

107
00:10:14,160 --> 00:10:16,520
I got it that day, right?

108
00:10:16,520 --> 00:10:25,640
I list on Reddit, I'm on X, I never left X from the Twitter days when a lot of people did.

109
00:10:25,640 --> 00:10:28,320
And so I heard about it and I was on it that day.

110
00:10:28,320 --> 00:10:30,960
And I called my wife over and said, well, check this out.

111
00:10:30,960 --> 00:10:32,000
What I was able to do.

112
00:10:32,000 --> 00:10:41,600
Now, at that point, Microsoft had already done the deal about two years earlier with OpenAI to acquire the IP.

113
00:10:41,600 --> 00:10:52,200
And, you know, I can remember Charles Lamana talking about the initial versions of GPC and in regards to power effects and things like that.

114
00:10:52,200 --> 00:10:59,480
And I started really getting interested in AI, I suppose, around 2018 when I was in London.

115
00:10:59,480 --> 00:11:07,920
And particularly, you know, Google were doing some great things and I always saw that what Google was doing was academic AI.

116
00:11:07,920 --> 00:11:12,640
In other words, it was like awesome stuff, but like, how do I use it?

117
00:11:12,640 --> 00:11:13,240
Right?

118
00:11:13,240 --> 00:11:18,880
And what I saw from Microsoft at those early days, and this is back in, this is pre GPC.

119
00:11:18,880 --> 00:11:21,440
So this is back 2018, 2019.

120
00:11:21,440 --> 00:11:26,920
And so really much more around ML and cognitive services and things like that.

121
00:11:26,920 --> 00:11:32,160
Microsoft was starting to really what I call created practical AI.

122
00:11:32,160 --> 00:11:34,840
In fact, they might have even been calling it practical AI.

123
00:11:34,840 --> 00:11:38,600
Like AI that really could move the dial in your business.

124
00:11:38,600 --> 00:11:42,840
And so, you know, that's where I started getting excited about it.

125
00:11:42,840 --> 00:11:44,240
I started writing blog posts.

126
00:11:44,240 --> 00:11:50,560
In fact, I'm sure you can go on my blog and find posts on AI from 2018,

127
00:11:50,560 --> 00:11:56,400
where I was writing and exploring and I was interviewing people on my podcast that were in AI,

128
00:11:56,400 --> 00:12:00,080
particularly across Europe at the time, because I was in the UK.

129
00:12:00,080 --> 00:12:12,080
And then, but it was, I suppose, there was an MVP session, like an MVP summit that I was, it was in COVID.

130
00:12:12,080 --> 00:12:13,840
And so it was still locked down.

131
00:12:13,840 --> 00:12:20,760
We couldn't travel from memory, or they just at the last minute allowed travel into the US at the end of the COVID type run.

132
00:12:20,760 --> 00:12:29,600
And Charles Lamana got on stage and talked about, you know, co pilot inside of the power platform.

133
00:12:29,600 --> 00:12:35,000
And you have been your ability to just speak into creation.

134
00:12:35,000 --> 00:12:38,680
And while he was doing it, he said, and by the way, in your MVP tenant, it's their available one.

135
00:12:38,680 --> 00:12:50,040
So while he's presenting, I'm on my laptop and I built an app while he's talking to manage seeds.

136
00:12:50,040 --> 00:12:54,520
And, you know, I've got a big garden, I've got a centropic forest that I'm building.

137
00:12:54,520 --> 00:12:59,640
And so, and one of the things I want to do is like when's the optimal time to plant seeds, you know,

138
00:12:59,640 --> 00:13:05,120
if for any type of species that I was wanting to plant, what was the best conditions, etc.

139
00:13:05,120 --> 00:13:10,000
And I was able to prompt that app into reality while he was doing the presentation.

140
00:13:10,000 --> 00:13:16,040
And for me, it was like, I could see the future and, you know, where it was going to go.

141
00:13:16,040 --> 00:13:25,880
And so I haven't been a Dynamics 365 or Power Platform MVP for two, three years now.

142
00:13:25,880 --> 00:13:27,000
So I pivoted it.

143
00:13:27,000 --> 00:13:33,320
I pivoted first into the next category I went into was AI platforms at Microsoft.

144
00:13:33,320 --> 00:13:37,320
And then in the last renewal cycle, I've actually gone into co pilot.

145
00:13:37,320 --> 00:13:42,880
And that's because, you know, writing the book, as you said, on co pilot adoption with my wife,

146
00:13:42,880 --> 00:13:50,960
has taken that pivoting journey and they switched AI platform MVP just to Foundry MVP.

147
00:13:50,960 --> 00:13:57,360
And, you know, bless Microsoft, but they get so enamored with their own product names

148
00:13:57,360 --> 00:14:00,000
that they forget that it means nothing in the market.

149
00:14:00,000 --> 00:14:05,720
And so, you know, I wasn't too much of a fan of being a Foundry MVP

150
00:14:05,720 --> 00:14:08,840
because you had to explain it to everybody what it meant.

151
00:14:08,840 --> 00:14:15,800
And I'm happy to go to co pilot because at least I think it has a higher profile, but also in more recent times,

152
00:14:15,800 --> 00:14:20,760
you know, I have got heavily into AI outside of Microsoft.

153
00:14:20,760 --> 00:14:27,520
And because I fundamentally feel Microsoft has lost its way in the last three years in the AI space as a whole.

154
00:14:27,520 --> 00:14:34,080
It went from a absolute, you know, when if you look at November, going into the new year,

155
00:14:34,080 --> 00:14:40,240
calendar, new year in 2023, I think there was a graphic that came out at that time showing Microsoft

156
00:14:40,240 --> 00:14:51,360
that a 64% market share in AI because of its relationship to open AI and the assets that it already had in Azure.

157
00:14:51,360 --> 00:15:02,920
And unfortunately, my observation, Microsoft was always good at chasing the market leader.

158
00:15:02,920 --> 00:15:10,520
They've never, ever, ever in my estimation, and I'm happy to be proved wrong, although it's irrelevant,

159
00:15:10,520 --> 00:15:15,960
not good at playing lead and owning and demanding a space.

160
00:15:15,960 --> 00:15:18,120
And I give you like three or four examples.

161
00:15:18,120 --> 00:15:19,480
There was no Valnetware.

162
00:15:19,480 --> 00:15:23,520
Then, he four came out and Microsoft dominated and ultimately took over that space.

163
00:15:23,520 --> 00:15:26,680
There was Lotus 123, right?

164
00:15:26,680 --> 00:15:30,920
Spreadsheets ex-out dominated that space took the market share.

165
00:15:30,920 --> 00:15:34,320
Word perfect, word, even let's go into gaming, right?

166
00:15:34,320 --> 00:15:39,480
There was PlayStation from Sony and then Microsoft jumped in with Xbox.

167
00:15:39,480 --> 00:15:42,160
So they're good at chasing a category.

168
00:15:42,160 --> 00:15:44,640
They don't seem to be good at leading a category.

169
00:15:44,640 --> 00:15:50,840
And what I feel that's happened in the last three years, their sales org, their marketing org,

170
00:15:50,840 --> 00:15:58,120
and even their R&D or product teams just went after the wrong goals.

171
00:15:58,120 --> 00:16:00,120
They didn't have clarity.

172
00:16:00,120 --> 00:16:04,760
They just thought if we chuck the name Copilot on everything and force it down people's

173
00:16:04,760 --> 00:16:07,000
throats that people had adopt.

174
00:16:07,000 --> 00:16:11,880
And of course at the start of this year, the data came out in the earnings report.

175
00:16:11,880 --> 00:16:19,960
That something like 3.4% adoption of Copilot globally, which is, if you're a startup,

176
00:16:19,960 --> 00:16:23,320
that is a multi-billion dollar business, about a $4 billion business.

177
00:16:23,320 --> 00:16:24,320
Nice.

178
00:16:24,320 --> 00:16:26,760
But you're the biggest company in the world at the time.

179
00:16:26,760 --> 00:16:28,120
That's not good enough.

180
00:16:28,120 --> 00:16:32,280
That's not how the game is played when you're the biggest company in town.

181
00:16:32,280 --> 00:16:34,840
And so I feel that they've lost their way.

182
00:16:34,840 --> 00:16:39,560
Now one thing I'll credit Microsoft, they tend to play a long game, right?

183
00:16:39,560 --> 00:16:43,760
And so they will iterate and iterate and probably ultimately get this right.

184
00:16:43,760 --> 00:16:47,280
But right now, they aren't.

185
00:16:47,280 --> 00:16:52,040
They're playing catch-up, they're playing follow me, and Throppaker releases co-work.

186
00:16:52,040 --> 00:16:56,720
Oh, now Microsoft's under deal with them because hey, this is the latest shiny thing.

187
00:16:56,720 --> 00:17:01,040
OpenClaw becomes a big deal then we've got Scout.

188
00:17:01,040 --> 00:17:08,080
And I'm just like, you know, and then they've released three or four models, the Maya models,

189
00:17:08,080 --> 00:17:14,000
and on the announcement that built, they're nowhere near on par with what's in market even now.

190
00:17:14,000 --> 00:17:17,320
They're like, all five, like the open models are ahead of them.

191
00:17:17,320 --> 00:17:19,400
And I know that that's the start.

192
00:17:19,400 --> 00:17:23,280
And they will probably win long term with this strategy.

193
00:17:23,280 --> 00:17:30,240
But I didn't want to be held up with only drinking Microsoft's cool aid for this AI era.

194
00:17:30,240 --> 00:17:32,640
So I have gone deep into a topic.

195
00:17:32,640 --> 00:17:35,160
I've gone deep into open AI.

196
00:17:35,160 --> 00:17:37,440
I've gone deep into open claw.

197
00:17:37,440 --> 00:17:40,760
I have nine different APIs into other models.

198
00:17:40,760 --> 00:17:42,920
So like I use Chinese models.

199
00:17:42,920 --> 00:17:44,920
I use European models.

200
00:17:44,920 --> 00:17:53,240
I don't want to be restricted to only one flavor or only one dish on the menu.

201
00:17:53,240 --> 00:17:57,720
Yeah, I think that's really interesting.

202
00:17:57,720 --> 00:18:06,400
I think also the start of co-pilot was really, really bad that start because it's, don't

203
00:18:06,400 --> 00:18:07,400
feel like an AI.

204
00:18:07,400 --> 00:18:09,160
It feels like clippy is back.

205
00:18:09,160 --> 00:18:10,160
It's only says you're okay.

206
00:18:10,160 --> 00:18:15,480
Yeah, I mean, I look at how much it got mocked and, and for that, that, that exact type of

207
00:18:15,480 --> 00:18:16,480
thing.

208
00:18:16,480 --> 00:18:20,040
And I think what they did is they didn't use the latest models from day one.

209
00:18:20,040 --> 00:18:25,800
They always used behind and so people were getting this AI experience and market with the

210
00:18:25,800 --> 00:18:28,360
consumer type apps.

211
00:18:28,360 --> 00:18:32,640
And Microsoft just sucked them comparison and their only kind of story was, hey, it's on

212
00:18:32,640 --> 00:18:33,960
your data.

213
00:18:33,960 --> 00:18:37,760
But nobody was experiencing the value of it being on your data.

214
00:18:37,760 --> 00:18:43,760
And another thing is companies data estates are so bad and full of so much human error,

215
00:18:43,760 --> 00:18:46,640
duplicated thousands of times.

216
00:18:46,640 --> 00:18:51,640
And what happened is that the results weren't great even if it's on your own data because

217
00:18:51,640 --> 00:18:57,080
you know accounting and set that spreadsheet out for the last five years every week and

218
00:18:57,080 --> 00:19:03,320
there's like 500 or 1000 copies of that spreadsheet all with the same formula error, all with

219
00:19:03,320 --> 00:19:05,880
the same formatting error or whatever other error.

220
00:19:05,880 --> 00:19:09,560
And then you go, AI, look at this and give me the correct answer and it goes, well, your

221
00:19:09,560 --> 00:19:12,240
pattern is fully human error.

222
00:19:12,240 --> 00:19:16,000
And so I'm just going to copy it and then everyone gets upset about hallucination and

223
00:19:16,000 --> 00:19:18,000
AI's sucks and stuff.

224
00:19:18,000 --> 00:19:20,800
And I'm like, it's just train on bad human data.

225
00:19:20,800 --> 00:19:25,400
Yeah, yeah, I think that's a real big topic.

226
00:19:25,400 --> 00:19:28,000
But have you also tried the Microsoft models?

227
00:19:28,000 --> 00:19:32,200
I think it's P4 and MIRR.

228
00:19:32,200 --> 00:19:37,040
So it's MIRR is as I'm building a product at the moment as an ISV that I am only using

229
00:19:37,040 --> 00:19:44,440
the MIRR models because I want it to be economical for the people that buy this product.

230
00:19:44,440 --> 00:19:51,840
And I wanted to 100% sit in Microsoft's ecosystem, in other words, on their infrastructure

231
00:19:51,840 --> 00:19:56,600
with no inference being handled off to our third party AI model.

232
00:19:56,600 --> 00:19:58,200
And the reason is trust.

233
00:19:58,200 --> 00:20:03,160
Microsoft has created a good trust profile with their customers.

234
00:20:03,160 --> 00:20:10,920
And you know, right now, if you're using co-pilot and you're using opus 5, for example, you

235
00:20:10,920 --> 00:20:17,400
know, if you go, you know, move away from the auto selector and choose your model and co-pilot,

236
00:20:17,400 --> 00:20:22,120
the compute or what's happening there is not even being done on Azure infrastructure.

237
00:20:22,120 --> 00:20:24,800
It's been handed off to AWS infrastructure.

238
00:20:24,800 --> 00:20:29,840
It's been computed outside Microsoft's ecosystem and been handed in, same for co-work.

239
00:20:29,840 --> 00:20:32,480
It's not been computed on Microsoft's infrastructure.

240
00:20:32,480 --> 00:20:38,960
And so for a lot of regulated industries, that's a problem.

241
00:20:38,960 --> 00:20:40,520
Data software, that's a problem.

242
00:20:40,520 --> 00:20:42,880
You know, it's not operating in my local data center.

243
00:20:42,880 --> 00:20:46,600
And even, you know, I'm in a little country called New Zealand.

244
00:20:46,600 --> 00:20:52,120
We have got no AI infrastructure by the hyperscalers in country save.

245
00:20:52,120 --> 00:20:58,160
AWS about three months ago put a bit of infrastructure in.

246
00:20:58,160 --> 00:21:02,640
So they're really the first move, even though Microsoft has its own data center in country.

247
00:21:02,640 --> 00:21:05,200
There's just not enough silicon to go around.

248
00:21:05,200 --> 00:21:09,360
And, you know, New Zealand, five million people total.

249
00:21:09,360 --> 00:21:11,920
We've got more sheep than we have people.

250
00:21:11,920 --> 00:21:15,840
It's not like a prime market where they're going to make a lot of money on AI.

251
00:21:15,840 --> 00:21:18,160
So I can see why it's not here.

252
00:21:18,160 --> 00:21:22,880
But it changes the profile in a regulated industry where let's say the government says,

253
00:21:22,880 --> 00:21:26,880
you're not allowed to send financial data outside the borders of the country.

254
00:21:26,880 --> 00:21:29,000
That creates a problem for people.

255
00:21:29,000 --> 00:21:31,960
And, you know, in the financial or regulated industry.

256
00:21:31,960 --> 00:21:38,360
So therefore, even co-pilot, you know, can be difficult unless they, you know,

257
00:21:38,360 --> 00:21:41,400
talk down and say, we don't want to throw up in the mix.

258
00:21:41,400 --> 00:21:46,840
Let's make it just GVT that's running on Azure and having that control.

259
00:21:46,840 --> 00:21:48,360
Yeah, I know it.

260
00:21:48,360 --> 00:21:49,600
I live in New Europe.

261
00:21:49,600 --> 00:21:51,640
We love Rayleigh.

262
00:21:51,640 --> 00:21:52,640
Yeah, what?

263
00:21:52,640 --> 00:21:57,480
I mean, just at the first month, New Rules kicked in in the EU AI Act, right?

264
00:21:57,480 --> 00:22:00,640
Now, new penalties just kicked in to play on the first of this month.

265
00:22:00,640 --> 00:22:05,920
So you know, yeah, it's a, it's a really, really hard topic here.

266
00:22:05,920 --> 00:22:13,360
What, what, what, I think you have the, this road, AI software factories.

267
00:22:13,360 --> 00:22:16,160
What, what does this mean?

268
00:22:16,160 --> 00:22:20,880
Yeah, so an AI software factory, you know, over my career, I've had, you know,

269
00:22:20,880 --> 00:22:26,120
teams of developers work for me on software projects.

270
00:22:26,120 --> 00:22:32,000
So I've had my architects, I've had developers, I've had my QA testing teams,

271
00:22:32,000 --> 00:22:36,120
and my project managers that, you know, have run the team.

272
00:22:36,120 --> 00:22:40,520
And I've always loved the concept of DevOps, although I've really struggled to ever

273
00:22:40,520 --> 00:22:44,400
see it fully implemented in the organizations I have been in.

274
00:22:44,400 --> 00:22:47,400
And that's partly because I've always worked for partners and you really don't run

275
00:22:47,400 --> 00:22:49,680
a DevOps for another customer.

276
00:22:49,680 --> 00:22:54,680
The whole idea is it's an in-house operational thing between the developer side of

277
00:22:54,680 --> 00:22:58,760
the organizational engineering and your business.

278
00:22:58,760 --> 00:23:04,520
So what I did is I sat down and I said, could I construct a, in my case, it's now a

279
00:23:04,520 --> 00:23:12,520
nine agent team that each one falls a role in the DevOps, Infinity Loop.

280
00:23:12,520 --> 00:23:16,760
And they are gated, they can't do any work outside their role.

281
00:23:16,760 --> 00:23:21,560
So, you know, I have, uh, ARC, and the ARC is my architect.

282
00:23:21,560 --> 00:23:26,160
I've scouted, my scout is my, um, takes requirements.

283
00:23:26,160 --> 00:23:31,760
And so it has a formalized requirements gathering process that it goes through with me.

284
00:23:31,760 --> 00:23:37,280
Hands-it-arc, ARC, you know, has to go out is very deterministic and very many elements

285
00:23:37,280 --> 00:23:42,480
I put into is about how they research, then I'm allowed to just start roofing on something

286
00:23:42,480 --> 00:23:45,480
without showing that they have researched it.

287
00:23:45,480 --> 00:23:50,080
And so one of the kind of, um, parts of the scaffold I have in place is I require them

288
00:23:50,080 --> 00:23:55,440
to always look at today's date and then they have to research the latest finding in

289
00:23:55,440 --> 00:23:57,440
whatever I'm doing.

290
00:23:57,440 --> 00:24:01,800
And so I don't want historic, oh, three years ago, this is how it was done.

291
00:24:01,800 --> 00:24:03,320
And that's why I'm architect me this way.

292
00:24:03,320 --> 00:24:04,480
Hell no, right?

293
00:24:04,480 --> 00:24:08,520
It's got to be how would we do it if we were starting today from scratch?

294
00:24:08,520 --> 00:24:09,720
How would the architecture look?

295
00:24:09,720 --> 00:24:14,160
And then, you know, it goes through, I've got Cody, does the actual code development.

296
00:24:14,160 --> 00:24:18,400
Now, I've got different models that are doing different that, that,

297
00:24:18,400 --> 00:24:20,400
a power these different agents.

298
00:24:20,400 --> 00:24:25,840
I have Tara, Tara is my, um, engineering manager.

299
00:24:25,840 --> 00:24:28,160
She's the orchestrator across all of them.

300
00:24:28,160 --> 00:24:33,600
She makes sure they hand off, um, I've built in Ralph, what's called Ralph loops, which is

301
00:24:33,600 --> 00:24:39,200
make sure that they keep, they keep going to they solve because agents often will go

302
00:24:39,200 --> 00:24:45,880
or that they will stop and ask just a benign question, but that stops them.

303
00:24:45,880 --> 00:24:50,240
I want to get up in the morning and a piece of software that I've specced is built.

304
00:24:50,240 --> 00:24:52,440
And it's now ready for me to get demoed.

305
00:24:52,440 --> 00:24:54,040
It's gone through its test cycle.

306
00:24:54,040 --> 00:24:58,040
Um, I have a security, a role that is security.

307
00:24:58,040 --> 00:25:04,320
It uses, um, um, um, Microsoft's red teaming resources as part of that.

308
00:25:04,320 --> 00:25:08,000
It does a red teaming process on my release cycle.

309
00:25:08,000 --> 00:25:10,240
It goes to Rex, my release manager.

310
00:25:10,240 --> 00:25:14,160
It goes to Wiki that does all the documentation for it.

311
00:25:14,160 --> 00:25:16,200
So it's this continuous loop.

312
00:25:16,200 --> 00:25:21,360
And then recently I built a maintenance system in that it's always checking the security

313
00:25:21,360 --> 00:25:22,960
posture of my environment.

314
00:25:22,960 --> 00:25:29,000
Or by the way, all this runs on Azure, I run the entire thing on the, um, and, um, and, um,

315
00:25:29,000 --> 00:25:33,800
I've got a lot of Azure resources coming into the mix now, you know, of, uh, started to

316
00:25:33,800 --> 00:25:35,440
have to add in blob storage.

317
00:25:35,440 --> 00:25:40,880
I've had to start adding in, you know, you've quickly find API key management becomes

318
00:25:40,880 --> 00:25:41,880
unwieldy.

319
00:25:41,880 --> 00:25:45,280
I think I'm over 300 API keys now.

320
00:25:45,280 --> 00:25:48,920
You don't want to be managing those, um, manually.

321
00:25:48,920 --> 00:25:51,600
And you never want them into being in plain text format, right?

322
00:25:51,600 --> 00:25:54,880
Because it's a security, um, vulnerability.

323
00:25:54,880 --> 00:25:59,200
And then what would often happen if they weren't encrypted, you would get an AI model

324
00:25:59,200 --> 00:26:03,120
that would output a key to screen and go, oops, oops, we need to rotate the keys because

325
00:26:03,120 --> 00:26:05,200
I fucked up type thing.

326
00:26:05,200 --> 00:26:10,480
And then I'd be like, well, how do I stop the AI making these stupid mistakes?

327
00:26:10,480 --> 00:26:14,800
And so, you know, um, they use things like key vault.

328
00:26:14,800 --> 00:26:17,360
You don't crypt, you, you, you abstract the way.

329
00:26:17,360 --> 00:26:18,480
And this is all the learning.

330
00:26:18,480 --> 00:26:25,560
So, but now I've got to kind of, I, I use, um, uh, uh, DevOps to, sorry, I don't use DevOps.

331
00:26:25,560 --> 00:26:28,800
I use, um, GitHub to run all my repos.

332
00:26:28,800 --> 00:26:33,080
The agents have, um, app, what's called app level access to those.

333
00:26:33,080 --> 00:26:37,600
So I can see the identity of who's doing what, um, across those.

334
00:26:37,600 --> 00:26:42,480
I have, I use the project management board, um, inside the company profile.

335
00:26:42,480 --> 00:26:45,200
So it spans all my repos.

336
00:26:45,200 --> 00:26:48,040
And, um, so I can get a real time dashboard.

337
00:26:48,040 --> 00:26:49,960
What cards, what tickets been worked on?

338
00:26:49,960 --> 00:26:53,840
Are they, you know, at what stage of that DevOps cycle are they in?

339
00:26:53,840 --> 00:26:59,480
Are built multiple dashboards that, you know, are built full routing tool for all my, um,

340
00:26:59,480 --> 00:27:01,440
all my, uh, AI models.

341
00:27:01,440 --> 00:27:05,800
And so it has a, a price comparison.

342
00:27:05,800 --> 00:27:08,840
At the moment, it's, it's, uh, it's selectable by agent.

343
00:27:08,840 --> 00:27:15,160
My next bill I'm going to make is I'm going to make it, um, route based on task.

344
00:27:15,160 --> 00:27:20,000
So in other words, it's going to choose the API or the LLM that it's going to use based

345
00:27:20,000 --> 00:27:22,000
on the task that it's actually doing.

346
00:27:22,000 --> 00:27:26,080
And so this is all around cost optimization, um, of the models.

347
00:27:26,080 --> 00:27:30,280
And so now I'm starting to build, and the crazy thing is the first bit of software I built

348
00:27:30,280 --> 00:27:31,640
was back in January.

349
00:27:31,640 --> 00:27:38,560
And it was because my kids' local skill wanted to run a fishing competition as a fundraiser.

350
00:27:38,560 --> 00:27:42,960
And someone told them that I knew something about AI and my girl had only just started five

351
00:27:42,960 --> 00:27:44,400
years old, started at school.

352
00:27:44,400 --> 00:27:49,040
And so they said, yeah, here's the, the paper that we used to run this competition.

353
00:27:49,040 --> 00:27:52,240
It's been running for 25 years as fishing comp.

354
00:27:52,240 --> 00:27:58,960
And I used AI to build out a full, uh, dashboard for at the event, somebody displayed on

355
00:27:58,960 --> 00:27:59,960
screens.

356
00:27:59,960 --> 00:28:03,960
I did apps that people out in their boats when they're fishing could measure and weigh

357
00:28:03,960 --> 00:28:06,920
and photograph their fish for a catch and release.

358
00:28:06,920 --> 00:28:15,080
I built this whole thing myself and it kind of stunned what I could do, you know, and, um,

359
00:28:15,080 --> 00:28:20,760
all that kind of my whole IT career, I've gone from being the lead of teams and stuff to

360
00:28:20,760 --> 00:28:23,040
not to be able to build myself.

361
00:28:23,040 --> 00:28:24,840
Have an idea, I'm always an ideas person.

362
00:28:24,840 --> 00:28:29,680
So I'm now able to quickly take an idea, iterate it into a production based app.

363
00:28:29,680 --> 00:28:39,120
And so the, the, um, the software factory is, you know, um, at the end of the day, uh, a DevOps

364
00:28:39,120 --> 00:28:48,080
team with Ralflux loops and, um, and very segregated role functions to make sure, you know,

365
00:28:48,080 --> 00:28:51,720
I was one of the, even the commands that said, you can never mark your own homework.

366
00:28:51,720 --> 00:28:54,360
A developer can never say, my shit's awesome, right?

367
00:28:54,360 --> 00:28:57,240
It has to be verified by my case, Vera.

368
00:28:57,240 --> 00:29:03,360
She's my verification and she's got a whole, uh, over 20 different release patterns that

369
00:29:03,360 --> 00:29:07,120
it must comply with before it will, the PR will go through.

370
00:29:07,120 --> 00:29:13,800
And so, um, yeah, I've, it's amazing what you can build once you start bringing, if you

371
00:29:13,800 --> 00:29:19,760
like, all your career experience together, knowing how software is developed and then

372
00:29:19,760 --> 00:29:22,920
being able to go, Hey, what have I made every single role in agent?

373
00:29:22,920 --> 00:29:24,200
What would that look like?

374
00:29:24,200 --> 00:29:25,680
And, um, it's been fun.

375
00:29:25,680 --> 00:29:28,680
It's built a lot of software in the last six months.

376
00:29:28,680 --> 00:29:29,680
Yeah.

377
00:29:29,680 --> 00:29:36,680
Uh, I also, uh, have done a lot of an AI factory, uh, Azure factory, uh, I don't know.

378
00:29:36,680 --> 00:29:39,280
They, they, they renamed it every time.

379
00:29:39,280 --> 00:29:43,240
Um, uh, and that's really amazing.

380
00:29:43,240 --> 00:29:51,120
I have built an, um, yeah, and a research tool, uh, with thousands of companies and all

381
00:29:51,120 --> 00:29:58,680
the employees and, uh, my idea was, uh, do a research for cyber security, uh, if all

382
00:29:58,680 --> 00:30:03,360
the best practices to the companies and they have started perfectly and then look, where,

383
00:30:03,360 --> 00:30:05,840
where did the cyber security risk come from?

384
00:30:05,840 --> 00:30:10,440
And I have checked, checked this and, yeah, you can ask every, every company and every, every

385
00:30:10,440 --> 00:30:17,000
user, uh, some questions and then it makes, uh, yeah, similar to a wall, yeah, and, uh,

386
00:30:17,000 --> 00:30:22,000
or enterprise, uh, will companies and that's really, really cool whether you can build, but,

387
00:30:22,000 --> 00:30:29,400
um, how autonomous, actually agents from, from your perspective.

388
00:30:29,400 --> 00:30:30,400
Sorry.

389
00:30:30,400 --> 00:30:31,400
Can you say that again?

390
00:30:31,400 --> 00:30:34,280
Autonomous, uh, um, or autonomous, autonomous.

391
00:30:34,280 --> 00:30:35,280
Yeah.

392
00:30:35,280 --> 00:30:38,640
Uh, how autonomous are the, these agents today from your perspective?

393
00:30:38,640 --> 00:30:46,960
So, so I, I have chat interfaces to about half my agents.

394
00:30:46,960 --> 00:30:50,400
So, so Tara, for example, is my interface.

395
00:30:50,400 --> 00:30:57,280
I have a direct chat interface to her and then she oversees the entire DevOps team.

396
00:30:57,280 --> 00:31:01,920
I don't have any direct interfaces with those individual DevOps teams.

397
00:31:01,920 --> 00:31:06,120
I can speak to any of them, but I speak through Tara to them.

398
00:31:06,120 --> 00:31:10,480
And so, because as I say, you know, there's, there's so much to learn.

399
00:31:10,480 --> 00:31:11,480
How do you handle memory?

400
00:31:11,480 --> 00:31:15,640
How do you make, you know, the difference between short term memory, um, medium term and

401
00:31:15,640 --> 00:31:20,040
long term memory, that's a whole thing you've got to sort out with your systems.

402
00:31:20,040 --> 00:31:22,200
That's why I spend a lot of time on the Wiki side.

403
00:31:22,200 --> 00:31:25,280
The Wiki is not for me to know what the documentation is.

404
00:31:25,280 --> 00:31:30,320
The Wiki is so that DevOps team can refer to and know what was built three months, five

405
00:31:30,320 --> 00:31:37,360
months, six months ago and build their, my system only became autonomous when I got Ralph

406
00:31:37,360 --> 00:31:43,600
Loops working correctly, um, which is this whole, I need to, you know, Ralph Loop is

407
00:31:43,600 --> 00:31:50,080
like forward slash goal, um, if you were in, in one of the other, one of the, um, frontier

408
00:31:50,080 --> 00:31:55,640
lab type products and the idea is you say, don't stop until you sort this out like to

409
00:31:55,640 --> 00:31:57,600
you have solved it.

410
00:31:57,600 --> 00:32:03,680
And so they will go and so I will go, I'll wake up in the morning and I will have over 50

411
00:32:03,680 --> 00:32:07,760
PR notifications from GitHub from through the night.

412
00:32:07,760 --> 00:32:09,280
They are working.

413
00:32:09,280 --> 00:32:12,120
They find a problem, verifies a problem in their code.

414
00:32:12,120 --> 00:32:14,760
They send it back and it goes through.

415
00:32:14,760 --> 00:32:20,240
Now I do have a jump out of loop if they just keep screwing up because I don't want to

416
00:32:20,240 --> 00:32:26,280
wedge my VM that I've got running everything and, you know, I've gone through that process

417
00:32:26,280 --> 00:32:29,880
where they get into a, uh, out of control loop.

418
00:32:29,880 --> 00:32:38,480
And so in that scenario outside of open claw, I created a, a entity called, uh, Ruru and

419
00:32:38,480 --> 00:32:41,360
Ruru in New Zealand is the name for Owl.

420
00:32:41,360 --> 00:32:46,800
So it's, it's the Maori name for Owl and what it does is it observes everything.

421
00:32:46,800 --> 00:32:52,480
It's observing my infrastructure, health, it's observing, um, all my API health and this

422
00:32:52,480 --> 00:32:56,120
is the API that I have built.

423
00:32:56,120 --> 00:33:02,040
And anytime it detects something, it sends me a notification around severity.

424
00:33:02,040 --> 00:33:07,400
So it's looking across 20 dimensions of my level one layer, level two is then looking

425
00:33:07,400 --> 00:33:11,680
for downtime, uh, can't reach for a certain period of time.

426
00:33:11,680 --> 00:33:16,080
And ultimately that goes up to a Zua notifications when Ruru dies.

427
00:33:16,080 --> 00:33:17,560
How do I know that Ruru's died?

428
00:33:17,560 --> 00:33:24,160
Well I use a Zua then through their notification system to say, hey, your CPU's gone through

429
00:33:24,160 --> 00:33:27,880
the roof, you run out of RAM or you run out of this space.

430
00:33:27,880 --> 00:33:33,120
And by the way, Ruru hasn't phoned home, you know, in a set frequency of time.

431
00:33:33,120 --> 00:33:34,840
So Ruru might be down.

432
00:33:34,840 --> 00:33:43,440
So Ruru is really about making sure I keep my system in top, um, you know, peak state at

433
00:33:43,440 --> 00:33:48,160
any time because the more code you build, right, the thing that bogs you down is maintenance

434
00:33:48,160 --> 00:33:50,080
then of that code.

435
00:33:50,080 --> 00:33:55,880
And so that's why Ruru and as part of that model, it sits outside or how I've designed

436
00:33:55,880 --> 00:34:02,560
it outside of open claw as an observer of open claw and of anything that could break.

437
00:34:02,560 --> 00:34:08,800
And so the minute it finds a break that it, it, it tries again and let's say it doesn't

438
00:34:08,800 --> 00:34:15,040
get the response or it, or it can repeat or prove the, um, the issue.

439
00:34:15,040 --> 00:34:19,160
It then raises a ticket straight away over on my DevOps board.

440
00:34:19,160 --> 00:34:24,680
Tara is then on her loop, which she's looking at the board every 15 minutes.

441
00:34:24,680 --> 00:34:27,080
She picks up the new ticket that's arrived.

442
00:34:27,080 --> 00:34:29,320
She then starts handing it through the DevOps cycle.

443
00:34:29,320 --> 00:34:33,680
So I can have an incident overnight, but when I get up in the morning, it's solved because

444
00:34:33,680 --> 00:34:39,800
it's been triaged through, um, and the outcomes been addressed and, um, built into the code.

445
00:34:39,800 --> 00:34:46,560
And so what could one of my drivers is, is around how do you create a, a self improving

446
00:34:46,560 --> 00:34:47,560
system?

447
00:34:47,560 --> 00:34:52,320
And this is a big thing with AI models at the moment, recursive self improvement.

448
00:34:52,320 --> 00:34:57,880
So I take that thinking and go, okay, how can I improve my DevOps team?

449
00:34:57,880 --> 00:35:02,080
What's the new learnings it's going to take from the last month and improve itself for the

450
00:35:02,080 --> 00:35:04,200
next month's worth of work?

451
00:35:04,200 --> 00:35:10,760
And so the DevOps team that I created five months ago is far superior now than it was then

452
00:35:10,760 --> 00:35:14,480
because it's actually always improving itself.

453
00:35:14,480 --> 00:35:18,920
And I've got this maintenance layer that is always scanning things like security, best

454
00:35:18,920 --> 00:35:21,520
in class security, best in class architecture.

455
00:35:21,520 --> 00:35:24,480
Um, I have all these different layers.

456
00:35:24,480 --> 00:35:32,760
And the minute it detects a maintenance issue or I'm using, you know, um, uh, a vulnerable

457
00:35:32,760 --> 00:35:36,880
piece of code or something like that, it then just raises a ticket straight away on the

458
00:35:36,880 --> 00:35:41,080
DevOps team and their job is to research and solve it.

459
00:35:41,080 --> 00:35:47,280
And so my, my system is super stable, super secure.

460
00:35:47,280 --> 00:35:52,280
And um, because I'm losing all the best in class security from Microsoft and I did that

461
00:35:52,280 --> 00:35:53,280
from day one.

462
00:35:53,280 --> 00:35:59,920
I originally built on Windows, um, first PM and I lasted three days until I went with a headless

463
00:35:59,920 --> 00:36:03,280
and put into environment and I tell you, I've never looked back.

464
00:36:03,280 --> 00:36:10,040
Um, it's just, yeah, I mean, I built full rag databases and all sorts for, for handling, um,

465
00:36:10,040 --> 00:36:11,040
cross agent.

466
00:36:11,040 --> 00:36:12,040
How do you get out?

467
00:36:12,040 --> 00:36:15,960
How do you tell agents that they know other agents are involved in your business?

468
00:36:15,960 --> 00:36:20,240
Like had to build a crew of a global address list that you would have in real life, but for

469
00:36:20,240 --> 00:36:21,240
agents.

470
00:36:21,240 --> 00:36:27,640
And I can know who else could help me to do something, um, built hundreds of skills.

471
00:36:27,640 --> 00:36:34,080
I don't like to take anybody else's, um, skills like if there's skill marketplaces and stuff.

472
00:36:34,080 --> 00:36:42,080
So what I typically do is I will point, um, my AIs at a, a, a repo where somebody's got

473
00:36:42,080 --> 00:36:47,880
a skill or, or some idea and I'll say research it, then go out and five, five competing products

474
00:36:47,880 --> 00:36:50,720
and research what their nuances.

475
00:36:50,720 --> 00:36:53,920
And now let's plan our skill and how we'll create it.

476
00:36:53,920 --> 00:37:00,280
So I don't have any dependencies on anybody else's, um, stuff to say politely.

477
00:37:00,280 --> 00:37:04,600
I don't want any risk like having an early days in the marketplace where you're getting

478
00:37:04,600 --> 00:37:09,840
some, you know, um, bad actors putting skills up to get, you know, access.

479
00:37:09,840 --> 00:37:13,480
I've never had those issues because I don't use anybody else's skills.

480
00:37:13,480 --> 00:37:18,440
I always, uh, research the concept of their skill, then build it myself.

481
00:37:18,440 --> 00:37:20,440
Awesome.

482
00:37:20,440 --> 00:37:26,440
So, so the soft, the system do is the requirement gathering, architecture, UX design, coding,

483
00:37:26,440 --> 00:37:29,760
testing, security reviews, documentation, and deployment.

484
00:37:29,760 --> 00:37:30,760
Yeah.

485
00:37:30,760 --> 00:37:37,240
So what's your, uh, my, my job is just keep feeding the new ideas.

486
00:37:37,240 --> 00:37:43,040
You know, for example, um, about a week ago, I started to build a full accounting system.

487
00:37:43,040 --> 00:37:48,400
Um, and, uh, but, you know, and like accounting software doesn't spin my, um,

488
00:37:48,400 --> 00:37:53,920
my wheels, but I need an account, I, you know, I've used their company for 15 years in my

489
00:37:53,920 --> 00:37:56,520
own business, um, called zero.

490
00:37:56,520 --> 00:38:00,840
Um, they're one in, they're New Zealand's most successful company on the global stage with

491
00:38:00,840 --> 00:38:01,840
its software.

492
00:38:01,840 --> 00:38:07,560
Build probably rocket labs is up there challenging them now, but each year the price goes up and

493
00:38:07,560 --> 00:38:09,560
accounting is accounting, right?

494
00:38:09,560 --> 00:38:12,760
The government doesn't change the rules around accounting all that often.

495
00:38:12,760 --> 00:38:16,840
If there's a change, it's just a new tax.

496
00:38:16,840 --> 00:38:21,840
But the price keeps going up for the SaaS service of kind of accounting has been done the same

497
00:38:21,840 --> 00:38:24,360
way in New Zealand for the last hundred years.

498
00:38:24,360 --> 00:38:28,120
It's probably going to be done the same way for the next period of time.

499
00:38:28,120 --> 00:38:32,080
And so I was just like, I'm sick of paying these SaaS fees.

500
00:38:32,080 --> 00:38:36,920
Why don't I build an accounting kernel that every type of business software, small business,

501
00:38:36,920 --> 00:38:37,920
not the enterprise.

502
00:38:37,920 --> 00:38:39,840
I'm not tackling that, that, that game.

503
00:38:39,840 --> 00:38:41,320
And I've opened source it.

504
00:38:41,320 --> 00:38:42,320
But I'm getting up open source.

505
00:38:42,320 --> 00:38:47,120
So I'm designed for New Zealand because I just want to give something back to the New Zealand

506
00:38:47,120 --> 00:38:50,960
market, but allow any business to point their AI at it.

507
00:38:50,960 --> 00:38:56,640
And it's, you know, from the core kernel of my, what I call the New Zealand ledger, it

508
00:38:56,640 --> 00:39:02,160
has full CLI access, full MCP access, full API access.

509
00:39:02,160 --> 00:39:06,760
But it's built with the idea that agents are probably going to be the main operator of

510
00:39:06,760 --> 00:39:09,320
this accounting system as well as humans.

511
00:39:09,320 --> 00:39:14,320
Where most software accounting software is designed for people and accountants.

512
00:39:14,320 --> 00:39:19,840
But by booting this core kernel, I can then allow any company to build their unique

513
00:39:19,840 --> 00:39:20,840
layer over the top.

514
00:39:20,840 --> 00:39:25,120
So if they're a project management business, they can build a project management module.

515
00:39:25,120 --> 00:39:30,080
If they've, you know, got warehousing, they can boot a warehousing module on top.

516
00:39:30,080 --> 00:39:35,520
But it's going to be AI first in how it's been engineered from the ground up.

517
00:39:35,520 --> 00:39:39,800
Yeah, that did.

518
00:39:39,800 --> 00:39:41,200
It's really cool.

519
00:39:41,200 --> 00:39:42,200
Awesome.

520
00:39:42,200 --> 00:39:44,440
Yeah, we also an expert in open claw.

521
00:39:44,440 --> 00:39:48,360
What problem do you solve, Zulford?

522
00:39:48,360 --> 00:39:55,640
So the big thing for me with open claw, right, is that open AI has been the main product I

523
00:39:55,640 --> 00:39:58,040
have been on since November, 2022.

524
00:39:58,040 --> 00:40:02,920
As soon as the $20 plan I was on it, as soon as the $200 plan I was on it.

525
00:40:02,920 --> 00:40:09,840
And then open AI started to make some really dick moves in the market, just fumbles back

526
00:40:09,840 --> 00:40:10,840
in 2025.

527
00:40:10,840 --> 00:40:13,760
And so I was like, okay, I'm going to go deep on on Thropic.

528
00:40:13,760 --> 00:40:19,240
So I went deep on on Thropic January this year, February.

529
00:40:19,240 --> 00:40:24,960
And then, and then, you know, and Thropic starts shooting itself in the foot, you know, they

530
00:40:24,960 --> 00:40:29,600
started screwing the model, right, because they ran out of compute.

531
00:40:29,600 --> 00:40:33,760
And so rather than tell the market what's going on, they start to throttle you back.

532
00:40:33,760 --> 00:40:37,280
And so all of a sudden, I'm looking at some code that it's producing.

533
00:40:37,280 --> 00:40:40,400
And I'm like, it's producing what looks like code.

534
00:40:40,400 --> 00:40:43,600
And then when you look at it, it's just, it's not there.

535
00:40:43,600 --> 00:40:44,600
It's saying it did it.

536
00:40:44,600 --> 00:40:46,320
And it's not there.

537
00:40:46,320 --> 00:40:52,520
And so what I loved about open claw is that I own the harness, right?

538
00:40:52,520 --> 00:40:57,040
I can plug, as I said, I've got nine different API connections, not even including open

539
00:40:57,040 --> 00:41:03,760
router. That's another connection I have that allows me to pull on Chinese models, European

540
00:41:03,760 --> 00:41:10,320
models in US models as as I see fit, but none of them own all my stuff, all my own stuff

541
00:41:10,320 --> 00:41:16,160
sits in Azure, all my own that whole DevOps team, I've changed the models behind various

542
00:41:16,160 --> 00:41:19,320
agents multiple times now, right?

543
00:41:19,320 --> 00:41:23,160
And the beauty is, I don't have to reinvent my system where I don't have to move the context

544
00:41:23,160 --> 00:41:27,640
out of one system and import it into another system because the context sits in my open

545
00:41:27,640 --> 00:41:29,160
claw environment.

546
00:41:29,160 --> 00:41:30,680
And that's the power of the system.

547
00:41:30,680 --> 00:41:35,360
I don't care what models I don't care, you know, whose model is ahead at the moment because

548
00:41:35,360 --> 00:41:39,480
I will always have the latest models and I will always be able to switch the minute

549
00:41:39,480 --> 00:41:43,720
now to work on what, but I don't have to set context every time.

550
00:41:43,720 --> 00:41:51,440
Context sits with me.

551
00:41:51,440 --> 00:41:59,520
I think I have to ask you that question.

552
00:41:59,520 --> 00:42:01,520
Adulity?

553
00:42:01,520 --> 00:42:02,520
Yeah.

554
00:42:02,520 --> 00:42:03,520
Okay.

555
00:42:03,520 --> 00:42:04,520
Okay.

556
00:42:04,520 --> 00:42:05,640
I can still hear you.

557
00:42:05,640 --> 00:42:13,000
You don't want to ask me about what I think about co-pilot studio.

558
00:42:13,000 --> 00:42:14,760
Here.

559
00:42:14,760 --> 00:42:16,640
It's not positive.

560
00:42:16,640 --> 00:42:24,920
I think co-pilot studio is an interim solution to try and gather up the low-code audience and

561
00:42:24,920 --> 00:42:31,780
give them something a bone, you know, because I remember the day the predecessor, what co-pilot

562
00:42:31,780 --> 00:42:36,280
studio is built on, was released and there's a blog post where I put a little chat bot

563
00:42:36,280 --> 00:42:45,680
on my site, you know, this would be back in 2020, I would say, or 2019, the end of 2019.

564
00:42:45,680 --> 00:42:50,240
And the thing is, once again, I don't want to low-code, agentic platform.

565
00:42:50,240 --> 00:42:56,680
I want an, I, I, I, I prompt, I want English as the engagement or language as the engagement

566
00:42:56,680 --> 00:42:57,680
layer.

567
00:42:57,680 --> 00:43:04,040
I don't want to know, did I plug in the right API at the right time and did I, you know,

568
00:43:04,040 --> 00:43:08,720
did I put the right, I just, I hate the product.

569
00:43:08,720 --> 00:43:09,720
I think it's shite.

570
00:43:09,720 --> 00:43:12,240
I think it's a product that doesn't need to exist.

571
00:43:12,240 --> 00:43:15,800
People, if they want to build stuff, just go straight to Foundry and build there.

572
00:43:15,800 --> 00:43:19,920
Nowadays, get your AI skills up that you can just work directly with Foundry.

573
00:43:19,920 --> 00:43:26,800
You don't need an interim solution with a, a stupid monetization model in my mind in

574
00:43:26,800 --> 00:43:27,800
place.

575
00:43:27,800 --> 00:43:33,000
It's Microsoft once again, fumbling to find relevance in the space with a solution.

576
00:43:33,000 --> 00:43:36,040
So you asked the question, sorry about the answer.

577
00:43:36,040 --> 00:43:38,040
No, no, no problem.

578
00:43:38,040 --> 00:43:39,960
So I'm a little bit more happy.

579
00:43:39,960 --> 00:43:44,640
I never have used co-pilot studio yet because I'm happy with AI Foundry.

580
00:43:44,640 --> 00:43:49,160
I never, I also never see the reason for, for, for, for this product.

581
00:43:49,160 --> 00:43:51,280
So, yeah.

582
00:43:51,280 --> 00:43:57,600
Um, I think one topic, especially when we talk about agents, it's, it's governance.

583
00:43:57,600 --> 00:44:03,000
How, how did you handle the, the governance stuff?

584
00:44:03,000 --> 00:44:04,640
So this is a cool thing.

585
00:44:04,640 --> 00:44:11,520
Microsoft have got really strong governance, um, uh, content available.

586
00:44:11,520 --> 00:44:17,640
And so you can take that governance content that they have available and plug it into

587
00:44:17,640 --> 00:44:18,640
your system.

588
00:44:18,640 --> 00:44:21,320
You can say to your AI, go read this, understand it.

589
00:44:21,320 --> 00:44:26,440
And I want to implement that exact type governance framework in, in what I am building.

590
00:44:26,440 --> 00:44:32,680
And so governance is slightly easier when you're only one person, right?

591
00:44:32,680 --> 00:44:33,840
That's governing everything.

592
00:44:33,840 --> 00:44:38,640
I put very strict gates around what has to have my eyeballs on it.

593
00:44:38,640 --> 00:44:46,080
Um, well, like I don't let, um, my open core environment, I built a, this, my only other

594
00:44:46,080 --> 00:44:59,240
open source product, I built a CLI into, um, into Microsoft graph from, um, open core.

595
00:44:59,240 --> 00:45:05,360
And I can access anything that's in the open, over the Microsoft graph, um, and that means

596
00:45:05,360 --> 00:45:12,240
that I can do from open core posts into teams, I can delete posts in teams, I can send messages

597
00:45:12,240 --> 00:45:17,440
to people inside organization and teams, I can read all my email, read all my calendar.

598
00:45:17,440 --> 00:45:23,520
Um, I've had that maybe for five months now, but I have never given it the skill to write

599
00:45:23,520 --> 00:45:24,720
an email.

600
00:45:24,720 --> 00:45:29,080
Um, I've never given it, so in other words, I've given it, uh, the ability to

601
00:45:29,080 --> 00:45:30,640
create appointments for me.

602
00:45:30,640 --> 00:45:35,600
So what I do is I have my agents, my agents actually can create appointments with me when it

603
00:45:35,600 --> 00:45:38,920
has to present a concept to me, uh, whatever agent it is.

604
00:45:38,920 --> 00:45:42,640
And so they go through, I have a main agent called Rook.

605
00:45:42,640 --> 00:45:47,400
So Rook is my, uh, personal, uh, like my PA agent.

606
00:45:47,400 --> 00:45:53,360
So not all my agents get access to my diary on my M365 calendar.

607
00:45:53,360 --> 00:45:54,360
Only Rook does.

608
00:45:54,360 --> 00:46:00,160
And so if somebody wants a time in my diary from my agent team, they have to broker that

609
00:46:00,160 --> 00:46:01,160
through Rook.

610
00:46:01,160 --> 00:46:06,880
And so Rook has a whole bunch of operational rules around how it can set messages for me,

611
00:46:06,880 --> 00:46:09,880
what times of the day I do and don't take appointments.

612
00:46:09,880 --> 00:46:16,040
Um, it will, I'll let it draft the email, but I don't let it draft the email inside of

613
00:46:16,040 --> 00:46:17,040
outlook.

614
00:46:17,040 --> 00:46:23,640
I have a draft is, uh, to a markdown file and then I copy and paste that markdown file

615
00:46:23,640 --> 00:46:26,400
into, uh, an email.

616
00:46:26,400 --> 00:46:29,680
And I'm, I'm the person that doesn't have a lot of email nowadays.

617
00:46:29,680 --> 00:46:35,160
I've got, you know, I've run for over 10 years on a zero inbox principle in my business

618
00:46:35,160 --> 00:46:36,160
career.

619
00:46:36,160 --> 00:46:40,720
Um, something to learn from a book called Getting Things Done Years ago.

620
00:46:40,720 --> 00:46:47,560
And so because I have my email so optimized, like I don't get spam, I don't get newsletter

621
00:46:47,560 --> 00:46:53,880
emails because I have a, uh, automations that automatically clean those out.

622
00:46:53,880 --> 00:46:59,880
They automatically put them into my, uh, folder called spam and then, um, I will then point

623
00:46:59,880 --> 00:47:03,440
the AI at that spam photo and is there any, I don't even go look at it.

624
00:47:03,440 --> 00:47:08,920
I say, is there anything I need to be, uh, you know, identifying here and I let it handle

625
00:47:08,920 --> 00:47:09,920
that.

626
00:47:09,920 --> 00:47:16,200
So I'm, I, I, I believe that within 18 months, I won't have email anymore.

627
00:47:16,200 --> 00:47:21,960
I won't have that need for email in the traditional sense that, sorry, let's change it.

628
00:47:21,960 --> 00:47:26,400
I will have email, I won't have outlook and I won't have replaced outlook with another

629
00:47:26,400 --> 00:47:28,200
mail program.

630
00:47:28,200 --> 00:47:34,720
An agent will make me aware of any, uh, email and an agent will, at that same agent will,

631
00:47:34,720 --> 00:47:39,760
you know, take a dictation from me, whatever and send under my approval.

632
00:47:39,760 --> 00:47:43,840
Um, I will find the eliminate outlook from my life.

633
00:47:43,840 --> 00:47:47,720
From me, eyeballing outlook.

634
00:47:47,720 --> 00:47:59,240
Um, what, what did you think about, um, I think that needs to invest heavily in AI and, uh,

635
00:47:59,240 --> 00:48:06,800
data centers and, um, I think there's something coming new that's, uh, and, uh, media, how

636
00:48:06,800 --> 00:48:09,440
development with Microsoft.

637
00:48:09,440 --> 00:48:16,160
So this, I think it makes 1000 terror flops and the new windows should be in a minimum,

638
00:48:16,160 --> 00:48:17,960
I think 20 or 40 terror flops.

639
00:48:17,960 --> 00:48:24,440
It's the, uh, environment for next window system.

640
00:48:24,440 --> 00:48:35,240
Did you think we, uh, in, in having AI on your, on our, our out sees, if you don't?

641
00:48:35,240 --> 00:48:43,120
Yeah, I, yeah, I'm convinced that AI is going to move, um, like it won't move away from

642
00:48:43,120 --> 00:48:44,120
the cloud, right?

643
00:48:44,120 --> 00:48:49,000
AI will be, you know, still will have optimization, the cloud, but what I do really believe,

644
00:48:49,000 --> 00:48:55,640
and I've run, um, models locally on my, I've got a, you know, a high spec, um, Nvidia card in

645
00:48:55,640 --> 00:48:57,160
my computer.

646
00:48:57,160 --> 00:49:04,600
Um, so I've run models locally and I think that we're going to run to a world very soon

647
00:49:04,600 --> 00:49:09,320
within the next 12 months where AI will run locally.

648
00:49:09,320 --> 00:49:13,840
That will be as good as what the current front end models are providing, but it will be local

649
00:49:13,840 --> 00:49:14,840
on device.

650
00:49:14,840 --> 00:49:21,880
And so I think compute on device and the ability to run on device as good as what the current,

651
00:49:21,880 --> 00:49:23,640
um, providers are right now.

652
00:49:23,640 --> 00:49:26,760
So I'm not going to say they're going to be as good as the day that you're running them

653
00:49:26,760 --> 00:49:31,760
locally as the model that we're running that day in the cloud, but I absolutely believe

654
00:49:31,760 --> 00:49:42,960
compute on the edge and AI at the edge will be our first class and will be a, um, will be

655
00:49:42,960 --> 00:49:44,120
in all sorts of devices.

656
00:49:44,120 --> 00:49:49,000
I believe, you know, my, my money is still even though they've fumbled the ball badly, is

657
00:49:49,000 --> 00:49:58,520
that Apple will nail AI at the edge on their devices and we will naturally see it on, um,

658
00:49:58,520 --> 00:50:01,920
you know, on the PC as well, AI on the edge in time.

659
00:50:01,920 --> 00:50:09,240
Um, and that will be a massive, uh, massive enabler, um, of what's possible.

660
00:50:09,240 --> 00:50:10,240
Yeah.

661
00:50:10,240 --> 00:50:16,600
Um, what, what did you think for, for the people that they starting now, like students, uh,

662
00:50:16,600 --> 00:50:17,600
or so?

663
00:50:17,600 --> 00:50:23,400
What, how would it, well, they prepare for the, for the AI first career?

664
00:50:23,400 --> 00:50:24,400
Okay.

665
00:50:24,400 --> 00:50:26,280
So they need to learn a couple of things.

666
00:50:26,280 --> 00:50:30,680
They need, and you know, prompt engineering has been around a long time, right?

667
00:50:30,680 --> 00:50:36,400
Prompt engineering is, if you're getting it now, you need to really set yourself up to

668
00:50:36,400 --> 00:50:40,040
get a good, a prompting, but you need to move beyond prompt engineering.

669
00:50:40,040 --> 00:50:44,000
You need to get into context engineering and you need to really understand what context

670
00:50:44,000 --> 00:50:45,240
engineering is about.

671
00:50:45,240 --> 00:50:49,040
And then you should probably take a third step and go into outcomes engineering, um, in

672
00:50:49,040 --> 00:50:50,040
understanding it.

673
00:50:50,040 --> 00:50:51,880
You need to understand first principles.

674
00:50:51,880 --> 00:50:53,800
You need to understand critical thinking.

675
00:50:53,800 --> 00:50:57,200
And when I say you need to understand it, you need to be trained on it.

676
00:50:57,200 --> 00:51:00,880
And you don't have to go to fancy provider, get AI to train you on these subjects.

677
00:51:00,880 --> 00:51:04,040
Get it to, um, do space, space training.

678
00:51:04,040 --> 00:51:09,240
So in other words, you learn the same thing repeated over time, making the distance larger

679
00:51:09,240 --> 00:51:15,640
each time so that it bakes it into your, your computer, um, up here.

680
00:51:15,640 --> 00:51:17,320
Um, so those are the first things.

681
00:51:17,320 --> 00:51:21,520
The next thing I'd say, learn about harnesses and you learn everything you can about

682
00:51:21,520 --> 00:51:25,360
harnesses and why harnesses are so, so important.

683
00:51:25,360 --> 00:51:31,760
Um, the third thing I'd say, um, don't get bended locked in the day of, you know, drinking

684
00:51:31,760 --> 00:51:38,120
just Microsoft, cool aid or just AWS, cool aid or, or, um, uh, Google Cloud Platform,

685
00:51:38,120 --> 00:51:42,600
GBC, that, that gone, use whatever tool, use all the tools.

686
00:51:42,600 --> 00:51:48,000
You know, if your, uh, got xenophobia and anti-China, sort that shit out.

687
00:51:48,000 --> 00:51:52,800
Like they are, they're gonna win this race.

688
00:51:52,800 --> 00:51:54,480
Just watch the writing on the wall.

689
00:51:54,480 --> 00:51:59,920
They're gonna win this race and the reason is they are getting better results on poor

690
00:51:59,920 --> 00:52:01,920
a silicon at the moment.

691
00:52:01,920 --> 00:52:05,360
Um, then they're, they're, well, they're getting, not better results.

692
00:52:05,360 --> 00:52:08,720
They're getting on par results where the people that have the best computer

693
00:52:08,720 --> 00:52:10,600
infrastructure in the best silicon in the world.

694
00:52:10,600 --> 00:52:15,400
So if they're doing that in inferior silicon, you wait to their fabs get up to speed

695
00:52:15,400 --> 00:52:21,960
and they're on par at the silicon layer, they're getting so much additional layers in their

696
00:52:21,960 --> 00:52:28,840
architecture right that I think just like they overtook the solar industry globally, just

697
00:52:28,840 --> 00:52:34,440
like they've overtaken the, the, the EV market with electric vehicles and every other thing

698
00:52:34,440 --> 00:52:39,400
in manufacturing, they are going to be the model providers of the future.

699
00:52:39,400 --> 00:52:45,000
So if you've got some, you know, thing racism or anything like that about them,

700
00:52:45,000 --> 00:52:48,280
and you, you want to get locked into that type of thinking?

701
00:52:48,280 --> 00:52:49,480
Good luck.

702
00:52:49,480 --> 00:52:55,640
Um, but yeah, I definitely won't be and I want to know what the Chinese models are doing.

703
00:52:55,640 --> 00:53:01,040
I want to know what the, the, um, models are doing that are, you know, predominantly now I

704
00:53:01,040 --> 00:53:05,240
think of France, um, coming out of Europe and I want to know what the American models are

705
00:53:05,240 --> 00:53:06,240
doing.

706
00:53:06,240 --> 00:53:09,840
Um, and I think honestly, we're gonna get to the point where there's gonna be a lot of

707
00:53:09,840 --> 00:53:16,640
models that are much more refined on specific datasets, um, rather than just one of these

708
00:53:16,640 --> 00:53:19,920
bigger ubiquitous models that we currently have.

709
00:53:19,920 --> 00:53:23,080
Just industry data in the world, but we don't use it really good.

710
00:53:23,080 --> 00:53:32,000
So I think we have, yeah, we are doing too many compliance stuff around it and so on.

711
00:53:32,000 --> 00:53:39,040
And yeah, we are, I don't know, it's feeling like, uh, we have invented the wheel and, and

712
00:53:39,040 --> 00:53:42,720
uh, the other built the cars, uh, actually.

713
00:53:42,720 --> 00:53:43,720
Yeah.

714
00:53:43,720 --> 00:53:44,720
Yeah.

715
00:53:44,720 --> 00:53:50,360
Uh, or what I also would ask you, you have renamed your podcast, uh, from the intelligent

716
00:53:50,360 --> 00:53:57,800
edge to, um, to the Microsoft innovation podcast that has the intelligent age, uh, stopped,

717
00:53:57,800 --> 00:54:02,520
uh, get me all stupid, uh, through all my, yeah.

718
00:54:02,520 --> 00:54:07,000
So the new podcast is called the intelligence age, the old one, the, the original podcast

719
00:54:07,000 --> 00:54:12,600
was the Microsoft business application podcast, um, and then it became the Microsoft

720
00:54:12,600 --> 00:54:19,840
innovation podcast and surprisingly, I've gone eight and a half years using Microsoft's

721
00:54:19,840 --> 00:54:22,680
name in a domain name.

722
00:54:22,680 --> 00:54:28,840
And on a podcast and never been pinged legally by Microsoft because if you look at that T's

723
00:54:28,840 --> 00:54:30,280
and C's, that's a no no.

724
00:54:30,280 --> 00:54:35,480
You don't get to use Microsoft's name, um, like that.

725
00:54:35,480 --> 00:54:43,000
And so it was actually, um, Claude that pointed it out to me, it said, well, one day, do you

726
00:54:43,000 --> 00:54:50,040
realize that you're in breach of Microsoft's legal thing by using their name like this?

727
00:54:50,040 --> 00:54:54,480
And I'm like, yeah, but I've never been pinged and it was just like, cause I was, so some

728
00:54:54,480 --> 00:55:00,640
of the things I do with AI is I look at, um, risk profiles, how do I do risk things in my

729
00:55:00,640 --> 00:55:07,080
life? I run a dashboard around what I call situational intelligence, which has nothing to do with

730
00:55:07,080 --> 00:55:13,680
the guy that just lost a shirt and with a situational intelligence company, um, like lost 42 billion

731
00:55:13,680 --> 00:55:14,680
dollars or something.

732
00:55:14,680 --> 00:55:16,080
This week, just passed.

733
00:55:16,080 --> 00:55:23,200
Um, but situational intelligence is a, uh, security, a kind of posture, which I learnt when

734
00:55:23,200 --> 00:55:26,800
I won this award with Microsoft years ago for crime, safety and justice.

735
00:55:26,800 --> 00:55:32,920
And it's ability to look at all factors going on in your environment and be aware of things

736
00:55:32,920 --> 00:55:37,760
that could become, um, high risk to you.

737
00:55:37,760 --> 00:55:42,400
And so I was working with the Australian federal government, um, at that time and we were

738
00:55:42,400 --> 00:55:48,400
looking at, for example, camera feed data is this person in the way they're loitering?

739
00:55:48,400 --> 00:55:50,800
Are they about to do something?

740
00:55:50,800 --> 00:55:55,360
We should track them from camera to camera just to be aware of what potentially is going

741
00:55:55,360 --> 00:55:59,400
on. But I go, okay, how do I do that in my own personal life?

742
00:55:59,400 --> 00:56:04,680
And so that's how this thing flagged that I was, I potentially could be legally pursued

743
00:56:04,680 --> 00:56:09,920
by Microsoft and so I was like, okay, let's back out using Microsoft's name, um, before I

744
00:56:09,920 --> 00:56:11,280
get asked to.

745
00:56:11,280 --> 00:56:17,520
And then the other thing is, is that I wanted to talk about more than Microsoft.

746
00:56:17,520 --> 00:56:22,880
I wanted to have more than Microsoft's voice on my podcast.

747
00:56:22,880 --> 00:56:28,680
And I wanted to, you know, for the last three or four years, I've released three or four shows

748
00:56:28,680 --> 00:56:29,680
a week.

749
00:56:29,680 --> 00:56:34,640
And so that was a phenomenal amount of recording logistics around scheduling, et cetera.

750
00:56:34,640 --> 00:56:38,880
Now when, and I haven't even started the new podcast, it doesn't start till about four

751
00:56:38,880 --> 00:56:39,880
weeks time.

752
00:56:39,880 --> 00:56:43,400
I've only done my first load of recordings this week ready to launch.

753
00:56:43,400 --> 00:56:47,600
Um, and I just recorded my first six episodes ready to go, but I'm only going to release

754
00:56:47,600 --> 00:56:48,600
one a week.

755
00:56:48,600 --> 00:56:55,720
So I have rather than mass producing podcasts, I am going down to, um, you know, slightly

756
00:56:55,720 --> 00:57:01,760
longer podcast, but really around things that deeply interest me.

757
00:57:01,760 --> 00:57:07,160
And if the world benefits from what deeply interests me, awesome, but I'm not like, you know,

758
00:57:07,160 --> 00:57:12,440
one of the things in a conversation I have with AI often is I don't want to be an influencer.

759
00:57:12,440 --> 00:57:14,840
I want to be a value creator.

760
00:57:14,840 --> 00:57:20,600
So everything that I do, podcasts, et cetera, is it creating value for other people?

761
00:57:20,600 --> 00:57:21,600
I will do it.

762
00:57:21,600 --> 00:57:25,800
I'm not trying to make, um, I'm not trying to influence others.

763
00:57:25,800 --> 00:57:28,040
I'm trying to create value for others.

764
00:57:28,040 --> 00:57:29,040
Yeah.

765
00:57:29,040 --> 00:57:31,080
And the, the, the value topic is it's good.

766
00:57:31,080 --> 00:57:32,080
Yeah.

767
00:57:32,080 --> 00:57:35,680
Uh, what value can we expect from the 90 days mentoring challenge?

768
00:57:35,680 --> 00:57:36,680
Yeah.

769
00:57:36,680 --> 00:57:40,800
So the 90 mentoring challenge, like I've had a lot of people go through it.

770
00:57:40,800 --> 00:57:43,840
Um, of the people that have been on it over 65 of them.

771
00:57:43,840 --> 00:57:47,680
And they've become Microsoft, MVP's that have gone through that program.

772
00:57:47,680 --> 00:57:52,200
Um, I was running it all year round and it just became a hard slog for me.

773
00:57:52,200 --> 00:57:55,320
So I've, I've run it once this year, January, February, March.

774
00:57:55,320 --> 00:57:56,520
Um, that's run.

775
00:57:56,520 --> 00:58:00,880
I will probably release the next one in January, February, March next year.

776
00:58:00,880 --> 00:58:03,080
I'll do it once a year.

777
00:58:03,080 --> 00:58:05,080
And I've got percolating.

778
00:58:05,080 --> 00:58:10,960
And I mean, that 90 mentoring challenge is designed explicitly for anybody with Dynamics 365

779
00:58:10,960 --> 00:58:15,480
or their careers in Dynamics 365 and the power platform.

780
00:58:15,480 --> 00:58:17,000
And, and it is full on.

781
00:58:17,000 --> 00:58:21,400
It's not an easy, um, a light process, right?

782
00:58:21,400 --> 00:58:26,800
It's 12 weeks where every week you have detailed lab assignments and things to do.

783
00:58:26,800 --> 00:58:30,160
It's like, you know, it's like drinking from a fire hose, that course.

784
00:58:30,160 --> 00:58:35,400
And it's been running since, I think 2018 is when I launched that and ran it every year

785
00:58:35,400 --> 00:58:39,880
apart from one year when I was working at IBM and I was running that 90 day mentoring challenge

786
00:58:39,880 --> 00:58:45,280
internally for IBM is around the world and I didn't want to, um, and do it out in the market.

787
00:58:45,280 --> 00:58:48,720
So I've got, you know, I keep getting people gone, the wait list for that.

788
00:58:48,720 --> 00:58:50,200
So that will carry on.

789
00:58:50,200 --> 00:58:53,480
Um, I just refreshed all the content recently.

790
00:58:53,480 --> 00:58:57,760
Um, in the, for this year, um, just because so much has changed.

791
00:58:57,760 --> 00:59:03,520
Um, maybe I will release a 90 day mentoring challenge.

792
00:59:03,520 --> 00:59:06,520
Maybe it's a lot of work for me to do.

793
00:59:06,520 --> 00:59:13,400
Um, you know, my basically rule of thumb for every hour that I present in that 90 mentoring

794
00:59:13,400 --> 00:59:18,600
challenge, I've spent over 12 hours getting to that one hour of output.

795
00:59:18,600 --> 00:59:28,880
And so I am considering doing, um, one specifically on AI, which will be targeted at tech people

796
00:59:28,880 --> 00:59:36,680
that really want to become super proficient in AI, uh, consulting.

797
00:59:36,680 --> 00:59:42,960
So, um, but I don't know, I'm not, I've gone, I'm fluctuating.

798
00:59:42,960 --> 00:59:47,480
I'm whether I release that right now, I'm building software that I'm going to release

799
00:59:47,480 --> 00:59:49,040
in the Microsoft marketplace.

800
00:59:49,040 --> 00:59:52,560
I see there's gaps that I, I feel I can fill.

801
00:59:52,560 --> 00:59:57,440
So I've really gone down the, you know, what software can I create that's world class?

802
00:59:57,440 --> 01:00:02,120
I'm working with Microsoft internal stakeholders at the moment on that, um, having what I'm

803
01:00:02,120 --> 01:00:05,960
building architecturally reviewed and, and, and peer reviewed and things like that.

804
01:00:05,960 --> 01:00:11,200
So that's probably my focus at the moment is, um, what software can I build?

805
01:00:11,200 --> 01:00:13,480
Yeah, that is awesome.

806
01:00:13,480 --> 01:00:16,480
I have a rapid firewall in every session.

807
01:00:16,480 --> 01:00:17,480
Awesome.

808
01:00:17,480 --> 01:00:20,760
So, um, let, let us start short, short answers.

809
01:00:20,760 --> 01:00:27,160
And so, if there anything you say, um, you will never be automated in the future.

810
01:00:27,160 --> 01:00:29,160
No.

811
01:00:29,160 --> 01:00:34,120
And, uh, what did you think is the biggest thing?

812
01:00:34,120 --> 01:00:36,000
Oh, hang on, hang on, I do, sorry, just switch.

813
01:00:36,000 --> 01:00:38,400
Spending time with my family and, and friends.

814
01:00:38,400 --> 01:00:40,440
I don't think that will be automated.

815
01:00:40,440 --> 01:00:42,440
Yeah, okay, good.

816
01:00:42,440 --> 01:00:45,680
Um, is there one Microsoft product?

817
01:00:45,680 --> 01:00:47,160
Everybody should learn now.

818
01:00:47,160 --> 01:00:52,440
Uh, I would say co-pilot, like, learn it properly.

819
01:00:52,440 --> 01:00:59,760
Like, don't stay on auto, learn about work IQ, the importance of it, learn how to be really

820
01:00:59,760 --> 01:01:04,040
proficient in it, make sure it knows your context super well.

821
01:01:04,040 --> 01:01:09,560
Um, I think, yeah, there's a lot of runway for people as an, if you're just in a, if you're

822
01:01:09,560 --> 01:01:14,640
in a role, that is an information worker role, not a tech role, you should absolutely

823
01:01:14,640 --> 01:01:20,280
learn that if you're in that, what would be classified in information worker type role.

824
01:01:20,280 --> 01:01:21,280
Um, and, yeah.

825
01:01:21,280 --> 01:01:22,280
Yeah.

826
01:01:22,280 --> 01:01:26,720
What, what did you think, um, it's about a large language models or specialized language

827
01:01:26,720 --> 01:01:27,720
models?

828
01:01:27,720 --> 01:01:28,720
Right now, LLM.

829
01:01:28,720 --> 01:01:29,720
Okay.

830
01:01:29,720 --> 01:01:35,720
Um, you know, um, small language models, it smells, they've, they've got, they will become

831
01:01:35,720 --> 01:01:39,560
more prominent, but right now, LLM is where it's at.

832
01:01:39,560 --> 01:01:43,120
What's the habit that makes you so successful?

833
01:01:43,120 --> 01:01:44,120
Curiosity.

834
01:01:44,120 --> 01:01:49,920
Um, is there an AI list you will bust?

835
01:01:49,920 --> 01:01:55,880
Uh, that AI will become a, uh, sky net.

836
01:01:55,880 --> 01:02:01,920
Um, coffee tea or energy thing, three new development.

837
01:02:01,920 --> 01:02:06,280
I have been a massive energy drinker, like massive.

838
01:02:06,280 --> 01:02:12,560
Um, we have an energy drink in New Zealand called V and I just, I love that stuff so much.

839
01:02:12,560 --> 01:02:16,640
Uh, um, but I always start like, I have my own burst of machine.

840
01:02:16,640 --> 01:02:20,520
I have proper coffee machine.

841
01:02:20,520 --> 01:02:23,480
I always probably drink two coffees in the morning before lunch.

842
01:02:23,480 --> 01:02:26,720
Um, but yeah, I, I, you know, I, I do it.

843
01:02:26,720 --> 01:02:32,080
I don't do energy now because of diet and, and, and health, but every now and again, I

844
01:02:32,080 --> 01:02:33,680
let myself have one.

845
01:02:33,680 --> 01:02:38,920
Uh, what is the best food everyone should try when they come to New Zealand?

846
01:02:38,920 --> 01:02:43,880
Oh, if you come to New Zealand, you've got to try what's called a honey, which is food

847
01:02:43,880 --> 01:02:47,000
that is cooked in the ground.

848
01:02:47,000 --> 01:02:48,000
Okay.

849
01:02:48,000 --> 01:02:49,000
Let's go.

850
01:02:49,000 --> 01:02:50,000
So it's interesting.

851
01:02:50,000 --> 01:02:56,800
And, um, uh, co-pilot or chat GPT.

852
01:02:56,800 --> 01:02:57,800
Depends.

853
01:02:57,800 --> 01:02:58,800
Yeah.

854
01:02:58,800 --> 01:03:06,280
So, um, thank you for, for, for, for staying here with me, uh, over there.

855
01:03:06,280 --> 01:03:09,400
So thank you so much for, for your time.

856
01:03:09,400 --> 01:03:18,840
Um, what will you say when people can, uh, yeah, um, or what is the key, key takeaway from

857
01:03:18,840 --> 01:03:24,720
you from this session for what the people should recognize?

858
01:03:24,720 --> 01:03:30,800
I always not going anywhere and you need to do everything you can to be the best person

859
01:03:30,800 --> 01:03:37,360
in your place or the most knowledgeable, the most proficient and, and, and really, knowledge

860
01:03:37,360 --> 01:03:39,800
does not replace skill.

861
01:03:39,800 --> 01:03:41,440
We have infinite knowledge.

862
01:03:41,440 --> 01:03:46,720
It's the people that can apply the knowledge that can say, I've done it rather than I know

863
01:03:46,720 --> 01:03:47,720
it.

864
01:03:47,720 --> 01:03:50,080
There's a big difference.

865
01:03:50,080 --> 01:03:55,640
And, um, yeah, but my last question is, you have so many guests on your podcast, uh, who

866
01:03:55,640 --> 01:04:01,440
should I invite to them to my podcast and what questions should I ask?

867
01:04:01,440 --> 01:04:07,000
Um, you should invite Charles Lamana.

868
01:04:07,000 --> 01:04:15,040
To your podcast and get him to based on everything he's seen behind the curtain, so to speak.

869
01:04:15,040 --> 01:04:22,280
Uh, where does he see the next, uh, 24 months to 36 months going in tech?

870
01:04:22,280 --> 01:04:24,040
Yeah, thank you.

871
01:04:24,040 --> 01:04:29,000
Uh, yeah, that was fantastic and, and really interesting conversation.

872
01:04:29,000 --> 01:04:34,280
So Mark, thank you so much for joining me here on the MC65FM podcast and, uh, sharing your

873
01:04:34,280 --> 01:04:40,440
experience across AI, adoption, Microsoft technologies, uh, OpenClaw and, yeah, software factories

874
01:04:40,440 --> 01:04:45,400
and, uh, also the old words about Microsoft co-pilot studio.

875
01:04:45,400 --> 01:04:52,440
And, yeah, I think we now understand what the intelligent age, uh, means and what's upcoming

876
01:04:52,440 --> 01:04:54,000
and, yeah, thank you.

877
01:04:54,000 --> 01:04:55,000
Thank you so much.

878
01:04:55,000 --> 01:05:01,200
It was, was really cool and I think, yeah, thanks for for listening and until next time,

879
01:05:01,200 --> 01:05:03,680
keep learning, keep building and stay curious.

880
01:05:03,680 --> 01:05:04,500
- Yeah.

881
01:05:04,500 --> 01:05:05,740
- Ta-jao.

882
01:05:05,740 --> 01:05:06,580
- Bye.

883
01:05:06,580 --> 01:05:14,580
[BLANK_AUDIO]

Mirko Peters Profile Photo

Founder of m365.fm, m365.show and m365con.net

Mirko Peters is a Microsoft 365 expert, content creator, and founder of m365.fm, a platform dedicated to sharing practical insights on modern workplace technologies. His work focuses on Microsoft 365 governance, security, collaboration, and real-world implementation strategies.

Through his podcast and written content, Mirko provides hands-on guidance for IT professionals, architects, and business leaders navigating the complexities of Microsoft 365. He is known for translating complex topics into clear, actionable advice, often highlighting common mistakes and overlooked risks in real-world environments.

With a strong emphasis on community contribution and knowledge sharing, Mirko is actively building a platform that connects experts, shares experiences, and helps organizations get the most out of their Microsoft 365 investments.

Mark Smith Profile Photo

Mark Smith, known online as nz365guy, hosts The Intelligence Age Podcast. A Microsoft MVP for 15 years and a long-time Microsoft Certified Trainer, he combines technical depth with business strategy, and he has spent his career helping organisations put technology to work.

Today his focus is practical AI: adoption that sticks, governance that holds, and the skills that matter next. Every week he talks with practitioners, leaders, and innovators about thriving in The Intelligence Age, drawing on more than 830 episodes since 2017 and deep roots in the Microsoft ecosystem, including Dynamics 365, the Power Platform, and Copilot. In 2025 he co-authored Microsoft 365 Copilot Adoption, a Microsoft Press book for leaders and consultants.

Mark created the 90 Day Mentoring Challenge to help people reach their full potential with technology. Running since 2018, it has impacted the lives of more than 1,300 people across more than 70 countries. He is the founder of Cloverbase Ltd in New Zealand.