Everything you need to go from "I tried ChatGPT once" to running real AI workflows in your business — without hiring a developer or reading a manual.
Most people open Claude and start typing. That works for one-off questions. It doesn't work for running a business. Do this once — this weekend.
The web version works for basic use. The desktop app unlocks Cowork (autonomous tasks), local file access, Skills, and keyboard shortcuts. Install the app.
Why the desktop app? Cowork — Claude's autonomous mode — only works in the desktop app. You describe an outcome, approve a plan, and Claude executes it across your files for minutes or hours while you do other work.
The single most impactful step most people skip. Go to Settings → Profile → "What preferences should Claude consider?" Every conversation follows these rules automatically.
Example: "I run a 15-person e-commerce agency. Always give me the answer first, then explain. Never use corporate jargon. When I describe a problem, diagnose root cause before suggesting solutions."
Create a folder called "Claude-Business" on your computer with three markdown (.md) files. Upload these to every Project you create. This is what makes Claude actually understand your business.
Why markdown? Claude reads .md files natively and treats them as structured context — not as text to summarise. Your instructions stay active across the entire project.
Projects are persistent workspaces — every conversation has access to your uploaded files and follows your instructions. Start with your single most repetitive workflow.
Team plans: On Team or Enterprise, you can share Projects with your team. Viewer, Editor, or Admin access — Claude becomes a shared business asset, not a personal chatbot.
These aren't instructions — they're onboarding documents. Like hiring a new team member, you wouldn't give them a spreadsheet with no context. These files give Claude full context about your business.
The foundational document. Claude reads this before every conversation in any project where it's uploaded.
How Claude should behave across all your work. Prevents the frustrating defaults that make AI feel generic.
The file that makes Claude sound like you — not like AI. Paste real examples of your writing and describe your voice.
Copy, paste, adapt. Written for founders doing real work — not theory. Each includes a sample output so you know what to expect.
Describe something your team does repeatedly. Claude turns it into a structured SOP your team can actually follow.
You are a business operations specialist. I'll describe a process we do repeatedly. Turn it into a clear SOP with: (1) overview and purpose, (2) who is responsible, (3) step-by-step instructions numbered, (4) edge cases and what to do, (5) checklist at the end. Process to document: [describe what happens] Team members involved: [roles] Current bottleneck or failure point: [what goes wrong] Tools used: [software/tools]
SOP: Client Onboarding Process Purpose: Ensure every new client is set up within 48 hours of signing. Owner: Account Manager Steps: 1. Send welcome email (template in Drive) within 2 hours of signature 2. Create Notion workspace from template — invite client within 24h 3. Schedule kickoff call via Calendly link... Edge cases: Client doesn't respond to invite within 48h → escalate to AM lead...
Stop fixing symptoms. Use this to find the actual root cause of recurring operational problems.
You are an operations advisor. I have a recurring problem in my business. Use the 5 Whys method to help me find the root cause, then give me: (1) the most likely root cause, (2) two alternative causes I might be missing, (3) the fix for each — ranked by effort vs impact. The problem: [what keeps happening] How often: [frequency] Who's affected: [team/customers] What I've already tried: [previous fixes]
Paste your rough notes from a client call. Claude structures a professional proposal in your format.
Write a professional service proposal. Clear, direct — no filler. Structure: Executive Summary → Their Problem (use their exact words where possible) → Our Approach → Deliverables (numbered) → Timeline → Investment → Next Steps. Client: [name, company] What they told me their problem is: [their words] What we'll actually deliver: [scope] Timeline: [weeks/months] Investment: [price] One thing that would make them say no: [objection to pre-empt]
Three different response strategies — choose based on what you know about the prospect.
A prospect said our price is too high. Give me 3 different responses — each with a different strategy: (1) Reframe the ROI — make the cost feel small vs. the outcome (2) Diagnose — ask a question that uncovers if it's budget, trust, or urgency (3) Cost of inaction — what does NOT solving this actually cost them? Our price: [amount] What they get: [outcome, not features] Their exact words: [what they said] What I know about their budget: [context]
Stop getting 200 applications from unqualified candidates. Specificity is the filter.
Write a job description that attracts exactly the right person and filters out the wrong ones. Be specific about what success looks like in 90 days — not just a list of skills. No corporate clichés. Role: [title] What they'll do day-to-day (be specific): [actual tasks] What they must have done before: [non-negotiable experience] What success looks like at 30/60/90 days: [outcomes] Salary range: [range] Deal-breakers (what I don't want): [list] Our culture in 3 honest words: [words]
Paste your interview notes. Claude structures a scorecard and gives you a hire/no-hire recommendation with reasoning.
Based on my interview notes, score this candidate against the role requirements. Give me: (1) score out of 10 for each dimension, (2) top 3 signals that stood out — positive and negative, (3) the biggest risk if we hire them, (4) a hire/pass/strong hire recommendation with one-sentence reasoning. Role requirements: [paste JD or list] My interview notes: [paste raw notes] My gut feeling: [initial impression]
Paste your numbers. Claude tells you what's actually happening, what's concerning, and what to focus on this month.
You are a CFO advisor explaining financials to a founder who is not a finance expert. Analyse these numbers and tell me: (1) what's healthy, (2) what's concerning, (3) the ONE thing to focus on this month, (4) what question I should be asking that I'm not asking. [Paste your P&L or key numbers here] Also flag: anything unusual for a business at this stage and size.
What's healthy: Gross margin at 68% is solid for a services business. Revenue is up 18% MoM — good momentum. What's concerning: Your payroll cost jumped 34% while revenue grew 18%. That gap will compress margins if it continues. Focus this month: Understand why payroll outpaced revenue. Was it planned hires? If not, find the leak. Question you're not asking: What's your average revenue per employee, and is it trending up or down?
Claude asks you for inputs section by section, builds the forecast, and flags the weeks you should worry about.
Help me build a simple 12-week cash flow forecast. Ask me for inputs one section at a time — don't ask everything at once. After each section I answer, confirm you have what you need before moving to the next. Sections: (1) opening cash, (2) expected revenue by week, (3) fixed costs, (4) variable costs, (5) one-time large payments. Then build the table and tell me which weeks are concerning. My business type: [describe] Do I have seasonal patterns? [yes/no — describe]
No question hooks, no hashtags, no "I'm excited to share". Just a founder's perspective that builds real authority.
Write a LinkedIn post from this insight or story. Rules: (1) hook in the first line — make a statement, not a question, (2) under 200 words, (3) end with one clear takeaway — not a question, (4) no hashtags, (5) sound like a founder sharing hard-won experience. The insight or story: [describe what happened or what you learned] Who I'm writing for: [audience] The one thing I want them to take away: [the point] My tone: [direct / honest / slightly contrarian]
Each piece uses a genuinely different angle — not just a shortened version. Different hook, different audience, different format.
Repurpose this blog post into 5 formats, each with a DIFFERENT angle — not the same content in a different wrapper. Formats: (1) LinkedIn post — the contrarian take, (2) Email newsletter opener — the personal story angle, (3) Twitter/X thread — the tactical how-to, (4) 60-second video script — the problem/solution hook, (5) Pull quote for a graphic — the most shareable line. [Paste blog post here] My audience: [who reads this] Brand voice: [describe tone]
Get the skeptical investor take before you invest time building something.
Stress-test this idea like a skeptical investor. Cover: (1) who actually has this problem and how painful is it really, (2) why would someone pay vs do nothing, (3) the 3 most likely reasons this fails, (4) who I'm competing with including indirect alternatives, (5) what would have to be true for this to work. Be direct — I'd rather hear hard truths now. The idea: [describe] Target customer: [who] How they pay: [model] Why me: [unfair advantage]
Claude acts as a strategic advisor — section by section, honest read on what the numbers actually mean.
Run me through a structured quarterly business review as my strategic advisor. Ask me one section at a time and wait for my answers before moving on: (1) Revenue and goals — what we hit vs. planned, (2) What worked and why, (3) What didn't — root cause, not symptoms, (4) Customer insights from this quarter, (5) Team and operations health, (6) Top 3 priorities next quarter with reasoning. After I answer each section, give me your honest interpretation — don't just summarise what I said. Tell me what you actually think it means.
Paste a prompt that's giving you bad outputs. Claude diagnoses what's wrong and rewrites it.
I have a prompt that isn't giving me good results. Diagnose what's wrong with it and rewrite it. Tell me: (1) what's missing from the current prompt, (2) what ambiguity Claude has to guess at, (3) the rewritten version with your reasoning for each change. My original prompt: [paste it] What I got back: [paste the output] What I actually wanted: [describe]
Before giving any complex task to Claude, use this to turn your rough idea into a proper brief that gets good results first time.
I need to give Claude a task but I haven't thought it through properly. Interview me about the task — ask me the questions you'd need answered to do excellent work, one at a time. After I answer all of them, write the full brief you'd want to receive as if you were a contractor about to start work. The task I need done (rough version): [describe vaguely]
Skills are not prompts. A prompt is something you type every time. A Skill is something you install once and Claude applies automatically, every time it's relevant.
Think of Skills as hiring a specialist for a specific task — except you only have to brief them once. You upload a SKILL.md file that contains deep domain knowledge, formatting rules, and judgment instructions. Claude reads it and activates when the relevant task comes up.
The difference: Without a Skill, you re-explain context every time. With a Skill, Claude already knows your preferred proposal format, your SOP structure, your brand voice rules — without you saying anything.
Anthropic's Skills Directory has 11 built-in Skills. You can also create custom Skills for your specific business workflows. The best ones are reusable business logic that would otherwise live in your head.
Tip: If you find yourself copying the same instructions into multiple Projects, that's a signal to make it a Skill instead. Skills work across ALL conversations. Projects only work within one project.
| Built-in Skill | What it produces | Activates when you say |
|---|---|---|
| Proposal Writer | Structured client proposals with scoping, timeline, and pricing | "Write a proposal for..." |
| SOP Builder | Step-by-step SOPs with checklists and edge cases | "Document this process..." |
| Meeting Summariser | Action items, decisions, owners, deadlines from meeting notes | "Summarise this meeting..." |
| Job Description Writer | Role-specific JDs with 90-day success criteria | "Write a job description for..." |
| Financial Analyser | P&L interpretation with trends, flags, and recommendations | "Analyse these numbers..." |
| Email Drafter | Context-aware emails matching your writing style | "Write an email to..." |
| Content Repurposer | Multiple formats from one piece with genuinely different angles | "Repurpose this..." |
Regular Claude chat answers questions. Cowork executes work. You describe an outcome, approve the plan, then Claude works through it — reading files, creating documents, running analysis — while you do something else.
Real example: A 12-person agency drops 3 months of invoice exports into data/. Cowork ingests them, categorises by client and type, builds a margin analysis by project, flags underpriced work, and outputs a board-ready summary — in one session, no manual work. MEMORY.md remembers the categorisation rules for next month.
Claude Code is not a chatbot. It's a command-line tool that can read your entire codebase, write code, run tests, and deploy changes. Here's what that actually means for your business.
For everything that doesn't require custom software. Prompts, documents, analysis, automation workflows between existing tools. No code needed.
For simple custom tools — a booking form, a calculator, a basic dashboard. Claude Code can build these if you're willing to learn the basics of reviewing code output.
For real software — mobile apps, SaaS platforms, CRMs, AI tools, complex integrations. We use Claude Code + AI-assisted development to ship 50% faster than traditional dev.
The honest truth about Claude Code for founders: Claude Code is extraordinary for developers. For non-developers, it's a tool that generates code you can't fully evaluate — which is dangerous if you're building something real. The risk isn't that it won't work today. The risk is the architecture decisions made early that you'll pay for later. This is where we come in. Talk to us before you start building →
Pick the right model for the task. Wrong choice = slower results and wasted tokens. Here's the practical breakdown — no technical jargon.
| Business Task | Best Model | Why |
|---|---|---|
| High-value client proposal | Claude Opus 4.6 | Quality matters — worth the extra time |
| Daily emails and follow-ups | Claude Sonnet 4.6 | Fast, good quality, your default |
| Quarterly business review | Opus 4.6 + Deep Research | Complex reasoning + multi-source |
| Monthly P&L analysis | Claude Opus 4.6 | Financial reasoning is critical |
| LinkedIn and social content | Claude Sonnet 4.6 | Speed + quality, no need for Opus |
| SOP writing and team docs | Claude Sonnet 4.6 | Structured output at speed |
| Cowork autonomous tasks | Claude Sonnet 4.6 | Best balance for long running tasks |
| Anything client-facing | Human + any model | Always review before sending |
Projects aren't folders — they're persistent workspaces. Every conversation inside a project has your uploaded documents and follows your custom instructions automatically.
| Project | What to upload | Custom instructions | Best for |
|---|---|---|---|
| Sales & Proposals | Pricing sheet, proposal template, case studies, objection responses | "Write proposals in our template. Lead with outcomes. Never use the word 'leverage'." | Proposals, follow-ups, objection handling, RFP responses |
| Weekly Operations | SOPs, team org chart, KPIs, recurring agenda templates | "When I describe a problem, give root cause first. Always consider team capacity constraints." | Standup agendas, process docs, team decisions, SOP creation |
| Hiring & HR | Culture doc, job descriptions, interview scorecards, offer template | "Our values: directness, ownership, curiosity. Filter candidates against these. No jargon." | JDs, interview questions, offer letters, onboarding docs |
| Finance Review | P&L template, last 3 months actuals, budget, chart of accounts | "When I share numbers: compare to prior period, flag anything unusual, give me one focus." | Monthly P&L, cash flow, budget planning, investor updates |
| Content & Marketing | Brand voice guide, top 5 posts, customer testimonials, competitor notes | "Write in my voice (samples uploaded). No question hooks. No hashtags. Specific, not vague." | Blog posts, social content, email campaigns, ad copy |
| Customer Success | FAQ doc, product docs, common objections, escalation process | "Resolve in one reply. Be warm but concise. Always end with a clear next step." | Customer emails, support responses, renewal conversations |
Any guide that doesn't tell you the limitations is selling you something. These are real constraints — know them before you rely on Claude for critical work.
Most founders who say "AI doesn't work for me" are making one of these seven mistakes. Fix these and the results change immediately.
Typing short queries expecting magic answers. "Write me a proposal" gives you a generic template. Claude needs context, constraints, and a clear output format.
Starting every conversation from scratch. Claude doesn't know your business, your style, or how you like to work — unless you tell it once in Preferences.
Claude's first response is a draft, not a finished product. The output gets dramatically better with one or two specific rounds of feedback.
The real value is in systematic use — Projects, Skills, recurring workflows. Using Claude for occasional tasks is like hiring a consultant for one call and ignoring them.
Claude can be confidently wrong. Spelling errors, incorrect facts, wrong tone. Sending unreviewed output damages your reputation and can create legal exposure.
"Write me a proposal, also check for errors, also make it shorter, also add a risk section" produces mediocre results for all of them.
Claude amplifies your thinking — it doesn't replace it. If you don't know what a good proposal looks like, Claude can't write you one. Garbage in, garbage out.
Prompts are easy. Skills help. But building an actual AI system in your business — agents, workflows, integrations — requires architecture decisions that are hard to undo.
Every time Claude releases something new, the terminology gets more confusing. Here's every term you'll encounter — explained for founders, not developers.
Everyone says they use AI. Here's the honest comparison of how traditional development, no-code, and AI-powered development actually differ — in time, cost, and what you get.
We use AI as infrastructure in our development process — not as a gimmick. Every project at Phos uses a stack of AI tools that we've spent years refining: Claude Code for development, Cursor AI for code review, n8n for automation architecture, and our own QA processes on top.
The result isn't "AI-generated code we ship and hope for the best." It's properly architected software built by experienced developers who use AI to move 2–3x faster — and pass that speed advantage to clients in cost and timeline.
The thing most founders miss: Claude can write code. Claude Code can build features. But the architecture decisions made in week one determine whether your product scales or breaks at 1,000 users. That's the part that requires human expertise — and that's what we bring.
Not chatbots. Not automations. AI employees — custom-built agents that handle entire roles: responding to customers, qualifying leads, processing applications, managing inventory alerts, and more.
Claude and similar models are powerful — but a general-purpose AI assistant is not the same as an AI built specifically for your business, trained on your data, integrated with your systems, and designed to do one job extremely well.
We build custom AI employees — agents with a defined role, connected to your CRM, your database, your email, your Slack. They work 24/7, handle volume your team can't, escalate intelligently, and get better over time.
The founders seeing the biggest ROI from AI right now aren't just using better prompts. They're replacing specific, defined job functions with AI — not augmenting them.
Answer 7 questions and find out exactly where to start — and what to build or fix first in your business.
7 questions · 2 minutes · Personalised recommendation
You can use Claude today to write better emails, analyse your P&L, and draft proposals. This guide gives you everything you need for that.
But when you're ready to build something with AI — a custom app, an AI employee, an automated workflow connected to your systems — the prompting part is the easy 10%. The 90% is architecture, integration, reliability engineering, and knowing which decisions you'll regret in 6 months.
That's what we do. We've built it before. We can build it faster and cheaper than traditional development — and we'll make sure it's built right.