uncleLukie/sparklabs-6-presentation
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update index.html

Browse source
This commit is contained in:
uncleLukie 2026-06-25 14:06:19 +10:00
parent 8ba679afe2
commit 88cc622b9b
1 changed files with 199 additions and 160 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

359
index.html
View file

@ -7,7 +7,7 @@
<title>The AI Advantage: Rethinking 'Build vs. Buy' in Government IT</title>
<!-- SEO and Meta tags -->
<meta name="description" content="A provocative and disruptive 30-minute presentation deck arguing for digital sovereignty and AI-powered custom build over vendor lock-in in government IT." />
<meta name="description" content="A professional presentation deck arguing for digital sovereignty and AI-powered custom build over vendor lock-in in Australian government IT." />
<!-- Google Fonts -->
<link rel="preconnect" href="https://fonts.googleapis.com">
@ -25,24 +25,24 @@
<h1 class="main-title">THE <span class="highlight-cyan">AI</span> ADVANTAGE</h1>
<p class="main-subtitle text-gradient-purple">Rethinking "Build vs. Buy" in Government IT</p>
<div class="divider"></div>
<p class="tagline">A Playbook for Digital Sovereignty in the Generative Era</p>
<p class="tagline">Digital Sovereignty in the Generative Era</p>
<div class="audience-badge">2026 Government Digital Graduates</div>
</div>
<aside class="notes">
Good afternoon, graduates. Today, we're going to talk about a trillion-dollar problem. We're going to talk about how government IT became a hostage situation, and how you—armed with generative AI and open-source infrastructure—are going to stage the rescue mission. You're entering public service at the most disruptive moment in the history of technology. Let's make sure you aren't spending it managing vendor licenses.
Good afternoon, everyone. Thanks for coming to SparkLabs. I want to start by acknowledging the massive, glaring irony of this presentation. I am about to give a talk on why government should reconsider its reliance on mega-vendors. And I am delivering it to you right now, over a Microsoft Teams call, while most of you are watching on Windows work laptops, probably taking notes in Microsoft OneNote. I think it's safe to say that we, as a government entity, are completely captured. Today, we are going to explore why Australian governments are so deeply tethered to this model, how other nations are breaking free, why the vendor safety net is an illusion, and how you—as the next generation of digital leaders—can actually do something about it.
</aside>
</section>
<!-- Slide 2: The Status Quo -->
<!-- Slide 2: The Status Quo (VSA6) -->
<section id="slide-status-quo" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Mega-Vendor Tax</h2>
<h2 class="slide-header">The Australian Megavendor Tax</h2>
<div class="grid-2col">
<div class="card glassmorphic shadow-red animate-pulse-border">
<div class="card-badge bg-red">THE BUDGET HOLE</div>
<h3 class="card-title text-red">Proprietary Licensing</h3>
<p class="card-desc">Millions of dollars funneled annually to mega-vendors for generic office utilities and closed-source databases.</p>
<div class="card-badge bg-red">VSA6 AGREEMENT</div>
<h3 class="card-title text-red">Locked Until 2031</h3>
<p class="card-desc">The upcoming Volume Sourcing Agreement anchors government deeper into a single, restrictive vendor ecosystem.</p>
<!-- SVG Visualisation: Tax Drain -->
<svg viewBox="0 0 200 100" class="mini-chart" id="svg-tax-drain">
@ -51,67 +51,185 @@
<animate attributeName="stroke-dashoffset" values="50;0" dur="2s" repeatCount="indefinite" />
</path>
<circle cx="150" cy="50" r="25" fill="#ef4444" opacity="0.2" />
<text x="50" y="55" fill="#f3f4f6" font-size="12" font-family="Space Grotesk" text-anchor="middle">Public Funds</text>
<text x="50" y="55" fill="#f3f4f6" font-size="12" font-family="Space Grotesk" text-anchor="middle">Taxpayer</text>
<text x="150" y="55" fill="#ef4444" font-size="12" font-family="Space Grotesk" text-anchor="middle">Vendor</text>
</svg>
</div>
<div class="card glassmorphic shadow-cyan">
<div class="card-badge bg-cyan">THE STAT</div>
<div class="big-metric text-gradient-cyan">80%</div>
<p class="metric-label">of typical public IT budgets are locked into maintaining static legacy vendor software with zero active development.</p>
<div class="card-badge bg-cyan">THE BASELINE TRAP</div>
<div class="big-metric text-gradient-cyan">$1.6B</div>
<p class="metric-label">The 'discounts' secured in the 2019-2024 VSA5. Because true contract costs are scattered and opaque, the discount highlights the astronomical scale of the hidden bill.</p>
</div>
</div>
<aside class="notes">
Let's start with a hard truth. Government departments spend billions of dollars every single year on software licensing. You will enter departments where millions are spent just to license basic tools like case management databases. Historically, custom building was deemed too risky. So, we bought off-the-shelf software from mega-vendors. But we didn't just buy software; we bought vendor lock-in. We signed up for a subscription tax that drains public funds and leaves us dependent on foreign tech giants.
Let's talk about the bill. In July 2026—literally next month—the federal government's new Volume Sourcing Agreement, or VSA6, kicks in. This essentially locks the public sector into the Microsoft ecosystem until 2031. When the government signed the previous agreement, they proudly boasted about securing a 1.6 billion dollar discount. But because government IT spend is scattered across dozens of agencies, the true, total cost of that single contract is notoriously opaque. I want you to think about that math. If the discount alone is 1.6 billion dollars, imagine the astronomical size of the actual invoice. Across all vendors, federal IT spend topped 5.8 billion dollars last year. We aren't simply buying software anymore; we are paying a permanent rent on our own digital infrastructure. And when the landlord says they're going to up their rate by 20%, we are too captured to move—so we simply hand over our wallet.
</aside>
</section>
<!-- Slide 3: The Procurement Trap -->
<!-- Slide 3: The Risk Aversion Paradox (QLD Health Disaster) -->
<section id="slide-procurement" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Procurement Trap</h2>
<p class="slide-subtitle text-gradient-purple">The Cover-Your-Ass (CYA) Lifecycle</p>
<h2 class="slide-header">The Risk Aversion Paradox</h2>
<p class="slide-subtitle text-gradient-purple">The Illusion of Outsourcing Risk</p>
<!-- Visual: Waterfall CYA Steps -->
<!-- Visual: Waterfall Risk Steps -->
<div class="pipeline-container">
<div class="pipeline-step">
<div class="step-num">01</div>
<div class="step-label">CYA Planning</div>
<div class="step-duration">12 - 18 Months</div>
<p class="step-detail">Writing 300-page specs to shift liability.</p>
<div class="step-label">The Safe Bet</div>
<div class="step-duration">Procurement</div>
<p class="step-detail">Buying a global brand to outsource accountability and mitigate risk.</p>
</div>
<div class="arrow-connector">➔</div>
<div class="pipeline-step">
<div class="step-num">02</div>
<div class="step-label">RFP & Legal</div>
<div class="step-duration">6 - 12 Months</div>
<p class="step-detail">Mega-vendors dominate with dedicated bidding teams.</p>
<div class="step-label">The Mega-Contract</div>
<div class="step-duration">Implementation</div>
<p class="step-detail">Massive reliance on Tier 1 systems integrators.</p>
</div>
<div class="arrow-connector">➔</div>
<div class="pipeline-step warning-glow">
<div class="step-num text-red">03</div>
<div class="step-label text-red">Outdated Launch</div>
<div class="step-duration text-grey">Day 1</div>
<p class="step-detail">Delivered system is obsolete before first login.</p>
<div class="step-label text-red">The QLD Health Disaster</div>
<div class="step-duration text-grey">Local Case Study</div>
<p class="step-detail">IBM payroll project: started at $6.2M, blew out to $1.25B with 35,000 payroll errors.</p>
</div>
<div class="arrow-connector">➔</div>
<div class="pipeline-step highlight-cyan-glow">
<div class="step-num text-cyan">04</div>
<div class="step-label text-cyan">Locked In</div>
<div class="step-duration text-cyan">5+ Year Contract</div>
<p class="step-detail">Paying consultants $300/hr for minor edits.</p>
<div class="step-label text-cyan">Capability Lost</div>
<div class="step-duration text-cyan">The Result</div>
<p class="step-detail">We didn't outsource the risk, we just outsourced our ability to fix the problem.</p>
</div>
</div>
<aside class="notes">
Why does this happen? It's driven by a culture of 'Cover Your Ass'. In government, buying from a massive vendor is the ultimate shield. If a project fails and you bought it from Microsoft or Accenture, nobody gets fired. It's the vendor's fault. But if you try to build it internally and it fails, it's on you. This fear has created an 18-month procurement cycle where we write 300-page requirement documents for software that is already obsolete by the time the contract is signed.
So why do incredibly smart executives keep signing these deals? It comes down to risk aversion, which is completely understandable. In government procurement, there is a fundamental belief that buying from a massive global brand equals safety. We think we are outsourcing the risk. But look in our own backyard at the Queensland Health Payroll disaster. Management sought a safe bet by contracting IBM for 6.2 million dollars. It blew out to 1.25 billion dollars, caused 35,000 payroll anomalies, and required hundreds of staff to process manual workarounds. Buying a massive vendor name did not buy a successful project. We didn't outsource the risk; we just outsourced our internal capability to fix it.
</aside>
</section>
<!-- Slide 4: The Generative Shift -->
<!-- Slide 4: The Federal Disaster (BOM) -->
<section id="slide-bom-case-study" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">Not Just a Local Problem</h2>
<p class="slide-subtitle text-gradient-red">The Bureau of Meteorology Redesign</p>
<div class="grid-2col margin-top-md align-center">
<div class="card glassmorphic border-red">
<div class="big-metric text-red">$4.5M</div>
<p class="metric-label">Original Budget for Website Redesign</p>
<div class="flow-arrow text-red text-center" style="font-size: 2rem;">▼</div>
<div class="big-metric text-gradient-red">$96.5M</div>
<p class="metric-label">Final Cost Exposed in Late 2025</p>
</div>
<div class="text-block text-left">
<h3 class="text-white">A Front-End Fiasco</h3>
<p class="margin-bottom-md">The multi-million dollar redesign was heavily criticised because Australians actually struggled to read the new weather maps and radar.</p>
<ul class="clean-list">
<li><span class="text-red">➔</span> Parts of the site had to be reverted to the old view due to public outcry.</li>
<li><span class="text-red">➔</span> Bloated by an additional $80M+ for "technical build and underpinning systems" by external vendors.</li>
<li><span class="text-red">➔</span> Pushed through without adequate oversight due to reliance on mega-vendor "expertise".</li>
</ul>
</div>
</div>
<aside class="notes">
If you think that's just an old Queensland problem, look at the federal level. In late 2025, it was exposed that the Bureau of Meteorology website redesign—which originally had a 4.5 million dollar budget—blew out to 96.5 million dollars. And the result? Australians couldn't even read the weather map properly. It infuriated farmers and regional citizens to the point where portions of the site had to be rolled back to their original views. It sailed through without proper oversight because the front-end redesign was anchored to an 80 million dollar external technical rebuild. We keep throwing hundreds of millions at external vendors for basic digital touchpoints, and we end up with products that are functionally worse for the citizens who rely on them.
</aside>
</section>
<!-- Slide 5: Audience Participation -->
<section id="slide-audience-poll" class="slide-content title-slide" data-transition="zoom-in fade-out">
<div class="glow-orb" id="orb-3" style="background: radial-gradient(circle, rgba(168,85,247,0.4) 0%, transparent 60%);"></div>
<div class="title-container">
<h2 class="main-title big-bold text-white">Let's do a quick poll.</h2>
<div class="divider"></div>
<h3 class="tagline text-cyan" style="font-size: 3rem; line-height: 1.2;">Where were you on</h3>
<h3 class="tagline text-red" style="font-size: 4rem; line-height: 1.2; font-weight: 700; margin-bottom: 2rem;">July 19th, 2024?</h3>
<!-- Clear instructions for the audience -->
<div style="padding: 20px; background: rgba(255,255,255,0.05); border-radius: 12px; border: 1px solid rgba(255,255,255,0.1); display: inline-block;">
<p class="text-white" style="font-size: 1.5rem; margin: 0;">✋ Raise your hand or drop an anecdote in the Teams chat.</p>
<p class="text-grey" style="font-size: 1.2rem; margin-top: 10px;">Were you travelling, working, or trying to buy groceries?</p>
</div>
</div>
<aside class="notes">
Before we move on, I want to pause and hear from you. Where were you on July 19th, 2024? Raise your hand on Teams or drop a quick note in the chat if you were personally affected by this. Were you stuck at an airport? Trying to pay for groceries? Locked out of a critical government system?
[PAUSE FOR 10-15 SECONDS TO LET CHAT POPULATE / READ OUT 1 OR 2 REPLIES]
For anyone who somehow missed it, or managed to block it out of their memory: that was the day of the global CrowdStrike outage. A single, routine software update pushed by one vendor crashed eight and a half million Windows machines worldwide. It grounded flights, halted hospital surgeries, and crippled banking and government infrastructure.
Now, raise your hand if you think CrowdStrike fully compensated the Australian economy for the estimated 1 billion dollars in damage that outage caused.
[PAUSE]
Of course they didn't.
</aside>
</section>
<!-- Slide 6: "Too Big To Fail" & The SLA Myth -->
<section id="slide-sla-myth" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">Too Big To Fail</h2>
<p class="slide-subtitle text-gradient-purple">Cloud Concentration Risk & The SLA Myth</p>
<div class="grid-2col margin-top-md">
<div class="card glassmorphic">
<h4 class="text-red">The CrowdStrike Reality</h4>
<p class="text-sm margin-bottom-sm">It wasn't a cyber attack. A routine vendor software update brought down airlines, supermarkets, and government infrastructure globally.</p>
<div class="choice-footer border-red text-red text-center" style="margin-top: 1rem;">
Under contract law, liability is capped at "fees paid." No compensation for the $1B+ in Australian economic damage.
</div>
</div>
<div class="card glassmorphic">
<h4 class="text-cyan">The SLA Illusion</h4>
<p class="text-sm margin-bottom-sm">Vendors offer SLAs (Service Level Agreements) to simulate accountability. But the math doesn't protect the taxpayer.</p>
<ul class="sovereign-list text-sm">
<li class="locked-item">Vendor Outage Cost: <strong>$150,000</strong> in lost public sector productivity.</li>
<li class="free-item">Vendor SLA "Penalty": A <strong>10% credit</strong> on a $50k monthly bill = <strong>$5,000</strong>.</li>
</ul>
<p class="text-sm text-grey margin-top-sm" style="font-style: italic;">We absorb 96% of the damage.</p>
</div>
</div>
<aside class="notes">
When a major vendor goes down, they are essentially 'too big to fail.' What we used to call vendor lock-in has evolved into Cloud Concentration Risk. Three vendors control two-thirds of the world's infrastructure. When they go down, the state stops. And the moment you suggest building locally, someone will say, 'But we need a vendor SLA for protection.' Let's be realistic about what an SLA actually is. If an Azure or AWS outage costs a department $150,000 in lost productivity, standard vendor SLAs typically cap liability or offer a 10% credit on your next monthly bill. That’s maybe a $5,000 credit for a massive operational disaster. The SLA doesn't protect our operations; it protects the vendor's liability. We take all the actual risk.
</aside>
</section>
<!-- Slide 7: Real Sovereignty (Global Proof) -->
<section id="slide-global-proof" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">Real Sovereignty</h2>
<p class="slide-subtitle text-gradient-cyan">The Global Rebellion</p>
<div class="grid-2col margin-top-md">
<div class="card glassmorphic">
<div class="card-badge bg-cyan">GERMANY</div>
<h3 class="card-title text-white">Schleswig-Holstein</h3>
<p class="margin-bottom-md">Migrating tens of thousands of public servants off Windows and Microsoft Office, entirely over to Linux and LibreOffice.</p>
<div class="choice-footer text-cyan">Goal: National Security & Data Control</div>
</div>
<div class="card glassmorphic">
<div class="card-badge bg-cyan">FRANCE</div>
<h3 class="card-title text-white">National Police Force</h3>
<p class="margin-bottom-md">Ditched proprietary operating systems to build and deploy a custom Ubuntu-based environment across their entire fleet.</p>
<div class="choice-footer text-cyan">Goal: Sovereign Digital Borders</div>
</div>
</div>
<aside class="notes">
If you think ditching these megavendors is a pipe dream, look at Europe. Other governments are waking up. Right now, the German state of Schleswig-Holstein is actively migrating tens of thousands of public servants off Windows and Microsoft Office, entirely over to Linux and LibreOffice. Why? Their minister explicitly stated it was about Digital Sovereignty. They realized that handing their government's operational capability and data architecture to a foreign corporation was a national security risk. France's national police force did the exact same thing years ago, saving millions and taking back complete control of their digital borders. It is entirely possible.
</aside>
</section>
<!-- Slide 8: The AI Multiplier -->
<section id="slide-generative-shift" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Generative Shift</h2>
<h2 class="slide-header">The AI Multiplier</h2>
<p class="slide-subtitle text-gradient-purple">Why Now?</p>
<div class="grid-2col align-center">
<div class="chart-container glassmorphic">
@ -127,12 +245,12 @@
<!-- X-Axis labels -->
<text x="40" y="185" fill="#9ca3af" font-size="9" text-anchor="middle">2020</text>
<text x="210" y="185" fill="#9ca3af" font-size="9" text-anchor="middle">2023 (LLM Boom)</text>
<text x="210" y="185" fill="#9ca3af" font-size="9" text-anchor="middle">2023</text>
<text x="360" y="185" fill="#9ca3af" font-size="9" text-anchor="middle">2026</text>
<!-- COTS cost curve (stays high) -->
<path d="M 40 40 Q 210 40 360 35" fill="none" stroke="#ef4444" stroke-width="3" />
<text x="350" y="55" fill="#ef4444" font-size="9" text-anchor="end">SaaS Subscription Cost</text>
<text x="350" y="55" fill="#ef4444" font-size="9" text-anchor="end">Vendor Licensing Cost</text>
<!-- AI-Assisted Build cost curve (drops sharply) -->
<path d="M 40 50 Q 150 60 210 120 T 360 160" fill="none" stroke="#06b6d4" stroke-width="3" id="ai-path" />
@ -142,202 +260,123 @@
<div class="text-block text-left">
<h3 class="highlight-cyan font-grotesk">The Death of the Trade-off</h3>
<p class="margin-bottom-md">Traditional software required a massive engineering budget. Today, AI-powered coding agents dramatically compress development loops.</p>
<p class="margin-bottom-md">Historically, building required armies of developers. Today, AI completely changes the economics of software development.</p>
<ul class="clean-list">
<li><span class="text-cyan">➔</span> <strong class="text-white">90% Reduction</strong> in lines of code written by hand.</li>
<li><span class="text-cyan">➔</span> <strong class="text-white">Instant Scaffolding</strong> of databases & APIs.</li>
<li><span class="text-cyan">➔</span> <strong class="text-white">Sovereign Hosting</strong> on public/internal cloud.</li>
<li><span class="text-cyan">➔</span> <strong class="text-white">Small Teams:</strong> Cross-functional internal capability.</li>
<li><span class="text-cyan">➔</span> <strong class="text-white">Rapid Scaffolding:</strong> Built in weeks using lightweight open-source stacks (Vite, React, TS).</li>
<li><span class="text-cyan">➔</span> <strong class="text-white">Sovereign Hosting:</strong> True ownership, code that lives locally.</li>
</ul>
</div>
</div>
<aside class="notes">
But the calculus has completely changed. In 2026, the old trade-offs of 'Build vs. Buy' are dead. Historically, building custom software required massive engineering teams, multi-million dollar budgets, and years of development. Today, generative AI tools act as massive force multipliers. A single graduate developer, equipped with AI coding agents, can build, document, and test a custom application in weeks. The financial justification for vendor lock-in has crashed.
The traditional pushback in Queensland has always been: 'We don't have the armies of developers needed to build and maintain our own open-source solutions.' And five years ago, that was a completely fair argument. But that argument is dead. AI has completely changed the economics of software development. A small, cross-functional internal team using AI coding assistants and modern lightweight stacks—like React, Vite, and TypeScript—can now scaffold, build, and secure custom open-source infrastructure in weeks. Building sovereign software is now demonstrably cheaper and faster than adapting our workflows to fit a vendor's rigid template.
</aside>
</section>
<!-- Slide 5: Digital Sovereignty -->
<section id="slide-sovereignty" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">Digital Sovereignty</h2>
<p class="slide-subtitle text-gradient-cyan">Choosing Who Controls Your Infrastructure</p>
<!-- Slide 9: The Local Economy -->
<section id="slide-local-economy" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Local Economy</h2>
<p class="slide-subtitle text-gradient-cyan">Where Do Our Taxes Go?</p>
<div class="grid-2col margin-top-md">
<div class="card glassmorphic hover-red-glow">
<div class="card-badge bg-red">PROPRIETARY COLONY</div>
<div class="card-badge bg-red">THE VENDOR MODEL</div>
<h3 class="text-red">Offshore Transfer</h3>
<ul class="sovereign-list">
<li class="locked-item">Data processed through black-box vendor APIs</li>
<li class="locked-item">Codebase owned entirely by the supplier</li>
<li class="locked-item">Compulsory SaaS licensing fee increases</li>
<li class="locked-item">Dependency on vendor roadmap for updates</li>
<li class="locked-item">Hundreds of millions routed to US server farms.</li>
<li class="locked-item">Pads the margins of global multinationals.</li>
<li class="locked-item">Locks local tech companies out of government contracts.</li>
</ul>
</div>
<div class="card glassmorphic highlight-cyan-glow">
<div class="card-badge bg-cyan">SOVEREIGN STATE</div>
<div class="card-badge bg-cyan">THE SOVEREIGN MODEL</div>
<h3 class="text-cyan">Queensland Investment</h3>
<ul class="sovereign-list">
<li class="free-item">Self-hosted, transparent open-source LLMs</li>
<li class="free-item">Full ownership and visibility of the codebase</li>
<li class="free-item">$0 licensing fees — pay only for compute</li>
<li class="free-item">Deploy customizations at the speed of command</li>
<li class="free-item">Licensing budget redirected to internal capability.</li>
<li class="free-item">Pays for local graduate jobs and tech roles.</li>
<li class="free-item">Funds local Brisbane startups for integration and support.</li>
</ul>
</div>
</div>
<aside class="notes">
The alternative is Digital Sovereignty. It's the simple idea that a sovereign nation should own and control the digital infrastructure it relies on. When we buy proprietary SaaS platforms, we hand over our data, our workflows, and our public capabilities to private entities. If we want to change a form, we have to pay a consultant $300 an hour. Digital sovereignty means we use open-source foundation models, write our own custom wrappers, and host them on our own cloud infrastructure. We control our own destiny.
This isn't just about code; it is a macroeconomic choice. The Queensland Government's ICT spend routinely runs into the billions. When we sign a massive SaaS contract, a huge portion of those taxpayer dollars goes straight to a server farm in Seattle or Silicon Valley. If we take even a fraction of that licensing budget and redirect it to building open-source sovereign capability, where does that money go? It stays in Queensland. It pays for local graduate jobs—jobs for people like you. It funds local Brisbane tech startups who we can hire to support and integrate our open-source tools. Public tech budgets should be used to build the local digital economy.
</aside>
</section>
<!-- Slide 6: Case Study -->
<section id="slide-case-study" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">Case Management Reimagined</h2>
<table class="sovereign-table glassmorphic margin-top-md">
<thead>
<tr>
<th>Criteria</th>
<th class="text-red">Commercial SaaS (COTS)</th>
<th class="text-cyan">Sovereign Build (AI-Driven)</th>
</tr>
</thead>
<tbody>
<tr>
<td class="table-label">Licensing Cost</td>
<td class="text-red">$180 per user / month</td>
<td class="text-cyan">$0 (Compute only)</td>
</tr>
<tr>
<td class="table-label">Customization</td>
<td class="text-red">Paid contractor config contracts</td>
<td class="text-cyan">AI code updates in minutes</td>
</tr>
<tr>
<td class="table-label">Integration</td>
<td class="text-red">Complex proprietary APIs</td>
<td class="text-cyan">Standard open-source APIs</td>
</tr>
<tr>
<td class="table-label">Data Privacy</td>
<td class="text-red">Stored in vendor cloud tenant</td>
<td class="text-cyan">Fully isolated in local gov cloud</td>
</tr>
</tbody>
</table>
<aside class="notes">
Let's look at a concrete example. Imagine a case management system for a public services department. Traditional route: Buy a major SaaS platform, pay $150 per user per month, plus $2 million in customization fees. Under the new model: We use a lightweight open-source template. We use AI to build custom integrations for our specific departmental workflows in two weeks. Total licensing cost: Zero. Total control: Absolute. The money we save is reinvested back into building local capabilities.
</aside>
</section>
<!-- Slide 7: Debunking Support -->
<section id="slide-support-myth" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">"But Who Will Support It?"</h2>
<p class="slide-subtitle text-gradient-purple">The Myth of Vendor Support Liability</p>
<div class="grid-2col margin-top-md">
<div class="card glassmorphic">
<h4 class="text-red">The Vendor Support Illusion</h4>
<div class="flow-chart">
<div class="flow-node border-red">Bug Detected</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-red">Open Support Ticket</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-red">Wait 3 Weeks for Escalation</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-red">"Works as Intended / Paid Request"</div>
</div>
</div>
<div class="card glassmorphic highlight-cyan-glow">
<h4 class="text-cyan">The AI-Powered Sovereign Dev</h4>
<div class="flow-chart">
<div class="flow-node border-cyan">Bug Detected</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-cyan">AI Agent Diagnoses Trace</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-cyan">Dev Reviews Generated Patch</div>
<div class="flow-arrow">▼</div>
<div class="flow-node border-cyan">Test Passed & Deployed (15 mins)</div>
</div>
</div>
</div>
<aside class="notes">
The number one objection you will hear from senior management is: 'But if we build it ourselves, who will support it when it breaks? We need a vendor for liability.' This is an illusion. The reality of vendor support is endless ticket queues, escalating costs, and finger-pointing. With modern AI-assisted engineering, your own team can maintain sovereign code. AI agents can analyze log traces, pinpoint bugs, write unit tests, and suggest patches. You are not just building software; you are building the capability to support it.
</aside>
</section>
<!-- Slide 8: The Choice -->
<!-- Slide 10: The Choice -->
<section id="slide-choice" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Graduate's Choice</h2>
<h2 class="slide-header">The Choice for 2026 Grads</h2>
<div class="grid-2col margin-top-md">
<div class="card glassmorphic choice-card locked-opacity" id="choice-admin">
<div class="card-icon text-grey">📋</div>
<h3 class="card-title text-grey">License Administrator</h3>
<p class="choice-text">Spend your career configuring enterprise templates, filing vendor tickets, and managing access tokens.</p>
<div class="choice-footer text-red">Vendor Locked-in Career</div>
<p class="choice-text">Spend the next thirty years managing vendor lock-in, filling out procurement forms, and apologizing to users for interface problems you aren't allowed to fix.</p>
<div class="choice-footer text-red">The Status Quo</div>
</div>
<div class="card glassmorphic choice-card highlight-cyan-glow animate-pulse-border" id="choice-builder">
<div class="card-icon text-cyan">⚡</div>
<h3 class="card-title text-cyan">Sovereign Builder</h3>
<p class="choice-text">Use AI agents to design microservices, customize open-source infrastructure, and deploy real digital products.</p>
<div class="choice-footer text-cyan">Future-Proof Architect</div>
<p class="choice-text">Champion open standards, use AI to create incredible local systems, and actually own the infrastructure that runs this state.</p>
<div class="choice-footer text-cyan">The Future Architecture</div>
</div>
</div>
<aside class="notes">
As graduates entering the digital stream in 2026, you face a critical choice. You can become professional license administrators—spending your careers configuring proprietary templates and managing vendor relationships. Or, you can become sovereign builders. You can use generative AI to write code, design architectures, and deploy open-source solutions that actually solve problems for citizens. Choose to build. Choose to be sovereign.
You are the 2026 digital graduates. In five years, you are going to be the lead enterprise architects, the senior BAs, and the design directors for the Queensland government. You have a choice regarding what your career looks like. You can be a professional license administrator, managing vendor lock-in. Or, you can be builders. You can champion open standards, use AI to create incredible local systems, and actually own the infrastructure that runs this state. When something breaks, you won't be submitting a ticket to a vendor in another timezone; you'll be fixing it because you own it.
</aside>
</section>
<!-- Slide 9: The Playbook -->
<!-- Slide 11: The Playbook -->
<section id="slide-playbook" class="slide-content" data-transition="slide-in fade-out">
<h2 class="slide-header">The Sovereign Playbook</h2>
<p class="slide-subtitle text-gradient-cyan">How to Disrupt the Status Quo Tomorrow</p>
<h2 class="slide-header">The Playbook</h2>
<p class="slide-subtitle text-gradient-cyan">Where to start tomorrow.</p>
<div class="playbook-steps margin-top-md">
<div class="playbook-card glassmorphic">
<div class="playbook-num text-cyan">01</div>
<h4 class="playbook-title text-white">Find the excel mess</h4>
<p class="playbook-body">Identify a slow, manual database-in-a-spreadsheet or a paper-and-form process.</p>
<h4 class="playbook-title text-white">Demand a Plan B</h4>
<p class="playbook-body">When the team defaults to Azure or SaaS, raise your hand. Ask for an open-source assessment and a concrete exit strategy.</p>
</div>
<div class="playbook-card glassmorphic">
<div class="playbook-num text-cyan">02</div>
<h4 class="playbook-title text-white">Scaffold open source</h4>
<p class="playbook-body">Use a clean, secure open-source template (Node, Python, Postgres) as your base.</p>
<h4 class="playbook-title text-white">Find a clunky process</h4>
<p class="playbook-body">Locate a terrible, manual process or messy spreadsheet system within your immediate department.</p>
</div>
<div class="playbook-card glassmorphic">
<div class="playbook-num text-cyan">03</div>
<h4 class="playbook-title text-white">Code with AI agents</h4>
<p class="playbook-body">Let generative agents write custom business rules, API connectors, and unit tests.</p>
<h4 class="playbook-title text-white">Build the prototype</h4>
<p class="playbook-body">Use AI and lightweight stacks (e.g., Vite/React) to scaffold a clean, secure, local internal app in three weeks.</p>
</div>
<div class="playbook-card glassmorphic">
<div class="playbook-num text-cyan">04</div>
<h4 class="playbook-title text-white">Ship and show</h4>
<p class="playbook-body">Deploy internally. Show a working tool to leadership before they even write the RFP.</p>
<h4 class="playbook-title text-white">Show, don't tell</h4>
<p class="playbook-body">Present leadership with a working tool that solves the problem with zero ongoing licensing fees.</p>
</div>
</div>
<aside class="notes">
How do you do this without getting crushed by the bureaucracy? Follow the playbook. Don't try to rewrite the core taxation system on day one. Start small. Find a manual Excel process or a clunky form. Scaffold an open-source tool. Use AI to write the custom business logic. Deploy it on internal infrastructure. Show, don't tell. Once senior leadership sees a working tool built in three weeks for zero dollars, the procurement arguments start to crumble.
How do we actually start? You don't walk into work tomorrow and try to aggressively unplug a critical legacy system. You start at the project level. For your next assignment, when the team defaults to 'Let's put it on Azure' or 'Let's just buy a SaaS product,' push back politely. Raise your hand and request an open-source viability test. At the very least, ask what our 'Plan B' is if we need to migrate off the vendor later. Then, find a terrible, clunky manual process in your department. Use an AI assistant and a lightweight framework to scaffold a clean, secure, local internal web app to fix it. Show leadership a working tool built in three weeks with zero licensing fees. The best way to win the argument is simply to build something better.
</aside>
</section>
<!-- Slide 10: Conclusion -->
<!-- Slide 12: Conclusion -->
<section id="slide-conclusion" class="slide-content title-slide" data-transition="fade-in">
<div class="glow-orb" id="orb-2"></div>
<div class="title-container">
<h1 class="main-title big-bold text-gradient-cyan">PUBLIC FUNDS</h1>
<h1 class="main-title big-bold text-gradient-purple">PUBLIC CODE</h1>
<h1 class="main-title big-bold text-gradient-cyan">PUBLIC FUNDS.</h1>
<h1 class="main-title big-bold text-gradient-purple">PUBLIC INFRASTRUCTURE.</h1>
<div class="divider"></div>
<p class="tagline">Let's build a sovereign future.</p>
<p class="tagline">Let's start building it.</p>
<div class="q-a-badge">Questions & Discussion</div>
</div>
<aside class="notes">
Let's build a future where public funds create public code. Let's build a government that is capable, agile, and sovereign. You have the tools, the technology, and the opportunity. Thank you, and let's get to work.
Digital infrastructure is exactly like physical infrastructure. We wouldn't let a private foreign company own the M1 motorway and charge Queenslanders a toll every time they drive to work. We shouldn't let them own the digital highways our citizens rely on either. Public funds should build public infrastructure. Let's start building it.
Thanks for listening. We have about eight minutes left, and I'd love to open the floor up. To kick us off: what proprietary tools are driving you crazy right now, and what could we realistically replace them with?
</aside>
</section>
@ -346,4 +385,4 @@
<script type="module" src="/src/main.js"></script>
</body>
</html>
</html>