Agentic Systems.
A useful agent needs the right information, a defined task and someone responsible for its results. Matt helps you choose where agents fit, build the knowledge behind them and plan how the work will run.
Five ways to put agents to work.
Second Brain.
Maintain the knowledge your people and AI tools need. Start with a two-week build in SharePoint Online or Claude Code and Codex.
Build a second brain for your business
Team Modernization.
Redesign a team's work task by task: what people keep, what AI prepares for review and what runs on its own, with checks.
See how agents change a team's work
Cost Planning.
Compare the cost of a result your team accepts, including model use and review, and set allowances by role before you scale.
Plan what your AI agents cost to run
DevOps & Scaling.
Take a useful prototype into team use. Plan testing, release, access and support for the destination platform, including Microsoft 365 Copilot where it fits.
Scale a Claude or Codex workflow to Microsoft 365
AI-Ready Websites.
Make your website easier for AI assistants to read and navigate, with supported actions that people remain in control of. This site demonstrates the approach.
Make your website work with AI agents
What to know first.
Where this starts.
You may have switched on Copilot without finding a daily use for it, or already build with Claude and Codex and need a consistent source of knowledge.
Copilot answers from whatever the person asking can access, so existing oversharing becomes easier to find. An agent's tools may reach further. Review access and ownership with the first workflow.
What this looks like in practice.
Claude and Codex work from the maintained wiki behind this website, with less repeated briefing from Matt.
- A website moved between content platforms in two weeks, after a purpose-built transpiler converted its content.
- An Azure subscription move delivered in two weeks against a six-week estimate.
- Agentic software since 2024; Microsoft 365 Copilot architecture since 2023.
You work directly with Matt, with contractors when needed, or he plans and shadows a larger firm's delivery.
Old systems are not a blocker.
Old systems often have no current documentation, and the people who knew them have moved on.
On a legacy enterprise content system, Matt recovered what the migration needed from old manuals and source code.
Start with the reliable source material that remains, then check it against the running system.
How Matt can help.
Work with us.
The first scope should include the information an agent needs, the actions it can take and how people will check its work. Access and governance decisions belong in that conversation.
Remote first, and in person across Toronto, Mississauga and the Golden Horseshoe when that is useful.
Bring the work that takes too much effort.
You do not need a specification. Bring the question nobody can answer quickly, or the Copilot rollout that stalled, and we will work out what is worth building.