Define the job before the demo
Write down the workflows you need before watching any demo: who publishes what, how often, to which surfaces, with which live data, and with which commercial placements. Demos show features; your workflows determine which features matter.
One content model, or several
Ask whether content created once can flow to the app, website and widgets from one model, or whether each surface needs a separate workflow. Apply the same test to live data: one ingestion point with editorial control, or a separate feed implementation for every channel.
Who operates it after launch
Ask who handles hosting, monitoring, operating-system updates, store-policy changes and incident response, then check which responsibilities are written into the contract. Ongoing operation should be explicit before launch, not discovered during the second year.
How pricing is structured
Expect several cost layers rather than one figure: a platform subscription, implementation and customisation, separately licensed sports data where needed, and hosting, operations and support. A vendor who cannot explain what drives each layer will struggle to explain a renewal.
iPublisher framework
The iPublisher evaluation framework
Score each vendor answer as clear, vague or absent. Vague and absent answers are your risk register.
Content flow
One model to every surface? Migration path from your current CMS?
Live data
Which providers are supported? Who holds the licence? Who corrects errors live?
Operations
Hosting, monitoring, updates, store compliance — whose job, in writing?
Commercials
Cost layers explained? What drives each? What happens at renewal?
Exit
What do you take with you if you leave?
Buyer checklist
- ✓ Document your publishing and matchday workflows before any demo
- ✓ Ask whether content and live data each have one model or several
- ✓ Get operational responsibilities in writing
- ✓ Ask for the cost-layer breakdown and what drives each layer
- ✓ Ask the exit question early
- ✓ Check accessibility, performance and consent handling, not just features
Limitations and dependencies
No framework removes the need to check references and evidence for your specific use case.
Sports-data availability and cost vary by sport, competition and territory.
This guide reflects iPublisher's view of good evaluation; apply it to us as well.