1. Connect the data
Show the source discovery flow, table profiling, connection test, and workspace setup before modelling starts.
Evaluation playbook
Use a business journey to prove Tessallite, not a feature checklist.
The Acme Payments playbook follows a realistic team through their first two weeks with Tessallite: connecting data, building a model, answering business questions, investigating issues, adding governance, accelerating slow queries, and using the agent.
Suggested demo flow
Six milestones that tell the story clearly.
2. Build the model
Create the fact, dimensions, joins, measures, hierarchies, glossary terms, and display names that business users will see.
3. Ask business questions
Run the first query, use the pivot-style surface, connect Excel, and confirm that results match the semantic model.
4. Investigate trust
Use drill-through, lineage, query logs, model health, and diagnostics when a number needs explanation.
5. Govern access
Introduce row security, personas, column controls, and audience-specific views before exposing sensitive data broadly.
6. Scale the rollout
Show aggregates, optimizer recommendations, pocket tables, BI endpoints, agent answers, and operational evidence.
Why this matters
A good evaluation proves behaviour across roles.
The playbook is useful because it is cumulative. A data engineer, finance analyst, compliance officer, BI developer, analytics leader, and system admin all work against the same Acme workspace. That makes governance, routing, Excel, model health, and agent behaviour easier to judge in context.