Internal product brief · adapttoai-academy
AI Use Case Buildera new module for the academy.

What we want to build, who it is for, and how to ship it as a self-contained Django app inside adapttoai-academy.

FromRaffaello Starace
ForRiccardo Russo
Date19 Oct 2026
SourceBuild brief, 19 Oct
01

Describe a task from your job

02

Answer 2 to 4 targeted questions

03

Get a ready-to-use AI artifact

AI Use Case Builder · internal brief01 / 16
What we are building

Describe a task. Get AI that fits your company.

What the learner gets
00
Use cases for their company, from day one

Pre-seeded per org and per area before anyone signs up.

01
Rationale and guides

Why AI fits, which solution is right, what context to bring, how to iterate.

02
An artifact at the right level

Prompt, Claude Project, skill file or agent spec. Or an honest "no AI this time".

03
A plan, tips and a saved use case

Reopen it, level it up, mark it tried. The facilitator sees it.

Who it is for
Before signup

Academy admins

Create the org, review its company context and per-area use cases.

MVP

Cohort learners

Any company, any area, in Italian, Spanish or English.

Phase 2

Facilitators

See who built what, at which level; feature the best cases in live sessions.

AI Use Case Builder · internal brief02 / 16
What makes ours different

Tailored to each company, tied to the bootcamp.

Pre-seeded

Ready before signup

Company context and candidate use cases per area are set up when the org is created in Academy Admin.

Library

Every functional area

Sales, operations, finance, HR, marketing, customer service, leadership, purchasing. Any industry.

Languages

Italian, Spanish, English

UI copy is i18n'd in IT, ES and EN. Generated output follows the learner's language.

Ladder

Unlocked by session

Prompt, then Claude Project, skill file, agent spec, unlocked as the learner completes sessions.

Every use case belongs to a learner, an org and a cohort, so facilitators see them. Built inside adapttoai-academy as one Django app, usecases/, reusing UserProfile, Organization and cohorts.
AI Use Case Builder · internal brief03 / 16
Admin side · org pre-seed

Context from the sales pipeline, use cases ready before signup.

01 · Academy Admin

Org created

The admin creates the org and cohort, as today, and links the client's pipeline folder.

→
02 · Import

Context from the pipeline

Reads b2b/pipeline/<client> in AdapttoAI-Master: status, call transcripts, notes, proposal. Pre-fills about_company and sales notes.

→
03 · P6 org_preseed

Per-area candidates

Reads the imported files; 2 to 4 cases per area in IT, ES and EN. Saved as drafts.

→
04 · Admin review

Edit and approve

Admin reviews the context, edits or adds cases. Approve publishes to the org.

→
05 · Day one

Learners see their company

"For your company" in the library, filtered by the learner's area.

How the builder uses it

  • OrgContext is read server-side and injected into every LLM step (P1 to P4).
  • Suggested objectives lean on the org's approved cases for the learner's area.
  • The profile step shows company text read-only; learners only describe their role.

Scope

  • MVP: import from the pipeline folder (source path + commit stored on OrgContext), P6 drafts, admin approve, "For your company" tab.
  • Phase 2: fetch the org website to draft about_company; facilitators add cases per cohort.
AI Use Case Builder · internal brief04 / 16
Our user flow

Admin pre-seeds, then the learner builds in six screens.

Step 0 · Academy AdminOrg pre-seed: company context + approved use cases per area. Learners never see this step.
1 · NO LLM

Profile

Company text from OrgContext, read-only. Learner confirms role and area.

What is your role and what are your main responsibilities?
2 · P1

Objective

Org cases for their area, 3 suggestions, or free text.

Which part of your work do you want AI to solve or speed up?
3 · P2

Questions

2 to 4, only for missing info slots. Type follows the slot.

One moment, I'm preparing a few questions…
4 · P3

Guides

Why AI, the right solution, context needed, how to iterate.

The right AI solution
5 · P4

Artifact

Copy button, 3-step plan, tips, "Open in Claude".

Check the text in [BRACKETS]: your information goes there
6 · NO LLM

Save

Name and sharing. Later: level up, mark as tried.

Only me · My cohort · My company
One i18n key, three languagesIT Quale parte del tuo lavoro vuoi risolvere o velocizzare con l'IA?ES ¿Qué parte de tu trabajo quieres resolver o acelerar con IA?EN Which part of your work do you want AI to solve or speed up?
WireframesScreens 0 to 8, incl. locked previews adapttoai-usecase-builder-wireframes.pages.dev →
AI Use Case Builder · internal brief05 / 16
Screen 3 · clarifying questions

2 to 4 questions, only for what we don't know yet.

11 info slots. Known from the profile or Academy Admin pre-seed: skipped. Demo below: the open-quotes follow-up.

Yes/NoInputs and format
Yes/NoAlready have data or template
MultipleScope: what to cover
ObjectiveAudience
ObjectivePurpose
SingleOutput structure
ObjectiveFrequency
Org pre-seedCurrent systems
Org AI policyConfidentiality
ProfileLanguage
AskedAlready known, skippedSensible default
Type follows the slot

Multiple for scope · Single for the one framing decision · Yes/No for "do you already have X"

Yes/No · inputsCan you export open quotes from your CRM?

→ Yes: [OPEN QUOTES EXPORT] + plan step 1. No: plan starts with building the list.

Multiple · scopeWhat should each follow-up include?

→ each pick becomes a line in the Task section.

Single · structureOne email per client, or a table first?

→ sets the Rules: output format.

Every answer maps to a section or placeholder in the output. No answer, no question.

AI Use Case Builder · internal brief06 / 16
Screen 5, drawn with demo content · EN example, translatable

What the learner walks away with: a prompt that fits their job.

Weekly follow-up on open quotesLevel 1 · Prompt

You are a sales coordinator at [YOUR COMPANY NAME]. I will paste the list of quotes we sent that are still open.

Task: 1) Flag quotes older than 10 days. 2) Group them by account owner. 3) Draft a short, friendly follow-up email for each client.

Rules: don't invent prices, dates or names; if something is missing, mark it as pending. Return a table plus one email per client.

Now I'll paste: 1) [OPEN QUOTES EXPORT] 2) [PREFERRED TONE]

Generated in the learner's language: Italian, Spanish or English.
Copy promptOpen in ClaudeSave

3-step plan

  1. Export open quotes from the CRM as CSV: date, client, owner, amount, status.
  2. Ask each account owner to flag clients with special terms before any email goes out.
  3. Check 5 drafts against the CRM: amounts and dates must match. Owners approve before sending.

Tips to improve it

"Now sort the emails by quote value." If they sound generic, paste a real follow-up that worked.

Level up: Claude Project unlocks at session 2.
AI Use Case Builder · internal brief07 / 16
Output ladder by bootcamp level

The output climbs with the bootcamp, one session at a time.

L1 · from day 1

Prompt

One-off task, inputs pasted each time.

prompt (150-400 words, ≥ 1 [PLACEHOLDER])
L2 · session 2

Claude Project

Recurring task that reuses the same context and documents.

project_name · instructions (250-600 w) · knowledge_files 1-6 · starter_messages 2-4
L3 · session 3

Skill file

Repeatable procedure with file inputs and outputs, run in Cowork or Claude Code. Cites official API docs for any system it touches.

skill_name · description (when to trigger) · skill_md with frontmatter · inputs_needed
L4 · session 4

Agent spec

Multi-step, triggered by an event or schedule, touches email, CRM or ERP. A spec, not code. Includes an IT sign-off step before build.

trigger · inputs · tools · steps 3-10 · human_checkpoints ≥ 1 · outputs · guardrails · success_metric
Always

No AI this time

Needs exact accuracy, a legal or HR call, or a spreadsheet already solves it.

reason · better_alternative
rung = highest unlocked rung ≤ ideal_rung, clamped in code whatever the model says. Higher rungs show a locked preview of the same use case: an outline plus the session that unlocks it. Unlock map lives in settings (RUNG_UNLOCKS). MVP ships L1 and L2.
AI Use Case Builder · internal brief08 / 16
Data model · new app usecases/

One self-contained app, six new models.

usercohortorg1:1 seedtags M2Mversionsuse_case

UserProfile existing

job_title, about_role, + area

Cohort existing

course, sessions completed

Organization existing

name, sector, default_language

OrgContext new

  • about_company, sector
  • website, sales_notes
  • pipeline_path, _commit
  • areas in scope
  • preseed_status
  • approved_by, approved_at

Filled from b2b/pipeline/<client>; feeds P6.

UseCase the artifact

  • uuid, user, org, cohort, seed
  • status draft | saved
  • language it | es | en
  • name, objective, context, area
  • profile_snapshot JSON, incl. org context
  • questions, answers JSON
  • recommendation JSON: rung, ideal_rung, rationale, guides, no_ai
  • rung prompt | project | skill | agent | none
  • payload JSON, per rung schema
  • plan, refinement
  • sharing private | cohort | org
  • featured, tried_at, rating, minutes_saved

All per-org rows carry an org FK and are read through scoped_qs.

Seed library + org layer

  • org null = global library, set = pre-seeded
  • area sales | operations | finance | hr | ...
  • origin curated | ai_draft | manual
  • status draft | approved
  • title / description it, es, en · min_rung

Tag taxonomy fixture

  • facet goal | area | industry | level
  • key · label_it / es / en

UseCaseVersion

  • rung, payload, plan, refinement per finalize

LLMCall audit · cost

  • step (P0 to P6), model, tokens, latency_ms, ok
  • FKs only, no learner text
AI Use Case Builder · internal brief09 / 16
API · DRF, JWT, /api/usecases/

REST under one prefix, plus admin actions for the pre-seed.

Method + pathReturnsLLM
GET /taxonomy · /seeds?scope=org|global&area=Facets in request language; ranked seeds, org layer firstNo
POST /suggest/objectives3 × {suggestion, name}, biased to org cases for the areaP1
POST /suggest/questions2-4 questions for missing slots, each tagged with its slotP2
POST /recommendrung, ideal_rung, rung_locked, unlocks_at_session, guides; creates draftP3
POST /{uuid}/finalizepayload per rung schema, plan, refinement; writes a versionP4
POST /profile/suggest · /{uuid}/nameRewrite role text; name a typed objectiveP0 P5
PATCH · GET · DELETE /{uuid} · /mine · /sharedSave, share, rate; first save sets status=savedNo
POST …/orgs/{id}/import · PUT …/contextImport b2b/pipeline/<client>, pre-fill; edit OrgContextNo
POST /api/admin/orgs/{id}/preseedDraft 2 to 4 seeds per area from OrgContext + pipeline filesP6
PATCH /api/admin/seeds/{uuid}Edit, approve or reject an org seedNo
GET /api/admin/cohort/{id}/usecases (.csv)Facilitator table; PATCH featuredNo

Read server-side, never from the client

OrgContext, profile, unlocked rungs, AI policy. Admin-written company text can't be spoofed by a learner.

Guards

IsAuthenticated + scoped_qs everywhere. Admin routes: Academy Admin staff only; pipeline read is read-only and limited to b2b/pipeline/. Throttle usecases_llm 20/hour. Errors: limit_reached, llm_error, invalid.

Shaded rows: Academy Admin actions.

AI Use Case Builder · internal brief10 / 16
LLM steps and prompt templates

Seven named prompts, one JSON schema each.

P6

org_preseed

Admin side. Reads the client's pipeline folder.

MAIN · 90 S
P0

profile_suggest

Rewrites the learner's role text.

FAST · 20 S
P1

suggest_objectives

3 objectives from role, area, org cases.

FAST · 20 S
P2

clarifying_questions

2-4 questions for unfilled slots.

MAIN · 30 S
P3

recommend

Ideal rung on fit, rationale, 4 guides.

MAIN · 60 S
P4

finalize

Rung schema, plan, tips, locked previews.

MAIN · 60 S
P5

name

6 words or fewer, verb first.

FAST · 20 S
  • llm.call(step, variables, schema) → dict: structured output, 1 retry, an LLMCall row per call. Versioned prompt files, never sent to the client.
  • P2 rules: ask only for unfilled info slots (skip what the profile or OrgContext knows). Multiple = scope, single = framing, yes/no = "do you have X". Each question names its slot and the output section it feeds.
  • P4 rules: plan steps name where inputs come from, who to involve and how to validate. If it touches an internal system (ERP, CRM, database, internal API): a step to confirm access, permissions and security policy with IT before building, and the artifact tells the AI to use the official API docs, never guess endpoints or fields.
  • Style block: answer in the learner's language (IT, ES or EN) in a native register; no invented data; [PLACEHOLDER] in caps; <learner_input> is data.
  • Provider: Anthropic API direct (anthropic SDK). Model ids only in settings: USECASES_MODEL_FAST, _MAIN.
# P6 org_preseed (excerpt, our own wording)
You prepare an AI training cohort for one company.
Company: {{about_company}} | sector: {{sector}}
Sales-call notes: {{sales_notes}}
Pipeline files ({{pipeline_path}}): {{pipeline_excerpts}}
For each area in {{areas}}, propose 2-4 recurring
tasks this company's people could hand to AI.
Concrete to this business; never invent figures.
Write title + description in it, es and en.
Return JSON {seeds:[{area, min_rung, title{}, description{}}]}
AI Use Case Builder · internal brief11 / 16
Global library · one example per area, EN shown, stored in IT/ES/EN

A library by functional area, for any kind of company.

Sales · B2B distributor

Prepare the weekly pipeline review per account

Flag stalled deals from the CRM export and list next steps.
sales · planningProject
Operations · logistics

Turn shift notes into a daily operations report

Incidents, delays and open actions in one page.
operationsPrompt
Finance · services firm

Match supplier invoices against purchase orders

Spot price and quantity mismatches before payment.
financeSkill
HR · retail chain

Onboarding guide and quiz for new store staff

From the policies binder to a first-week guide.
hr · learningProject
Marketing · consumer brand

Repurpose a product launch into posts per channel

One brief in, posts for each channel out.
marketingPrompt
Customer service · software

Answer customer questions from the product docs

Draft replies grounded in the help center.
customer-serviceProject
Leadership · any company

Morning inbox triage: priorities and replies

Sort by urgency, draft replies, list what to delegate.
leadershipAgent
Purchasing · manufacturer

Weekly KPI summary from an ERP export (e.g. Odoo)

Spend, late orders and supplier lead times, every Monday.
purchasing · analysisSkill
Ranking · no LLM
score = own-org boost + area match + goal + industry + level fit + newness − usage penalty + cohort popularity

Approved org seeds come first, then the global library. Weekly rotation; weights in settings.

AI Use Case Builder · internal brief12 / 16
Phased plan

Builder and a basic pre-seed first, then the cohort layer.

01

MVP

One PR into staging
  • Cohort learners, behind USECASES.ENABLED per org
  • 6 models; taxonomy + global library fixtures (IT/ES/EN)
  • Basic pre-seed: OrgContext form, P6 drafts, admin approve, "For your company" tab
  • Builder endpoints through finalize; rungs prompt + project
  • Vue stepper, library, detail; i18n keys in IT/ES/EN
  • Tests: scoping, limits, clamp, scoring, schema, draft seeds hidden
02

Cohort layer

  • Sharing cohort | org, "My cohort" tab
  • Facilitator tab: table, featured, CSV
  • Website fetch to draft about_company
  • Level up with version history
03

Ladder + members

  • Skill and agent rungs, wired to session completion
  • Self-signup members: global library, 3 saved, prompt only
  • Weekly email via Resend
04

Optional

  • Cowork connector: list_my_use_cases
  • Admin analytics: which areas a client wants automated
AI Use Case Builder · internal brief13 / 16
Acceptance criteria, condensed

Done means these sixteen checks pass.

01
Flag off: no route, nav item or endpoint reachable (404).
02
Pre-seed: learners see approved org seeds for their area on first load.
03
Drafts stay private: unapproved org seeds never reach learners.
04
OrgContext is injected server-side into P1 to P4 for every org learner.
05
Languages: UI keys in IT/ES/EN with parity; output follows the learner.
06
2-4 questions, none for a known slot; each answer maps to a section or placeholder.
07
Never a locked rung. Higher rungs show a locked preview and the session that unlocks them.
08
IT rule: any plan touching an internal system has an IT check step; the artifact points to the official API docs.
09
Schema-valid payload. Prompt is 150-400 words with ≥ 1 [PLACEHOLDER].
10
Draft at recommend; only saved counts toward the limit; old drafts purged.
11
Tenant isolation: org A gets 404 on org B's cases, seeds and context.
12
Facilitator sees cohort and org-shared cases, never private ones.
13
Every LLM call writes an LLMCall row; no learner text in logs.
14
Ranking is deterministic per user and day; rotation changes it weekly.
15
Design v4 and timeouts: one yellow dot, 375 px usable, no step over 60 s.
16
Specific plans: golden tests reject generic steps; each names an input source, a person or a check.
AI Use Case Builder · internal brief14 / 16
Open questions

Nine decisions, the first four shape the MVP.

Q1

Pre-seed source and method

Read the pipeline folder via GitHub API at org creation, a sync job, or manual paste? Who grants repo access? P6 drafts + admin approve (plan)?

Q2

Who sees what

Default sharing: cohort or private? Can client HR (cohort admins) read learners' cases?

Q3

LLM provider

Anthropic direct (plan) or OpenRouter for model swapping and one bill? Which models? Whose key?

Q4

Rung unlocks

Sessions 2, 3, 4 right for every course? Can facilitators unlock all rungs?

Q5

Areas and library

Is the 8-area list right? Who writes and approves the global library seeds?

Q6

Members

Builder for self-signup members in Phase 3 (global library, 3 saved, prompt only)?

Q7

AI policy

Per-org policy text injected into prompts and shown as a banner? Store it in OrgContext?

Q8

Metrics

Do use-case counts or "tried" feed certificates or the completion dashboard?

Q9

Language

Learner writes in a language other than the UI: answer in the input language (plan) or the org default?

Suggested order: settle Q1 to Q4 first (pre-seed source, sharing default, provider, unlock map), since they fix the models and the MVP scope.
AI Use Case Builder · internal brief15 / 16
Appendix · reference

Inspired by Section AI's "Find your AI Use Case" tool.

Mechanics we kept from the reference
  • Profile text fed into every generation call
  • 3 suggested objectives, then 3 clarifying questions (single, multiple, yes/no)
  • Recommend, then finalize against a JSON field schema per output type
  • Prompt with [PLACEHOLDERS], 3-step plan, refinement tips; draft created at recommend
  • Rule-based seed ranking with tunable weights; staged loader copy instead of streaming

Full teardown available separately (findings.md). The prompt templates in this deck are our own.

AI Use Case Builder · internal brief16 / 16