// work with us

Turn an AI workflow into a decision your team can review.

If your team has a workflow it wants to improve with AI, I can help map what it touches, compare the implementation paths, and make the open decisions clear before anyone moves toward rollout.

A focused research and planning engagement.

We start with a non-confidential description of the workflow and the decision in front of the team. We agree on the scope before any work begins.

Start a conversation →

// AI workflow review

Review one workflow before committing to a rollout.

For a team considering AI support drafting, the review would start with one bounded workflow: how a support request becomes a proposed response, where approved knowledge comes from, and when a person must take over.

What you bring

  • A plain-language workflow description and the decision the team needs to make.
  • A list of relevant systems, data sources, permissions, and known constraints.
  • A description of the current process, review steps, and escalation path.
  • Sanitized examples or references to representative cases, with no customer data or credentials.

What comes back

  • A short decision brief comparing improve, buy, extend, or build paths for this workflow.
  • A dependency and risk map covering knowledge, access, actions, handoff, and ownership.
  • A proposed test plan with acceptance criteria, failure cases, and evidence to collect.
  • Open decisions, accountable owners, and conditions that should pause further rollout.

Read an illustrative sample review (.md) →

The sample is fictional and illustrative. It is not a customer case study, measured result, security review, or production-readiness approval.

What I can help with

The work is designed for a specific workflow, such as finding answers across internal knowledge, drafting support responses, or coordinating an AI-assisted business process.

01

Define the workflow

Clarify the user, the outcome, the boundary of the first release, and the decision the team needs to make.

02

Map the dependencies

Document the systems, data, identity and permissions, human owners, integrations, and fallback process the workflow depends on.

03

Compare the paths

Assess whether the right next step is improving the current process, using an existing platform, buying a specialist product, or building a custom workflow.

04

Prepare the decision brief

Leave with the proposed approach, unresolved questions, tests to run, owners for the next decisions, and conditions that should pause the rollout.

The scope, deliverable, and working arrangement are agreed before any work begins. This page describes a proposed service, not a customer case study or a claim about completed engagements.