The Thesis
Every growing business ends up with the same three pillars: a CRM for relationships, a document system for contracts, and a commerce layer for transactions. The default answer is a monolith that bundles all three. Salesforce. HubSpot. Pick your vendor lock-in.
I think there’s a better shape. What if these weren’t one platform but three independent services that compose into one workflow? Same outcome, radically different architecture.
The Three Pieces
Twenty CRM is the relationship layer — contacts, deals, pipeline. It’s the source of truth for who you’re working with and where things stand.
Documenso handles documents and digital signatures. Contracts, agreements, anything that needs a legally binding “yes.”
Medusa is headless commerce. Orders, inventory, payments, fulfillment — all behind clean APIs.
How They’d Talk
The glue is events, not API calls bolted together.
A deal closes in Twenty. That emits deal.closed. Documenso picks it up, generates the contract, sends it for signature. The client signs. Documenso emits document.signed. Medusa catches that, creates the order, triggers fulfillment.
Three systems. One flow. No system knows the internals of the others. They just listen and react.
Why Composable Matters
Each piece deploys independently. Scales independently. Fails independently. If Documenso goes down, your CRM still works. If you outgrow Medusa, swap it for Shopify’s API — the event contracts stay the same.
This is the same principle behind every reliable distributed system I’ve worked on: loose coupling, strong contracts. The business logic lives in the events, not in the wiring.
The Honest Reality
This is an architectural sketch. I’ve mapped the APIs, designed the event schemas, and validated that the integration points exist. I haven’t built the event bus or run a real workflow end to end yet.
The hard problems are still ahead: data consistency across services, unified auth, and making the UX feel like one product when it’s actually three. These are solvable problems, but they require building, not just diagramming.
Related Projects
- Unified Payment Gateway — the natural payment layer for Medusa in West African markets
- Unified Digital Identity — SSO across all three services
If you’re thinking about composable business infrastructure or building something similar, I want to hear from you: laminekalinko2@gmail.com