Before you build anything, you need a clear way to talk about what AI changes inside a small company, which Claude product fits which problem, and what evidence backs your claims.
For a company of 10 to 200 people, AI transformation is not a moonshot. It is a sequence of small changes to how work gets done, each one measurable. The useful mental model has three levels.
| Level | Example in a 40-person distributor | Typical Claude product | What you measure |
|---|---|---|---|
| Assist | Sales reps ask Claude to draft replies to quotes | Claude app with a Project | Weekly active users, minutes saved per task |
| Augment | Incoming supplier invoices are extracted and pre-coded; a clerk reviews | API + a small Python service, or a Skill | Documents per hour, error rate |
| Automate | Every new lead is researched, scored and given a draft proposal overnight | Agent SDK + MCP to the CRM | Time to first response, conversion rate |
Value hides in tasks, not job titles. A finance clerk's job contains dozens of tasks; a few of them (matching invoices, chasing late payers, writing the monthly variance comment) are text-heavy, repetitive and rule-guided. Those are your targets.
A quick screen you can run in any client conversation. A task is a good first candidate when it scores yes on at least four of these:
| Function | Common first wins |
|---|---|
| Sales | Lead research, proposal drafts, CRM notes from calls, follow-up emails |
| Finance | Invoice extraction, payment reminders, month-end commentary, expense coding |
| Operations | SOP writing, supplier email triage, order exception handling |
| HR | Job posts, CV screening summaries, policy Q&A, onboarding packs |
| Customer service | Reply drafts, ticket triage, knowledge base answers in Hebrew, Russian and English |
| Management | Weekly business summary across tools, meeting notes to tasks |
Anthropic ships models in tiers. In October 2026 the public models are Claude Haiku 5.5, Claude Sonnet 5.5 and Claude Opus 5.5, plus Claude Fable 5.1 in the top Mythos tier with extra safeguards. Version numbers change; the tiers stay the same, so think in tiers.
| Task | Start with | Why |
|---|---|---|
| Classify 10,000 emails by topic | Haiku (via Batch API) | Simple decision, huge volume, cost dominates |
| Extract fields from invoices | Haiku or Sonnet | Try Haiku first, keep Sonnet for messy scans |
| Draft a proposal from notes | Sonnet | Writing quality matters, moderate volume |
| Agent that researches, plans and calls tools | Opus for the planner, Sonnet or Haiku for sub-steps | Planning errors are expensive; sub-steps are not |
| Coding with Claude Code | Sonnet or Opus | Depends on codebase size and task difficulty |
Exact prices, context windows and model IDs change. Always read the current models overview and pricing page before you put a number in a proposal.
Clients will hear brand names. You need to map each one to a job.
| Surface | What it is | Use it when the client needs |
|---|---|---|
| Claude app (web, desktop, mobile) | Chat plus Projects, artifacts, Docs, Slides, Sheets, research, memory, connectors, scheduled tasks | Fast adoption across a team with no code |
| Claude in Chrome | Claude acting in the user's own browser | Work in web tools that have no API or connector |
| Claude for Microsoft 365 | Claude inside Office apps | Teams that live in Word, Excel and Outlook |
| Claude Tag (Slack) | A shared, proactive agent in team channels | Team-wide assistance where conversations already happen |
| Claude Code | Agentic coding in terminal, IDE, web, desktop | Building and maintaining software, including your client deliveries |
| Claude API and Console | Programmatic access, keys, usage, workbench | Custom apps, integrations, batch processing |
| Claude Agent SDK / Managed Agents | Libraries and hosting for your own agents | Multi-step automations that run without a person in the chat |
| Claude Security | Finds and patches vulnerabilities in a codebase | Clients with in-house software and a security worry |
| MCP | Open protocol for connecting Claude to tools and data | Any of the above talking to the client's systems |
Skills, plugins, Projects and artifacts are capabilities inside these products, not separate products. "Claude for Financial Services" and similar names are packages of Claude for an industry.
The first three questions every owner asks: "Will it train on our data?", "Who can see what?", and "What does it cost per person?". Have a clear, sourced answer for each.
| Plan | Who it fits | Points to check in current terms |
|---|---|---|
| Pro / Max | Individuals, the owner, you | Consumer terms; model-training setting is the user's choice |
| Team | Small teams, the usual SMB starting point | Commercial terms, admin console, shared Projects, connectors |
| Enterprise | Larger or regulated clients | SSO, audit logs, retention controls, larger context, network controls |
| API | Custom builds | Commercial terms, retention options, usage-based billing |
The Anthropic Economic Index publishes how Claude is actually used, broken down by work task, occupation category and country (Israel included). It shows patterns of use, not job outcomes, and you should present it that way.
Three ways to use it in consulting:
Correct phrasing: "conversations matched to bookkeeping tasks", not "accountants use Claude".
Goal: feel the speed, cost and quality differences yourself, and start the Python repo you will use all course.
Setup
mkdir claude-transformation && cd claude-transformation
python -m venv .venv && source .venv/bin/activate
pip install anthropic python-dotenv
echo "ANTHROPIC_API_KEY=sk-ant-..." > .env # key from console.anthropic.com, set a monthly spend limit
compare_models.py
import os, time, json
from dotenv import load_dotenv
import anthropic
load_dotenv()
client = anthropic.Anthropic()
# Check current model IDs at docs.claude.com before running
MODELS = ["claude-haiku-5-5", "claude-sonnet-5-5"]
TASK = """You are helping a 40-person Israeli logistics company.
Below is a customer email. Return JSON with keys:
intent (quote|complaint|tracking|other), urgency (1-5), language,
summary (one sentence, English), draft_reply (in the customer's language).
EMAIL:
שלום, המשלוח שלנו לחיפה מתעכב כבר שלושה ימים ואנחנו צריכים אותו עד יום חמישי.
מה קורה? יוסי, מחסני הצפון"""
def run(model: str) -> dict:
start = time.perf_counter()
msg = client.messages.create(
model=model,
max_tokens=600,
messages=[{"role": "user", "content": TASK}],
)
elapsed = time.perf_counter() - start
return {
"model": model,
"seconds": round(elapsed, 2),
"input_tokens": msg.usage.input_tokens,
"output_tokens": msg.usage.output_tokens,
"text": msg.content[0].text,
}
if __name__ == "__main__":
results = [run(m) for m in MODELS]
for r in results:
print(f"\n=== {r['model']} {r['seconds']}s in={r['input_tokens']} out={r['output_tokens']}")
print(r["text"])
with open("results_lab1.json", "w", encoding="utf-8") as f:
json.dump(results, f, ensure_ascii=False, indent=2)
Steps
Part B (30 min): in the Claude app, use the Anthropic Economic Index connector (or the website) to find the top work tasks matched to two occupation categories your target clients employ, and Israel's usage index. Save the numbers and the date.
A single page you can send to a prospect after the first call. Write it with Claude, but every claim must be yours and sourced. Suggested structure:
Save it as a Claude Docs document or a one-page PDF. Keep an English version and plan a Hebrew one.