What a Seneca pilot looks like

Seneca lets your product start every new learner from their real history instead of a diagnostic they have taken somewhere else. A pilot is the quickest way to check whether that's worth anything to you. It answers one question: if a new learner arrived with evidence from somewhere else, would your product start them differently? You can find out without a real student and without touching production.

What you send

Invent one student and 20 to 50 events, in whatever shape your product already exports. An export you already produce works. Names, scores and dates can all be made up. CSV is fine, and so are JSON, xAPI or Caliper. Something like this:

learner_id,timestamp,activity,item,correct,seconds,help_used
demo-01,2026-09-20T15:02,quiz,frac-03,1,41,
demo-01,2026-09-20T15:04,quiz,frac-07,0,55,
demo-01,2026-09-20T15:05,quiz,frac-07,1,38,worked_example
demo-01,2026-09-20T15:11,quiz,word-02,0,7,

Add one question you'd want answered before that student's first session in your product. Email both to kevinchoi@vindicaseneca.com.

What comes back

• A short learner summary, three or four lines a teacher or tutor model can read
• The evidence behind each line, with counts
• Strong conclusions marked apart from ones that still need checking
• What helped before, and where it was seen
• An example first step inside your product

Every conclusion says which product it came from, when and how many observations support it. It's the same kind of picture the tutoring app receives in our interactive demo. Seneca provides a starting point. Your product decides what to teach.

How your team decides

Put the summary next to your question and ask whether your product would have started that learner differently. If it would, that's worth a follow-up conversation. If it wouldn't, you've spent an afternoon. That's the whole cost.

What the pilot involves

• Fake data only. The student you invent is the only learner involved in this step.
• No production access. We work from the file you email, so nothing connects to your systems.
• No engineering sprint. An export you already produce is enough to start.
• No commitment to a full integration. Once you've seen the result, whether to go further is your call.

What happens after

If the result is useful, the next step is to bring one real item type. We map the observable fields, agree what has to stay local to your product, set an onboarding baseline and scope a contained production pilot. Pilots receive the current record contract.

Learners pay nothing to carry their record and can export it at any time. Companies pay an annual contract for the operated platform: hosted reads and writes, identity, permissions, connectors, audit and support.

The pilot page has the kit and the details, or you can send your fictional learner to the address above whenever it's ready.