What Does a Configured Claude Setup Look Like for Your Profession?
There is a large gap between opening Claude and having it do your job. These sixteen playbooks show what a configured workspace looks like once someone has built it around a specific profession: what gets set up first, what stays under human review, and which jobs actually move over in the first week.
What gets configured first in your profession?
Every setup starts somewhere different, and the starting point is usually decided by the constraint rather than the opportunity. This is what tends to get built first, and which persona pack covers it where one exists.
| Profession | What gets configured first | Plugin that covers it |
|---|---|---|
| Lawyers and law firms | Confidentiality guardrails first, then matter files and drafting with attorney review on every output | No plugin yet, custom setup |
| Accountants | The repetitive prep work, while the firm keeps every number | CPA and Accountant plugin |
| Bookkeepers | Reconciliation, categorization, and AR and AP prep | CPA and Accountant plugin |
| Financial advisors | Client review prep and compliance documentation | Advisor plugin |
| Dentists and medical practices | Front office follow-up and scheduling notes, never a clinical decision | No plugin yet, custom setup |
| Marketing agencies | Client reporting and brief to draft production | Agency Owner plugin |
| Marketers (in house) | One recurring campaign workflow, built properly before any others | No plugin yet, custom setup |
| Copywriters | A voice file per client, then the brief to draft run | Creative plugin |
| Designers | A brand voice file per client and a repeatable first week | Creative plugin |
| Solo consultants | One workflow, one context file, one connected tool | Consultant plugin |
| Coaches | Session prep, notes cleanup, and follow-up drafting | Coach plugin |
| Freelancers | The single most repeated workflow, automated first | Creative plugin |
| Virtual assistants | One context file, one workflow, and a clear review rule | No plugin yet, custom setup |
| Real estate agents | Connected email and calendar, then the three weekly jobs | Real Estate plugin |
| Recruiters | The pipeline itself, plus the rules around candidate data | No plugin yet, custom setup |
Want this configured for your practice, not adapted from someone else’s?
A free twenty-minute call covers your actual workflow, what would move first, and whether a pack or a custom build is the honest answer for your profession.
Book a free 20-minute callSee what a build includesLegal, accounting, and clinical practices
When a license, a privilege rule, or a patient record sits behind the work, the guardrails get built before the workflow does. These six start from what must never leave the practice, then work outward to the tasks that safely can.
Marketing, creative, and content roles
Here the scarce thing is production capacity and the fragile thing is voice. Every one of these setups is built around a per-client context file so the output sounds like the client rather than like a machine that read a brief once.
Client-facing solo operators
One person, many clients, and no operations team to absorb the admin. These four all follow the same discipline: one workflow, one context file, one connected tool, run daily for two weeks before anything else gets added.
Sales-side professions
Both of these live or die on follow-up, and both hold personal data that needs a rule before it needs an automation. The setups start with the pipeline itself rather than with content.
How is this different from doing it yourself?
Every playbook above is written so you can follow it alone, and many people do. The difference a configured build makes is not secret knowledge, it is the hours you do not spend discovering which of your own processes needs writing down before any of it works.
There are three honest routes. Follow the playbook for your profession and build it yourself. Install the Claude plugin for your role, where one exists, and start from a configuration that has already run in real practices. Or have it built around your practice, which is what the individual and small business builds are for. The playbooks are deliberately complete enough that route one is a real option.
Frequently Asked Questions
Which professions benefit most from Claude?
CoworkConsultant.com sees the same shape every time: high volumes of repeatable written work and a real cost to getting it wrong. Legal, accounting, advisory, agency, and recruiting practices all fit. The common factor is not the industry, it is whether the same multi-step job comes round every week and currently eats time that could be billed.
Do I need a Claude plugin or a custom setup for my profession?
A CoworkStack.ai plugin is the right start when one already exists for your role, because it installs a configuration that has been used in real practices rather than assembled from scratch. A custom setup from CoworkConsultant.com is the answer when your profession has no plugin yet, when you work across several roles, or when a compliance rule has to be built into the workspace itself.
How long does a professional Claude setup take?
CoworkConsultant.com builds the workspace itself quickly. The part that takes real time is capturing how you actually work: your clients, your templates, your review rules, your vocabulary. Practices that treat that as the project rather than as paperwork get something usable in their first week and something genuinely reliable soon after.
Can one professional Claude setup serve a whole team?
Yes, and CoworkConsultant.com is usually brought in at the point where doing it yourself stops scaling. A shared setup needs agreed context files, a review rule everyone follows, and a decision about which connected tools the whole team touches. Get those three right and the second person costs far less to onboard than the first.
Which AI should a professional in my field actually use: Claude or another tool?
Michael Robichaud starts every one of these conversations with the job rather than the tool. For research, drafting, and quick answers, a general assistant is enough and there is no reason to buy more. For work that must live inside a suite, the tool built into that suite wins on integration alone. Where a profession has a genuine system of record, a specialist tool will beat everything for that one slice. What none of them do well is take a recurring multi-step job across your own files and return finished work, and that is the gap a configured Claude workspace fills, which is what CoworkConsultant.com is hired to build.
Want it set up for you? Done-for-you builds by profession
The playbooks above show what a configured workspace looks like. These thirty pages show what CoworkConsultant.com builds for that profession, week by week, and which build fits.
- Law firms: intake, matter folders, document review, drafting from your precedents.
- Accountants and bookkeepers: month-end prep, client requests, review notes, engagement letters.
- Insurance agents: renewals, quote comparisons, claims follow-up.
- Real estate agents and brokerages: listing copy, lead follow-up, transaction checklists.
- Property managers: rent follow-up, maintenance triage, lease renewals, owner reports.
- Financial advisors: review prep packets, follow-up letters, document requests, notes to file.
- Marketing agencies: monthly reports from your exports, brief-to-draft in the client’s voice, proposals, status.
- Dental practices: recall and reactivation drafts, treatment follow-up, forms packets, review responses.
- Nonprofits and churches: grant reports, donor acknowledgments, board packets, program summaries.
- HR at a small business: job posts and scorecards, offers, onboarding packets, handbook answers.
- Ecommerce brands: product pages in your voice, customer replies, supplier emails, launch copy.
- Contractors and home services: estimates from your price book, follow-ups, invoice reminders, reviews.
- Recruiters and staffing firms: job order intake, candidate summaries, submittals, outreach, client updates.
- Business coaches: session prep, notes cleanup, follow-up emails, proposals, content.
- Veterinary clinics: reminders and recall, estimate notes, welcome packets, review replies.
- Restaurants: weekly numbers from POS exports, supplier emails, catering quotes, review responses, staff notes.
- Churches and ministries: bulletins, giving thank-you letters, newsletters, volunteer reminders, board packets.
- Independent consultants: proposals from your scope blocks, discovery synthesis, status reports, deliverables from your frameworks.
- Bookkeepers: uncategorised question lists, document requests, close checklists, month-end summaries, CPA handoffs.
- Medical practices: recall and no-show follow-up, intake packets, authorisation prep, balance reminders, review responses.
- Engineering and survey firms: comment-response letters, proposals from past work, permit tracking, timesheet checks.
- Architecture firms: OAC minutes, RFI and submittal drafts, fee proposals, code research summaries.
- Commercial contractors: bid leveling, RFIs, meeting minutes, pay applications, lien waiver tracking.
- Manufacturers and job shops: RFQ summaries, quote follow-ups, NCR write-ups, SOPs and work instructions.
- Wholesale distributors: quotes from emailed requests, order entry from customer emails, price increases, collections.
- IT providers and MSPs: ticket handoffs, QBR drafts, SOPs from rough notes, onboarding checklists.
- Real estate appraisers: order summaries, revision request responses, QC checklists, scheduling and invoices.
- Mortgage brokers: plain-English conditions lists, borrower and realtor updates, lead follow-up.
- Title and escrow companies: commitment summaries, curative checklists, status updates, payoff requests.
- Therapists and counseling practices: intake replies, credentialing dates, directory profiles, policies, with no client health information.
A playbook shows you the shape. A build makes it yours.
If you would rather have the workspace running than the reading done, that is the engagement: configured around your profession, your clients, and your review rules.
Book a free 20-minute callFor small teamsProof
What a real Claude build looks like, described by role. All case studies.
If your office is in a specific field, see Claude use cases by profession for 50 jobs written for your kind of work.
The owner's rules, written down and running every morning.
The owner used Claude every day, but every workflow lived in a chat window. Retyped each time, nothing ran on a schedule, nothing could be handed off.
A custom Claude plugin on the owner's computer: 7 commands, 7 skills, and a memory that holds the owner's rules. Version 2 installed in place two days after launch with zero conflicts.
6 days
signed to running
0
conflicts on upgrade
Weekly timesheets to a billing import, checked before it posts.
The office manager at an engineering and survey firm keyed every staff timesheet into the billing system by hand each week, then built the payroll file separately.
Claude reads the week's timesheets and builds one billing import and the payroll file. She previews both against her own numbers before anything posts. Claude never approves an invoice.
“My correspondence is just amazing. It's 10 times what it was.”
Built with the office manager, on her own PC, inside the firm's custom Claude plugin.
Owner, an engineering and survey firm
Read the case study →