Engagement · Co-founded

Campaign Finance. Built with the operator who knows the rules cold.

A non-technical political-finance operator brought us a decade of regulated-industry insight and a problem nobody had solved well. We didn’t take a brief. We took the problem, and Wojciech ended up a co-founder.

TanStack Start + Supabase. Bootstrapped, profitable, in production since 2023.

Co-founded
Engagement shape
Bootstrapped
No outside money
Profitable
Today, since 2023
TanStack + Supabase
Stack

What the founder brought

Boring software
with hard rules.
The rules are where everyone else got it wrong.

Political fundraising lives inside a regulatory frame the software almost always treats as an afterthought. Contribution limits, refund rules, donor disclosure, audit trails: the rules are the product, and the product has to enforce them before they become a problem.

The founder had spent a decade watching campaigns fight bad software at the worst possible moment. Election season, when nothing can break and nobody has time to fix it. The tools either treated compliance as a checklist someone forgot to consult, or buried it in spreadsheets nobody trusted.

This was a problem only an operator who’d been through several cycles could describe with the right specificity. Nothing about it was in a textbook.

How we worked

Co-founding shape,
from the first call.

We didn’t get a spec. The first conversation was about the regulatory model, not the UI. The architecture decisions came out of the rules, not out of a Figma file.

Wojciech ended up a co-founder because the work was the founding work. The product needed someone who’d still be in the room three years later, and equity is a better fit for that than invoices.

Vendor shape

Spec → build → handoff. Scope is a contract, and changes are friction. The relationship ends at “done.”

Founding shape

Problem → architecture → iterate. Scope changes as the founder learns, which is the point. The relationship is the product.

What’s running

TanStack Start + Supabase.
Picked because regulated industries punish creativity in the wrong layer.

Boring choices at the foundation, opinionated discipline on top. Type safety carries the regulatory schema from the database all the way to the frontend, so the rules end up enforced by the compiler instead of by a checklist somebody has to remember to open.

Database & auth

Supabase

Postgres + RLS for tenant isolation between campaigns. Auth and real-time done. We lean on RLS from day one rather than reaching for it later.

Full-stack framework

TanStack Start

Type-safe RPC, generated types from the schema. The compliance model lives in the type system, so an entry shaped like a regulatory violation doesn’t compile.

Status

In production since 2023.
Bootstrapped, profitable, still on it.

The product runs. The founder leads it. Wojciech is still in the architecture and the build. No outside funding got it here, and it’s profitable now. When a domain-expert founder asks what this kind of partnership actually looks like in practice, this is the one we point at first.

Visit campaignfinance.app

What this kind of engagement looks like for you

Different domain.
Same partnership shape.

The engagement pattern translates. The domain doesn’t need to.

Tell us about
your domain.

Tell us what you’re building and what you know about your field that nobody else does. We read every message and usually reply within a day.