Mark v5.0/v5.1 SUPERSEDED (error-detection thesis failed at -0.40 delta); v4.1 is canonical. Cut v4.1 proposal with 12 version strings bumped. Moonshot to Mistral across production seats; production worker de-kimi'd 2026-08-18. Data-retention posture corrected 7/9 to 8/9 no-training (DeepSeek sole exception). Reconciled COGS with measured Mistral spend. Committed deployed v4.0 content and research docs to resolve the repo/live fork.
180 lines
9.5 KiB
HTML
180 lines
9.5 KiB
HTML
|
|
<!-- ====== 7. PRICING ====== -->
|
|
<section id="pricing">
|
|
<h2><span class="n">07</span>Pricing: Priced Per Error Found, Not Per Point Gained</h2>
|
|
<p class="lead">
|
|
Three tiers. 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.
|
|
</p>
|
|
|
|
<div class="pricing-grid">
|
|
<div class="price-card">
|
|
<h3 style="margin-top:0">Free</h3>
|
|
<div class="price">$0</div>
|
|
<ul>
|
|
<li>1 full review</li>
|
|
<li>Top 3 Fix-It items</li>
|
|
<li>Panel score and spread</li>
|
|
<li>Reduced panel size</li>
|
|
</ul>
|
|
<div class="price-purpose">Purpose: prove it on one document</div>
|
|
</div>
|
|
<div class="price-card price-card--featured">
|
|
<div class="ribbon">Most popular</div>
|
|
<h3 style="margin-top:0">Pro</h3>
|
|
<div class="price">$79<span>/mo</span></div>
|
|
<ul>
|
|
<li>5 reviews per month</li>
|
|
<li>Full 11-seat panel</li>
|
|
<li>Complete Fix-It list, ranked</li>
|
|
<li>Panel spread and outlier flags</li>
|
|
<li>Solo-baseline delta comparison</li>
|
|
<li>Re-score loop with before and after</li>
|
|
</ul>
|
|
<div class="price-purpose">Purpose: the founder or solo bid writer</div>
|
|
</div>
|
|
<div class="price-card">
|
|
<h3 style="margin-top:0">Enterprise</h3>
|
|
<div class="price">$299<span>/mo</span></div>
|
|
<ul>
|
|
<li>Unlimited reviews</li>
|
|
<li>White-label branding</li>
|
|
<li>Multi-seat team workspaces</li>
|
|
<li>Configurable judge pool</li>
|
|
<li>Corpus isolation and data controls</li>
|
|
<li>Priority pipeline and support</li>
|
|
</ul>
|
|
<div class="price-purpose">Purpose: proposal teams running color reviews</div>
|
|
</div>
|
|
</div>
|
|
|
|
<h3>What a review costs us, and why the panel is affordable</h3>
|
|
<p>
|
|
The validation run cost approximately $150 in inference for three full proposals across eight
|
|
reporting seats, including retries against dead models before the health gate existed. That
|
|
burn is the honest anchor for panel economics: a clean 11-seat run on one proposal, with the
|
|
health gate preventing wasted dispatches, sits well inside single-digit dollars.
|
|
</p>
|
|
<p>
|
|
The reason a full 11-seat panel fits a $79 tier at five reviews per month is vendor mix. Only
|
|
a minority of seats run premium frontier models. The specialist Band B seats run strong
|
|
mid-tier models from five different vendors, which is where the error-detection value came from
|
|
in validation. Panel diversity is cheaper than panel depth, and diversity is what caught the 14.
|
|
</p>
|
|
|
|
<h3>Why the value question is not the score question</h3>
|
|
<table>
|
|
<thead><tr><th>Error class</th><th>Real example from validation</th><th>Cost of missing it</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Legal blocker</td><td>Charitable solicitation registration in 40+ states</td><td>$30K to $75K of registration, against $3K to $14K of projected revenue</td></tr>
|
|
<tr><td>Compliance total</td><td>Full first-year compliance load on the same proposal</td><td>$60K to $150K, exceeding Year-1 revenue by roughly 10x</td></tr>
|
|
<tr><td>Execution gap</td><td>Contractor budget short by 4x to 7x</td><td>Roughly 800 unbudgeted founder hours</td></tr>
|
|
<tr><td>Revenue arithmetic</td><td>$2.7M headline against $269K computed from the document's own inputs</td><td>Credibility with any investor who checks the math, which is all of them</td></tr>
|
|
<tr><td>Competitive blind spot</td><td>A $4M-seed funded direct rival never named in the document</td><td>The first question in the room, unanswered</td></tr>
|
|
</tbody>
|
|
</table>
|
|
<p class="table-note">
|
|
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.
|
|
</p>
|
|
|
|
<h3>Positioned against the authoring category</h3>
|
|
<table>
|
|
<thead><tr><th>Comparison</th><th>Their price</th><th>VerdictTank</th><th>Multiple</th></tr></thead>
|
|
<tbody>
|
|
<tr><td>Pro vs Bidara Starter</td><td>$499/mo</td><td>$79/mo</td><td><strong>6.3x cheaper</strong></td></tr>
|
|
<tr><td>Pro vs AutoRFP.ai Scale</td><td>$899/mo</td><td>$79/mo</td><td><strong>11.4x cheaper</strong></td></tr>
|
|
<tr><td>Enterprise vs Bidara Starter</td><td>$499/mo</td><td>$299/mo</td><td><strong>1.7x cheaper</strong></td></tr>
|
|
<tr><td>Enterprise vs AutoRFP.ai Scale</td><td>$899/mo</td><td>$299/mo</td><td><strong>3.0x cheaper</strong></td></tr>
|
|
</tbody>
|
|
</table>
|
|
<p>
|
|
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 without a second budget conversation. Pricing Pro at $79 makes VerdictTank an add-on
|
|
decision rather than a platform decision.
|
|
</p>
|
|
</section>
|
|
|
|
<!-- ====== 8. COMPETITIVE LANDSCAPE ====== -->
|
|
<section id="competitive">
|
|
<h2><span class="n">08</span>Competitive Landscape: Nobody Sells the Errors</h2>
|
|
<p class="lead">
|
|
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.
|
|
</p>
|
|
|
|
<table>
|
|
<thead>
|
|
<tr><th>Product</th><th>Category</th><th>Published price</th><th>Relationship to VerdictTank</th></tr>
|
|
</thead>
|
|
<tbody>
|
|
<tr><td><strong>AutogenAI</strong></td><td>Enterprise authoring</td><td>Custom, sales-led, no self-serve</td><td>Complementary. We find the errors in what it writes.</td></tr>
|
|
<tr><td><strong>Civio</strong></td><td>Gov RFP authoring</td><td>Custom, sales-led</td><td>Complementary. Downstream reviewer.</td></tr>
|
|
<tr><td><strong>Bidara</strong></td><td>Mid-market authoring</td><td>$499/mo Starter</td><td>Complementary. Transparent pricing, natural comparison anchor.</td></tr>
|
|
<tr><td><strong>AutoRFP.ai</strong></td><td>Response automation</td><td>$899/mo Scale</td><td>Complementary. Reviews its drafts.</td></tr>
|
|
<tr><td><strong>DeepRFP</strong></td><td>Lean-team authoring</td><td>$89/user/mo</td><td>Complementary. Lowest per-seat price in the category, natural partner.</td></tr>
|
|
<tr><td><strong>A solo frontier model</strong></td><td>DIY substitute</td><td>API cost only</td><td><strong>The real competitor.</strong> Measured: misses or underweights the material errors a panel catches.</td></tr>
|
|
<tr class="comp-table__us"><td><strong>VerdictTank</strong></td><td><strong>Panel error detection</strong></td><td><strong>Free / $79 Pro / $299 Enterprise</strong></td><td><strong>The only 11-seat, 9-vendor review panel with a published integrity gate</strong></td></tr>
|
|
</tbody>
|
|
</table>
|
|
<p class="table-note">
|
|
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.
|
|
</p>
|
|
|
|
<h3>Why the DIY substitute is the row that matters</h3>
|
|
<p>
|
|
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.
|
|
</p>
|
|
|
|
<div class="defense-grid">
|
|
<div class="defense-item">
|
|
<h4 style="margin-top:0">1. Incumbents cannot sell honest criticism</h4>
|
|
<p>
|
|
Authoring tools sell the promise that they write your proposal. A brutal error list on the
|
|
output that same tool just produced is a direct admission the generated draft is losing. It
|
|
is structurally against their interest. We have no draft to defend. The verdict is the
|
|
product.
|
|
</p>
|
|
</div>
|
|
<div class="defense-item">
|
|
<h4 style="margin-top:0">2. Review is where the money is decided</h4>
|
|
<p>
|
|
Every serious bid already goes through a review gate, the color-team pass organizations run
|
|
manually by pulling senior staff off billable work. That labor is expensive, slow,
|
|
inconsistent between reviewers, and unavailable to the solo consultant. The demand is proven
|
|
by the existence of the manual process.
|
|
</p>
|
|
</div>
|
|
<div class="defense-item">
|
|
<h4 style="margin-top:0">3. Panel orchestration is a real moat</h4>
|
|
<p>
|
|
Nine vendors, health gating, pre-baked failover, no model double-ups, and an integrity gate
|
|
that challenges its own outliers is not a prompt. It is an operations problem, and the
|
|
2026-08-12 run is the evidence of what it costs to learn.
|
|
</p>
|
|
</div>
|
|
<div class="defense-item">
|
|
<h4 style="margin-top:0">4. An empty category sets its own price</h4>
|
|
<p>
|
|
A crowded category means the budget line exists and you fight for share. An empty review
|
|
category means we define the line and set the reference price, while remaining complementary
|
|
to every authoring tool in the table above.
|
|
</p>
|
|
</div>
|
|
</div>
|
|
|
|
<div class="positioning-statement">
|
|
The authoring tools write proposals. A solo model grades them smoothly.<br>
|
|
VerdictTank tells you the fourteen things both of them got wrong.
|
|
</div>
|
|
</section>
|