Services
What we build, and how.
Six things we do well, each with a live example you can open. Available for contract builds, retainers, and reviews.
Storefronts and booking systems
For small businesses that sell or rent over chat today. Checkout that clears, addresses a courier can deliver to, and an admin that reconciles. Your accounts, your code.
Negros Peanut Butter Co., U-Ride Details → Start hereNative Android and iOS apps
Offline-first apps in Kotlin and Swift, tested on every commit and submitted to the stores for you. Builds, ports, and rescues.
AidNow, 1,600+ tests Details →Everything we do
Native mobile apps
Android with Kotlin and Jetpack Compose, iOS with Swift and SwiftUI. Offline-first sync, maps, background work, push, and the release discipline to get through store review and stay there.
See it: AidNow →Public data tools
Directories, maps, and dashboards built on open data: OpenStreetMap, Census, government registries, community spreadsheets. Repeatable pipelines with a verification layer on top, so the data stays right after launch.
See it: US Ice Rink Directory →Storefronts and full-stack systems
Next.js, Express, FastAPI, Postgres. Payments, address validation, courier integrations, admin tooling, audit logs. Working systems with tests, not clickable mockups.
See it: Negros Peanut Butter Co. →Quantitative research
Backtests of trading strategies, signal services, and market claims. Real fills, walk-forward validation, Monte Carlo, slippage sensitivity, and a written report you can hand to someone sceptical.
See it: Research reports →AI-assisted engineering setup
We set up Claude Code and Codex workflows for engineering teams: repo instructions, test gates, review passes, and cost guardrails, so generated code is held to the same bar as hand-written code. Everything on this site ships through that workflow.
See it: AidNow, 1,600+ tests →Technical advisory
Architecture and release-readiness reviews for mobile and backend systems. We tell you where it is going to break before it breaks, and what to do about it, in writing.
See it: About the team →How we work
- Scope in a week. A short discovery, a written scope with what is out, and a first milestone you can see.
- Ship in short loops. Weekly deliverables and a working build at every step. No quarterly reveals.
- Verify the data. If the product depends on data being right, verification is part of the build, not a follow-up.
- Document as we go. Runbooks, architecture notes, and deployment guides ship with the code.
- No handoff cliff. Boring tech, tests, and CI, so the system is maintainable without us.
Ways to engage
Build
A defined product or feature, scoped and delivered end to end.
Retainer
Ongoing engineering capacity for a product that is already live.
Review
A fixed-price architecture, security, or release-readiness review with a written report.