CaseMark stops its demo from disguising spent budgets as broken documents

Trial users who ran out of demo credit were seeing documents fail to load with no explanation - now the system says what's actually wrong and what to do about it.

workflowchat-ui

In CaseMark's demo, every user gets a small spending allowance against the AI behind the product. When someone exhausted that allowance, document previews simply broke - a generated file would sit ready in the database, but the viewer showed a generic load failure that looked like a bug. The real cause, a depleted budget, was being swallowed before it reached the screen.

CaseMark threaded that budget signal all the way up to the browser and replaced the noise with a fixed, actionable line: add your own Case.dev key under Account settings, or ask the demo operator to reset your budget. The team also retuned how the demo meters cost - charging mostly for actual AI usage and settling against real prices rather than rough reserves - and added clean handling for oversized uploads.

So what Anyone running a trial or freemium tier of a legal-AI product should note how cheaply a masked quota error reads as a broken feature.

View this fork on GitHub →

Spotted something wrong? Or know the PR text has fresher detail than the writeup above?

Commits in this thread

3 commits from CaseMark/mikeoss-casedotdev, oldest first. Source extracted verbatim from the harvested git log.

SHA Subject Author Date
5e899345 Surface demo budget errors for document loads kveton 2026-05-04 ↗ GitHub
c4a955e2 Tune demo usage metering kveton 2026-05-04 ↗ GitHub
57ba208c Harden document load error responses kveton 2026-05-04 ↗ GitHub

Capture this thread into my fork

Download a single Markdown prompt that tells Claude how to port every commit above into your working tree — adapting paths and structure to match your repo. Run it via claude -p < capture-thread-282.md from inside the repo you want the changes in.

⬇ Download capture-thread-282.md