I build systems that carry the load people are carrying in their heads.

I entered technology through AI-assisted development and now ship products for people running complicated lives and complicated work: households, family health, trades operations. Four are built and running, each on the architecture its problem actually needs. You would not be building the backend, and you would not be joining one product. I need a technical cofounder to harden what exists, judge what I got wrong, and take the intelligence layer somewhere I cannot take it alone.

products built end to end

engineers hired, all of it solo

founding technical role open

the flagship

Munus

household operating system · preparing beta

Families run on agreements nobody wrote down and schedules nobody agreed to. Munus makes both explicit: a written household standard, a calendar that reflects what was actually committed, and a study layer that helps a teenager inside the rules the family set.

built: Two-tier product, parent and teen, on Supabase auth (Apple, Google, magic link, passcode), five edge functions and RevenueCat subscriptions
hard part: Household-scoped identity and permissions. Who can see what, who can change what, and what a teenager is owed privately
ai layer: Multi-provider routing with retry, under household rules and auditable to a parent

and three more built on the same thesis

Acesa Health

Family health memory. Symptoms, medications, appointments and history in one private place, so patterns become visible. A provisional patent application has been filed for aspects of the health intelligence layer behind Acesa Health.

private beta

Tekton Mechanics

Operating system for small trades businesses. Jobs, crews, scheduling, fleet and documents in one place.

in build

Text It

Turns cluttered messages into dates, tasks and forms, then sends each person only their part.

waitlist open

What I need engineered

Not screens. The layer underneath: context and memory, retrieval, orchestration, data architecture, privacy, evaluation. The hard part is the boundary. What should be deterministic, what should be inferred, and how intelligence helps without taking over. I can specify that work. I cannot engineer it alone.

also built solo

acesa

Body-region, medication and trigger ontologies · episode lifecycle and recovery scoring · versioned migrations

tekton

Contract-first typed API · Postgres via Drizzle · jurisdictional tax engine · object ACLs · redacted logs

text it

Local SQLite · hybrid semantic and lexical retrieval

evaluation

I measure the AI instead of trusting it. Speech and retrieval harnesses with holdout sets, graders and invented-fact checks

Who I want to build with

Someone who thinks about architecture and the human being on the other side of it, and who understands the people we are building for. Solve the intelligence layer once and it serves four products, not one. That is the actual offer: a portfolio to build against, not a single bet.

tools, not products

What these products hold stays on the device or in the user's own cloud. I do not want custody of anyone's data. Anything shared is opt-in, off by default, and as coarse as it can be.

funding and founding reality

nomos is founder-funded and I cannot offer a salary yet. What I can offer is a genuine founding position on software that already exists, with a founder who knows every product line by line. Role, equity, and decision rights get agreed in writing before substantial work begins.

the thesis

The person is carrying the system.
The system should carry more.

connect

nomosind.com/connect [email protected]

Work with me →

San Francisco, California nomos industries inc. · 2026