sharper ACADEMY
AI training. Built around your people.

Give your team the skills to put AI to work.

Self-paced AI training for your whole team. Add AI Adoption, Live for hands-on guidance as your people put it to work.

Learn More Find your team’s training
Read the executive brief

Know what to hand over.

Spot useful tasks for AI and keep human judgment where it belongs.

Make something useful.

Turn a clear brief and the right context into work your team can build on.

Stand behind the result.

Check the sources, challenge the answer, and own what gets shared.

YOUR TOOLS. YOUR TEAM’S WORK.

Build on the systems
you already use.

AI assistants

ChatGPTClaudeGeminiMicrosoft Copilot

Everyday work

Microsoft 365Google WorkspaceSlackNotion

Sales & automation

SalesforceHubSpotZapiern8n

Finance & ERP

QuickBooksNetSuiteSage IntacctXero
THE TRAINING TRACKS

One foundation.
Every role.

Start together with Foundations. Then go deeper by role.

For your whole teamPut AI
to work.SHARPER ACADEMY ↗

AI Foundations

Give everyone a shared way to use AI, check its work, and put it into practice.

Sales teamsWalk in
prepared. 1:48SHARPER ACADEMY ↗

AI for Sales

Marketing teamsOne idea.
More content.SHARPER ACADEMY ↗

AI for Marketing

Operations teamsMake repeat
work easier.SHARPER ACADEMY ↗

AI for Operations

Finance teamsFrom numbers
to insight. 1:28SHARPER ACADEMY ↗

AI for Finance

People teamsA better
first day.SHARPER ACADEMY ↗

AI for People & HR

Leadership teamsSee what
needs you.SHARPER ACADEMY ↗

AI for Leadership

People managersSet the
standard.SHARPER ACADEMY ↗

AI for Managers

Hands-on buildersYour first
automation.SHARPER ACADEMY ↗

AI for Builders

EOS companiesYour system.
In sync.SHARPER ACADEMY ↗

AI for Companies Running on EOS

FROM LEARNING TO DOING

Start with everyone.
Go deeper from there.

Self-paced. Practical. Built around the working day.

01 /

Build a shared foundation.

AI Foundations for your whole team, with a companion introduction for managers.

02 /

Go deeper by role.

Help each department apply AI to the work it knows best.

03 /

Make it part of the culture.

Add AI Adoption, Live to help managers address hesitation, share useful examples, and build habits that last.

AI Adoption, Live · private company program

Get people excited.
Help them get unstuck.

Show your people what’s possible, then help them apply it to their own work. Private AI demonstrations and office hours give your company a regular rhythm of practice, questions, and visible progress.

Show what’s possible

A company AI demo every month.

Relevant workflows, live questions, and employee wins. Give people examples they recognize and a practical next thing to try.

Work through the details

Two private office hours each month.

Bring a task, a disappointing answer, or a workflow that’s stuck. Pair with an experienced facilitator and leave with a useful next step.

Help leaders act

A sponsor check-in and recap.

Understand hesitation, surface recurring blockers, and choose next month’s focus. Give managers concrete examples and actions to carry forward.

Optional with annual Academy · priced per company.

A monthly demo, two office hours, a sponsor check-in, and a practical recap.

Explore AI Adoption, Live ↗

Private to your company, delivered by trained AI facilitators using a consistent program. Academy seats are separate. Implementation projects, policy development, and fractional CAIO leadership are separately scoped.

THE PEOPLE BEHIND THE TRAINING

Built by people who’ve
run the business.

Operators who’ve led teams and put AI to work inside businesses.

Chris Dumas

Chris Dumas

CEO & co-founder, Sharper AI

Has held CEO and COO roles across media, AI agencies, marketing, and legal companies. Brings the perspective of the leader responsible for the team and the work.

Ryan O'Connor

Ryan O'Connor

Principal AI operator & co-founder

A product leader across life sciences companies, working at the forefront of AI for several years. Builds the Academy curriculum and leads client rollouts.

A FEW GOOD QUESTIONS

Before you bring
the team.

Who is Sharper Academy for?

Teams that want to use AI in everyday work. Start with Foundations, then specialize by role.

How is the training delivered?

Self-paced video with practical work you complete as you watch. Guided support is available separately.

Which AI tools does it cover?

Tools such as Claude, ChatGPT, Microsoft 365, and Google Workspace. We confirm coverage for your stack before you start.

How does our company’s AI policy fit in?

Foundations teaches what to share, check, and approve. We discuss your policy during planning; policy development is a separate option.

Where does our team start?

Foundations gives everyone shared skills. Department tracks then take people deeper into their own work.

How will we judge what people learned?

Review the eight practical outputs people create in Foundations. Human-reviewed certification is an additional option.

What does team training cost?

Pricing depends on team size, tracks, and support. We’ll scope those together on your call.

How do we choose the right tracks?

Start with Foundations. We’ll help you choose department tracks and confirm availability.

YOUR PEOPLE. THEIR NEXT CHAPTER.

Build a training plan
for your team.

See the training live. We’ll walk you through it and discuss the right fit for your team.

Learn More Share the executive brief
Learn More
Explore the track
For your whole teamPut AI
to work.SHARPER ACADEMY ↗

AI Foundations

A shared foundation for everyone on your team. Learn what to hand over, how to ask, and what to check.

Learn More

Who it’s for

Everyone on your team, with a companion introduction for managers.

Key takeaways

  • Decide which tasks to delegate and which to keep.
  • Give AI a useful brief and the right company context.
  • Check the result and take responsibility for the work you share.

Example tools

  • Claude
  • ChatGPT
  • Microsoft Copilot
  • Gemini

A few examples, not an exhaustive list.

Inside the course

One practical course, from your first useful result to a repeatable workflow. Each part builds on the work you did before it.

Welcome, and what this thing isWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Turn a messy note into a useful first draft and check it against what you know.
  • Understand why AI can sound confident while guessing.
  • Map real tasks into what to hand over, what to keep, and what needs a closer look.

What you’ll create

Your trust map: two weeks of real work, each item marked hand over, keep, or not sure.

The four ways it's wrongWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Name the four failure signatures: it made it up, it wasn't there, it lost the thread, it heard something else.
  • Diagnose a bad answer as one of the four, or two at once.
  • Know the fix for each, so the second try is a different try instead of the same one louder.

What you’ll create

Your diagnosis card: the four signatures in your words, with one example of each from your own work.

Brief it like a personWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Write an ask with the goal, the audience, the context, the constraints, and an example of good, on purpose.
  • Make it interview you before it writes when the task is worth it.
  • Refine in the same chat instead of starting over or fixing the answer by hand.

What you’ll create

Your brief: one real ask from your trust map, rewritten with the five parts, saved beside the cold version and the result of each.

Hand it the thingWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Hand it a PDF, a spreadsheet, or a screenshot, and always ask for the page or the cell.
  • Get a real file back and open it where you actually work.
  • Check one thing in every deliverable against the source before you use it.

What you’ll create

One real deliverable, made from your own material, opened in the real app, with one thing checked against the source.

Give it your companyWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Set up a project with standing instructions and approved company documents.
  • Check citations and keep shared information current.
  • Understand the different roles of projects, profile, memory, and connectors.

What you’ll create

Your project: instructions plus your real knowledge loaded, and the first answer that cites your own document, saved.

Check what comes backWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Run the thirty-second check before anything ships: write your answer first, name the one detail it could have invented, verify that one.
  • Make it disagree with you, and know why it flatters by default.
  • Apply the precision rule: the more precise a claim, the more it needs verifying.

What you’ll create

Your thirty-second check, written in your words for your work, plus a comparison of an agreeable answer and one you asked to challenge your view.

Your policy in practiceWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Apply company policy to real situations involving files, personal data, and account choice.
  • Review memory, data-use settings, connector permissions, and temporary chats.
  • Know when to disclose AI use, read an approval, and report a mistake.

What you’ll create

Ten situations from your own week, called before the reveal, with the two you were unsure about sent to the policy owner.

Make it yours, then hand offWho it’s forEveryone on your team, working through AI Foundations.

What you’ll learn

  • Save and share a repeatable process as a skill.
  • Test it on completed work before using it on a live task.
  • Hand off a bounded task, review the plan, approve important actions, and check the finished file.

What you’ll create

One skill from a task you repeat, one bounded task handed off with approvals on, and your completed trust map with what you flagged for help.
Track preview · 1:48

AI for Sales

Turn account research, proposals, and follow-ups into a more prepared sales day.

Learn More

Illustrative workflows. Personalization and connected tools are scoped separately.

Who it’s for

Sales leaders, sellers, SDRs, and sales operations.

Key takeaways

  • Build an account brief before a prospect conversation.
  • Draft proposals grounded in current pricing and case studies.
  • Turn call notes into clear next steps and follow-ups.

Example tools

  • Salesforce
  • HubSpot
  • Gong
  • Fireflies
  • PandaDoc

A few examples, not an exhaustive list.

Inside the course

Start with the core classes, then explore deeper paths for your role. Additional classes from the expanded syllabus are marked as planned.

Prospect research and call preparationWho it’s forEvery seller and SDR. Anyone who takes first calls.

What you’ll learn

  • Build a research brief that runs on a company name
  • Match the brief against the company's own past wins
  • Open every call with the right question

Lesson topics

  1. What a good brief has in it
  2. Build the brief: company, person, news, priorities
  3. Do it: a real account in your pipeline
  4. Match it to your own wins
  5. The three opening questions
  6. Push it: the brief in Slack an hour before every meeting, from Salesforce or HubSpot

What you’ll create

A research brief template that runs on any company name, and a version that lands in Slack before every meeting on your calendar.

The proposal packWho it’s forEvery seller who writes proposals. Sales ops or whoever owns pricing takes it too.

What you’ll learn

  • Pull current pricing, standard terms, and matched case studies from approved sources
  • Draft a proposal in the company’s language using current source material
  • Trace every number back to where it came from

Lesson topics

  1. Why proposals go stale
  2. Sources: pricing, terms, case studies
  3. Build the pack
  4. Do it: a live deal
  5. Check every number

What you’ll create

A proposal workflow pulling current pricing and matched case studies into PandaDoc, DocuSign or Proposify.

Follow-ups that never slipWho it’s forEvery seller. Sales leader takes it to set the standard.

What you’ll learn

  • Write down the team's follow-up standard
  • Build a watcher that reads CRM, email, and calendar and pings when a thread goes quiet
  • Act on the ping instead of the quarterly pipeline scrub

Lesson topics

  1. Where deals actually die
  2. Your team's follow-up standard, written down
  3. Build the watcher with Zapier, n8n, and scheduled tasks
  4. Do it: point it at your pipeline
  5. When it pings: what to do

What you’ll create

A running follow-up watcher on your pipeline in Salesforce or HubSpot.

The Friday pipeline briefPlannedWho it’s forSales leaders and front-line managers. Sales ops builds the feed with them.

What you’ll learn

  • Combine CRM, call, and forecast information into one pipeline brief.
  • Surface slipped deals, quiet opportunities, and missing next steps.
  • Use exceptions to focus the pipeline review.

Lesson topics

  1. What a pipeline review is for, and why yours is a status meeting
  2. The five things the brief must say: forecast delta, slipped, gone quiet, no-decision risk, data to fix
  3. Build the feed: Salesforce or HubSpot reports, Gong or Fireflies summaries, into Claude
  4. Do it: your pipeline, this Friday
  5. Run the review from the brief

What you’ll create

A Friday brief that reads Salesforce or HubSpot, the call recordings, and the forecast, and lands in Slack with Claude Tag before the pipeline review.

Coaching from the callsPlannedWho it’s forSales managers and enablement. Reps take lesson 5 so they know what the coach sees.

What you’ll learn

  • Define the skills that make a strong call for your team.
  • Compare call transcripts with that model to find coaching opportunities.
  • Turn specific examples into a useful coaching conversation.

Lesson topics

  1. Why call reviews never happen
  2. Your skill model: discovery, multi-threading, value, next step
  3. Build it: transcripts in, one coaching note per rep out
  4. Do it: this week's calls, your team
  5. The coaching conversation, and what reps see

What you’ll create

A weekly coaching note per rep, built from Gong, Zoom, Fireflies or Fathom transcripts against your own skill model.

The CRM that updates itselfPlannedWho it’s forSales ops and RevOps. Managers take lesson 1 to set the standard.

What you’ll learn

  • Define the CRM fields and quality standards your team needs.
  • Draft record updates from calls and emails for a rep to approve.
  • Check for missing or stale information each week.

Lesson topics

  1. Why the CRM is wrong, and whose fault it is not
  2. The fields that matter and the standard for each
  3. Build it: call and email in, Salesforce or HubSpot fields out
  4. Do it: your pipeline, backfilled and kept current
  5. The weekly data-quality check

What you’ll create

Automations that write call notes, next steps and stage changes into Salesforce or HubSpot from calls and email, with Zapier, n8n and scheduled tasks.

Pricing, terms and the deal deskPlannedWho it’s forSales ops and whoever approves discounts. Sellers take lessons 1 and 5.

What you’ll learn

  • Keep pricing, terms, and discount rules in a current source.
  • Check a deal request against the policy and explain the result.
  • Route exceptions to the person authorized to decide.

Lesson topics

  1. Where the wrong number came from
  2. The source: price book, terms, discount policy, in one place
  3. Build the deal desk: a request in Slack, a decision with the policy cited
  4. Do it: three live discount requests
  5. Keeping it current when pricing changes

What you’ll create

A pricing and terms source the proposal pack pulls from, discount guardrails, and a deal-desk review that runs in Slack before anything goes to PandaDoc, DocuSign or Proposify.

Winning the no-decisionPlannedWho it’s forEvery seller and every manager.

What you’ll learn

  • Recognize indecision signals in transcripts and deal history.
  • Review older opportunities for missing buyers, risk concerns, and repeated delays.
  • Choose a concrete next step for each flagged deal.

Lesson topics

  1. Where deals really go: not to competitors
  2. The signals of indecision in a transcript: risk talk, missing buyer, the fourth push
  3. Build the detector: transcripts and CRM in, flagged deals out
  4. Do it: your five oldest opportunities
  5. The next step that ends the maybe

What you’ll create

An indecision detector on your pipeline, built from the call transcripts, and a next-step playbook for the deals it flags.

Practice before the callPlannedWho it’s forEvery seller and SDR, especially anyone in their first ninety days. Managers set the scenarios.

What you’ll learn

  • Create practice scenarios using your buyers, offering, and objections.
  • Rehearse discovery and difficult conversations before a live call.
  • Use a shared skill model to review practice and choose what to improve.

Lesson topics

  1. Why reps practice on prospects
  2. Your buyers, your objections, your offering: the scenario set
  3. Build the partner: a persona that pushes back the way your buyers do
  4. Do it: ten reps, the discovery call, scored
  5. What managers do with the scores

What you’ll create

A practice partner that plays your buyers, on your offering, with your objections, and scores the rep against your skill model.
Explore the track
Marketing teamsOne idea.
More content.SHARPER ACADEMY ↗

AI for Marketing

Create more from a strong brief while keeping your company’s voice and claims intact.

Learn More

Who it’s for

Marketing teams and the people who publish for your company.

Key takeaways

  • Turn a source idea into useful content across formats.
  • Apply a consistent house style to drafts.
  • Check claims against source material before publishing.

Example tools

  • ChatGPT
  • Claude
  • HubSpot
  • Google Docs
  • Zapier

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

Content at scale without losing the voiceWho it’s forMarketing teams and content owners; Founders and executives who post as the company; Anyone publishing more than once a week.

What you’ll learn

  • Teach the AI the company's voice with examples and rules, not adjectives
  • Turn one long piece into ten on-brand pieces
  • Pull only from approved claims and real proof points

Lesson topics

  1. Why it sounds like AI
  2. Teach it your voice: the house-style instruction
  3. Do it: build yours from three real pieces
  4. One in, ten out
  5. Do it: repurpose last month's piece
  6. Approved claims only

What you’ll create

A house-style skill and a repurposing workflow.

The claims checkerWho it’s forMarketing leads who own the website and decks; Product marketers who own claims; Ops or a builder who can wire it up.

What you’ll learn

  • Establish what is currently true and who owns each claim
  • Build a checker that compares published claims to the current truth
  • Read the drift report and fix in priority order

Lesson topics

  1. How claims drift
  2. What is currently true, and who owns it
  3. Build the checker with Zapier, n8n, and scheduled tasks
  4. Do it: run it on your own site
  5. The first report, and what to fix first

What you’ll create

A checker that compares published claims to what is currently true.

Competitive monitoring on autopilotWho it’s forMarketing and product leads; Sales enablement; Founders who watch competitors on Friday afternoons.

What you’ll learn

  • Choose the five competitors that matter and what to watch
  • Build a weekly digest from pricing pages, job postings, releases, and news
  • Turn the digest into questions sales can use

Lesson topics

  1. What to watch and what to ignore
  2. Sources: pricing, jobs, releases, news
  3. Build it with Zapier, n8n, and scheduled tasks and Claude Research
  4. Do it: your five competitors
  5. Reading the first digest

What you’ll create

A weekly competitor digest that writes itself.
Explore the track
Operations teamsMake repeat
work easier.SHARPER ACADEMY ↗

AI for Operations

Give recurring processes, SOPs, and status reports a better starting point.

Learn More

Who it’s for

Operations leads, process owners, and people responsible for recurring reports.

Key takeaways

  • Turn a real process into a usable SOP.
  • Prepare status updates from the work being tracked.
  • Identify conflicting documents and record the resolution.

Example tools

  • Microsoft Excel
  • Google Sheets
  • Notion
  • Zapier
  • n8n

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

SOPs that write themselvesWho it’s forOps leads and every process owner; Anyone whose departure would break something; Companies onboarding faster than they can document.

What you’ll learn

  • Narrate a process once while doing it
  • Turn the recording into an SOP in the company format
  • Fix, version, and publish so it stays current

Lesson topics

  1. Why SOPs do not get written
  2. Record once: how to narrate the work
  3. Draft it with Claude Cowork
  4. Do it: your first real process
  5. Fix, version, publish
  6. Do it: two more

What you’ll create

Three real SOPs, versioned, in your company's format.

The self-prepping status reportWho it’s forAnyone who owns a recurring report; Ops, PMs, and department leads; Executives tired of reports that arrive late and half-assembled.

What you’ll learn

  • Map where every number and blocker in the report lives
  • Connect the sources and build the assembly on a schedule
  • Review the assembled report for accuracy, missing context, and next steps

Lesson topics

  1. What is in your report and where it lives
  2. Connect the sources
  3. Build and schedule it with Zapier, n8n, and scheduled tasks
  4. Do it: your real report, this Friday
  5. The ten-minute review

What you’ll create

A weekly report that runs on a schedule from your real sources.

When two documents disagreeWho it’s forOps and finance leads; Whoever owns pricing, policy, or terms; Leadership teams that keep re-arguing settled questions.

What you’ll learn

  • See how a company knowledge base surfaces conflicts between official documents
  • Make a ruling: who decides, how it is recorded, where it lives
  • Use the log so the same fight does not happen twice

Lesson topics

  1. Why official documents disagree
  2. How conflicts get surfaced
  3. Do it: find your first one
  4. Making a ruling: who, how, where it lives
  5. The log, and why it ends relitigation

What you’ll create

A ruling log and a process for settling conflicts.
Track preview · 1:28

AI for Finance

Help your finance team prepare reporting, explain variances, and review the details.

Learn More

Illustrative workflows. Personalization and connected tools are scoped separately.

Who it’s for

CFOs, controllers, analysts, and payables and receivables teams.

Key takeaways

  • Draft close commentary grounded in financial source data.
  • Build a clearer narrative for management and board reporting.
  • Use review steps to check numbers and surface anomalies.

Example tools

  • QuickBooks
  • NetSuite
  • Sage Intacct
  • Xero
  • Microsoft Excel

A few examples, not an exhaustive list.

Inside the course

Start with the core classes, then explore deeper paths for your role. Additional classes from the expanded syllabus are marked as planned.

Month-end close and variance commentaryWho it’s forControllers and the close team; Finance teams closing in more than five days; CFOs who write commentary at midnight.

What you’ll learn

  • Match exceptions and draft variance notes with the numbers already in them
  • Point an agent at the supporting-file folder so backup finds itself
  • Rebuild the close checklist with AI steps marked for the whole team

Lesson topics

  1. Where the close actually loses time
  2. Exceptions and matching in Claude in Excel
  3. Variance notes with the numbers in them
  4. Do it: last month's close
  5. The supporting-file folder with Claude Cowork
  6. Your new close checklist

What you’ll create

A close checklist with AI steps you actually run.

Board reporting without the scrambleWho it’s forCFOs and finance leads; Whoever builds the board deck today; Founders reporting to investors quarterly.

What you’ll learn

  • Generate the pack from current numbers and recorded decisions, stamped current-as-of
  • Review instead of assemble
  • Build three scenarios before the board asks

Lesson topics

  1. What a board pack costs today
  2. Sources: numbers, decisions, open items
  3. Build the pack, stamped current-as-of
  4. Do it: your last pack, regenerated
  5. Three scenarios in Claude in Excel

What you’ll create

A board pack that regenerates, stamped current-as-of.

The Friday finance briefPlannedWho it’s forCFO and controller. Finance ops builds the feed with them.

What you’ll learn

  • Bring cash, close status, forecast, receivables, and payables into one brief.
  • Trace important exceptions back to financial sources.
  • Design a recurring update for finance leaders and daily priorities for AP and AR.

Lesson topics

  1. What the CFO asks every Friday, and who scrambles
  2. The five things the brief must say: cash and runway, close status, forecast vs budget, AR and AP, anomalies
  3. Build the feed: bank feed, QuickBooks or NetSuite, Bill.com or Ramp, into Claude
  4. Do it: your books, this Friday
  5. The morning push for AP and AR

What you’ll create

A Friday brief that reads the bank feed, the ledger, AP and AR, and the forecast, and lands in Slack with Claude Tag before the week ends. Plus a morning push for AP and AR.

Collections workflowsPlannedWho it’s forAR and whoever chases invoices today. The controller sets the tone and the escalation rule.

What you’ll learn

  • Define a reminder ladder and escalation rules.
  • Use aging data to draft reminders and prioritize follow-up.
  • Route disputes and promises to pay to a person with the relevant history.

Lesson topics

  1. Where DSO actually comes from
  2. Your reminder ladder, in your words
  3. Build it: aging in, drafts and flags out
  4. Do it: your 60-plus accounts, today
  5. Disputes, promises, and when a person calls

What you’ll create

A collections workflow that reads the aging from QuickBooks, NetSuite or Bill.com every morning, drafts reminders in your voice, and flags disputes and promises to pay.

Invoice coding and approval workflowsPlannedWho it’s forAP and finance ops. The controller approves the coding rules.

What you’ll learn

  • Document invoice coding rules and approval thresholds.
  • Extract invoice details and prepare coding suggestions for review.
  • Flag duplicates and low-confidence items while keeping an approval record.

Lesson topics

  1. What an invoice costs to touch
  2. Your coding rules and approval thresholds, written down
  3. Build it: inbox in, coded and routed out, with Zapier, n8n and scheduled tasks
  4. Do it: last week's invoices, re-run
  5. Duplicates, exceptions, and the audit trail

What you’ll create

An AP workflow on Bill.com, Ramp or QuickBooks that extracts, codes to the GL, checks for duplicates and policy, and routes approvals in Slack, with low-confidence items held for review.

Cash you can see thirteen weeks outPlannedWho it’s forCFO and controller. FP&A takes it too.

What you’ll learn

  • Combine bank, receivables, and payables data in a thirteen-week view.
  • Identify the cash low point and assumptions that could change it.
  • Explore how collection and payment timing affect the forecast.

Lesson topics

  1. Why the cash forecast is always stale
  2. The three inputs and where they live
  3. Build the view: bank, AR, AP into the sheet
  4. Do it: your next thirteen weeks
  5. What moves the low point, and who decides

What you’ll create

A 13-week cash view in Claude in Excel or Google Sheets that rebuilds from the bank feed, AR and AP every week, with the low point and what moves it.

Driver-based reforecastingPlannedWho it’s forFP&A and the CFO. The controller takes lesson 2 so the actuals land in the right place.

What you’ll learn

  • Map actual results to the drivers in a forecast.
  • Prepare updated scenarios and draft variance commentary.
  • Explain the model’s assumptions and changes to leadership.

Lesson topics

  1. Why the forecast takes a week
  2. Your drivers, and where the actuals come from
  3. Build the model: actuals in, drivers reforecast, variances explained
  4. Do it: last month's actuals, this quarter's reforecast
  5. Three scenarios in twenty minutes
  6. The story for the leadership team

What you’ll create

A driver-based forecast in Claude in Excel that pulls the actuals from QuickBooks or NetSuite, reforecasts the drivers, and writes the variance story.

Anomalies before they postPlannedWho it’s forController and finance ops. AP takes lesson 4.

What you’ll learn

  • Define vendor patterns, thresholds, and coding checks.
  • Flag possible duplicates, unusual spend, and missing purchase orders with evidence.
  • Test against past records and tune the check to reduce noise.

Lesson topics

  1. What slips through, and what it costs
  2. Your patterns: vendors, thresholds, codes, policy
  3. Build the check: ledger and AP in, flagged items with evidence out
  4. Do it: last month, re-run
  5. Tuning the noise down

What you’ll create

A daily anomaly check on the ledger, AP and spend (QuickBooks, NetSuite, Bill.com, Ramp) that flags duplicates, out-of-pattern spend, missing POs and miscodes into Slack with the evidence.

Audit evidence and controlsPlannedWho it’s forController and anyone who owns a control. The CFO takes lesson 1.

What you’ll learn

  • Build review steps and evidence capture into AI-assisted workflows.
  • Organize a controls matrix from the resulting records.
  • Prepare supporting documentation for auditor requests.

Lesson topics

  1. What the auditor will ask about AI
  2. Review steps and evidence, built into every workflow
  3. Build the controls matrix that updates from the trail
  4. Do it: your top five controls
  5. The PBC list that assembles itself

What you’ll create

A documentation habit for every AI-assisted workflow, a controls matrix that updates itself, and a PBC list that assembles from the trail.
Explore the track
People teamsA better
first day.SHARPER ACADEMY ↗

AI for People & HR

Bring structure to hiring documents and give new teammates a clearer place to start.

Learn More

Who it’s for

People teams, HR leads, and hiring managers.

Key takeaways

  • Prepare a consistent hiring kit for a role.
  • Build an onboarding path from company materials.
  • Use approved sources to draft answers to new-hire questions.

Example tools

  • Microsoft Word
  • Google Docs
  • Claude
  • Microsoft Teams
  • Slack

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

Build your hiring kitWho it’s forHR leads and recruiters; Every hiring manager; Companies opening more than two roles a quarter.

What you’ll learn

  • Load the kit with values, leveling, and what the best hires had in common
  • Draft a job description, interview questions, scorecard, and offer for human review
  • Apply bias checks to questions and scoring

Lesson topics

  1. Why hiring docs take a week
  2. Load the kit: values, leveling, your best hires
  3. Generate the four documents in Claude in Word
  4. Do it: a role you are hiring for now
  5. Bias checks and the scorecard

What you’ll create

A hiring kit that runs on any role.

Build a new-hire onboarding pathWho it’s forHR leads and the manager of the next open role; Companies where senior people field new-hire questions all day; Fast-growing teams.

What you’ll learn

  • Help a new hire find answers grounded in approved company sources
  • Build a 30-day path for one role
  • Capture the questions so the next hire finds the answers waiting

Lesson topics

  1. What the first month really costs
  2. Day one: ask the company anything
  3. Build the 30-day path for one role
  4. Do it: your next hire's role
  5. Questions that improve the answers

What you’ll create

An onboarding path that runs from your company knowledge base.
Explore the track
Leadership teamsSee what
needs you.SHARPER ACADEMY ↗

AI for Leadership

Bring company context, open decisions, and daily priorities into sharper focus.

Learn More

Who it’s for

CEOs, executives, and leadership teams.

Key takeaways

  • Prepare an executive brief from relevant company information.
  • Ask focused questions of company source materials.
  • Keep a decision log with context and next steps.

Example tools

  • Claude
  • ChatGPT
  • Microsoft Copilot
  • Slack
  • Microsoft Teams

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

The morning briefWho it’s forCEOs and every member of the leadership team; Integrators and COOs; Founders who find out about problems late.

What you’ll learn

  • Decide what the brief reads overnight
  • Build it on the company knowledge base and an agent
  • Get three things with evidence attached, each already a task, before the first call

Lesson topics

  1. Why you find out late
  2. What the brief reads overnight
  3. Build it on Claude Projects and skills and Claude Cowork
  4. Do it: your first brief
  5. Three things, evidence, task

What you’ll create

A brief that arrives before your first meeting.

Ask your company anythingWho it’s forThe whole leadership team, together; Integrators who are the company's memory; Companies where 'who approved that' has no answer.

What you’ll learn

  • Recognize what a cited answer with an owner looks like
  • Decide what goes into the brain and what does not
  • Handle the week the team stops asking you

Lesson topics

  1. What a cited answer looks like
  2. What goes in the brain, and what does not
  3. Do it: ten questions your team asks you
  4. Ownership: every answer has a name
  5. The week they stop asking you

What you’ll create

A brain that answers with sources and owners.

The decision logWho it’s forLeadership teams; Integrators and COOs who own the log; Companies that relitigate decisions.

What you’ll learn

  • Capture every decision with date, owner, and why from the meeting where it happened
  • Query the reasoning when the question comes back
  • Keep the log honest

Lesson topics

  1. Why decisions get relitigated
  2. Capture: date, owner, why, from Granola or Fireflies
  3. Do it: last month's decisions, logged
  4. Query: the reasoning, one question away
  5. Keeping the log honest

What you’ll create

A decision log your leadership team actually uses.
Explore the track
People managersSet the
standard.SHARPER ACADEMY ↗

AI for Managers

Help managers set clear expectations and review how their teams use AI.

Learn More

Who it’s for

Anyone with direct reports, ideally before their team begins Foundations.

Key takeaways

  • Write practical expectations for AI use on your team.
  • Review AI-assisted work against a clear quality standard.
  • Identify where teammates need support or a human decision.

Example tools

  • Microsoft Copilot
  • Gemini
  • Claude
  • Microsoft Teams
  • Slack

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

Before your team startsWho it’s forManagers and leaders preparing their team for Foundations.

What you’ll learn

  • Explain why the training matters for your team in one clear sentence.
  • Make time for the work, name a team champion, and model AI use yourself.
  • Recognize the work learners create and sort blockers into fixes, help from others, and future builds.

Lesson topics

  1. What your team will be able to do
  2. The eight things learners create
  3. Recognizing and sorting blockers
  4. Say why and model the behavior
  5. Make it safe to report a mistake

What you’ll create

A clear message to your team, a named champion, and a plan for supporting the first week.

Managing AI teamsWho it’s forEvery person with direct reports; New managers and team leads; Executives who want adoption they can read by department.

What you’ll learn

  • Set the expectation for AI use on their team and say it out loud
  • Review AI-assisted work without redoing it
  • Coach the avoider and the first-draft shipper differently, and read real adoption

Lesson topics

  1. Setting the expectation
  2. Reviewing AI-assisted work
  3. What your team should never paste in
  4. Coaching the two failure modes
  5. Reading adoption

What you’ll create

Your team's AI expectations, written down and said out loud.
Explore the track
Hands-on buildersYour first
automation.SHARPER ACADEMY ↗

AI for Builders

Turn a recurring task into a workflow, agent, or internal tool your team can use.

Learn More

Who it’s for

Hands-on operators, administrators, and your team’s emerging builders.

Key takeaways

  • Map a repeatable task into an automation.
  • Connect an agent to relevant files and tools.
  • Build an internal tool with human review where needed.

Example tools

  • Zapier
  • n8n
  • Make
  • Power Automate
  • Google Apps Script

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

Automation without codeWho it’s forOps, admin, and anyone who does the same thing every week; Your first builders cohort; Teams that tried Zapier once and gave up.

What you’ll learn

  • Tell automation, AI automation, and agents apart and pick the right one
  • Build two automations that run in their own accounts
  • Rank the next twenty workflows in their job

Lesson topics

  1. Automation, AI automation, agents
  2. The twenty most automatable workflows
  3. Build one: email to task
  4. Build two: one in, three out
  5. Do it: rank your own twenty

What you’ll create

Two live automations and the list of your next twenty.

Agents on your filesWho it’s forBuilders cohort; AP, contracts, support, and anyone processing files in volume; IT generalists who will set the guardrails.

What you’ll learn

  • Understand what an agent can touch, approvals, cloud versus local, and folder scope
  • Hand an agent a folder and a job and review what it did
  • Put it on a schedule

Lesson topics

  1. What an agent is, and is not
  2. Approvals, cloud, local, scope
  3. Do it: a folder and a job
  4. Review what it did
  5. Put it on a schedule

What you’ll create

A scoped agent workflow you run weekly, and a schedule for it.

Ship an internal toolWho it’s forYour two or three most capable operators; Ops and finance people who keep asking IT for a tool; Anyone who has never opened a terminal and wants to ship something.

What you’ll learn

  • Write a one-page spec that produces good code
  • Build across three sessions with AI as the developer
  • Deploy where the team can reach it and register it in the company knowledge base

Lesson topics

  1. The PM mindset
  2. Write the spec
  3. Spec review
  4. Build session one
  5. Build session two
  6. Build session three
  7. Deploy where they can reach it
  8. Demo day

What you’ll create

A deployed tool your team uses, with its spec.
Explore the track
EOS companiesYour system.
In sync.SHARPER ACADEMY ↗

AI for Companies Running on EOS

Apply AI to the scorecards, meetings, and core processes your company already runs.

Learn More

Who it’s for

Visionaries, Integrators, leadership teams, and EOS Implementers.

Key takeaways

  • Prepare meeting materials from current company information.
  • Use source data to help maintain scorecards and track commitments.
  • Document core processes so teams can put them to work.

Example tools

  • Microsoft Excel
  • Google Sheets
  • Claude
  • Fireflies
  • Slack

A few examples, not an exhaustive list.

Inside the course

Explore the classes for your role. Open a class to see its learning goals, lesson topics, and the work you will practice.

AI and the six componentsWho it’s forLeadership teams running on EOS; Visionaries and Integrators together; Implementers preparing a client for an AI conversation.

What you’ll learn

  • See what AI changes and does not in each of the six components
  • Build a six-component AI map from the real V/TO, scorecard, and issues list
  • Turn AI from an issue into three Rocks with owners

Lesson topics

  1. Not a seventh component
  2. Vision and People: what changes, what does not
  3. Data and Issues: the scorecard and the list
  4. Process and Traction: followed by all, and the L10
  5. Do it: your six-component map
  6. Three moves, three owners

What you’ll create

A one-page map of AI against your six components, with the first three moves marked.

The Visionary's idea engineWho it’s forVisionaries; Integrators who absorb the idea firehose; Founder-led companies.

What you’ll learn

  • Capture ideas by talking, not typing
  • Vet each idea against the V/TO, core focus, and prior decisions
  • Route it to the issues list, the quarterly, or the parking lot with a case attached

Lesson topics

  1. The twenty-ideas tax
  2. Capture: talk, do not type
  3. Vet it against the V/TO and what was decided
  4. Build the inbox on Claude Projects and skills
  5. Do it: run your last ten ideas through it
  6. What the Integrator sees

What you’ll create

An idea inbox that vets and routes on its own.

The three-year picture, researchedWho it’s forVisionaries and Integrators, four to six weeks before the annual; Leadership teams rewriting the V/TO; Implementers who want a client to arrive prepared.

What you’ll learn

  • Research market size, direction, and the real target list
  • Study what competitors promise versus deliver and what a guarantee looks like in the category
  • Bring an evidence brief into the room

Lesson topics

  1. What the V/TO usually gets written from
  2. Research the market and the target list with Claude Research
  3. Proven process, guarantee, and what the category does
  4. Do it: your three-year picture, researched
  5. Into the room: the evidence brief

What you’ll create

A researched draft of your three-year picture and marketing strategy sections.

The self-prepping L10Who it’s forIntegrators; Whoever runs the L10 agenda; Leadership teams whose L10 spends thirty minutes on status.

What you’ll learn

  • Pull Rock status, scorecard trends, carried issues, and last week's decisions automatically
  • Schedule the brief to land an hour before
  • Capture the meeting and update the brief

Lesson topics

  1. Status archaeology
  2. Sources: Rocks, scorecard, issues, decisions
  3. Build the brief with Zapier, n8n, and scheduled tasks and Claude Projects and skills
  4. Do it: next Monday's L10
  5. Capture with Granola or Fireflies, update the brief

What you’ll create

An L10 prep brief that runs every week on a schedule.

Rocks and commitments that track themselvesWho it’s forIntegrators; Leadership teams whose Rocks slide silently; Companies where 'we decided that' does not mean it happened.

What you’ll learn

  • Extract commitments with who, what, and when from transcripts
  • Build the watcher that nags before the deadline
  • Read the decision-to-done rate per person and per Rock

Lesson topics

  1. Where accountability leaks
  2. Extract commitments from Granola or Fireflies
  3. Build the watcher with Zapier, n8n, and scheduled tasks
  4. Do it: your last three meetings
  5. The decision-to-done rate

What you’ll create

A commitment tracker with a decision-to-done rate you can read.

The scorecard that fills itself inWho it’s forIntegrators and whoever owns the scorecard; Leadership teams typing measurables in on Monday; Companies with numbers in three systems.

What you’ll learn

  • Find where each measurable actually lives
  • Pull it on a schedule and flag what went off track
  • Show thirteen weeks of trend instead of one number

Lesson topics

  1. Where each measurable actually lives
  2. Connect the sources
  3. Pull and flag with Zapier, n8n, and scheduled tasks into Claude in Excel
  4. Do it: your scorecard, automated
  5. Thirteen weeks, not one

What you’ll create

A scorecard that updates from your real systems on a schedule.

Core processes, documented and followed by allWho it’s forIntegrators and every process owner; Leadership teams with a weak Process component; Companies about to scale past what people carry in their heads.

What you’ll learn

  • Name the six to ten processes that run the business
  • Record each once and draft at the twenty-percent level of detail
  • Simplify, version, and load it so followed-by-all is checkable

Lesson topics

  1. Why Process gets skipped
  2. Name the core processes
  3. Record once, draft with Claude Cowork
  4. Do it: three of yours
  5. Simplify, version, load into Claude Projects and skills
  6. Followed by all: how to check

What you’ll create

Your core processes documented, simplified, and versioned.

The Integrator's sidekickWho it’s forIntegrators; Leadership teams with a single point of failure; Companies where one person's vacation is a risk.

What you’ll learn

  • Collect the fifty questions that reach the Integrator most
  • Load a brain that answers with the number, the file, the date, and the owner
  • Come back from a week away to a briefing instead of a fire

Lesson topics

  1. The single point of failure
  2. The fifty questions you get most
  3. Load the brain with Claude Projects and skills
  4. Do it: answers with owners
  5. Take the week off: the briefing you come back to

What you’ll create

A company knowledge base your team asks before they ask you.

Client session preparationWho it’s forProfessional and Certified EOS Implementers; Coaches running quarterlies and annuals for multiple clients; Implementer practices adding capacity without adding hours.

What you’ll learn

  • Load a client's V/TO, last session outputs, Rocks, and scorecard
  • Cluster the issues list and read what changed in the client's market
  • Turn session notes into actions and send the follow-up same day

Lesson topics

  1. What you walk in with today
  2. Load the client: V/TO, last session, Rocks, scorecard
  3. Cluster the issues, read the market with Claude Research
  4. Do it: a real client, next session
  5. Session notes to actions with Granola or Fireflies

What you’ll create

A quarterly prep pack that runs on any client.

The AI RockWho it’s forImplementers whose clients keep asking about AI; Coaches who want a move, not just an opinion; Implementers interested in a referral relationship with Sharper.

What you’ll learn

  • Run a twenty-minute AI readiness read in the session room
  • Build an AI issues list from vague worry
  • Shape a 90-day AI plan as a Rock with milestones and one owner

Lesson topics

  1. What clients are really asking
  2. The twenty-minute readiness read
  3. The AI issues list
  4. The 90-day AI Rock: milestones and owner
  5. Do it: run it on a real client
  6. When they want more

What you’ll create

A 90-day AI Rock template and a readiness read you run in the room.

Run your practice with AIWho it’s forImplementers, especially solo practices; Coaches whose follow-ups lose to the session calendar; Anyone running a one-person advisory business.

What you’ll learn

  • Put a watcher on the prospect list
  • Draft proposals and referral notes from past engagements in their own voice
  • Turn one session insight into three posts

Lesson topics

  1. The between-sessions business
  2. Follow-up watcher on your prospects with Zapier, n8n, and scheduled tasks
  3. Proposals and referral notes from your own work
  4. Do it: your real pipeline
  5. Session insight to three posts

What you’ll create

A follow-up watcher and a content workflow for a one-person practice.