Professor energy. Builder results.

You don’t need a “strategy offsite.” You need one workflow turned into one working feature—fast.

The 2-week loop

Day 0–1 — Pick one thing.
We choose a workflow that touches revenue or time saved: job intake, event publishing, lead routing, simple search.

Day 2–5 — Build while teaching.
We pair. I explain just enough (prompts, data plumbing, guardrails) while wiring the real thing.

Day 6–10 — Ship + measure.
We launch quietly, set one metric (e.g., form submissions, map clicks, search CTR), and learn.

Keep the surface small; make the feedback tight. That’s how AI projects stick.

What we build (common wins)

• Intake → Map/Search: posts become GeoJSON; Leaflet renders events/jobs within 50km automatically.
• Tiny search: CSV/Markdown → SQLite/JSON → instant search with zero vendor lock-in.
• Content helpers: safe prompt patterns + human review → faster drafts, consistent tone.

Guardrails I insist on

• Local-first data: you keep a simple export (CSV/JSON/SQLite) that survives any platform.
• Explainability: prompts and transformations live in plain text in your repo.
• Rollback: everything shippable in under an hour, reversible in five minutes.

What you leave with

• A working prototype, not homework.
• A playbook (readme + prompts + scripts).
• A next-feature short list ranked by ROI.

If you want slides, I’m not your person. If you want something live next week, I’m your guy.