BUYER-SIDE VENDOR EVALUATION
Compare what vendors can document—not who tells the best story.
Put two or three GEO providers through the same twelve requests. Score only the material you actually receive, then export the comparison for procurement or leadership review.
This scorecard measures documentation completeness from your inputs. It does not validate a vendor, verify its claims, rank service quality, or recommend a winner.
Browser-only · Vendor names and ratings stay on this device
12 EVIDENCE REQUESTS
Build a side-by-side accountability record
Name the vendors locally, then rate the evidence each one supplies. ‘Not applicable’ removes that row from its denominator.
| 12 EVIDENCE REQUESTS | Vendor 01 | Vendor 02 |
|---|---|---|
| 01Observation method Ask for the exact engines or surfaces, dates, locales, repeated-run policy, and raw fields behind any visibility claim. | ||
| 02Query-set provenance Ask how buyer questions are sourced, approved, grouped by intent, versioned, and refreshed. | ||
| 03Surface scope Ask which answer engines, search features, publishers, communities, and owned surfaces are in or out of scope. | ||
| 04Evidence separation Require technical readiness, live mentions, citations, rankings, modeled opportunity, and revenue to remain separate measures. | ||
| 05Proof status Require every case or number to be labeled named, anonymized, illustrative, modeled, or self-reported with dates and limitations. | ||
| 06Intervention trace Ask to see a finding → owner → shipped change → dated re-test chain, including misses and unchanged results. | ||
| 07Attribution limits Ask how referral, self-reported discovery, CRM source, assisted conversion, and dark traffic are combined—and where attribution under-counts. | ||
| 08Deliverable ownership Confirm who owns prompt sets, evidence logs, content, source files, dashboards, and access after the engagement. | ||
| 09Implementation ownership Name who deploys technical changes, supplies expert facts, approves claims, handles legal review, and clears dependencies. | ||
| 10Failure disclosure Ask for documented failure modes, stop conditions, and the data used to persist, pivot, or halt. | ||
| 11Commercial terms Compare scope, exclusions, dependencies, third-party costs, renewal, termination, and change-control terms—not price alone. | ||
| 12Guarantees and ethics Reject guaranteed rankings/citations, fabricated experts, fake testimonials, stealth seeding, undisclosed paid editorial, or review manipulation. |
How to use the score responsibly
- 01Score artifacts and contract language you can inspect, not confidence in a sales answer.
- 02Use the same written request and deadline for every vendor.
- 03Treat critical missing items as review flags even when the overall percentage is high.
- 04Verify claims, references, security, legal terms, and financial fitness through your normal procurement process.
Scorecard boundaries
Does Tenten see the vendor names or scores?
No. The scorecard runs in your browser. Analytics receives only a vendor count and broad score bands after completion, never names or row responses.
Does the highest score mean the best agency?
No. It means that vendor supplied more of the requested documentation. Fit, execution quality, references, security, price, and contract review remain separate decisions.
Can I use this to evaluate Tenten?
Yes. Apply exactly the same requests to Tenten. Mark anything we cannot document as Partial or Not shown and retain the exported record.