Why the motivation assistant stayed a concept instead of becoming a prototype
What made us stop at a documented concept instead of rushing into a build, and what would need to be true to change that.
Documented decisions, lessons, and trade-offs from building Bersaglio products and tools. Notes interpret what we learned; the Lab records active experiments in progress.
What made us stop at a documented concept instead of rushing into a build, and what would need to be true to change that.
Decisions, post-mortems, and documented lessons.
How we turned the site's peripheral surfaces — from the 404 error page to accessibility and privacy — from generic templates into a cohesive, tactile editorial system.
Why we refuse to add databases, user accounts, and server persistence to focused utilities — and how client-side execution makes software faster, safer, and timeless.
How a two-column workbench, client-side calculation, and precise statutory citations turn a flight rights check from a generic form into a reliable decision aid.
A product decision behind Knessetil’s civic interface: show discrete activity counts, separate source data from calculated metrics, and never collapse several measurements into one quality score.
How we turned the Israeli traveller's trip readiness planner from a boring form into an editorial workbench inspired by our 61 Coalition Calculator, pairing live readiness tracking with official government sources.
A product decision behind Bersaglio’s first public tool: start with a private, browser-only monthly cash-flow view instead of trying to automate a person’s entire financial life.
The product and architectural decisions behind evolving Festivalio from an Ozora 2026 companion into an offline-first, multi-edition festival platform.
Why we replaced vague positioning with explicit terminology — and what it changed across Bersaglio's site, projects, and architecture.
A record of hypotheses, prototypes, and early product exploration. The purpose here is learning. Not every experiment becomes a product. And that's a good thing.
An AI-assisted first draft of a product requirements doc, reviewed and edited by a human, is faster than writing the first draft manually without reducing decision quality.
A background assistant that only surfaces suggestions when confidence is high will get used more than one that comments on everything.