Works. Company overview
Prepared for
Carey O'Dowd · JPM Valuers
Introduced by Jason Cake

Works.

We find the work AI can improve, build the workflows with your team, and leave your people able to run the system themselves.

A short overview
AI that Works.
How we audit, install and hand over the operating layer.
StartMap the real work
FinishYour team owns it
Stage 01Audit
Stage 02Embed
Stage 03Build
Stage 04Optimize
The problem
Most companies are stuck at scattered experiments.

Most teams have access to AI and a handful of useful experiments. Very few have turned those wins into a repeatable way of working.

The gap is not another tool. It is the operating layer between AI and the business.

Works.// The Problem
02 / 13
What Works installs

AI-native runs on four layers. We install all four.

Four connected layers turn scattered AI use into infrastructure your team owns.

01

Architecture

Where AI sits, what it can access, and how it connects to the business.

The foundation
02

Context

The knowledge AI needs before anyone asks it to do the work.

Source of truth
03

The Brain

Living company knowledge that stays current as the team works.

Stays alive
04

Skills

The repeatable workflows that return time to the team.

Runs on top
×

Tools

Chosen last. The value sits in the system, not the software logo.

Downstream

All four installed inside your business during the 90 days. Owned and run by your team after handoff.

Works.// The Four Layers
03 / 13
How the engagement works

The engagement, end to end.

Step 01

Audit

1–4 weeks

Map the work, rank the opportunities and build the 90-day plan.

Step 02

Embed

90 days

Install the system, ship the workflows and train an internal owner.

Step 03 When needed

Build

Scoped

Add custom infrastructure only where a workflow genuinely needs it.

Step 04

Optimize

Ongoing

Keep the workflows and company knowledge current after handover.

One sequence. One install. One team that owns it.

Works.// The Approach
04 / 13
04 · The Architecture

Inside your stack. Not on top of it.

The context and brain layers, up close: a shared brain that gives every team the same context, every time. Built on the tools you already use. Engineering keeps its own lane.

The Works Brain, layered context stack
Layer 01 / Company
About your business
Who you serve, ICP, voice, glossary, org chart, engagement history. The single source of truth every skill reads first.
Read by all
Layer 02 / Teams
Sales · CS · Marketing · Ops · Finance · People
Per-team playbook, KPIs, current focus, evidence base. Skills scoped to the team that uses them.
Team-scoped
Layer 03 / Individual
Each operator
Role, voice, current projects. Personal context that overlays the team and company layers.
Per-user
Skills + agents read top-to-bottom on every run
Execution
Skills + agents (Claude · Gemini · Cowork)
Review, Debrief, Research, Pre-call Prep, Voice Check, ICP Score, Win/Loss Log, Quote Capture. Plus the custom workflows selected in the Audit. Built on top of your existing licences.
Your stack
Out of scope
Engineering / product AI
Your CTO's lane. Claude Code, in-product AI, model strategy. Separate stack, separate governance.
Eng-owned
Works.// The Architecture
05 / 13
Audit

We start with the work. Not the tools.

Duration1–4 weeks
InvestmentStarting from $5K
OutputDiagnostic + Embed plan

What we look at

  • Workflow inventory across the in-scope team
  • AI proficiency ladder per role: L0 curious, L1 chatbot, L2 context, L3 operating
  • Tools and stack audit, including what is already plumbed in
  • Quick wins that can ship in weeks, and structural builds that need architecture first

What you get

  • Diagnostic report with workflow maps and an AI readiness scorecard
  • The workflows to test and ship first, ranked by evidence and value
  • Architecture recommendation for your stack
  • 90-day Embed plan with named workflows and outcomes

The Audit is your low-risk way in. You walk away with a workflow map and a 90-day plan, whether you go further with Works or not.

Works.// Audit
06 / 13
Embed

90 days inside the business.

One Works operator works alongside your team, inside the systems you already use.

What gets installed during the 90 days

  • Company knowledge organised for AI
  • Typically 6–10 workflows shipped
  • One real workflow running autonomously
  • An internal owner trained to run the system
How each workflow ships
01Build it.
02Run it.
03Improve it.

Tested on real work with the people who will own it after handover.

Works.// Embed
07 / 13
Scope

Tight scope. Deep work.

Clear lines on what we do and don't do are how the install holds after we hand it back. Here's what we leave to your team or your CTO.

×

We don't do engineering work

If a workflow needs custom code, we scope a Build engagement around it. JPM or its nominated technical partner owns the codebase.

×

We don't do product AI

If a product has AI features, that stays with the product or technology owner. Works is for the operating layer between AI and the business.

We work inside your existing architecture

We use what you already run. If a workflow needs a different tool, we flag it in the Audit with reasoning. No surprise stack changes, no sprawl.

×

We don't replace your team

We install the layer that lets your people do their best work. Then we leave them with the keys, the architecture, and an internal owner who can run it.

Works.// Scope
08 / 13
The business benefit

We turn your team into AI operators.

Your people spend less time on repeatable work and more time applying judgement.

In 90 days, Works installs the operating layer, ships the first workflows and trains your team to own it.

AI becomes part of how the business operates.

Works.// The Business Benefit
09 / 13
Blind case study · Boutique homebuilder

$10.5M additional revenue capacity unlocked.

A boutique homebuilder wanted to grow without adding headcount. The Audit unlocked the capacity already inside the business.

Overview

Boutique homebuilder

A growing, design-led business with strong demand and a lean team.

Situation

Growth was trapped in admin

Repeatable work across proposals, design administration and quality assurance was constraining capacity.

Result

105–120 days saved each year

Nine workflows mapped. The client approved the 90-day sprint and moved into implementation.

Works.// Blind Case Study · Boutique Homebuilder
10 / 13
Investment

Transparent pricing. Scoped after Audit.

The Audit establishes the evidence. The implementation scope follows.

Stage
What it covers
Duration
Investment
Audit
Workflow maps, opportunity ranking and a practical 90-day roadmap.
1–4 weeks
Starting from$5K
Embed
Architecture install, typically 6–10 workflows, training and handover
90 days
Starting from$40K
Build
Custom infrastructure for workflows that need it
Scoped
Fixed range$50–100K
Optimize
Office hours, skill library curation, continuous improvement
Ongoing
Per month$4K

Final scope and commercials are set after the Audit.

Works.// Investment
12 / 13
Works. // Next Step
workshq.com.au

Start with one real workflow.

A 30-minute working session with Carey and Zac. Pick one valuation workflow, trace where time and judgement sit today, and decide whether an Audit would create a useful answer.

No preparation deck. No commitment beyond the conversation.

Meet Zac
The first question
Where does skilled valuation time get spent on repeatable work before the valuer can exercise judgement?
BringOne workflow
Leave withA clear next step
Works.// AI that Works.
13 / 13
Space next prev F fullscreen ? help
Engagement analytics may be used. Privacy