Skip to content
Stefan Manja
EN СР
01 / contact

Workflow review

Start with the workflow.

I take on a small number of projects where the operating problem, owner, and boundaries are concrete enough for the work to be useful. You do not need the solution shaped yet; the useful starting point is the workflow and what needs to become easier, faster, safer, or more reviewable. Workflow conversations are handled discreetly, and internal context is treated with care.

Direct email

stefan@stefanmanja.com

Clear workflow outlines usually get a response within 3 business days.

A rough workflow outline is enough for a first review; the key details are the workflow, users, current stage, and the constraints that will matter in practice.

Useful first emails

  • The workflow and users are easy to describe.
  • You can describe whether this is a new build, an existing prototype, or a workflow decision that needs review.
  • There is already an owner, a current stage, and a constraint that will matter in practice.

Usually too early or not the right shape

  • Pure idea-stage exploration with no real workflow owner or adoption path.
  • Generic “AI transformation” requests without a defined problem to solve.
  • Chatbot or demo-first work where operational quality and adoption are not the goal.

Workflow review

Enough context for a first workflow review.

One or two sentences are enough.

Known constraints

Current tooling, team size, timeline pressure, or trust requirements - whatever is already clear.

Submissions are sent via Formspree and used only to reply to your message.

What happens next

  • I review the workflow, current stage, and constraints.
  • If it looks like a fit, I reply within 3 business days.
  • If useful, I point to the likely next path: build, harden, simplify, stop, or a scoped advisory conversation.
  • If it is not the right shape, I will usually say that directly.