GENERATIVEDUCATION
  Consulting  ·  Workflow & agentic systems

You don't buy hours.
You buy the opposite of hours.

Every consulting engagement you've ever bought was priced on how long it took, which means you were paying more for slower. I price the work, not the clock, and then I move as fast as your team can keep up.

The short version

Most organizations buy AI. Very few build the capacity to use it.

I do the second thing. I come in, map how your people actually work, and then build the workflows, Skills, and agentic systems that take the repetitive load off them. Then I hand it over. Your staff maintain and extend it without me.

That last part matters. Sovereignty is the deliverable. If you still need me in six months to change a prompt, I did the job wrong.
Who this is for

Organizations with data they can't move to a vendor, workflows that don't fit off-the-shelf tools, or a team that's smart and stretched thin.


The packages

Three ways in. Fixed price.

They stack, but most people only ever need one. No hourly billing anywhere in here. The constraint on delivery is your team's bandwidth, not my calendar.

01$5,000
Sprint

Your team already uses AI. It's just scattered, fragile, and nobody trusts it.

A short, hands-on engagement that ends with working systems in your accounts. I map how your people actually work, then we build it together, live, on your real data. Not a demo. By the end of a session the workflow is running.

  • Workflow mapping by department
  • Custom Skills & prompt library in readable markdown
  • Live builds: CRM, transcript pipelines, nudges, dashboards
  • Recorded sessions and email support window
02$15k–$25k
Program

The full arc, department by department, ending with your staff building their own systems.

The flagship. Discovery through handoff, with a KPI framework agreed up front so we both know what success looks like. This is the one that changes how an organization operates rather than how one team does one task.

  • Discovery & readiness baseline + KPI framework
  • Pilot on real work with a small group
  • Custom Skills and connector-based agentic workflows
  • Train-the-trainer handoff with an internal owner
03from $25,000
Build

When the workflow isn't the answer and you need the thing itself.

Engineering work. Either infrastructure you own outright, or a platform built from scratch. Delivered on a two-week iteration cadence with working software in front of you continuously, not a six-month black box.

  • On-premise or private-cloud AI, data never leaves your control
  • Document intelligence over your institutional knowledge
  • Full platform builds, incl. compliance architecture
  • Deep human- and AI-readable docs. No lock-in.

Ongoing supportattaches to any of the three. Monthly access for build work, troubleshooting, architecture decisions, and keeping current with a field that changes every eight weeks. Quoted with your package.


Selected work

Built, handed off, still running.

Executive coaching platform, large urban school district

A coaching program with roughly 145 coaches was running on Microsoft Forms, Excel, and Power BI held together by hand. I ran discovery, isolated the real problem behind the coach-matching failure (a data structure problem, not a model problem), and designed a vectorized coach-profile approach so the system retrieves instead of hallucinates. Built for a locked-down district environment where only approved suites are permitted.

discoverydata structureconstrained ITaudit logging

Talent network, workflow automation

A recruiting founder running his pipeline out of his head and his inbox. Two working sessions produced a live CRM with automations built in-session: meeting transcripts scanned to propose leads and update records, nudges on stalled deals, and dashboards showing where everything sits. Followed by a custom Skills pack delivered as editable markdown.

working sessionstranscript pipelinescustom Skillshandoff

Math curriculum company

A publisher spending heavily each summer on curriculum writing labor, with a team already working in Claude but fragile: prompts scattered across desktop folders, no naming convention, everything in one long thread per project. The work restructured project architecture by grade level and task type, consolidated the prompt library, and connected Claude to the founder's operational load with a daily prioritization routine.

prompt libraryproject architecturecost review

Independent high school, AI readiness

A full program across HR, Athletics, and the Principal's Office. Discovery through handoff over 18 weeks: workflow mapping, tool evaluation with privacy flags routed to IT and legal, a staff readiness baseline, pilot builds, and train-the-trainer. Staff finished the engagement building and maintaining their own Skills and agentic workflows.

full program arcKPI frameworkgenuine handoff

How I work

Conductivity over control.

Sovereignty as a service.

Your data, your models where it matters, your team holding the keys. If the engagement ends with you dependent on me, it failed.

Technical courage.

Most of what stops teams isn't capability. It's the belief that this stuff is for other people. Half my job is proving otherwise, in the room, on their own work.

Speed is the product.

Not the deliverable, the product. Everything I've built was built to compress the distance between “we should try that” and “it's running.”

Honest scoping.

I tell you what's automated, what's semi-automated, and what isn't worth automating. I'd rather lose the sale than oversell the system.

Documentation is a deliverable.

Not a courtesy. Deep, human- and AI-readable so you can micro-iterate yourself or hand off to anyone.

No corporate tone.

Direct, collaborative, willing to push back. Build, don't lecture. Capability over perspective.

Background

Former Administrator of AI and Innovation at a county office of education serving 28 districts and roughly 450,000 students. Former principal. Published author. Keynote speaker to education leadership audiences nationally. Hardware founder before that, which is where I learned that shipping is a different skill than knowing.

I've been building with these tools since before there were tools, and I've made most of the mistakes already.

Start here

Tell me what your team keeps doing by hand that they shouldn't be.