Skip to content

Entry offer

Stage 01 of 6

AI opportunity assessment

Stage 01 of the KARPINITY Method, sold on its own: in 1 to 2 weeks, one AI idea becomes a business case with a named metric and owner, a regulatory screen and a first read on the data.

Duration
1-2 weeks
Price
On request, scoped to your use case
What you receive
  • A concept and business case: the use case, one named metric, a named owner, today’s baseline, the target and the reasoning behind it.
  • A regulatory applicability note: which frameworks plausibly apply to this use case, and why.
  • A first read on the data: whether the sources exist, who owns them, and whether anything obvious blocks access.
  • A recommendation: go straight to a proof of value, commission a data readiness review first, or stop.
What this doesn’t include
  • A source-by-source data audit. This stage establishes whether the data plausibly exists and who owns it. The data readiness review scores each source.
  • Building, prototyping or vendor selection.
  • A legal opinion. The regulatory note is a screening flag from people who work with revFADP, the EU AI Act and sector rules regularly. Your counsel signs off on a specific system.
  • A predetermined yes. A documented no is a valid result.
Who you need involved
  • The person who will own the metric if the project proceeds: two to four hours across the engagement, mostly interviews and one review session.
  • Someone who can speak for data protection or compliance: one to two hours.
  • Optionally, an expert on the process being changed: one to two hours.

What it is

A fixed-scope engagement that turns one AI idea into a concept and business case. You get the use case, one metric with a named owner, today’s baseline, a target, a screen of the rules that plausibly apply, and a first verdict on the data.

This is stage 01 of the KARPINITY Method. The method allows 3 to 5 weeks for stage 01; the assessment is its fixed-scope core at 1 to 2 weeks. When the data is the main risk, the data readiness review is added inside the same stage.

The success metric, defined up front

By the end of week 1 we write one sentence with you: “This succeeds if [metric] moves from [baseline] to [target], and [owner] signs off the measurement.”

Only 13% of Swiss companies work against clearly defined, measurable KPIs for AI projects (CorpIn GmbH with the University of St. Gallen, March 2025, n=1,338). If nobody on your side can own the number, that is the finding, and you learn it before paying for a build.

Week by week

Week 1

  • Kickoff with the metric owner and the people who touch the process today.
  • Discovery interviews: the current process, the decision it changes, who is affected.
  • First pass of the regulatory screen: whether revFADP, the EU AI Act or a sector rule such as GxP plausibly applies, and how seriously.
  • Agree the success sentence.

Week 2 (in a one-week engagement, this moves into the second half of week 1)

  • Draft the business case: metric, baseline, target and the assumptions behind the target.
  • Review session with your side to test the number and confirm the owner.
  • Finalise the regulatory note and hand over both documents with a walkthrough.

What you decide at the end

You decide one of three things, with a short document you can forward internally:

  1. Proceed to a proof of value. The case holds and the data question is already answered.
  2. Commission a data readiness review first. The case holds, but the data behind the metric is the main risk.
  3. Stop. The number does not justify the build, or nobody can own it. You leave with a documented reason.

Questions

How is this different from a strategy workshop?

A workshop produces ideas. The assessment produces one decision on one idea: a named metric, a baseline, a target and an owner, plus a recommendation to proceed or stop.

Do we need to have the data ready?

No. The assessment checks whether the data plausibly exists and who owns it. The data readiness review scores each source.

Is the regulatory note legal advice?

No. It flags which frameworks plausibly apply, so your counsel starts from a map. Counsel signs off on a specific system.

What if the answer is no?

You have spent 1 to 2 weeks instead of a build budget, and you hold a written reason.

What does it cost?

Price is on request and depends on the use case. We scope it on a short call before anything is signed.

What happens next

If the case holds, the usual next step is the data readiness review or, when the data question is already answered, the proof of value sprint. Start a project with the idea you want priced.