From understanding AI to using it — consistently, inside your business.
With a live demo built inside Claude Cowork.
Part 2 of the AI for Local Businesses series. Part 1 covered the fundamentals — what AI is, how LLMs were built, and why it matters now. Today we go further: how to think in systems, what Claude Cowork is, and a live demo of LaymanCRM — a real skill built to solve a real problem local business owners face every week.
Everything we cover today maps to one of these four steps. By the end, you will have seen every one in action.
AURA is the adoption framework at the heart of The AI Guy's approach to local businesses. It is not a product — it is a progression. Today every section of this session lives inside one of these four steps, so the framework becomes real through experience rather than description.
These three ideas from Part 1 form the foundation for everything in Part 2. The third point is the most important for today — it is the bridge from understanding AI to using it in a way that creates real, consistent business value.
The difference between using AI as a novelty and using it as a business asset is systematic thinking. A system is simply a repeatable workflow: defined inputs, a reliable process, and a predictable output. Once that exists, AI stops being something you try and starts being something you rely on.
"Think of it as a team member who already has your onboarding done — and gets smarter every time you add to the project."
Claude Cowork (referred to as a Claude Project in Anthropic's tooling) is a persistent, configurable workspace. Unlike a standard chat session, a Cowork project retains context between conversations, follows configured instructions, and can run saved workflows called skills. This makes it suitable for systematic, repeatable business use rather than one-off queries.
A skill is the fundamental unit of an AI system inside Claude Cowork. It is a saved set of instructions that defines what to do when given a specific type of input. Because it is reusable and consistent, it can become a reliable part of how the business operates — rather than something that needs to be set up from scratch each time.
Cowork is not just a tool. It is where AURA lives — the environment in which each step of the framework becomes something you can actually do.
Claude Cowork provides the technical foundation for the AURA framework. Each step of AURA corresponds to a specific way of working inside a Cowork project. Activate means connecting data sources. Use means running skills daily. Rely means embedding skills in standard workflow. Automate means configuring skills to trigger without manual initiation.
You had real conversations. Right here at 25N. Five business cards in your pocket. Three LinkedIn connections pending. A few names you remember vaguely and one person you genuinely want to follow up with.
In 48 hours, the context is gone. Who they were, what you talked about, why it mattered.
The networking follow-up problem is nearly universal for local business owners. The challenge is not motivation — it is friction. Without a system, even well-intentioned follow-ups get delayed until they feel irrelevant. LaymanCRM eliminates the friction by making the process instant, automatic, and personal.
Two inputs. Thirty seconds. A complete contact record — and a personalized email ready to send. This runs entirely inside Claude Cowork.
LaymanCRM is a Claude Cowork project built to solve the post-networking follow-up problem. It uses two skills: an enrichment skill that processes a business card photo and LinkedIn screenshot to populate a structured JSON contact record, and a brand voice skill that drafts a personalized outreach email based on the enriched data. No external CRM. No monthly fee. Your data stays local.
The enrichment skill inside LaymanCRM reads both inputs simultaneously — card photo and LinkedIn screenshot — and produces a structured JSON contact entry. It extracts factual fields from the card, supplements them with context from LinkedIn, and adds the event context. The output is richer than anything you would have time to type manually, and it is immediately ready for outreach.
The brand voice skill knows how Raj writes — his rhythm, his directness, his warmth. It produced this from the enriched CRM entry in seconds. It is not a template. It is a trained voice that sounds like a real person, because it learned from one.
The brand voice skill is a separate Cowork skill configured with writing samples and tone guidelines. It reads the enriched contact record, pulls the relevant context, and produces a personalized email that reflects the actual conversation from the event. The result feels handwritten — because the pattern it follows was built from real writing, not generic prompts.
The LaymanCRM demo illustrates every element of the AURA framework in a single workflow. It is not a complex system — it is two skills, two inputs, and two outputs. But because it is repeatable and reliable, it qualifies as a genuine system. That is what creates business value: not sophistication, but consistency.
Every one of these follows the same structure. Same input. Same process. Consistent output. A real estate agent, a therapist, a caterer, an accountant — the pattern is the same. Only the subject matter changes.
These four examples illustrate that the skill pattern from LaymanCRM is universal. Any business that receives recurring inputs and produces recurring outputs can build a skill for it inside Claude Cowork. The goal is to identify one high-friction, high-frequency workflow and start there.
The thing that piles up in your business and rarely gets done — not because you don't want to, but because there is no system. That is your starting point.
What is yours? Take 30 seconds. You already know the answer.
This is the highest-value moment of the session. Every business owner has at least one workflow that accumulates and goes undone — a stack of friction that quietly costs them time and opportunity. The goal is for each person in the room to name theirs, because naming it is the first step toward building a skill for it.
If you can answer these three questions, you can build the skill inside Claude Cowork — in plain language, today. No code. No technical background required.
These three questions are the design framework for any skill built inside Claude Cowork. They force clarity on what the workflow does and why it matters, before any configuration begins. Most business owners can answer all three in under two minutes once they have identified their card pile.
The most common mistake after a session like this is trying to build everything at once. One skill, one real input, one result this week is the target. The goal is not to automate the whole business — it is to create one moment where a system works and you trust it. Everything else follows from there.
If you want help setting up your first Cowork project — or thinking through which workflow to start with — I am happy to continue the conversation.
No pitch. No pressure. Just a practical conversation.
The local accountant who knew your name. The small firm that actually had time for you.
These businesses deserve the same tools the big companies are building for themselves.
That is why I am here.
If this session raised questions about your own business and where a Cowork skill could help, reach out. The best next step is usually a short conversation — not a sales process. Part 3 of this series will go deeper into automating full workflows.