Explore three projects, then open a case study for product screens, implementation evidence, and the decisions behind the build.
Founder and sole developer
Building communication scattered across inboxes. One tenant-scoped system for announcements, requests, documents, and decisions.
Evidence: Six captured product screens; tenant and role separation documented in the repository.
Read the Community Hive case studyFounder and sole developer
Household managers coordinating care through notes and messages. Private task assignment, rotating schedules, handoffs, and employer records.
Evidence: Public product and sign-in screens; role isolation and employer exports documented in the repository.
Read the CareBoard case studyFounder and developer
Accessibility details missing before a visit. Structured place checklists, labelled scores, photos, and community reports.
Evidence: Place cards pair colour with written score labels and screen-reader text; score boundaries have unit coverage.
Read the AccessLens case studyFounder and sole developer
Evidence: Delivery tracking with sent, delivered, opened, and acknowledged states; SHA-256 content fingerprints; CSV/JSON audit export.
Read the Digital Notices with Proof of Delivery case studyProduct capabilities are demonstrated separately from intended benefits. Case studies identify what is implemented, what is still developing, and where measured impact is unavailable.
Let’s look at the workflow, the people using it, and where custom software could help.
Talk to Dan about your problem