Find a useful starting point
AI Discovery & Readiness
Turn “we should use AI” into a small, sensible plan that fits your people, information and budget.
Quoted to scope. Deliverables, schedule and fees are agreed before work begins.
Who it is for
Organizations interested in AI but unsure where it belongs
What we can deliver
- A working session to identify tasks worth improving.
- A prioritized shortlist of use cases, including where AI adds little value.
- Tool and data-handling considerations, approved uses and human review points.
- A scoped pilot proposal with success measures and a named owner.
The final scope, access requirements, schedule and included handoff are agreed for your engagement.
01 / Fit
When this is a useful next step
- Your team has several AI ideas but no agreed first use case.
- You need to understand information access, review responsibilities and tool costs before committing to a pilot.
- You want a decision document that explains what to try, defer or avoid.
02 / Delivery
How the work unfolds
Start with the work
Interview the process owner and review representative tasks. Describe the desired outcome and current constraints before choosing an AI product.
Compare candidate uses
Assess repeatability, available source material, data sensitivity, error consequences and whether a simpler change could help.
Check readiness
Review tool access, ownership, approved information, human review and practical operating costs. Document gaps that would block a responsible pilot.
Define the decision
Prioritize the opportunities and outline one pilot with a named owner, sample cases, success criteria and a go-or-stop checkpoint.
We agree on the scope, responsibilities, schedule and completion criteria before starting. These steps are adapted to that agreement.
03 / Handoff
What you can put to use
Use-case comparison
A prioritized shortlist with business rationale, assumptions, risks and reasons to defer unsuitable ideas.
Readiness and information map
The people, tools, information sources and approvals needed to begin.
Pilot brief
A proposed scope, evaluation approach and decision criteria that can inform a separate implementation quote.
Your proposal identifies the included outputs, their format and the review or handoff session. Further implementation or support is agreed separately.
04 / Preparation
What we need from you
- Invite someone who performs the work and someone who can approve a pilot.
- Bring examples of the task, existing policies and the tools already available to the team.
- Identify constraints such as budget, access, sensitive information and the consequences of a wrong answer.
Scope boundaries
This engagement produces analysis and a pilot recommendation. Building an integration, migrating information or rolling out a tool is separately scoped. Estimated benefits remain hypotheses until measured in the agreed workflow.
05 / Illustrative scope
What an engagement could look like
This is a planning example, not a client result or a promise of outcomes.
Starting situation
A team is considering AI for meeting summaries, document drafts and searching internal guidance.
Agreed work
Compare source availability, error impact and reviewer effort, then select the most testable use case.
Useful handoff
A decision-ready pilot brief with sample tasks, an owner and a review checkpoint. The example is illustrative; it is not evidence of a customer outcome.
06 / Questions
Before you inquire
What if we are not ready for AI?
The recommendation can be to improve process, access or source material first. Identifying a reason not to proceed is a useful discovery outcome.
Will we get a tool recommendation?
Where the evidence supports one, the brief explains suitable options and the requirements behind them. Licensing, implementation and any vendor relationship are disclosed in a separate proposal.
Start with a conversation.
Tell us who the work is for, what you want to improve and your preferred timing. We will confirm fit and provide a scope-based quote, with deliverables, schedule and fees agreed before work begins.