Not a product. An approach to running a business, and a life, with AI as infrastructure. I built it for myself first; increasingly it is also something I build for other small businesses.
The philosophy
Every tool in this system was built because something was broken, slow, or missing. Not because AI is interesting (though it is), but because I had a specific problem and the fastest path to solving it was to build a small, focused tool. The school email scanner exists because I kept missing permission slips. The order processing skill exists because compiling WhatsApp orders took two hours. The finance dashboard exists because I needed to know our margins without spending a morning in spreadsheets.
The compound effect is what makes it interesting. One tool saves twenty minutes. Nearly thirty tools, working together, change how you operate. The system becomes greater than the sum of its skills, because the skills reference each other, share data, and build on patterns set by earlier tools. The newest skill takes a fraction of the time to build because the earlier ones created the infrastructure.
What it looks like
The system runs on Claude Code, Anthropic’s CLI tool, with a library of custom skills, agents, and workflows. Each skill is a Markdown file that teaches the system how to handle a specific domain. The skills compose: order processing talks to Google Sheets, which feeds the finance dashboard, which generates the monthly report. Current inventory, roughly grouped:
- Bakery operations: WhatsApp orders compiled into Google Sheets, Shopify product and content management, and weekly delivery manifests.
- Financial infrastructure: a finance dashboard, monthly accounting and GST workflows, and branded MIS snapshots.
- Content and brand: blog writing with multi-agent research, brand-voice guidance, and website content for fikablore.com and rosheden.com.
- Family and personal: a school email scanner, a morning briefing, and an Obsidian knowledge vault.
- Property management: a Hostex connector for our family house in Ystad, rented while we are in India.
How I work
Most days start with a morning briefing that pulls together calendar, school updates, and business status. Work happens in Claude Code sessions, sometimes short (fix a bug, update a price), sometimes long (build a skill, write an essay, redesign a system). At the end of meaningful sessions a digest captures what was built and learned, and feeds a persistent memory so the next session starts where the last one ended.
The distinction that matters: I am not an engineer. I am an operator who builds tools. The skills are not elegant code; they are effective tools that solve real problems for real businesses on a real timeline. The question I ask before building anything is not “is this technically interesting?” but “will this still be saving me time next month?”
What this could look like for your business
The specific tools are specific to my life, but the pattern travels. Any owner-led business running lean can have a version of this: the repetitive admin handled by a system, the judgment left to people. The entry point is not technical skill; it is operational awareness, knowing where your time goes, what is repetitive, and what genuinely needs a person.
When I build this for a client, it starts the same way any operations engagement does: a short diagnostic to find where the hours actually go, then the smallest tool that removes the worst of it, then the next. No platform to buy, no migration. It is built to your operation and you own it.
If that is the kind of thing you need, see how I work or write to me at dennis.roslund@rosheden.com.
Last updated: June 2026. This page evolves as the system does. That is the point.