14 blind errors your solo model missed

01The Thesis Changed, Because the Data Said So

VerdictTank v4.0 was sold on a claim we could not defend: that a multimodel panel produces a better score than a single strong model. On 2026-08-12 we ran that claim against real proposals and it failed. What we found instead is a stronger product.

Why the spread is the signal

A single model scoring alone produces low variance. It reads the document once, forms one coherent opinion, and every dimension it emits is downstream of that opinion. The result feels authoritative precisely because nothing inside it disagrees.

A 6-seat panel of five different vendors cannot produce that coherence, and the incoherence is diagnostic. When a Financial Integrity judge scores a proposal 8.2 while an Execution Feasibility judge scores the same document 2.8, that 5.4-point spread is not noise. It is a precise statement: the money works, the delivery plan does not. A solo model averages that tension away into a single confident 6.1 and tells you nothing actionable.

02How We Found This: Four Generations and a Self-Review

VerdictTank is a proposal review engine, not a proposal writer. It ingests a finished document and returns scored dimensions plus a ranked list of concrete Fix-It items. The pipeline was not designed in the abstract. It was hardened across four architectural generations, and then it was pointed at its own proposals.

The self-review that broke the old thesis

Before selling a review engine we ran the engine on our own work. We assembled the panel and scored three real proposals, in full, with the same prompts and rubric a paying customer would get. One of the three was VerdictTank's own sibling product. The panel returned a NO GO on it.

That run executed on the v2.2 roster. It cost roughly $150 in inference across the three proposals and returned 8 reporting seats. Two seats were lost to a provider credit wall hit mid-run, one to a model family that could not be dispatched at all, and a meaningful share of the spend went to retries against models that were already dead. The incomplete panel is why v2.3 of the judge pool spec introduces a pre-flight health gate, a pre-baked failover roster, and a consolidated 6-seat roster, all covered in section 5. The results below are what those 8 v2.2 seats actually produced. We report them as measured and do not extrapolate them onto the 6-seat roster.

03Validation Run: 3 Real Proposals, 8 Reporting Seats

Every figure in this section comes from the 2026-08-12 validation run. Nothing is modeled, projected, or illustrative. The solo baseline is Claude Opus 5 scoring the same documents against the same 10-dimension rubric.

Panel mean vs solo baseline

Thesis under test: the panel must show a greater than 0.5 point advantage over the solo mean to justify premium pricing. Result: FAIL on all three proposals and FAIL in aggregate. Panel composition for this run was 8 reporting judges (4 Band A, 4 Band B) on the v2.2 roster. The v2.3 roster documented in section 5 consolidates to 6 seats.

Why the panel scored lower

The panel does not elevate scores. It sharpens error detection, and error detection on a flawed document moves the number down. All three proposals contained severe cross-cutting defects that additional specialist scrutiny exposed more precisely: fatal execution gaps, competitive mispositioning, and legal blockers. The solo baseline was directionally correct on all three. The panel added precision, not points.

That is the entire finding, and it inverts the sales pitch. If your proposal is sound, the panel will roughly agree with a good solo model and cost you more. If your proposal has a hole in it, the panel finds the hole and the solo model does not. You are not buying a score. You are buying the probability that a specific, expensive, named mistake gets caught before an evaluator or an investor finds it for you.

Specialist divergence, measured

04The 14 Errors: Every One Named

This is the product. Fourteen material errors the 8-judge panel caught that the solo baseline missed or underweighted, grouped by failure class. Each is a real finding from the 2026-08-12 run against a real document.

RFP Tank v1.0 · panel 4.40 vs solo 4.93

Panel verdict: NO GO. Estimated rework 40+ hours. Recommendation is to cut scope to two features, extend to 20 weeks, hire a second developer before month one, rebuild the financial model, and address CLEATUS directly.

VentureBuilt v2 · panel 6.14 vs solo 6.10

Panel verdict: CONDITIONAL GO with six named conditions. Estimated rework 15 to 20 hours. This is the case that most clearly shows the value: the panel mean (6.14) and the solo mean (6.10) are statistically tied, so on score alone the panel added nothing. What it added was a bimodal split, Financial 8.2 against Execution 2.8, and the four errors above.

CartMySupply · panel 4.29 vs solo 5.00

Panel verdict: NO GO, unanimous, zero outliers, tightest spread of the three. Estimated rework 60+ hours. The build estimate of 116 hours was independently judged 4x to 10x too low.

05Judge Pool v2.3: 6 Seats, 5 Vendors, Zero Double-Ups

The panel that produced the validation data ran 8 reporting seats on the v2.2 roster, after two seats hit a provider credit wall mid-run and one model family could not be dispatched at all. v2.3 is the spec written in response to that failure. It cuts the roster to 6 seats, keeps every distinct question the validation run proved was load-bearing, and drops the redundant generalist cross-checks that contributed correlated opinions rather than new findings. Full detail lives in the judge pool specification v2.3.

The roster

Five distinct vendors across six seats. Four scoring seats, four distinct scoring models. Zero model double-ups: no single model occupies two scoring seats, which is the constraint that keeps correlated failure out of the panel mean. Maximum vendor concentration is Anthropic at 2 of 6 (33%), inside the 40% ceiling. Every other vendor holds exactly one seat. The Research Agent and the Synthesis seat do not score, so the panel mean is computed from four independent specialist verdicts across four vendors.

The 6-seat flow

The Free tier runs a reduced 4-seat version of this flow: Research Agent, Primary Reviewer, Legal + Compliance, Synthesis + Gate. It drops Cross-Check and Financial + Market. That configuration still catches legal and compliance blockers, which was the single highest-value error class in validation, so a free review proves the concept on the errors that matter most without carrying the full panel cost.

What changed in v2.3

Latency

v2.3 targets a critical path of roughly 113 seconds, against 218 seconds measured on the v2.1 architecture. The improvement comes from band parallelism: Band A and Band B seats execute concurrently rather than sequentially, and the Synthesis seat is the only stage that must wait for all scoring seats to return.

The ten scored dimensions

Every scoring seat rates the proposal 1 to 10 on the same ten dimensions, so panel spread is computed dimension by dimension and not only in aggregate:

The Synthesis and Integrity Gate

The Band C seat never scores. It reads all scoring output and performs a fixed checklist: verify score arithmetic, compute panel means and per-dimension spread, compute the delta against the solo baseline, flag every score more than 1.5 standard deviations from the panel mean with a written rationale, and confirm the verdict follows from panel evidence rather than from the Primary Reviewer alone. That gate is what turns four scored opinions into one auditable report.

06Worked Example: VentureBuilt v2, Where the Score Said Nothing

This is the clearest case in the validation set, because it is the one where score elevation delivered exactly zero and error detection delivered everything. Real scores from the 2026-08-12 run.

Individual seat scores

What the outlier actually found

The 2.8 was not a grumpy model. The Integrity Gate challenged it at 1.91 sigma and it survived the challenge on evidence: a contractor budget broken 4x to 7x, an architecture that regressed from v1 with no schema and no API contract, and a founder workload of 37 engagements plus 950 hours alongside an MSP day job. The Team seat (4.4) and the Band A generalists (6.2 to 6.9) all acknowledged the same workload problem. They weighted it less severely. The Execution specialist is the only seat that forced it into the verdict.

Fix-It items, ranked by materiality

1. CriticalExecution
   Fix the contractor budget or cut the scope. $1,500/mo buys 105 to 140 hours at market rates, not the volume the plan assumes. Raise to roughly $7,500/mo or reduce scope to fit the hours actually purchased.
2. CriticalFinancial
   Restate Year 2 on a recognized-revenue basis. On run-rate the year looks healthy. On recognized revenue it loses roughly $11K to $18K. Present both.
3. HighCompetitive
   Withdraw or qualify the uniqueness claim. LivePlan Plan Review and IdeaProof already ship in this space. Reposition on a defensible axis.
4. HighTeam
   Name the contractor and the sourcing plan before Phase 2. A budget line with no named person is not a capacity plan.
5. MediumGo-to-market
   Map the Year 1 to Year 2 GTM bridge. Eight net-new signups per month appear in the model with no acquisition mechanism behind them.
6. MediumLegal
   Complete data protection and trademark clearance before Phase 0 to 1.

Panel verdict: CONDITIONAL GO. Estimated rework 15 to 20 hours. The solo baseline returned a 6.10 and none of the six conditions above.

07Pricing: Priced Per Error Found, Not Per Point Gained

Four tiers with declared review quantities. No asterisks, no fair-use clauses, no metered surprises. Every tier states exactly how many reviews it includes and exactly what an extra review costs. The pricing logic follows the revised thesis directly: a panel run is worth what a caught error is worth, and a caught error is worth far more than a point of score.

Full tier comparison

Declared quantities only. When a tier is exhausted the customer either buys overage at the published per-review rate or waits for the next cycle. Nothing is throttled silently and no tier promises capacity it cannot cost out, because a panel review has a real marginal cost and pretending otherwise is how usage-based products lose money.

What a review costs us, and why the panel is affordable

The v2.2 validation run cost approximately $150 in inference for three full proposals across eight reporting seats. That figure includes retries against dead models before the health gate existed, which is exactly the waste v2.3 was written to remove. It is the honest anchor, and it is deliberately the worst number we have.

A clean run on the consolidated 6-seat roster, with the pre-flight health gate preventing wasted dispatches and only four seats actually scoring, costs $5.20 per review. That is the number every tier below is built on.

Unit economics at declared quantities

Every declared quantity is margin-positive at full consumption, and so is every overage unit. The $15 overage prices at roughly 3x COGS. The $10 White-Label overage prices at roughly 2x COGS, which is the deliberate discount that makes the reseller math work. There is no consumption pattern inside these tiers that produces a negative unit, which is the whole reason every tier on this page ships a counted quantity and a published overage rate.

The reason a full 6-seat panel fits a $249 tier at five reviews per month is vendor mix and seat discipline. Only the Primary Reviewer runs a premium frontier model. The remaining scoring seats run strong mid-tier models from three different vendors, which is where the error-detection value came from in validation. Consolidating the roster down to six seats removed the redundant generalist cross-checks, not the specialists. Panel diversity is cheaper than panel depth, and diversity is what caught the 14.

Why the value question is not the score question

A single caught item in the top two rows pays for a decade of the Pro tier. That is the entire pricing argument, and it does not depend on the panel producing a higher score, which it does not. Note that the two highest-value rows are both legal and compliance findings, which is precisely why the Free tier keeps the Legal + Compliance seat.

Positioned against the authoring category

We are not a proposal team in a box. We are one high-value pass in the workflow. A buyer already spending $499 to $899 per month on an authoring tool should be able to add the error-detection layer. Pricing Pro at $249 is below the GC AI critique seat benchmark at $500/mo, and Enterprise at $799 is a peer price to the authoring tools that feed it while landing 3.1x under an enterprise authoring contract on an annualized basis. White-Label at $1,499 makes resellers whole: 50 included reviews re-billed at $200 to $500 each is $10,000 to $25,000 of tenant revenue against a $1,499 cost.

08Competitive Landscape: Nobody Sells the Errors

Every AI-native player in this space is an authoring tool. They generate drafts. The nearest substitute for what we do is not a competitor product at all. It is a single frontier model and a prompt, and validation showed exactly what that substitute misses.

Competitor prices are vendors' own published rates as of July 2026. Tools without public pricing are shown as sales-led. Every named product was verified to exist and to occupy the authoring category.

Why the DIY substitute is the row that matters

Any buyer sophisticated enough to want proposal review can paste their document into a frontier model and ask for a critique. That is the honest competitive threat, and it is the one we tested against rather than around. The result is in section 3: the solo model returns a defensible, directionally correct score, and it returned none of the six VentureBuilt conditions, none of the CartMySupply compliance exposure, and none of the RFP Tank competitive reality.

09Deployment Options

Two supported deployment shapes. Both are managed by IT Pro Partner below the application layer.

Shared responsibility: IT Pro Partner manages everything below the application layer (OS, container runtime, networking, backups, monitoring) under both options. The VerdictTank application and its model pipeline are the product team's responsibility.

10Legal, Privacy & Compliance

Trademark clearance, the Minimum Viable Legal framework, the controller and processor role map, the sub-processor training guard, corpus confidentiality, and incident response. Carried forward from v4.0 and updated for the five-vendor panel.

10.1 USPTO trademark clearance: "VerdictTank"

Status: preliminary clearance only. This is not a substitute for a formal search. This assessment was performed with open-web search tools only. USPTO TESS is a JavaScript-rendered application and a static fetch returns only the search shell with no query results. Before any trademark application is filed, a live interactive TESS search or a paid clearance search through a trademark attorney is required.

Open-web common-law search results (performed)

Recommendation

• Before Series A close or any public marketing scale-up, commission a formal USPTO clearance search for Classes 9, 42, 35 and 45.
• File an intent-to-use application for VERDICTTANK as a standard character word mark, Class 42 primary and Class 9 secondary.
• Do not file on the basis of this document alone. It is a preliminary desk review.

10.2 Minimum Viable Legal (MVL) framework

MVL is the internal gate name used in the architecture documents as the precondition for onboarding white-label and enterprise customers. It is not one document. It is five interlocking instruments that must all exist and be internally consistent before the white-label provisioning gate turns green.

The Free, Pro, Enterprise and White-Label tiers all require Terms of Service, Privacy Policy and the AI Disclaimer at minimum before any paid launch. White-Label additionally requires an executed DPA as a hard provisioning gate.

10.3 Controller and processor role map

10.4 Sub-processor training guard

Model clause for vendor DPAs

Enforcement rule: a vendor without a public, contractually confirmable training opt-out is excluded from the panel roster entirely and cannot be selected as a failover target. The only acceptable path for a non-compliant provider is a customer-side, explicit, revocable opt-in. Never a silent default, and never for corpus-eligible content. Each of the five rostered vendors is audited against this clause before it is eligible for a seat, and the audit is re-run at each roster revision.

10.5 Corpus confidentiality

The corpus is VerdictTank's most valuable long-term asset and its highest confidentiality exposure.

Anonymization pipeline

1. Source-content exclusion. Raw text fields excluded at the schema and ETL level.
2. Structural extraction only. ETL reads scored and aggregated fields, never freeform text.
3. Identifier stripping. Review, user and org identifiers replaced with a one-way surrogate key.
4. Free-text quarantine. A stricter named-entity pass before any inclusion.
5. k-anonymity floor. Public content published only when the cohort exceeds a minimum threshold.

Corpus contribution is off by default and requires explicit, separate opt-in. It is not bundled into ToS acceptance and is revocable at any time from account settings.

10.6 Incident response

Structured around the six functions of NIST CSF 2.0.

Wrong-verdict liability

Scenario: a customer submits a proposal, receives a favorable panel verdict, acts on it, and the verdict was wrong in a way that led to a bad decision. This is primarily a reputational risk. The liability cap bounds legal exposure and does nothing for reputation.

• Legal layer: the AI disclaimer fails closed on every surface, a $100 or 12-months-of-fees liability cap applies, and the terms explicitly instruct users not to rely on AI output for investment decisions.
• Confidence calibration: every verdict ships with panel spread, standard deviation, and outlier flags. A verdict with a 5.4-point spread is a materially different signal from a unanimous one, and the report says so on its face.
• The published FAIL: section 3 of this document is itself part of the defense. We publish the case where our own thesis failed, which is a stronger honesty posture than any disclaimer.
• Incident playbook: do not litigate merits publicly, point to the auditable disclaimer version shown to the user, offer a private re-review, and disclose plus correct any systematic flaw found.

Model provider outage disclosure

• Public status page distinguishing VerdictTank infrastructure incidents from upstream model provider incidents.
• Degraded-mode behavior: a panel that ran short of its full six seats is flagged visibly with the seat count and which roles failed over. We never silently substitute a provider without disclosure. The 2026-08-12 validation run is reported throughout this document at the 8 reporting seats it actually produced on the v2.2 roster, for exactly that reason.
• SLA language: uptime commitments are qualified as dependent on upstream provider availability.