Free scorecard · 8 pages · Decide
A model cannot tell a stale feed from a fresh one.
Is your product's data ready for AI? Check before you build
Which of our data can an AI feature trust today, and what must we fix before we build?
- For CTOs, VPs of Engineering and Heads of Data or AI at U.S. B2B and vertical SaaS companies planning an AI feature on the data their product already holds and receives
- Proposed approach · Scorecard · 8 pages, PDF
What is inside
Score seven data areas from 0 to 2, run a one-day check on each, and know what to fix before the build and what can wait.
- Copperline Field scores 6 of 14, with two zerosA filled example
- Score seven areas before anyone writes a promptStep 1 · The scorecard
- Seven checks you can run this weekStep 2 · Check each area in a day
- Four questions decide the orderStep 3 · Fix first or fix while building
- Data first, then the model. Every number traced to a sourceFrom our work
- Bring this page to the Product ReviewYour notes for the call
This answers
Which sources, records and documents can the AI trust today?
Score seven areas from 0 to 2: sources, ownership, quality, history with outcomes, permissions and tenancy, freshness, and documents and text. An area scores 2 when, for example, every feed logs what loaded and failed, each source has a named owner and every row carries its customer before storage. Any 0 is fixed before the build, whatever the total.
Do we have past cases with known outcomes to test it against?
Take 25 closed cases and check whether you can find the real outcome of each without asking anyone. When past cases record what really happened, you can test the AI on your own cases before customers use it; when they do not, that gap is a finding.
What must we fix before we build, and what can wait?
Fix first anything that could show one customer's data to another, let the AI state a wrong number as a fact, or leave a source with no owner and no rule for which source wins. A gap the AI can see and say so about can be fixed while building, by passing the input status to the AI.
You also get
- A filled example: one product scored across seven data areas
- A scorecard for sources, ownership, quality, history, permissions, freshness and documents
- A one-day check you can run for each area
- Four questions that decide what to fix first and what can wait
Free preview
Read the first 3 of 8 pages now
Free to read here, no form needed. The form opens the other 5 pages and the PDF.
Page 1 of 8Cover 
Page 2 of 8Copperline Field scores 6 of 14, with two zeros 
Page 3 of 8Score seven areas before anyone writes a prompt 
5 more pages after the form
Seven one-day checks, the four questions that set the order of fixes, proof from our work and a page to bring to the call.
- Page 4Seven checks you can run this week
- Page 5Four questions decide the order
- Page 6Data first, then the model. Every number traced to a source
- Page 7Bring this page to the Product Review
- Page 8Find what your data must fix before the AI ships. Book a free 30-minute Product Review.
Related guides
More for the Decide stage
Report · 14 pages
What does an AI feature in an established software product really take to ship?
Report: State of AI features: what 52 projects needed
Get the reportWorksheet · 8 pages
EdTechWhich steps in our product need AI, and which feature should come first?
Guide: Pick your first AI feature: code, search, model or agent?
Get the guideTake the 3-minute checkChecklist · 8 pages
What must we know about our own product, and agree, before we add AI to it?
Guide: Before you build AI: inspect the system, agree on done
Get the guide
Your customers already expect AI from your product.
Let us make it real inside the product you run today.
