ProofCase: Build case studies from project evidence
I started ProofCase because AI can turn rough project material into a polished case study in minutes. Hiring teams need to see the decisions a candidate owned and the evidence behind each result.
I wanted candidates to keep those details visible. With ProofCase, you separate your decisions from the team’s work and tie each claim to a source.
npx skills add getkishore92/proofcase
A case study before / after
On the left, I describe the project and process. On the right, I connect each decision and result to its owner and source.
Improving invoice approvals
Finance teams used several reports to review each invoice. I redesigned the billing dashboard with users to make approvals faster and easier to follow.
Cutting invoice review time without losing the audit trail
Finance admins used four exports for every approval. I owned the reconciliation flow and brought the evidence into one review workspace.
Context
Finance admins moved between four exports before they could approve an invoice.
Context
In the pilot, admins spent 43 minutes on a routine review because they reconciled four reports and preserved an audit trail.
My role
I led the service-design work with a product manager and two engineers.
My role
I owned workflow and interaction design. The product manager set approval policy, and two engineers led implementation.
Approach
I interviewed eight admins, then redesigned the dashboard around their approval workflow.
Decision
We placed the audit trail beside each exception. Admins saw more information on screen and backtracked less during approval.
Outcome
Pilot reviewers completed approvals faster and said the new flow was easier to understand.
Outcome
Admins cut average review time from 43 to 18 minutes in this fictional pilot. They contacted support more often about exceptions, so the team delayed the wider rollout.
Reflection
I learned that teams lost time when they stored audit information in separate reports.
Next step
The team will add bulk resolution for repeated exceptions, then track review time and support volume in the next pilot.
What ProofCase checks
With ProofCase, you trace each claim to its source and match the case study’s depth to the role. You keep the team’s ownership clear when you describe shared outcomes.
- OwnershipYou separate your work from the team’s work.
- DecisionsYou explain the constraint and tradeoff behind each decision.
- EvidenceYou link each result to its source and confidence level.
- LearningYou name the open question and next step.