"Experience counts", this is very true, but do we even try to preserve it in a real persistent way? This article introduces a template for building an experience database on top of a workflow system. The presented solution is based on minimal effort approach which is truly cost efficient. Another advantage of this approach is low risk connected with introduction of new features, because we only add them in an independent way without modifying any of core workflow system elements. To illustrate the idea we choose well-known open-source software and an ordinary relational database. The solution is universal and can be applied to other real life cases including commercially boxed software, because it focuses on public Application Programming Interface (API) and database integration level. As a result we get a case based experience database with browsing abilities.