PlaysbyMoat8
Back to the library
The workflow guideOperations

Compare software vendors

Research suitable vendors and compare pricing, requirements, and documented capabilities in a decision sheet.

6 implementation stepsIntermediate

How this works

Research suitable vendors and compare pricing, requirements, and documented capabilities in a decision sheet.

Compare vendors against requirements and a consistent usage model. Keep advertised capability, independently checked capability and unknown capability distinct, and show pricing assumptions so the decision sheet can be updated rather than rebuilt.

Before you start

Defined operating scope

A purchase decision requires comparable vendor capabilities, terms, and costs.

Required source material

Obtain Type of service needed; Selection criteria; Team size. If connectors are unavailable, use authorized files with the same fields.

Decision and exception rules

Pricing is quote-only. Mark price unknown and prepare a quote request instead of inventing an estimate.

Prepare the inputs

requirements
Required

Must-have and optional criteria

Define measurable acceptance where possible.

usage_model
Required

Seats, volume and billing period

Unknown demand remains an assumption.

vendor_candidates
Required

Product and official URLs

Compare the relevant plan and edition.

cost_rules
Required

Currency and included cost components

State taxes, overages and implementation assumptions.

Implementation, step by step

  1. Establish the working record

    • Confirm the selected records, effective versions and responsible owner.
    • Check requirements, usage_model, vendor_candidates, cost_rules before beginning. Record the source version and the selected scope; an unavailable value stays unknown rather than becoming an inferred fact.

    Checkpoint: The input record identifies the selected requirements and any missing required fields.

  2. Build a shortlist of suitable vendors

    • Build a shortlist that meets the stated service category and constraints; record why excluded options fail a must-have.
    • Recalculate comparable annual cost from the stated quantities and billing terms.

    Checkpoint: A saved intermediate result for: Build a shortlist of suitable vendors.

  3. Research pricing, documentation, and reviews

    • Research official pricing and documentation, using reviews only as attributed experience rather than product guarantees.
    • Check must-have claims against the exact plan and note missing evidence.

    Checkpoint: A saved intermediate result for: Research pricing, documentation, and reviews.

  4. Compare terms and costs against the selected criteria

    • Calculate comparable costs for the same seat count and billing horizon, preserving quote-only and usage-dependent values.
    • Recalculate comparable annual cost from the stated quantities and billing terms.

    Checkpoint: A saved intermediate result for: Compare terms and costs against the selected criteria.

  5. Create a spreadsheet with sources and a brief conclusion

    • Prepare the comparison sheet with gaps, tradeoffs and a recommendation conditional on unresolved requirements.
    • Check must-have claims against the exact plan and note missing evidence.

    Checkpoint: A saved intermediate result for: Create a spreadsheet with sources and a brief conclusion.

  6. Package the result and unresolved work

    • Check current pricing and essential features, and confirm terms before purchasing.
    • Do not purchase subscriptions or contact vendors unless authorized.

    Checkpoint: A vendor comparison with supporting reasoning and cost estimates. Unresolved items remain visible in the review record.

Decisions along the way

Pricing is quote-only.

Mark price unknown and prepare a quote request instead of inventing an estimate.

A feature exists only in a higher edition.

Compare that edition’s cost and conditions, not the cheaper plan’s headline price.

Evidence for a must-have is missing.

Keep the vendor conditional until a demo or documentation confirms the requirement.

What you will produce

vendor-comparison-sheet-result.json

JSON

A vendor comparison with supporting reasoning and cost estimates. Label proposed and completed states separately.

Include: vendor · plan · criterion_results · annual_cost · cost_assumptions · evidence_gaps · recommendation · status · evidence_reference · review_note

vendor-comparison-sheet-review.md

Markdown

Keep the evidence and unresolved decisions needed to apply this result, including exceptions involving cost_rules.

Include: source_reference · question · owner · next_action

Check the result

  • Recalculate comparable annual cost from the stated quantities and billing terms.
  • Check must-have claims against the exact plan and note missing evidence.
  • Inspect requirements and usage_model in both the original and output; confirm that record identity and interpretation survived the transformation.
  • Check current pricing and essential features, and confirm terms before purchasing.

When something goes wrong

Pricing is quote-only.

Mark price unknown and prepare a quote request instead of inventing an estimate. Retain the affected evidence and recovery status.

A feature exists only in a higher edition.

Compare that edition’s cost and conditions, not the cheaper plan’s headline price. Retain the affected evidence and recovery status.

Evidence for a must-have is missing.

Keep the vendor conditional until a demo or documentation confirms the requirement. Retain the affected evidence and recovery status.

A worked example

SYNTHETIC EXAMPLE · NOT A REPORTED BUSINESS RESULT

Request

Compare software vendors for the following bounded example; prepare the result for review.

Inputs

Synthetic example: Need five seats. Vendor V-1 charges 12 USD per seat monthly; V-2 charges 500 USD annually for five seats, but required export support is undocumented.

Expected result

Synthetic expected result: V-1 annual license cost is 720 USD. V-2 is 500 USD with export capability unknown; it cannot be declared the winner solely on price.

Run a small pilot

Start small

Trial a representative batch containing the ordinary case and the exception demonstrated above.

Record the baseline

Record current preparation time, review effort and correction types for the same records.

Agree success criteria

Agree acceptable review and error limits; measure time to a decision-ready comparison; stale or unsupported vendor claims.

Stop or revise

Evidence for a must-have is missing. Pause affected records and apply this recovery: Keep the vendor conditional until a demo or documentation confirms the requirement.

Keep the scope clear

  • Do not purchase subscriptions or contact vendors unless authorized.
  • A comparison recommendation is conditional on the supplied needs, not a universal vendor ranking.

Check before using

Check current pricing and essential features, and confirm terms before purchasing.

Business activities

  • Research customers and markets
  • Manage finances and accounting

Editorially adapted workflow; not independently tested.

FROM A RECIPE TO YOUR WORKFLOW

Bring the company context together.

This workflow needs reliable inputs before it needs a better prompt. Moat8 Vault brings working information into a readable archive for the AI tools you use.

For this recipe: Type of service needed · Selection criteria · Team size

Start with one recurring task, agree which sources to use, and review the first result with your team.

Discuss this workflow

What does your team do?

Choose the recurring work you would like to improve.

A field guide, made for work.

Plays is a curated library of anonymized business workflows. Each recipe explains the inputs, steps, tools, and checks you can adapt to your team. These are editorial guides, not independently tested implementations.

When you share a company website, the guide may read a limited number of public pages on that website. Messages and retrieved page text are sent to our AI provider, NVIDIA, to recommend relevant workflows. Share a general description rather than confidential information.

Saved workflows and selected activities stay in this browser. Your chat history and selected company website are kept in this tab and cleared when you reload or start a new chat. The server does not store conversations. Live source monitoring is not enabled.

If you allow analytics, PostHog receives page views and actions such as workflow saves, skill downloads and link clicks. Random browser and session identifiers connect these actions without identifying you by name. Your choice and browser identifier expire after 90 days; sessions restart after 30 minutes of inactivity or 24 hours. We use local storage, not analytics cookies. Messages, company URLs, search text, full referrers and IP addresses are not sent. There are no person profiles or session recordings. You can decline or withdraw in Analytics settings; Do Not Track and Global Privacy Control keep analytics off.

Read the Plays Privacy Notice ↗