Build the Business Case

The Scenario

You've been using Cowork for eight weeks. You know it saves time. You feel more productive. But when your CFO asks "what's the return on this investment?" you can't give a number. "It just feels faster" isn't a business case.

Your CEO has scheduled a 15-minute slot at next month's leadership meeting for you to present the case for expanding Cowork licences from 10 pilot users to 60 across the department. She wants numbers. Not testimonials, not demos — a quantified return on investment that she can compare against other technology investments competing for the same budget.

Today, you're going to build that business case. You'll set up a time-tracking framework, calculate ROI using a methodology your finance team will respect, and produce a presentation deck that turns "it feels faster" into "here's the measurable return per pound invested."

Prerequisites

• Claude Desktop with Cowork enabled (Pro or Max plan)
• At least 2-4 weeks of Cowork usage history (the more data, the stronger the case)
• A working folder for the project
• 5 real tasks you've completed both with and without Cowork (or can complete during this tutorial)
• Knowledge of your organisation's licence costs (or use the published pricing)

Step 1: Set Up the Time-Tracking Framework

Create a folder called Business-Case/ with subfolders:

• data/ — for your tracking spreadsheet and raw data
• analysis/ — for calculations and charts
• presentation/ — for the final deck

Create a time-tracking spreadsheet (CSV or Excel) with these columns:

Categories to use:

• Document creation (reports, emails, proposals)
• Data analysis (spreadsheet processing, trend analysis)
• File management (organising, renaming, batch processing)
• Meeting prep (agendas, briefing docs, presentation drafts)
• Communication (email drafts, Slack messages, client updates)
• Research and synthesis (summarising documents, competitive analysis)

Checkpoint: Your tracking spreadsheet is created with the correct columns and category definitions.

Step 2: Populate with Real Data

Fill in your spreadsheet with at least 5 tasks — ideally 10-15 for a stronger case. For each task:

If you completed the task both ways (manually and with Cowork): Record the actual times for both. This is your strongest evidence.

If you only completed the task with Cowork: Estimate how long it would have taken manually. Be conservative — overestimating manual time undermines your credibility. Base estimates on:

• Historical time for similar tasks before you had Cowork
• Ask a colleague who doesn't use Cowork how long it takes them
• Time yourself doing a comparable task without AI assistance

If you haven't tracked enough tasks yet: Run 5 tasks now, timing each one. Choose tasks from different categories:

1. Document creation: Draft a quarterly update email to a client (time both Cowork and manual)
2. Data analysis: Process a CSV file into a summary report with key metrics
3. File management: Organise a folder of 20+ mixed files into logical subfolders
4. Meeting prep: Create a briefing document for an upcoming meeting
5. Research: Summarise a 10+ page document into a one-page executive brief

For each task, record:

• The start and end time for both methods
• A quality score: was the Cowork output equal to, better than, or worse than what you'd produce manually?

Checkpoint: Your spreadsheet contains at least 5 documented tasks with both manual and Cowork times, and quality scores.

Step 3: Calculate the Core Metrics

Using your data, calculate:

Average time saved per task: Sum of all time-saved values divided by number of tasks. Express in minutes and as a percentage of manual time.

Weighted time saved per category: Calculate the average time saved for each category. Some categories will show larger savings than others — data analysis and file management typically save more time than creative writing tasks.

Quality-adjusted savings: If any tasks scored below 4 on quality, add estimated correction time:

• Quality 4: Add 5 minutes for minor edits
• Quality 3: Add 15 minutes for moderate editing
• Quality 2: Add 30 minutes for significant rework
• Quality 1: Task produced no usable output — time saved is zero

Recalculate time saved after quality adjustment. This is your conservative, defensible number.

Weekly time saved per person: Estimate how many Cowork-eligible tasks each team member completes per week. Multiply by average quality-adjusted time saved per task.

Example: If the average team member completes 8 Cowork-eligible tasks per week and saves an average of 18 minutes per task, that's 144 minutes (2.4 hours) saved per person per week.

Checkpoint: You've calculated average time saved per task, category-level savings, quality-adjusted figures, and weekly per-person projections.

Step 4: Build the ROI Calculation

Now translate time savings into financial returns. Create this calculation in your analysis/ folder:

Cost side:

Use your actual licence cost. If expanding from 10 to 60 seats on Team Premium at $150/seat:

• 60 seats x $150 = $9,000/month = ~£7,200/month (adjust for current exchange rate)

Include training time: if onboarding takes 4 hours per person at an average internal cost of £50/hour, that's £12,000 one-off for 60 people.

Benefit side:

For fully-loaded hourly cost, use your organisation's standard rate (typically salary + benefits + overhead, divided by working hours). If you don't know this, use a conservative estimate — £40-60/hour for mid-level professionals in the UK is reasonable.

ROI formula:

ROI = (Annual Benefits - Annual Costs) / Annual Costs x 100

Payback period:

Payback = Total First-Year Costs / Monthly Benefits

Checkpoint: You have a complete ROI calculation with costs, benefits, ROI percentage, and payback period.

Step 5: Address the Objections

Every business case faces scepticism. Pre-empt the common objections:

"The time savings are self-reported and unreliable." Response: Acknowledge this, then explain your methodology — timed tasks, quality adjustment, conservative estimates. Offer to run a controlled pilot with independent time tracking.

"What if Anthropic raises prices?" Response: Model a 20% price increase scenario and show the ROI still holds. If it doesn't, note the price sensitivity.

"What about security risks?" Response: Reference the security framework from your rollout playbook. Summarise the key controls: dedicated working folders, no regulated data, human review gate, Computer Use disabled by default.

"What about the risk of poor quality output?" Response: Present your quality scores. Show that X% of outputs required minimal editing. Acknowledge the human review requirement and factor its time cost into the benefits calculation.

"Why not use ChatGPT/Copilot/Gemini — they might be cheaper." Response: If you have comparative data, present it. If not, note Cowork's specific advantages for your use cases (direct file access, sub-agent parallelism, scheduling, connectors for your tool stack). Avoid a features arms race — focus on which tool best fits your team's actual workflows.

Document these objection-response pairs in your business case.

Checkpoint: You've written responses to at least 5 common objections with specific data or reasoning.

Step 6: Build the Presentation Deck

Now produce the actual deliverable — a slide deck for the leadership meeting. Ask Cowork to help, but drive the content yourself (you know the numbers better than anyone):

Slide structure (8-10 slides, 15 minutes):

1. Title slide: "The Case for Cowork: Measured Returns from the Pilot"
2. The opportunity: One sentence on what Cowork does, positioned as a productivity tool (not a toy)
3. Pilot results: Summary metrics — tasks tested, average time saved, quality scores
4. Time savings by category: Chart showing which task types benefit most
5. ROI calculation: Costs vs benefits, ROI percentage, payback period
6. Scaled projection: What the numbers look like for 60 people (extrapolated from pilot data)
7. Risk mitigations: Security framework, quality gates, known limitations
8. Objection responses: The top 3 objections addressed in one slide
9. Recommendation: Specific ask — how many seats, which plan, what timeline
10. Appendix: Detailed methodology, full data table, assumption list

For the presentation itself, ask Cowork:

Using the data in data/time-tracking.csv and the ROI calculations in analysis/roi-calculation.md, create a 10-slide presentation deck saved as presentation/cowork-business-case.pptx. Follow the slide structure I provide. Use British English. Keep each slide to a maximum of 5 bullet points. Include a chart on slide 4 showing time savings by category.

Checkpoint: The presentation deck has been created with data-driven content across all slides.

Step 7: Quality-Check the Numbers

This is non-negotiable. Before presenting to leadership, verify every number in the deck:

• Cross-check the summary metrics against your raw spreadsheet
• Verify the ROI calculation manually (calculator, not Cowork)
• Confirm the scaled projection uses the correct multiplier
• Check that charts accurately represent the underlying data
• Ensure cost figures use the correct licence pricing

If you find errors, correct them and regenerate the relevant slides.

Checkpoint: Every number in the presentation has been manually verified against source data.

Step 8: Prepare the Supporting Package

The deck gets you the 15-minute slot. The supporting package closes the deal. Create:

Executive summary (one page):

• The ask (60 seats, Team Premium, £X/year)
• The return (£X saved per year, X% ROI, X-month payback)
• The risk (security framework in place, quality gates defined)
• The next step (approve by [date], rollout begins [date])

Detailed methodology document:

• How you measured time savings
• How you calculated ROI
• All assumptions listed explicitly
• Sensitivity analysis (what if savings are 25% lower? What if costs increase 20%?)

Appendix with raw data:

• Full time-tracking spreadsheet
• Complete ROI model
• Quality scores for every task

Save everything in your Business-Case/ folder, organised for easy sharing.

Checkpoint: Supporting package is complete — executive summary, methodology, and raw data appendix.

Expected Output

Your deliverable is a complete business case package:

• data/time-tracking.csv — raw time-tracking data for 5-15 tasks
• analysis/roi-calculation.md — detailed cost-benefit analysis with ROI and payback period
• presentation/cowork-business-case.pptx — 10-slide leadership deck with charts
• executive-summary.md — one-page summary with the ask and the return
• methodology.md — how you measured, what you assumed, sensitivity analysis

This isn't a "Cowork is great" pitch. It's a financial case built on measured data, conservative assumptions, and pre-addressed objections. The kind of document that gets budget approved.

Extension Challenges

1. Competitive analysis slide — Add a slide comparing Cowork's cost and capabilities against ChatGPT Enterprise, Microsoft Copilot, and Google Gemini for Business. Use published pricing and feature sets. Focus on which tool best fits your team's specific workflows, not general capability comparisons.

2. 12-month projection model — Extend the ROI calculation to include adoption curve effects. Month 1-3 has lower savings (learning curve), months 4-8 reach full productivity, months 9-12 include efficiency improvements from accumulated context files and skills. Plot the cumulative ROI over 12 months.

3. Department-specific ROI — If your organisation has multiple departments interested in Cowork, calculate separate ROI figures for each based on their specific task mix and hourly rates. A finance team's time is costed differently from a marketing team's. Show the total organisational return as the sum of department-level cases.