Building SupportMeet: Matching by Lived Experience, Private by Default. What Worked, What Broke

Money troubles are a timing issue before they become a mathematical one. Rent comes due on one date, utilities on another, and a reduced work schedule or car repair in between. The bills do not wait for a paycheck, and the gap between income and expenses is where stress truly resides. Creating a peer support product to address that moment presented a design conundrum not faced by general advice websites: how do you match someone with those who have experienced the same financial squeeze, without requiring them to disclose their most intimate financial details?

Generic support spaces struggle due to their broad approach. Two people facing money issues may have nothing useful to share with each other. One is dealing with a late rent notice, while the other has weathered multiple winters of utility arrears and knows the quickest phone call, essential paperwork, and how to manage urgent decisions. The key unit is not the topic, but the lived experience behind it: the type of stress, its severity, and the geographic context, as programs, deadlines, and protections vary by location.

Three design choices formed the foundation of SupportMeet, a free peer support platform: matching based on lived experience in small circles, default privacy at the data level, and combining conversation with practical help.

Matching on lived experience in small circles proved to be effective. Early testing consistently showed that the most valuable feedback was not general encouragement, but specific details only someone with similar experience could provide. Private by default, at the data level, also performed well. Privacy was not a toggle to be found in settings, as those most in need of support were the least likely to look for a setting.

Posts started private to the circle, with sharing widened deliberately by the user later. This shift in default transformed the nature of first posts, making them longer and more specific.

Integrating conversation with practical help was another successful element. A supportive reply can help someone get through the immediate moment, without filling out forms. Circles were paired with pointers to practical help and nearby professionals, allowing conversations to conclude with concrete next steps alongside emotional support. This holistic approach ensures people receive both empathy and actionable assistance.

However, the product faced challenges. Initially, the matching categories were too broad, leading to weak matches that were less helpful than a brief wait. Narrow categories, though more precise, result in smaller pools and slower initial matches. The empty circle problem also emerged, where users posting at odd hours in less common situations might wait for a match and face a waiting screen that offers no reassurance.

This screen had to clearly communicate the situation, suggest immediate practical help, and never imply a match when none exists. Additionally, the tone of the interface needed refinement. Cheerful empty states and upbeat prompts were out of place next to posts about financial difficulties, so the interface settled on plain and steady language to avoid false hope.

For builders, these lessons emphasize the importance of matching on lived experience, not just topics, especially when the value of support hinges on shared experience. Keeping privacy as the default state is crucial; if privacy hinges on user settings, many may never experience the product's full benefit. Lastly, integrating human support and practical next steps within the same platform avoids the need for users to switch between different apps or directories, providing a seamless experience during difficult times.