Odysı
See if we fit
Field assessment Five questions · Two minutes

Is your AI project worth building?

The AI Project Scorecard scores your project on the five things that decide whether an AI build earns its cost. Honest by design: sometimes the right answer is do not build it.

The AI Project Scorecard
{{ counter }}
{{ qNum }}

{{ qTitle }}

{{ qDesc }}
{{ scoreDisplay }} / 10
{{ verdictKicker }}

{{ verdictTitle }}

{{ verdictCopy }}

Your weakest ground: {{ weakList }}. That is where we would look first.

Get your full readout

We will send your score, what it means for your case, and the two or three things to fix first. One email with your readout. No list, no sequence.

That did not go through. You can email us your score directly at thomas@odysi.studio.

We only use this to send your readout. Privacy policy

On its way

Your readout will land in your inbox shortly. If your score has you thinking, the fastest next step is a short call. No pitch, just a second opinion.

Book a 30-minute call

The scoring comes from our published framework, How to tell if an AI project is worth building. The most valuable outcome is often a confident no.

In full

The five questions

Each question scores 0, 1, or 2. Add them for a total out of 10. Here is the full scorecard in plain text, so you can think it through before you run the tool above.

  1. 01Is the problem real and expensive enough?It has to genuinely cost you time, money, missed revenue, or errors. A clear yes: you can point at the hours or the cost, and it is significant.
  2. 02Does the work follow a pattern?AI is strong on pattern-following work, weak where every case needs rare judgment. A clear yes: most of the volume follows a knowable pattern, and only a minority needs a person.
  3. 03Is the data or knowledge actually there?A tool is only as good as what it draws on. A clear yes: the data or knowledge exists and is accessible, or getting it there is cheap.
  4. 04Does the value clear the cost, including running it?Set the return against the build plus the ongoing cost. A clear yes: the honest return comfortably exceeds the build and running cost.
  5. 05Can your team keep it running on their own?A tool only one expert can keep alive is fragile. A clear yes: once built, your team can run it day to day, and maintenance is manageable.
Reading the score

What your total means

8–10 · Build
A strong candidate.

This has the shape of a project that earns its cost. Build it, ideally starting with a small proof of concept that touches your real data early.

5–7 · Not yet
Promising, but not obvious.

Worth pursuing, not worth committing to as framed. Fix the weak answers first, usually data or scope, and the score moves quickly.

0–4 · Wait
Not worth building as framed.

As it stands, this project would likely join the majority that fail. Narrow it, solve a different part of the problem, or decline. That decision is a win.