Internal · Operations · Q1 Review

Which AI model should
we standardize on?

A recommendation for a 60-person company with mostly non-technical users, limited IT bandwidth, and real customer data to protect.

Prepared by Ops Lead For Leadership ~12 min read
01 · Framing

The question, and how we'll answer it.

What leadership asked

"Everyone's using a different AI tool. Pick one, roll it out, and tell us what it'll cost."

What "standardize" means here: one default model for daily work, one approved vendor relationship, one set of usage rules. It does not mean banning every other tool — it means having a clear primary.

Decision criteria (weighted)

  • Quality for our actual work 35%
    Writing, summarization, analysis, light coding
  • Ease for non-technical users 25%
    If it needs a prompt engineer, it fails
  • Cost predictability 20%
    No surprise $8k months
  • Privacy & compliance 15%
    Customer PII, NDAs, EU customers
  • Switching risk 5%
    Can we leave in 12 months?
  • 02 · Context

    Who we are — and what we'd actually use AI for.

    60
    Employees
    ~40
    Likely daily AI users
    8
    Eng / product / data
    52
    Non-technical roles

    Top real use cases (from team survey)

    • Drafting client emails & proposals — sales, CS, account mgmt
    • Summarizing long docs & meetings — ops, legal, execs
    • Spreadsheet formulas & light analysis — finance, ops
    • Marketing copy, social, blog drafts
    • Code review, SQL, scripting — the 8 technical folks
    • Reading / querying PDFs & contracts — long context

    Constraints we can't ignore

    • No dedicated ML/AI team. IT is 2 people.
    • We handle customer PII (names, emails, some financials).
    • ~30% of revenue is from EU customers (GDPR matters).
    • Budget ceiling for year one: $30k all-in.
    • Most staff will not read a 20-page prompt guide. The tool has to just work.
    03 · Landscape

    The serious contenders, as of early 2025.

    Pricing and capability notes are based on publicly listed rates and my own testing; prices shift quarterly. I've flagged where I'm approximating.

    ModelVendorStrengthWeaknessInput $/M tokOutput $/M tok
    Claude 3.5 SonnetAnthropicWriting, long-doc reasoning, instruction-followingMultimodal weaker than GPT-4o; no image gen$3.00$15.00
    Claude 3.5 HaikuAnthropicCheap, fast, good enough for routine tasksNoticeably dumber on hard reasoning$0.80$4.00
    GPT-4oOpenAIMultimodal, broadest plugin ecosystem, codingWriting voice more generic; pricier than it looks$2.50$10.00
    GPT-4o-miniOpenAIDirt cheap for high-volume low-stakes workStruggles with nuance and long docs$0.15$0.60
    o1 / o3OpenAIHard reasoning, math, scienceVery expensive, slow, overkill for 95% of our work$15$60
    Gemini 2.0 FlashGoogleHuge context (1M+ tok), fast, cheapCan feel less careful; ecosystem more fragmented$0.10$0.40
    Gemini 1.5 ProGoogleLongest usable context window todayOutput quality inconsistent vs. Claude/GPT on prose$1.25$5.00
    Llama 3.3 70BMeta (open)Self-hostable, no data leaves our networkSmaller context, weaker at subtle writing, needs infra~$0.20 via API, or capex

    I excluded: Claude Opus (too expensive for daily use), Mistral Large (good, but no clear edge over the above for us), Grok (not serious for enterprise), and the long tail of smaller open models.

    04 · Capability

    How they actually perform on our work.

    Subjective 0–10 scores from running the same 20-task benchmark across our real use cases (emails, summaries, SQL, contract Q&A, image-to-text).

    Capability scores (0–10) 0 2 4 6 8 10 Writing Reasoning Coding Multimodal
    Claude Sonnet GPT-4o Gemini 2.0 Flash Llama 3.3 70B

    Reading the chart

    No model wins everywhere. The honest summary:

    • Claude Sonnet is the best writer and the most reliable on long, careful documents — which is most of what our 52 non-technical people do all day.
    • GPT-4o wins on multimodal (images, screenshots, diagrams) and is a hair better at coding — relevant to the 8-person technical team.
    • Gemini Flash is shockingly cheap and handles enormous context, but its prose is less polished and occasionally sloppy.
    • Llama 3.3 70B is the only option where data truly never leaves our network. It's meaningfully weaker at writing and multimodal.

    The gap between the top three is small enough that how the tool feels to a non-technical user matters more than benchmark scores. That favors Claude and GPT's first-party UIs.

    05 · Cost

    What a year actually costs — at our scale.

    Estimated Year-1 cost by option (USD, all-in) Assumes 40 active users, moderate usage Claude Team (Sonnet) $14,400 + GPT Plus for 8 tech staff $1,920 Self-hosted Llama (PII work) $4,500 Training, rollout, buffer $3,000 Year 1 total: ~$23,800 well under the $30k ceiling

    Why this shape

    • Claude Team at $30/user/month for 40 people = $14.4k/yr. Predictable, no token math, no surprise invoices.
    • GPT Plus at $20/user/month for the 8 technical folks who need multimodal + coding = $1.9k/yr.
    • Self-hosted Llama on a used RTX 4090 workstation (~$3.5k one-time) + ~$50/mo power. Used only for PII-touching workflows.
    • Training budget for two half-day workshops and a written playbook.

    Honest caveat: if usage runs hot (e.g., sales starts auto-generating 500 proposals/week), API-based plans can spike. The Team/Plus flat-rate plans cap that risk — which is why I'm recommending them over raw API access for most staff.

    Compared against: going full API on Claude Sonnet at our estimated volume (~$18k/yr but volatile), or giving everyone GPT-4o API access (~$22k/yr, also volatile).

    06 · Privacy

    Where customer data is allowed to go.

    Model / planTraining on our data?EU optionsSelf-hostableVerdict for PII
    Claude Team / EnterpriseNo (contractual)Yes, EU data residency available on EnterpriseNoOK with policy
    GPT Plus / TeamNo on Team/Enterprise; yes by default on free/PlusLimitedNoTeam plan only
    Gemini (Workspace add-on)No when via WorkspaceYesNoOK via Workspace
    Llama 3.3 70B (self-hosted)N/A — runs on our boxN/AYesBest for sensitive
    Free / consumer tiersUsually yesUnclearNoDo not use

    Our policy (proposed)

    • Green: public info, internal drafts, generic analysis → any approved model.
    • Yellow: customer names, emails, contract text → Claude Team or GPT Team only (no-training contracts).
    • Red: financials, health data, auth credentials, anything we'd be breached for → self-hosted Llama only, or don't use AI.

    The uncomfortable truth

    Policies only work if they're easy to follow. That's why the default tool people open in the morning has to be one of the green/yellow-safe options — not a consumer-tier ChatGPT login they set up themselves.

    Shadow AI (employees pasting customer data into free tools) is the real risk. Standardization is mostly a shadow-AI-reduction project.

    07 · Usability

    Will a non-technical team actually use it?

    Usability for non-technical users (0–10) First-party chat UI, no setup, no prompt engineering needed Claude.ai (Sonnet) 9.0 ChatGPT (GPT-4o) 9.0 Gemini (Web) 8.0 Llama via Open WebUI 5.0 Raw API / Postman 2.0

    What non-technical users actually need

    • A web page they can bookmark. No CLI, no API keys.
    • Drag-and-drop for PDFs and images.
    • Decent memory across a conversation (projects, threads).
    • One click to share a conversation with a coworker.
    • SSO login — not another password.

    Claude and ChatGPT are effectively tied here. Both ship polished first-party UIs with projects, file upload, and SSO on their team plans. Gemini is close. Self-hosted Llama requires IT to maintain a UI — which is fine for 8 engineers, wrong for 52 everyone-elses.

    08 · Recommendation

    The call.

    Primary standard

    Claude Sonnet, via Claude Team.

    For every employee, as the default tool they open first thing. Best writing quality for our use cases, flat-rate pricing that won't surprise finance, no-training contract, SSO, and a UI a non-technical team will actually adopt.

    Default: Claude Sonnet — 60 seats
    Technical add-on: GPT Plus — 8 seats
    Sensitive data: Self-hosted Llama 3.3 70B

    Why not GPT-4o as the default?

    Close second. For a 60-person company whose work is mostly writing and summarization, Claude's output reads more like a human colleague and less like "AI copy." That difference compounds across 40 users every day. GPT-4o stays in the stack for the technical team where it's genuinely stronger.

    Why not Gemini — it's cheaper?

    Flash is 30× cheaper per token, yes. But flat-rate Team plans erase that advantage at our usage levels, and Gemini's UI and output polish are a step behind for non-technical users. Worth revisiting in 6 months — Google moves fast.

    Why not 100% self-hosted?

    Tempting for privacy. Realistic answer: we don't have the IT staff to run a reliable self-hosted stack for 60 people, and the quality gap would drive everyone back to shadow AI. Self-host the 5% of work that's genuinely sensitive; use a vendor for the rest.

    09 · Rollout

    How we ship it in 90 days.

    Week 1–2

    Procure & configure

    Sign Claude Team contract, GPT Plus for 8, buy the 4090 workstation. Wire SSO. Draft acceptable-use policy.

    Week 3–4

    Pilot (12 people)

    2 from each function. Collect real prompts, failure modes, and the questions people actually ask IT.

    Week 5–6

    Playbook & training

    Write a 4-page internal playbook. Run two 90-min workshops. Record them. Ship a "prompt library" of our 20 most common tasks.

    Week 7–10

    Company-wide rollout

    Open to all 60. Weekly 30-min office hours for the first month. Slack channel for questions.

    Week 12

    Review

    Usage, cost, incidents, NPS. Decide whether to expand GPT seats, add Gemini, or tighten policy.

    Success metrics

    • Adoption: ≥70% of staff active weekly by day 60.
    • Shadow AI reduction: self-reported use of unapproved tools ↓50%.
    • Time saved: ≥2 hrs/user/week on drafting & summarization (survey).
    • Cost: stays under $2k/month all-in.
    • Incidents: zero confirmed PII leaks to unapproved models.

    Who owns what

    • Ops lead (me): vendor relationship, policy, rollout.
    • IT (2): SSO, Llama box, offboarding.
    • People/HR: training scheduling, acceptable-use sign-off.
    • Each team lead: identify 2–3 workflow-specific prompts to standardize.
    • Legal: review the vendor DPA and our customer-facing AI disclosure.
    10 · Risks

    What could go wrong, and what we do about it.

    Risk
    Why it matters
    Mitigation
    Vendor lock-in
    Anthropic raises prices or degrades the product.
    Keep prompts & workflows in plain text, not Claude-specific features. Re-evaluate at 6 and 12 months. GPT-4o is already a warm backup.
    Model regression
    Vendors update models and our favorite prompts break.
    Maintain a 10-task regression suite. Pin to a named model version where the vendor allows it.
    Hallucinations in customer-facing content
    Sales sends an AI-drafted claim we can't support.
    Policy: anything sent externally must be human-reviewed. Add a footer watermark prompt for drafts.
    Shadow AI
    Employees paste PII into free ChatGPT / Gemini accounts.
    Make the approved tool easier to use than the shadow one. SSO + bookmarks + training. Quarterly audit of browser extensions on company devices.
    Regulatory change (EU AI Act, GDPR guidance)
    New rules on disclosure or data use.
    Legal review quarterly. Our "red data stays on Llama" rule already covers the strictest plausible interpretation.
    Over-reliance / skill atrophy
    Junior staff stop learning the underlying work.
    Managers flag this in 1:1s. Training includes "when not to use AI."
    11 · The Ask

    What I need from leadership today.

    • Approve Claude Team as the company-wide default — 60 seats, ~$14.4k/yr.
    • Approve GPT Plus for the 8-person technical team — ~$1.9k/yr.
    • Approve a one-time $4.5k for the self-hosted Llama workstation for PII work.
    • Sign off on the acceptable-use policy (draft attached) before rollout.
    • Greenlight the 90-day timeline with the first pilot starting next Monday.

    Total Year-1 ask: ~$23,800.
    $6,200 under the ceiling. Review at 6 months; cancel or switch if adoption <50% or cost overruns >20%.

    What this is not

    • Not a permanent lock-in. We review at 6 and 12 months and can switch primary vendors with ~2 weeks of work.
    • Not a ban on other tools — it's a clear default with an exceptions process.
    • Not an "AI transformation" project. It's an ops project: give people one good tool, one policy, one place to ask questions.

    Open questions for the room

    • Do we want to disclose AI use to customers by default, or only on request?
    • Should the CEO's exec assistant be in the pilot group? (High leverage.)
    • Any customer contracts that explicitly prohibit AI processing we need to check first?
    01 / 12