Hi. I built Stitch on Base44 and I'm looking for early testers. The problem: Plenty of teams have to prove what they did, not just say they did it. The evidence ends up in phone photos, inboxes and spreadsheets, and someone rebuilds the report by hand at the deadline. Even then, people still ask for proof. What Stitch does: It ties each claim to its evidence when it's captured. The report assembles itself, and proving it stops taking a fortnight. Why charities first: I volunteered at a charity event that never appeared in their comms. When I dug in, the work had happened but nobody had the time or tools to gather the evidence. A charity running trips abroad described the same problem. Small charities get judged against organisations with monitoring departments, so the pain is sharpest there. Early feedback from people in the sector called it a strong wedge that solves a real pain. Beyond charities: The same pattern shows up wherever reporting depends on scattered evidence, such as \[e.g. grant-funded projects, community groups, schools, field teams, compliance reporting\]. I'd like to hear where else you've seen it. Who I'd like to hear from: Anyone who's had to produce an impact, funder or compliance report. Tell me what's confusing, what's missing and what you wouldn't trust. Free access for early testers: https://stitch-impact-proof.base44.app/   submitted by   /u/Safe-Issue-5873 [link]   [comments]