← Back to Blog

Before You Upgrade to GPT-5.6, Build an Eval Suite

Dhaval Bhatt
A glowing AI model core moving through transparent evaluation checkpoints on a dark purple and electric-blue circuit

A new model launches. The benchmarks look better. The price looks lower. You swap it into your product and expect an instant upgrade.

Then a customer finds the thing it quietly made worse.

That is the trap behind every major model release. OpenAI launched GPT-5.6 on July 9 with three tiers—Sol, Terra, and Luna—covering different cost and capability levels. Anthropic launched Claude Sonnet 5 days earlier with its own range of effort settings. The menu is getting better and more complicated at the same time.

For an AI product founder, the question is no longer, “Which model is smartest?” It is, “Which model performs my customer’s job reliably at a cost my business can support?”

You cannot answer that from a leaderboard. You need an eval suite.

An eval is your product judgment written down

An evaluation, or eval, is simply a repeatable test of whether an AI system does what you expect. You give it realistic inputs, define what a good result looks like, run the test, and compare the outputs.

OpenAI describes the process in three steps:

  1. Describe the task you want the model to perform.
  2. Run it against representative test inputs.
  3. Analyze the results and improve the prompt or system.

That sounds technical. It does not have to be.

Imagine you are building an AI assistant for commercial insurance submissions. Your first eval suite could be a spreadsheet with 25 anonymized cases. For each case, you include the source material and the expected outcome:

  • Did it identify the correct risk category?
  • Did it flag missing documents?
  • Did it avoid inventing facts?
  • Did it explain the next step in language a broker would trust?
  • Did it complete the task within an acceptable time and cost?

That spreadsheet is not busywork. It is your domain expertise converted into a product asset.

Anyone can connect an API. The founder who knows what “correct” means in a messy real-world workflow has the advantage.

New model launches make evals more valuable

GPT-5.6 did not launch as one universal model. Sol is the flagship, Terra is positioned as a balanced option, and Luna is the lowest-cost tier. OpenAI prices them differently and gives users multiple effort settings. Anthropic makes a similar cost-performance argument for Claude Sonnet 5, which can use more effort for harder agentic tasks.

This creates real product choices.

A high-capability model might handle your hardest 5% of cases beautifully while making the common 95% too expensive. A smaller model might be perfect for classification but miss subtle exceptions. A new tokenizer, prompt format, safeguard, or tool-use behavior can also change results even when the headline benchmark improves.

That is why “the new model is better” is not a migration plan.

Your eval suite lets you compare the current model and the candidate model on the exact work customers pay you to complete. Track at least four things:

  • Task success: Did it reach the correct outcome?
  • Reliability: Does it succeed repeatedly, including on edge cases?
  • Cost: What does one completed customer task cost?
  • Latency: How long does the user wait for a useful result?

The best model is the one that clears your quality bar with the strongest economics. Sometimes that will be the frontier model. Often it will be a cheaper model for routine work with a stronger model reserved for exceptions.

Start with 20 cases, not a giant testing platform

Founders delay evals because they imagine a complex engineering project. Start smaller.

Choose one workflow your product must perform well. Then build a test set with four groups:

  • Ten normal cases: the work your product sees every day.
  • Five edge cases: ambiguous, incomplete, or unusually difficult inputs.
  • Three failure cases: examples where the product previously disappointed a user.
  • Two adversarial cases: inputs that tempt the model to ignore rules, invent information, or take the wrong action.

Now define a simple scoring rubric. Use pass/fail where the outcome is objective. Use a short rating scale where judgment matters. Anthropic recommends deterministic graders when possible, model-based graders when necessary, and human review to calibrate the system. In plain English: automate the obvious checks and personally inspect the nuanced ones.

You can do the first version manually. Both OpenAI and Anthropic provide evaluation interfaces, but the core discipline matters more than the tool. Save the inputs. Save the expected results. Run the same cases before and after every meaningful change.

Your suite will grow from real usage. Every surprising failure should become a new test. Every customer correction should sharpen the definition of good.

Evals turn domain expertise into a moat

Most founders talk about proprietary data as if it must mean millions of records. A carefully curated bank of real tasks, expert answers, edge cases, and grading rules can be more useful than a large pile of unlabeled data.

That bank captures what you learned in the field:

  • Which details change the decision.
  • Which exceptions beginners miss.
  • Which outputs create risk.
  • Which explanation earns trust.
  • Which task is safe to automate and which needs human review.

Anthropic makes an important point: teams with evals can test new models quickly, while teams without them can spend weeks checking changes manually. That speed compounds. Each model release becomes an opportunity to improve quality or margins instead of a fire drill.

This is where a domain-expert founder can beat a technically stronger generalist. You do not need to train the model. You need to define the work, encode the standard, and protect the customer outcome.

Before you upgrade to GPT-5.6, Claude Sonnet 5, or whatever launches next, write down 20 cases your product cannot afford to fail. Run them. Compare the results. Let evidence—not launch-day excitement—choose the model.

That is how an AI demo becomes a dependable product.

If you want help turning your domain expertise into a focused AI product, a testable workflow, and a 12-week launch plan, book a strategy call. That is the work we do inside the AI Product Accelerator.


Sources: OpenAI, “GPT-5.6: Frontier intelligence that scales with your ambition” (July 9, 2026); OpenAI, “Working with evals”; Anthropic, “Introducing Claude Sonnet 5” (June 30, 2026); Anthropic, “Demystifying evals for AI agents” (January 9, 2026).