Things worth writing down.
Practical notes on AI, software, and automation. We write them when the work teaches us something, not to fill a content calendar.
- Company Brain5 min
How to keep a company brain from going stale
Building a company brain is the easy part. Keeping it right a year later is the job. Ten practices for rules, Owners, conflicts and tests.
- Company Brain6 min
Why an AI second brain breaks when your team uses it
Obsidian plus Claude, Notion AI, ChatGPT memory: what people in forums love about AI second brains, what frustrates them, and what changes for a company.
- Company Brain6 min
What we learned running a company brain on ourselves
Before asking anyone else to trust a company brain, we ran our own company on one. Eight lessons, including the ones that made us change the product.
- Company Brain6 min
Getting expert knowledge out of people's heads with AI interviews
The rules that matter most are rarely written down. How AI interviews capture what your experienced people know, before they retire or move on.
- Company Brain5 min
Why your team gets different answers from the same AI
Two colleagues ask ChatGPT the same question about your company and get two answers. Why that happens, why better prompts won't fix it, and what does.
- Company Brain6 min
What is a company brain? And what it isn't
A company brain is the one place your AI reads before it acts: your rules, approved by the people who own them. How it differs from a wiki and a second brain.
- AI Consulting5 min
AI pilots that never leave the sandbox
Most companies have an AI pilot from the last two years. Few have one still running in production. The gap has little to do with the model.
- App Development4 min
What a fixed-price website actually buys you
Agency pricing is often a black box on purpose. What should be fixed, what should stay flexible, and why a firm quote means a well-scoped project.
- AI Automation4 min
The simpler AI pipeline usually wins
We built a multi-step scraper pipeline for a client, then replaced it with one model call that did the job better. Complexity is the default failure.
- App Development4 min
We build software you don't need us to run
Most agencies build so you have to come back. We build the opposite — and lose follow-up work on purpose. Here's why that's the better deal for everyone.
- AI Consulting5 min
Where does your data actually go?
Before you ask what an AI tool can do, ask where your data lands. That answer decides whether you're allowed to use the tool at all.
- AI Consulting4 min
You probably don't need a chatbot
When a company says 'we want AI', it usually means a chatbot. That's the most visible option and rarely the right place to start. Build this instead.
- Case Study3 min
Building Erikssonwood: making a traditional trade findable
A tree-felling firm does its real work in the forest. Its website has one narrow job: be found and be believed. Here's how we built for that.
- Case Study3 min
Building Enkel Natur: a wellness shop the owner can actually run
A physiotherapist wanted to sell essential oils online without calling a developer to change a price. Here's how we built a shop she runs herself.
- AI Automation4 min
Three automations that pay for themselves in the first month
Most automation pilots start too big and stall. These three work for almost any ops team, are narrow enough to actually ship, and the ROI shows up fast.
- App Development4 min
Build vs. buy: the question nobody answers well
CFOs say buy everything. Engineers say build everything. Both are wrong. Here's the one question that actually cuts through it.
- AI Consulting5 min
Why most AI consulting engagements fail before they start
Companies start with 'we want AI' instead of a specific problem. That's the mistake. Here's how the good engagements are different.
No other articles on this topic yet. The featured one above might be the only one.
Read something that raised more questions?
Good. That's usually where the interesting work starts. Book a free 30-minute call and we'll talk it through, without a sales pitch.
Book a call