the offering

Advisory

We sit between your executives and your IT department.

One side wants more of this. The other does not want the exposure. Every engagement has a name, a fixed price, and an end product: a verdict memo, a working prototype, or a spec ForgeWorks can build.

AN APP SHIPS IN 30 DAYS — OR YOU OWE NOTHING

Your problem

A Working Session — one structured session, one fixed price
BUILDBUYDO IT YOURSELFNOT YET

a one-page memo per problem, a ranked shortlist, and a fixed quote for the next step — or a no.

Fixed price · ends in a verdict

§2What the work is.

Three rungs, each priced up front.

A Working Session ends in a verdict memo. The verdict scopes a Sprint, which ends in a working prototype you own. A retainer keeps the same people on it, month after month.1Working Sessionone of four verdictsends in a verdict memothe work carries forward2AI Operating Sprintfive days, your data, you own itends in a working prototypethe work carries forward3A retainerthe knowledge staysthe same people, monthly
Every engagement has a name, a fixed price, and an end product. The verdict from one step scopes the next.
R-01

A Working Session

Bring every problem on your list. One structured session, one fixed price, verdict within three weeks.

R-02

An AI Operating Sprint

Five working days. Your team runs real work through AI on your own data and leaves operating it.

R-03

A retainer

The same people, month after month, so the knowledge stays when a person leaves.

Your team already uses AI. Our job is to make them better at it.

Someone in your company gets real work out of Claude Code right now.

The probable cause is the same every time: the work crossed from personal use to company use, and the controls did not cross with it.

what we usually find

Your people are already building with AI. These are the conditions we arrive at:

F-01

Thirty-eight Power BI workspaces and no one agrees what gross margin means.

F-02

Forty-five agents querying in thirty-seven ways through personal keys, none of it logged.

F-03

The prototype mostly works, and it runs on a laptop with credentials in a config file.

F-04

Nobody can produce the list of AI tools when counsel asks.

A self-built tool moves through four stages, and the problem changes hands at each one: the builder, the department head, the IT leader, and the executive.An app nobody maintainsthe builderA second userthe department headA support nightmarethe IT leaderA risk to the businessthe executivethe tool, over time

§3What you build it over.

Before you build an app, you build the layer underneath.

we bring — built and running

BR-01A governed data lake
BR-02A skills ladder
BR-03An orchestration layer
BR-04A governance framework
BR-05A reproducible cloud stack
BR-06A shared outreach database

we build with you — only exists in your company

BW-01Connections to your data
BW-02Your semantic layer
BW-03Your environment
BW-04Integration into your tools

Both are AI infrastructure for your organization. See the full layer breakdown →

§4Guardrails.

Nothing acts until you have watched it work and said go. Every call lands in an audit log your auditor can read. A named owner gets the 2 a.m. call, written down before anything runs.

Don't turn these tools loose on your production environment. And before anything runs: does gross margin mean the same thing in your BI tool and in the model?

See the infrastructure the work runs on →

§5Retainers.

T-01

Advisor

A named advisor who knows your business.

T-02

Builder

Embedded in your priorities every month.

T-03

Operating Partner

Roadmap, drivers, and the hard conversations.

T-04

Managed Hours

A prepaid capacity block, drawn by appointment.

T-05

Fractional CI Manager

Value-stream workshops and weekly project drives.

T-06

AI Stewardship

Governance, review, and audit of what you run.

A self-built tool with a heart on it: loved by its builder, harder to replace with every one-off feature.

The 70 percent trap

The builder loves it, it mostly works, and every one-off feature makes it harder to replace. Our one question: would a new hire choose this tool? If no — the prototype still did its job. It told you what to build for real.

A jagged line for a week that goes sideways, sitting above a solid floor: the spec, the signed controls, and the practice you keep.in writing

The Worst-Week Floor

A Sprint week can go sideways: fire drills, missing data, the champion out sick. Whatever happens, you keep the spec, the signed controls, and the practice. In writing.

01
Working Session

Ends in a verdict, not a deck.

02
Five-day sprint

A working prototype you own.

03
The app, shipped

Audit log on. Your repo on exit.

Bring us a problem worth solving

Start with a Working Session. It ends in a verdict you can act on, and the verdict names the next step if there is one worth doing.

Book a Working Session →

ForgeWorks Consultant

Ask me anything about your workflow.

Your ForgeWorks

0 modules

No modules yet. Chat to explore what fits your workflow.