Original operator worksheet

Build the real cost baseline for a 70-vendor market.

Before a demo turns into a feature checklist, model the work your market carries every week. This worksheet keeps the math in your browser and lets your team compare each option against the same operating reality.

No vendor pricing assumptions Designed for recurring markets Use the same inputs in every demo

Your baseline

Translate one market month into numbers.

Defaults are only an editable starting point for a 70-vendor weekly market. They are not a promise of savings, an estimate of any vendor’s price, or a substitute for contract review.

Market rhythm
$
Work around every event
Compare one candidate with your current stack
$
$
%

The calculations run locally in your browser. This page does not save or send these assumptions.

The test that matters

Evaluate one vendor through one real market week.

A 70-vendor market is large enough that copied handoffs become operational risk. A software demo should show the connected record, not just separate feature screens.

  1. 01 — Intake

    Application to vendor record

    Use a real application or renewal. Confirm who reviews it and whether approved information stays connected.

  2. 02 — Readiness

    Documents and exceptions

    Test an expiring permit, missing attachment, or changed insurance document. Find the owner and next action.

  3. 03 — Market day

    Assignment change in context

    Move a booth or log an arrival issue. Make sure staff can see the vendor, session, map, and notes together.

  4. 04 — Closeout

    Fees, notes, and reporting

    Ask what a manager can report after closeout without reconciling a second spreadsheet.

How to interpret the math

Separate software price from operating cost.

The subscription line is only one part of a market’s cost. For a recurring program, the ongoing work around applications, documents, booth changes, fee review, closeout, and follow-up can matter more than a monthly price difference. This worksheet puts that existing work in view before a team compares plans.

The redirectable-hours assumption is intentionally yours to set. Treat it as a testable hypothesis, not a vendor claim. During a demo, identify the exact handoff that would change, the person responsible for it, and the proof you need after the first month.

Finally, use the vendor-event figure as a discussion aid, not a procurement shortcut. A market with weekly regulars, one-off holiday events, food vendors, crafts, complex fee rules, or multiple sites can have very different needs even at the same vendor count.

Worksheet FAQ

Useful before a software decision.

How should a 70-vendor market compare software costs?+

Start with the operating work around each event: planning, market-day changes, follow-up, current tools, and staff time. Then use those same assumptions in every product demo and proposal review.

Does this worksheet recommend a specific platform?+

No. It is a neutral baseline. The right platform depends on the workflows you validate, implementation support, product fit, data boundaries, and contract terms.

What should a recurring market test in a demo?+

Run a complete market week using a representative vendor: application or renewal, document readiness, assignment change, fee posture, market-day note, and closeout report.