Start with the shape of the problem.
Every engagement is bounded before it begins — fixed scope, written acceptance criteria, documentation and a real handoff at the end. No open-ended dependency. No unlimited on-call promise.
AI implementation, sized to the constraint
I look for the current-state cost, quality risk, and adoption burden first. Then I recommend a system sized to the opportunity. Start with the business process, not the tool.
AI Opportunity Audit
- Workflow and constraint map
- Build-versus-buy guidance
- 90-day action plan, ranked by where AI earns its keep
Bespoke AI Agent / System Build
- Written scope and acceptance criteria
- Evaluation and reliability controls
- Documentation and handoff — you own it after
Fractional AI Advisory
- Roadmap and cost review
- Team training and evaluation discipline
- Incident diagnosis and governance
What the work actually looks like.
Illustrative samples — not client work. Names and numbers are fictionalized. These show the shape and rigor of a real engagement deliverable, so you know what you're buying before the discovery call.
Sample AI Opportunity Audit
A practical assessment of where AI can reduce friction, where it should not be trusted yet, and which pilot deserves investment first. The recommendation is not "add AI everywhere" — it is to remove one measurable bottleneck without weakening customer trust.
View the sample audit (PDF) →Sample AI Implementation Plan
A six-week, human-in-the-loop pilot plan for a retail and e-commerce operation — scope, milestones, responsibilities, and acceptance criteria, written the way a real engagement would be.
View the sample plan (PDF) →Fractional ops, not just advice about ops.
Before I built software, I spent 22+ years running frontline operations — teams, P&L, labor, inventory, multi-site transitions. If your problem is the operation itself rather than the technology around it, this is the lane.
Fractional operations leadership
- P&L ownership and financial accountability
- Labor planning, hiring, and team leadership
- Multi-site operations and transitions
- Training systems and operational documentation
Operator's-eye AI readiness
Most AI failures are operations failures with better branding. I evaluate whether your workflows, data hygiene, and team capacity can actually carry an AI system — before anyone builds one.
Discuss readiness →Design that makes ideas legible
I've iterated a brand identity through dozens of versions and condensed sprawling systems into 12–15 slide decks. That process — distill, draft, test against reality, refine — is the service.
Logo design
Discovery first — your three brand words, where the logo lives, what you dislike. Multiple concepts, structured revision rounds, final files in every format you need.
Start a logo project →Presentation design
Pitch decks, investor updates, conference talks. I condense complex material into a narrative an audience can follow — then make every slide earn its place.
Start a deck project →Web design
From landing pages to full sites — designed mobile-first, built to load fast, written so a human can maintain it after handoff. This site is the sample.
Start a web project →Custom software builds
Bounded builds with the same discipline as the advisory lane: written scope, acceptance criteria, evaluation where it matters, documentation at handoff.
Start a build project →Clarity before complexity
Discovery call
We confirm the business problem, urgency, owner, data, constraints — and whether there's a real fit. Bring the messy version.
Fixed-scope proposal
Outcome, deliverables, exclusions, timeline, price, responsibilities, acceptance criteria — written down before work starts.
Build or advise
Work moves through visible milestones. Uncertainty is surfaced early, not buried in the handoff.
Handoff
Documentation, operating guidance, known limitations, and a walkthrough. Useful systems leave you more capable — not dependent.
Asked plainly, answered plainly.
What does "fixed scope" actually include?
Every engagement starts with a written proposal: outcome, deliverables, exclusions, timeline, price, responsibilities, and acceptance criteria — agreed before work begins. If it isn't written down, it isn't in scope.
Who owns the work when it's done?
You do. Every engagement ends with documentation, operating guidance, known limitations, and a walkthrough for whoever owns it next. Useful systems leave you more capable — not dependent.
How do revisions work?
Creative work (logos, decks) includes structured revision rounds with multiple concepts up front. For builds and advisory, the acceptance criteria define "done" — anything beyond the agreed scope gets re-scoped in writing before it starts, never mid-stream by surprise.
What does the handoff look like?
Documentation, operating guidance, known limitations, and a walkthrough with the next owner. Uncertainty is surfaced early in the engagement — never buried in the handoff.
How long do engagements take?
Opportunity audits run 1–2 weeks. Bespoke builds typically run 3–8+ weeks depending on scope. Fractional advisory is month-to-month. Operations engagements are scoped per situation after a discovery call.
Do you work part-time / contract / fractional?
Yes — that's the model. Advisory, build, design, and operations engagements are all structured as bounded contracts, and I'm set up for part-time and fractional arrangements.