Most of what we build belongs to the company we built it for, and their name is not ours to publish. So this page has two things on it: a full platform this team designed, built and ran end to end, and examples of the shape a project takes.
It was built for our own account rather than a client's, which is the only reason we can describe every layer of it here.
A multi-tenant AI conversation platform: an embeddable assistant, a tenant admin portal, an operator console, a marketing site and a mobile app.
Retrieval over each customer’s own content with vector search, grounded answers, source attribution, answer-quality tracking and content-gap detection.
A FastAPI service with per-tenant data isolation, role-based access, background workers, scheduled crawls, webhooks and a documented API.
Plans, feature gating, usage metering, overage handling, trials and upgrade flows. Most teams build this later than they should have.
Shopify, WooCommerce, Slack, Jira, Linear and generic webhooks, with idempotent event handling and retry-safe delivery.
Deployed, monitored and operated by us: environments, migrations, backups, rate limiting, incident response and on-call.
Much of what we build is internal software, or a product our client would rather introduce to the market themselves. Publishing a client list would be easy. It would also be the first promise we broke.
Over email we can go through relevant work in detail, and where a client has agreed to it, introduce you directly. Ask. It is a fair question.
Describe the problem and we’ll sketch the product back: scope, shape, and a first version you could put in front of users.
