My role
Conjoin is where the business side of my work meets the deeply technical side. Beyond running commercial operations and leading Delalify's global expansion into new markets, I architect and build Conjoin's core infrastructure, networking layer, and distributed systems. The service routing, multi-region deployment topology, and cross-service coordination that hold eight independent products together are things I designed and continue to work on directly. This project reflects how I operate: I can walk into a sales meeting in the morning and debug a networking issue in the cluster that same evening.
Conjoin replaces the pile of vendors most teams wire together when building SaaS. Eight infrastructure services, one SDK, and every service works independently or together.
The services
Transactional and marketing email and SMS with 99.9% delivery. Template versioning, batch operations with rate limiting, verification codes, real-time delivery tracking, and compliance tools with GDPR-compliant unsubscribe handling. Over 100M messages processed monthly.
Where this is going
The end state for Conjoin is that no developer ever has to think about backend infrastructure again. Not auth, not payments, not messaging, not storage, not queues, not databases. You write your product logic and Conjoin handles every layer beneath it.
Today, building a SaaS product means stitching together a half-dozen vendors, each with its own SDK, its own billing, its own failure modes, and its own breaking changes. That tax compounds with every new service you add. Conjoin collapses that entire stack into one integration that scales from a side project to a publicly traded company.
The roadmap is to expand Conjoin's footprint into every region where developers are building, with edge compute, local compliance, and payment methods that work where global providers don't. The goal is to make Conjoin the default infrastructure layer for the next generation of software companies, especially in markets that the incumbents have underserved.
