Skip to content
Vertex Stack
Menu

Two build engagements per year

Blog

Notes on building SaaS and marketplaces, page 3

Long-form, technical writing on the decisions behind SaaS platforms and two-sided marketplaces: architecture, payments, trust and the parts that are expensive to get wrong.

SaaS · 6 min read

Building a SaaS admin portal that doesn't embarrass you

Every SaaS needs an admin portal by the time support has real customers. Many are stitched together from Retool screens and raw SQL, and many leak. Here's the pattern for a support-grade back office with safe impersonation, tight permission boundaries, and an audit trail you can actually hand to an auditor.

Backend · 8 min read

API versioning strategies that don't hurt later

Three ways to version an API, one way Stripe does it, and one trap that turns every v2 into a reimplementation project. Here's how to pick a strategy that survives three years of shipping without forcing a rewrite on every integrator.

Marketplaces · 6 min read

Real-time coordination for marketplaces: Socket.IO patterns that scale

Marketplaces live or die on coordination — two users need to see the same booking state, message thread, and availability window within the same second. Here are the Socket.IO patterns I use, and how they behave once the server count crosses one.

Payments · 6 min read

Handling refunds, disputes, and chargebacks in SaaS

SaaS is uniquely exposed to chargebacks because the product is intangible and subscriptions auto-renew. Friendly fraud is a large share of card losses. Here is the refund policy, evidence package, and dunning discipline that keep dispute ratios well below the card networks' monitoring thresholds.

Marketplaces · 7 min read

Two-sided marketplaces in 2026: the playbook for solving chicken-and-egg

Every two-sided marketplace starts with the same dead start: no supply means no demand, and no demand means no supply. The teams that solved it — Airbnb, Uber, DoorDash, and the less famous ones that copied the pattern — did not find a trick. They picked one side, faked it until it was real, stayed geographically dense, and only expanded when the first market stopped needing their attention.

Building a SaaS or marketplace?

Most projects start with a Discovery Sprint: a short, fixed-fee engagement that ends with a scoped brief and a fixed-price proposal.

Engagements from $50,000 · Two builds per year