A map of one workflow
The steps, tools, sample inputs, and recurring problems behind the task you choose.
Get a practical recommendation for one business workflow: what to change, whether AI fits, and what a first project would require.
From $1,500 USDOne-time project. Software and usage billed separately.
30 minutes with the co-founders. Check fit, tools and the next scoping step.
Before choosing an AI tool, check whether the problem is a handoff, missing source data, or a rule that could be automated without AI. Strategy should tell you what to do next, what to leave alone, and why.
You know which workflow causes repeated work but are unsure what to change.
You need to compare AI with automation, existing software, or a process fix.
A proposed build needs a clearer scope, owner, and acceptance criteria.
From $1,500 USD
One-time project. Final scope and price agreed in writing.
Decide whether one business workflow is worth improving, what to change, and what a first project would involve.
Book a free scoping call ↗30 minutes with the co-founders to check fit, tools and the next scoping step. No obligation to proceed.
All prices are in USD. Third-party software, API usage, hosting and any telephony charges are separate. Support is optional; its coverage and limits are agreed separately. New workflows need a new scope.

The steps, tools, sample inputs, and recurring problems behind the task you choose.
AI, standard automation, and process changes assessed against that workflow. Keeping the current approach can be a valid recommendation.
The next step, its dependencies, and a first project scope with acceptance criteria. Implementation is quoted separately.
Bring one task and your current tools. We’ll discuss the first step in a free 30-minute call.
Customer support is spending time looking for policy answers.
Map the questions, approved sources, and points where judgment matters.
Compare a source-linked assistant with better search and a simpler process.
Choose a bounded pilot only if it has an owner and a testable benefit.
Map recurring questions and source gaps before choosing an assistant or changing the support process.
Explore the workflow 02Separate missing information, unclear authority, and repeated handoffs to choose a useful first change.
Explore the workflow 03Identify one preparation task worth improving, with agreed records, definitions, and a finance owner.
Explore the workflowReview one workflow with its owner and inspect suitable examples.
Assess process changes, existing software, automation, and AI against the same need.
Review the recommendation and dependencies. Agree what to investigate, build, or leave unchanged.
An audit does not include an unbounded implementation, a guaranteed return, or a recommendation to replace your team. Access and interviews are agreed first; sensitive records are not needed for an initial outline.
Security and data questions ↗One-workflow AI assessment starts at $1,500 USD for the starter scope shown on this page. We confirm access, scope, exclusions, timing and a written price before work begins. Third-party software and usage charges are separate; ongoing support is optional.
In 30 minutes, we discuss one task, your current tools and the result you need. We check whether the starter fits and what is needed for a written proposal. If paid discovery is needed, we explain its scope and price first. You do not need a prepared brief or a paid assessment to book the call.
We agree a baseline and acceptance checks with the person who owns the work. You can decide what to build, what it depends on, and how to judge the result. Where relevant, we also compare manual effort, correction work and operating costs. These checks guide the handoff; they are not a promise of revenue or savings.
A scoped engagement can deliver a workflow map, a prioritized shortlist of opportunities, and a first-project brief. The brief records the users, sources, dependencies, acceptance criteria, and unresolved decisions. Implementation is a separate scope; the recommendation may be to improve the process before introducing AI.
Yes. Choose a recurring task and identify the person who owns it. A normal example, a difficult example, and a description of the current handoffs help make the assessment concrete. You do not need to choose a model or write a technical specification first.
The main factors are the number of workflows, stakeholder interviews, systems to assess, and depth of data review. A focused decision brief needs different work from an organization-wide roadmap. Agree the questions, deliverables, and access requirements before pricing the engagement.
Timing depends on access to the workflow owner, representative examples, and the people who can explain the systems. Unclear source ownership or unresolved business rules can add a discovery step. The proposed scope should identify these dependencies before a delivery date is agreed.
An initial discussion can use a process outline and redacted examples. Any deeper review should specify the records required, who can access them, and how they will be handled. Credentials and sensitive records should wait until an appropriate sharing method has been agreed.
Review the options with the people who will own the work. The next decision may be a scoped pilot, preparation of missing data, use of an existing tool, or no build. Any implementation, ongoing advisory work, and maintenance need their own agreed responsibilities and terms.