Blog · July 21, 2026 · James Forrester

Why I build threndle.ai on Claude

Before threndle.ai had a name, it had a decision to make: if I was going to connect an AI to a small business's books, inbox, and CRM, whose platform was I willing to stake someone else's livelihood on?

We didn't land on Claude first try. We'd been messing around with agentic frameworks for a while before that. Started with n8n, which is great for stringing together simple automations but starts to strain the moment you want something that can actually reason through a task. Next came OpenClaw. That one lasted a while, until we ran into some security issues we weren't willing to put in front of a client, and not the kind you patch and move past either. It made us rethink the whole stack. Around then I received a scholarship from Amii in Alberta, and that pushed me toward Hermes. Hermes is genuinely capable, but it's also a lot. It's the kind of setup that assumes you're comfortable configuring an open agent stack from scratch, and most small business owners aren't going to sit down and learn that. Honestly, I didn't want to become the person explaining it to them every time either.

That's the backdrop for why Claude Cowork and the Small Business skill set became the answer. I spent that spring reading security documentation instead of marketing pages. Here's where I landed, and why.

Why did you choose Claude?

Because the job puts an AI inside a client's real accounting, email, and customer records, and that's not a decision you make off a demo. Not after OpenClaw, anyway. I wasn't going to take anyone's word for it. I wanted a platform with a genuinely serious security posture, from a company whose reputation is staked on doing AI carefully. Anthropic built its name on safety research. Its business terms don't train models on your data. Claude connects through official APIs, with permissions you approve. No getting under the hood required.

What is Claude Cowork?

Claude Cowork is Anthropic's own mode, the one that turns Claude into a coworker connected to the tools you already use, not a chatbot on the side. Of everything I tested, it was the best product to bring to small businesses. threndle.ai is how we set that up inside yours: reconciling transactions, drafting follow-ups, keeping records current, always under your control. The business keeps its software. Claude learns the workflow.

What are Small Business skills?

A skill is one specific job Claude knows how to do in your tools. Reconcile yesterday's Stripe payouts against QuickBooks. Chase invoices overdue past seven days. Draft a follow-up to a lead gone cold. Small Business skills are the starter set, built around the software Fraser Valley businesses already pay for: accounting, payments, CRM, email, files, team ops.

What does that mean for your data?

It stays yours, in your tools. We don't store your credentials or raw business data on our servers. Claude connects through official APIs and OAuth where available, using read-and-write permissions you approve. Any automation can be paused or revoked at any time, and every integration is reviewed before it goes live.

Would you choose it again?

Yes. Every engagement since has confirmed the same thing: the platform choice matters less for what it can do on a demo and more for what it can be trusted with on a Tuesday morning in someone else's books. Security posture and reputation were the right criteria then, and after n8n, OpenClaw, and Hermes, I'm even more convinced they're the right ones now.

Update, July 24

A few days after this went up, I had to pump the brakes for a bit. Turned out threndle.ai didn't actually have any infrastructure for Claude to connect to yet. All the platform research in the world doesn't help if there's nothing on the other end of the wire. So I picked a CRM and an accounting tool to standardize on, and built a custom market research MCP from scratch using MIT licensed repos off GitHub. More on that soon.

Update, August 4

After the long weekend, I got back to work on branding and our website, threndle.ai. And here we are, after connecting our workflows to our social media channels too.

This is the first entry in the threndle.ai build log. Next: what the first diagnostic actually surfaced. Until then, start with the three-minute diagnostic or email us at hello@threndle.ai.