# Marketplace & Brokerage URL: https://qualixsolutions.com/industries/marketplace-brokerage/ Build platforms that connect buyers, sellers, and brokers. Marketplace & Brokerage Software Development Build secure marketplace and brokerage platforms that connect buyers, suppliers, and brokers through seamless workflows. #### Overview Marketplace and brokerage businesses live and die by one thing: matching a supply side and a demand side reliably, then managing everything that happens between the two after the match is made. Qualix has built inside two very different versions of this problem, a household staffing marketplace connecting candidates and clients, and an internal platform managing broker relationships in a perishable goods supply chain. Both required software that could handle two sides of a transaction with different needs, different incentives, and different data, without forcing either side into a workflow built for the other. #### Who we build for - Two sided marketplaces: matching a supply side and a demand side, where both parties need their own portal, workflow, and visibility into the relationship. - Brokerages and middlemen businesses: managing relationships, pricing, and fulfillment between suppliers and buyers, even when the software is used internally by brokerage staff rather than by both sides directly. - Businesses built around ongoing relationships rather than one time transactions: where a match is the start of the relationship, not the end of it. #### Problems we solve - Supply & Demand Matching: Matching supply and demand without a system, relying on manual outreach, spreadsheets, or memory - Screening & Verification: Candidate or supplier vetting and screening that happens outside the system and never makes it into a usable record - Commission Management: Commission and margin tracking that gets recalculated by hand instead of living in the platform - Relationship Management: No single view of a relationship once a match is made, so follow up, renewals, or replacements start from scratch - Dynamic Pricing: Pricing that shifts constantly and needs to be tracked accurately per trade or per placement - Time-Sensitive Fulfillment: Time sensitive fulfillment where delays directly affect quality or client satisfaction - Role-Based Experiences: Two very different user experiences, supply side and demand side, being forced through the same interface - Trust & Safety: Trust and safety concerns that need to be handled before a match happens, not after #### Compliance and data handling SOC2 controls were implemented and achieved on Ivy at the project level, consistent with SOC2 being pursued across our SaaS builds. Westrow is an internal tool rather than a SaaS product, so SOC2 has not been pursued there, though the same underlying security practices still apply. - Encryption of data at rest and in transit - Role based access separating supply side, demand side, and internal staff views - Secure handling of background check and candidate screening data - Access controls around financial and commission data #### Complexities in Marketplace & Brokerage Tech **Beyond the Match** A match is the beginning of the relationship, not the end, so the system needs to support what happens after the match, not just the match itself. **Dual User Experiences** Supply side and demand side almost always need different portals, permissions, and workflows, even inside one platform **Marketplace Liquidity** Liquidity matters more than volume, since a marketplace with plenty of supply but no active demand at the right moment fails the same way as one with no supply at all **Sensitive Data Handling** Screening and vetting data, especially background checks, needs to be handled as sensitive personal data even outside formal healthcare style compliance **Flexible Commission Models** Commission structures often vary by relationship, placement type, or trade, and hardcoding one flat rate breaks the model quickly **Time-Critical Fulfillment** Perishable or time sensitive goods add a layer where fulfillment delay is not just an inconvenience, it directly affects the product **Relationship Retention** Replacement, renewal, or ongoing relationship management is often the real retention driver, more than the initial match **Internal Brokerage Workflows** Internal brokerage tools still need to reflect two sided dynamics even when only staff log in, since the system is managing both sides on their behalf **Trust & Verification** Trust signals, ratings, verification status, or track record often need to be visible before a match is finalized, not just after #### Tools and systems we integrate with - Verification Services: Background check and verification services. - Payments & Commissions: Payment and commission processing systems. - Scheduling & Communication: Scheduling and communication tools between matched parties. - CRM Systems: Internal CRM or relationship tracking systems. #### FAQs Q: Do you build for both sides of a marketplace, or just one? Both, when the business needs it. Ivy has a candidate facing portal alongside the client side, since matching only works if both sides trust the system. Q: Can you build internal tools for a brokerage that don't require external users to log in? Yes. Westrow is a good example, an internal platform managing broker relationships and transactions without requiring suppliers or buyers to log into the system directly. Q: How do you handle background check or screening data? We treat it as sensitive personal data from the start, with access controls and secure handling built in, even on projects where a formal certification like SOC2 hasn't been pursued. Q: Do you handle commission or margin calculations directly in the platform? Yes, when that's part of the scope. Commission structures tend to vary by relationship or trade type, so we build the logic to reflect that rather than assuming one flat rate. Q: Do you hold SOC2 certification as a company? Not yet at the company level. On Ivy, SOC2 controls were implemented and achieved at the project level, consistent with our approach to SaaS builds. Westrow is an internal tool, so SOC2 wasn't pursued there.