CeySource

Problem

• Buyers and suppliers were finding each other through scattered directories, referrals and unstructured messaging.
• Supplier capability was impossible to compare because nothing was captured in a common structure.
• Requests for quotation had no lifecycle — they were emails that went quiet.
• There was no shared record of who asked for what, or what was answered.

Approach

1. 01Discovery

   Separated the two sides of the marketplace and defined what each actually needed before any interface work started.

2. 02Architecture

   Designed products, supplier profiles, RFQs and conversations as distinct entities so sourcing has a traceable lifecycle.

3. 03UX

   Built browse, compare and request flows around procurement behaviour rather than consumer e-commerce patterns.

4. 04Engineering

   Combined a content-managed public surface with a React-driven application layer over a relational database.

5. 05Integration

   Wired messaging, RFQ state and supplier verification into one flow so a request stays attached to its context.

System

1. Public surface — WordPressL1
2. Application layer — ReactL2
3. Marketplace APIL3
4. PostgreSQLL4
5. Messaging + RFQ engineL5

Outcome

• Sourcing moved from unstructured messaging into a tracked request lifecycle.
• Supplier capability is captured in a comparable structure instead of prose.
• Buyer and supplier interactions leave a durable record attached to the request.

Tech stack