Claude Cowork Plugins: My Setup as a Solo Founder
Anthropic launched Claude Cowork Plugins yesterday. I built one that covers my entire workflow as a solo founder. Here is what that looks like.
Claude Cowork Plugins: My Setup as a Solo Founder
Yesterday Anthropic released Claude Cowork Plugins. I spent the evening building one. This morning it gave me my first briefing. I think my workday is going to look different from here on out.
But let me start from the beginning.
What is this about?
A Claude Cowork Plugin is a collection of skills. A skill is a Markdown instruction that tells Claude how to handle a specific task. On top of that, you get access to external tools through MCP connectors, which are interfaces to your project management, CRM, or calendar.
No code. Markdown files and a YAML config. If you can write prompts, you can build a plugin.
Why I built this
I am a solo founder. I do everything myself: client work, invoices, content, sales. I have been using Claude daily for over two years. For emails, proposals, blog posts, code.
The problem was always the same: every conversation starts from zero. Claude does not know my clients, knows nothing about my projects, has no access to my tasks or invoices. So every time, I explain again who I am and what I need. That takes time and it is annoying.
What I built
I wrote a plugin with about twelve skills. The most important ones:
Morning Briefing. I type /morning-briefing, and Claude pulls together my tasks for the day, open invoices, logged hours, and my monthly revenue. This morning I knew within ten seconds that I had two overdue tasks and had already hit my February revenue target. Without the plugin, that would have cost me three different tools and ten minutes.
Weekly Review. On Fridays I get a week-in-review. Hours per client, billable value, completed and postponed tasks. The plugin also tells me when I spent the whole week on client work and did nothing for my own business. That is the part I like to ignore when I am on my own.
Emails and Proposals. Claude now knows my clients and how I write. When I draft an email to a client, it sounds like me. Before, everything sounded like generic ChatGPT output, no matter how often I wrote "make it more casual" in the prompt.
Call Prep. Before a client call I type /call-prep, and Claude gives me a summary of what we last worked on, which tasks are open, and what should be discussed. No more frantic tab-switching five minutes before the call.
What else you can use plugins for
My plugin covers my daily routine as a solo founder. But the possibilities go much further. A few ideas that came to mind while building:
Onboarding assistant. Imagine you hire someone and have a plugin that knows all your internal processes, tools, and contacts. New employee asks Claude, Claude answers with your rules. No Confluence wiki that nobody reads.
Sales co-pilot. A plugin that knows your pricing tiers, typical objections, and client references. You feed in a request, and it drafts a proposal tailored to the client, with the right case studies and numbers.
Support plugin for agencies. Skills for ticket triage, client communication, and escalation rules. Instead of every employee maintaining their own ChatGPT prompt, there is one central plugin with all the agency knowledge.
Accounting plugin. Review time tracking, prepare invoice data, track revenue against your annual goal. I already built this for myself, but for an agency with multiple employees it gets really interesting because you can break things down by project and by person.
Content engine. A plugin that knows your brand voice, audience definitions, and format requirements. You enter a topic, and it produces a blog post, LinkedIn post, and video script, all in your tone, all aligned.
The pattern is always the same: you take knowledge that currently lives in your head or scattered across documents, write it into a skill, and make it available to Claude. From then on, you never have to explain it again.
What surprised me
I expected that building the plugin would mainly be prompt engineering. It was, but the harder part was something else: writing down my own processes.
How do I actually write emails? What do I really check first in the morning? What information do I need for a good proposal? I had to make all of this explicit instead of just going by instinct.
That was exhausting, but useful. I now have documentation of how I work. I did not have that before. And that alone is valuable, regardless of the AI.
Who this is for
If you are a freelancer, consultant, or small agency and you use Claude regularly, take a look at plugins. Especially if you have recurring workflows: weekly reports, client updates, invoice prep, call prep, content.
You do not need a technical background. You need to know how you work and be able to put that into words. Markdown does the rest.
If you have questions or want to know how a plugin is structured: write me. I am also building plugins for clients right now. If you are interested, let us talk.
joshua@pipewave.de or directly via the contact form on pipewave.de
Joshua Kresse is the founder of Pipewave UG. Pipewave automates marketing and sales processes for startups and B2B companies.