Automate the manual work in Stan

FullSpec maps how Stan fits into your day-to-day, finds the repetitive work worth automating, and gives you a clear plan to connect it with the rest of your tools.

Explore ideas

Stan by the numbers

Insights from real process mapping sessions that involve Stan.

No processes mapped yet using Stan. Map a process that uses Stan to see automation data here.

Map a Stan automation

Top 5 Stan friction points when done manually

Retyping Stan model code across files

You manually copy and paste Stan model specifications between documents, emails, and version folders instead of having one source of truth.

78% report this

Tracking Stan parameter changes manually

You keep separate notes or spreadsheets to document which Stan parameters were adjusted for each analysis run because there is no built-in change log.

52% report this

Reconciling Stan output with raw data

You spend hours matching Stan diagnostic results back to the original datasets by hand to verify which inputs produced which outputs.

41% report this

Sharing Stan results without context

When you send Stan output files to colleagues, you have to write separate emails explaining the model assumptions and parameter settings because the output itself contains no metadata.

29% report this