Ideas for people who run a company
Pieces on AI and systems, written in plain language so you can judge for yourself what suits your company.
Why I write these
I write for the people who hire me, who are rarely technical and don't need to be. What they need is to understand what is going on in their company and what their options are, without having to pick up a new vocabulary along the way.
These pieces put a name to problems I see often and that rarely make it onto the to-do list. I mean information lost between tools, data leaving through the back door or a website that doesn't serve the people who visit it. And when a problem has a name, it is easier to spot it in your own company and know where to start.
Topics
- How I work
The process step by step, what you pay for and which work fits.
- Copilot or autopilot: where the money is and where the margin is
What happens when you sell finished work instead of the tool, where I agree with Sequoia, where I add a caveat and which task to start with.
- Service-as-Software needs forward deployed engineers
Why selling the work needs engineers inside the client, where the business model breaks and the limits I set.
- AI agents that do real work every day
What an agent is and isn't, what it can do in each part of your company and what to have in place before you put it to work.
- Your company is already a system
From the website to how your remote team talks: where information gets lost and why to sort out the flow before adding AI.
- Shadow AI
Your company's data ending up in AI chats without a usage policy in place, and a way to sort it out without banning anything.
- Your website as your first employee
A website that answers, sorts and routes each visitor instead of waiting like a brochure, and that anyone can use.
- Do you need it?
Signs, by type of company, of problems you may not know you have yet.
Did any of these sound familiar?
Tell me how things work at your company and which of these pieces got you thinking.
Write to me