Cross Handle
CrossHandle is a marketplace I'm building around a simple but difficult problem: business owners need someone they can trust with their social media presence, while social media managers need a professional way to \prove their expertise, secure work, and get paid\. The interesting part isn't connecting two users — it's \designing the system that sits between them\. A business owner and a social media manager have \different goals, different permissions, different expectations, and different risks\. The platform needs separate experiences for each side while keeping the underlying workflow consistent enough for both to move from \discovery to agreement to delivery\. I'm designing CrossHandle as a \role-based marketplace\ where users can discover opportunities, create and manage listings, communicate, establish agreements, and move through a structured engagement flow, instead of relying on \informal conversations and ad hoc payment arrangements\. Right now the onboarding, role-based flows, and core design system are built; the marketplace, agreement, and payment layers are actively being designed and implemented on top of that foundation.
Problem and context
Hiring someone to run a social media account sounds simple until \responsibility and money enter the picture\. A business owner isn't just looking for someone who can create posts — they're giving another person access to \part of their public brand, content calendar, audience, and day-to-day communication\. At the same time, a social media manager takes on work without always knowing whether the client is serious, what's actually expected, when payment will happen, or how disagreements get handled. That's a \trust problem on both sides\. Most informal workflows solve it through DMs, spreadsheets, screenshots, separate payment links, and manually negotiated agreements — \fragmented communication with very little structure around the actual engagement\. CrossHandle is my attempt to \turn that fragmented process into a product\. The platform is built around \two distinct user roles\. Business owners discover managers, evaluate their capabilities, create opportunities, and manage engagements. Social media managers build a professional presence, showcase their expertise, discover opportunities, communicate with businesses, and work through a structured agreement and payment process. So the product has to solve more than discovery — it has to \create enough structure and trust for two strangers to confidently work together\.
Outcome
The current product is a functioning product prototype that clearly demonstrates the idea behind CrossHandle. The platform already shows the core user journeys for onboarding, account posting, browsing, messaging, and agreement-based work flows. The work is now at the stage where the concept is validated in product form, but the live backend, production data layer, and payment integrations still need to be connected and tested. The main outcome is a strong product foundation that is ready for deeper product validation.
Technologies: Next.js, TypeScript, Supabase, Tailwind, Flutterwave, Radix UI