Menu

AI Workshops

A practical AI workshop for owners who don't want to become AI experts.

How to put AI to work inside the software a business already runs, not how to write prompts. For trade associations, franchise groups, PE portfolios, chambers, peer groups and software user groups.

Request a Free Workshop

What we actually cover

The room leaves knowing what is worth automating, what is not, and what the first ninety days could look like. We walk through real follow-up work and a real deployment, not a chatbot demo.

Agents versus chatbots

What continuously watches a workflow versus what waits for a prompt. Why “we bought ChatGPT for the office” does not follow up an HVAC estimate at 9pm.

What you can automate now

Follow-up, monitoring, reporting, problem alerts. The work that slips between field software, CRM, ads, inbox, and books. We walk real files, not slides about the future.

What should stay human

Judgment, money, and customer promises. The work you would not hand a new hire on day one. If the room cannot name this, they are not ready to automate anything.

Connecting the software you already run

APIs, webhooks, approved integrations, and what to do when a vendor has no usable interface. Named tools are examples. We do not pretend every logo on a homepage is a certified connector.

Local versus cloud

When work should stay on hardware you control, when a cloud model is the right tool, and when a rule beats both. Hardware is a workload decision, not a flex.

Security and permissions

Minimum access, approvals, logs, who owns the logins, and the off switch. If you cannot shut it off, you do not launch it.

A real deployment

Detail Driven in Jackson Hole: four shop types, Tekmetric, CCC ONE, dedicated local hardware, hybrid local and cloud AI, one owner dashboard. What we can stand behind, and what we will not invent numbers for.

The first ninety days

What a practical sequence looks like after the room leaves: audit, one or two workflows, permissions, the people who will work next to the agents. Not a giant roadmap.

How a session runs

Operators, not an IT conference. Format follows the room. They leave with a map, not a recap deck.

  1. 01

    It is a working session, not a product pitch

    We will not spend the hour on a Cortex demo reel. The goal is that the room leaves knowing what is worth automating, what is not, and what the first ninety days could look like inside their software.

  2. 02

    We speak to operators

    Owners, GMs, operations leads. Trade associations, franchise groups, PE portfolios, chambers, peer groups, software user groups. Not an IT conference, not a prompt-engineering seminar.

  3. 03

    Format follows the room

    Ninety minutes for a peer group. A half day when the portfolio wants the architecture. On-site or remote. We confirm fit, timing, and whether we are the right people before anyone blocks a calendar.

  4. 04

    They leave with a map, not a recap deck

    Which slipping work to fix first. What to leave to people. Which systems have to connect. A sketch of the first workflow. If Cortex is the wrong builder, we will say that too.

The file we will walk

Leadership rooms ask for proof. We will not invent a recovered-revenue number. We will walk Detail Driven.

What we walk in the room

Detail Driven, end to end, without fake ROI.

The problem
Leadership rooms ask for proof. Most AI talks show a chatbot and a hockey-stick slide. Operators can smell it. We walk the real problems: stalled repair orders, quiet collision files, ads spending with nobody watching, a morning rebuilt from five logins.
What we build
Four shop types. Their software stayed. Agents set up for specific jobs. Dedicated Linux. One dashboard. What we can stand behind today is on the case study: four shop types, hybrid local and cloud AI, Tekmetric and CCC still the systems of record. No recovered-revenue number we cannot defend.
Why this way
A workshop that will not show a real file is a pitch. This is the file we will show. Everything else in the room is their own work, in their own words.

What a peer-group session is for

Ten HVAC owners, one afternoon, no software to sell them that day.

The problem
Every owner in the room has ServiceTitan or Jobber. Every one of them is still chasing estimates by memory. They have been pitched voice agents, chat widgets, and “AI CSRs.” None of that fixed the follow-up.
What we build
We put unsold-install follow-up on the table. Permissions. What stays human. What a thirty-minute audit would actually look at. They leave able to walk their own board on Monday. A few will apply for the audit. Most will at least stop buying chatbots.
Why this way
The workshop is useful even if nobody hires Cortex. That is the point. A pitch disguised as education is how this industry burned the last three acronyms.

Workshop

What the room actually sees in ninety minutes.

Agents vs chatbots. What to automate. What to leave human. A live walkthrough against real service software.

cortex@workshop · demo
agents-vs-chat.mdconnect.mdpermissions.md90-days.md
$ █

without cortex · someone still has to remember to look

with cortex · the layer watches, drafts, and waits for you

Who this is for

Leadership rooms that run service businesses. We speak to the operators, not an IT conference.

Trade associationsFranchise groupsPE portfoliosChambersPeer groupsSoftware user groupsOwner organizations

Request a free workshop

Tell us who the room is. We will follow up with format, timing, and whether we are the right fit.