Work

Systems in production, not portfolios in Figma

Everything below is live software with real users, real payments, and real consequences. Several of these businesses are our own, which is exactly the point: we ship what we are willing to run ourselves, and we publish the numbers that did not go our way alongside the ones that did.

11live sites and platforms
578Klines of production code in two flagship systems
3,268automated tests on those two alone
Platforms we built

Software running real businesses

620API endpoints

Bridal and alterations platforms

Two complete systems running our own stores: booking, pipeline, POS, payments, storefront, and customer portal.

Read the case study
18days to live

Self-publishing events platform

A nightlife site that maintains itself, with an AI vision gate that refuses to publish anything it cannot verify.

Read the case study
2Manhattan venues

NYC restaurant group

Reservations, large-party deposits, event ticketing, and SMS confirmations on one platform the venues own.

Read the case study
Marketing, measured through our own software

Because we own the data layer, we can prove what worked

We do not sell ad management on its own. We run paid media for businesses whose booking systems we built, because that is the only way to trace a click to a real order instead of a conversion column. These two case studies include the findings that embarrassed us, which is the only kind worth reading.

Bridal Google Ads

A 17x branded-click overpay found, and a budget cut that raised bookings.

Read the case study

Bronx med spa

Ad account rebuild, call tracking, and a profile that advertised the wrong services.

Read the case study

B2B ingredient supplier

AI lead discovery for a national sales team.

Read the case study