Work Minnesota

01Work

Not a portfolio. Proof of operation.

Products we run ourselves. Open a row for the problem, the system, and what came out of it.

Kind / /
01

Com²unity

Chat, membership, and billing for a Matrix community we run.
Owned / Production

Problem

Most community products are a forum bolted to a billing page. Members bounce between tools that were never designed as one room.

System

A Matrix community with entitlements, rooms, and the operational layer in production. A Rust API for the proprietary parts.

Homeserver: Continuwuity.

Outcome

One room, with the billing inside it.

02

LittleByLittle(opens in a new tab)

Execution and risk rails for a trading desk we run.
Owned / Production

Problem

A trading desk that lives in twelve tabs is a pile of exceptions.

System

Execution, risk rails, and the desk software we operate.

Outcome

A trading system we ship to ourselves first.

Visit
03

Lattice

Offline pocket DSA trainer. Recognize, diagnose, reconstruct.
Owned / In development

Problem

Interview prep turns into a dump of problems. The tell is recognition under time, not another tab of solutions.

System

An Expo iOS trainer with Breaks, Smell, and review that stays on the phone.

Outcome

The trainer is in active build. App Store listing next.

Open the product page
04

ArchStack(opens in a new tab)

Curriculum and labs for an agentic system. Lives on its own site.
Productized system

Problem

Engineers need a path that ends in a system running.

System

Curriculum and labs for shipping an agentic system.

Outcome

The curriculum shipped.

Visit
05

Drip Coffee Labs

Brand and storefront for a coffee side project.
Side project

Problem

A coffee side project with nowhere to sell from.

System

Drip Coffee Labs. Brand, site, storefront.

Outcome

The storefront is live.

We take a few engagements. If it is not a system we would run, we say no early.

Tell us what you’re shipping