🔍 Read the full analysis: My September 2026 AI Workflow: Build With Opus, Dig With Sol on ThorstenMeyerAI.com
Get the latest gadgets delivered free with Prime
- Fast, free delivery on millions of items
- Prime Video, Amazon Music and more included
- Member-only deals all year
TL;DR
In a September 29 account, Thorsten Meyer described a workflow that uses Claude Opus 5.5 for building and newly released GPT-6.1 Sol for detailed review. He cites Artificial Analysis benchmark figures showing much lower per-task costs for Sol, while warning that benchmark scores do not establish which model will work best for a particular task.
Thorsten Meyer said September 29 that he uses Claude Opus 5.5 for building software and the newly released GPT-6.1 Sol for detailed investigation and review, a division based on benchmark capability scores and reported per-task costs. The account describes one user’s workflow; its figures do not establish which model performs best across other teams’ workloads.
Meyer bases his comparisons primarily on the Artificial Analysis Intelligence Index v4.3.x, which he describes as a general capability measure rather than a verdict on any particular workload. In his table, Opus 5.5 scores 58 at its top setting and costs $5.98 per task. GPT-6.1 Sol scores 51 at xhigh and costs $0.39 per task. The comparison spans different effort settings and does not by itself show how the models perform on the same real-world job.
For his own development work, Meyer says he uses Opus at high effort for routine building tasks and xhigh for harder work such as architecture, migrations and trust boundaries. His cited index figures put Opus at 54 for $1.82 per task at high, and 56 for $3.46 at xhigh. He says max effort costs $5.98 per task for a score of 58, a trade-off he rarely considers worthwhile.
Meyer assigns Sol a different job: examining a specific file or code change and providing a second review. Artificial Analysis figures cited in the account list Sol at 50 points and $0.32 per task at high, and 51 points and $0.39 at xhigh. The account also reports first-token times of 57 and 69 seconds at those settings, respectively, which may make them unsuitable for interactive use. Meyer says Astra, Fable, Sonnet and Luna remain options for more specific tasks, while Jev handles high-volume yes-or-no and routing decisions.
Opus builds. Sol reviews. Jev decides.
One price tape, six models
Score against cost, at every effort setting
The effort dial moves the bill more than the model
Claude Opus 5.5
Claude Sonnet 5.5
GPT-6.1 Sol: near-Astra scores at a fraction of the price
Three published settings
| Setting | Index | Cost per task | Output tokens | First token |
|---|---|---|---|---|
| medium | 48 | $0.21 | 15M | 5.3 s |
| high | 50 | $0.32 | 25M | 57 s |
| xhigh | 51 | $0.39 | 36M | 69 s |
Same score band, very different bill
My stack: who builds, who reviews
Cheaper tokens are not cheaper work
Read the numbers with four warnings
Part 2: Jev, the model that decides instead of writing
One call in, typed answers out
Three question types
Confidence is the superpower
Three uses running in my publishing operation
The fit test, then the shadow test
- Replay 300 to 500 past decisions
- Compare overall and per confidence band
- Read 20 disagreements, decide who was right
- High band at 95% or better?
- Own flag, off by default
- Canary on 5 to 10 units
- Roll out in the confident band only
24 use cases, sorted by how well they fit
Proven in production
- 1Relevance gate
- 2Language check
- 3Classifier fallback
Publishing and content
- 4Thin-source detector
- 5Same-event dedupe
- 6Product fits roundup
- 7Disclosure present
- 8Headline quality
- 9Comment moderation
Commerce and support
- 10Support-ticket routing
- 11Return-reason coding
- 12Review to feature complaints
- 13Catalogue taxonomy
- 14Order-fraud pre-triage
Software and AI systems
- 15LLM guardrail
- 16RAG passage filter
- 17Citation check
- 18Tool and intent routing
- 19Log-line triage
- 20PR risk triage
Business ops and home
- 21Inbox triage
- 22Expense categorisation
- 23Lead qualification
- 24Smart-home intent
Limits, cost and one hard rule
Why the Review Seat Matters
Meyer’s proposed split makes model selection a question of cost per useful task, not just a ranking by benchmark score. If a lower-cost model can provide a helpful review, running it across more changes may be affordable. The account’s figures suggest a sizeable price difference between Sol and several higher-scoring options, but they do not measure the quality or time savings of Meyer’s actual review process.
The workflow also highlights a limit of automated checks: Meyer argues that a second model can catch problems, but that model may still share a flawed specification or miss a failing case. He says passing tests are not approval to ship, and recommends giving the builder concrete failure evidence when review finds a problem. These are his process recommendations, not independently evaluated results.
Products Worth Considering

Logitech MX Mechanical Wireless Illuminated Keyboard, Tactile Quiet, Graphite

Kindle Paperwhite Signature Edition 32GB (2024 Model) – Metallic Black

Sony WH-1000XM6 Wireless Noise-Canceling Headphones, Black
As an affiliate, we earn on qualifying purchases.
From Model Rankings to Task Costs
Meyer frames his September comparison as a shift from leaderboard positions toward the cost of completing a task. He says six models fall within about 20 index points of one another, while their reported task costs differ by roughly 100 times. The source does not specify the full calculation behind that broad range, so it should be read as his summary of the table rather than a universal price ratio.
His account says Opus 5.5 was released September 22, Sonnet 5.5 on September 28, and GPT-6.1 Sol on September 29. It reports that Sol kept the listed token prices of its predecessor, GPT-6 Sol, at $2 per million input tokens and $10 per million output tokens. These release dates, prices and benchmark readings are those reported in the source and may change over time.
The figures also depend on the effort setting. Meyer’s table shows Opus rising from 51 index points and $1.34 per task at medium to 58 and $5.98 at max. He reports that Sonnet at max generated about 193,000 output tokens per task in the benchmark, while its listed task cost rose from $2.74 at xhigh to $7.60 at max. Such benchmark task costs are not the same as a team’s total labor or operating costs.
“The practical reading: Sol is not the model I ask to build. It is the model I can afford to run on everything.”
— Thorsten Meyer
What the Benchmarks Cannot Show
The source does not provide independent testing of Meyer’s workflow, the underlying task prompts, or evidence that the benchmark costs match typical software projects. It also cautions that one index point may fall within measurement noise and says Artificial Analysis had not published Sol’s low or max settings at the time of writing. The account does not establish whether the models’ relative performance holds for other tasks, users or later versions.
Some comparisons use different settings, and the reported cost per task reflects benchmark usage rather than the full cost of engineering work. Meyer offers an illustrative point that human review time can outweigh token-price savings, but the source excerpt ends before providing the full example. The amount of human time saved, the review’s error rate and the total cost of the proposed stack remain unclear.
Testing the Stack on Real Work
Meyer advises teams to shadow-test models on their own work before changing defaults. That means comparing outputs against the existing process and a defined quality bar before routing more tasks to a new model. The source does not announce a formal trial, publication schedule or additional benchmark release.
For readers considering the same division of labor, the next useful evidence would be results from their own tasks: whether Sol catches meaningful issues, how much review time it takes, and whether Opus at high or xhigh meets the required standard. Updated index scores, newly published Sol effort settings and measured end-to-end costs could change the comparison; none is confirmed in Meyer’s account as a future date or commitment.
Key Questions
What workflow did Thorsten Meyer describe?
He said he uses Opus 5.5 for building and GPT-6.1 Sol for detailed investigation and review, with other models assigned to specific tasks.
Why does Meyer use GPT-6.1 Sol for review?
He points to its reported benchmark cost of $0.32 per task at high and $0.39 at xhigh, and says the lower cost makes routine review practical for his workflow. The source does not independently measure whether that review improves outcomes.
Does the comparison prove Sol is better value for every team?
No. The index measures general capability, and the source says teams should shadow-test on their own workloads. Benchmark costs and scores may not reflect a team’s actual tasks or review time.
What trade-off does the source report for Sol at higher effort?
At high and xhigh, the cited first-token times are 57 and 69 seconds. Meyer says that delay makes those settings unsuitable for interactive work.
Source: ThorstenMeyerAI.com
