USE CASE DISCOVERY
Document an AI use case in your own words.
Last updated: July 10, 2026
A guided interview that walks you through the same 16-field instrument TigerTiger uses in every Discovery Sprint and CAIO engagement — conversational instead of a form, and it runs entirely inside your own Claude.
Who this is for
Two kinds of people use this. A warm prospect who's had a Discovery Sprint call and wants to put a real process on paper before pricing gets discussed. Or an engaged CAIO client documenting the next use case in their pipeline. Either way, you're not filling out an intake form for TigerTiger — you're building your own write-up of how a piece of work actually happens today, detailed enough that TigerTiger (or anyone else) can scope and price it accurately.
How to start it
Open your own Claude (wherever TigerTiger is installed) and type:
let's start the AI use case discovery That's it. No form to open, no account to create, no separate app.
What to expect
It asks one question at a time — never a batch, never a form dump. There are 16 fields in total, and the second question is deliberately not about mechanics: before anything else, it asks why this matters to you — what's actually going wrong today, what it costs you. Everything after that traces back to that answer.
A single, well-answered use case can take 20–30 minutes or more — this is meant to get real detail, not a quick checklist. If an answer is thin on a field that matters for scoping, it'll ask a sharper follow-up rather than accept a one-line summary. You can stop at any point and pick up again later: it re-reads what you've already saved and continues from the first unanswered field. There's no session timer and nothing to lose by pausing.
Nothing you say reaches TigerTiger's server.
This isn't a policy promise — it's how the tool is built. Your own Claude asks the questions and writes your answers straight to a file on your own machine. TigerTiger's server hands your Claude the interview instructions once, at the start, and has no further part in it: no database write, no upload, nothing logged. The only way TigerTiger ever sees what you write is if you decide, afterward, to send the finished file yourself.
What happens after
You end up with a complete write-up — your own file, in your own words, covering the process, the numbers, the decision rules, and what "good" looks like. It's yours. Reuse it for internal buy-in, hand it to another vendor, keep it for your own records. Sending it to TigerTiger is a normal next step you take with your own document, not something the tool does for you — there's no submit button and no automatic upload.