Seventeen things in production. None of them mockups.
Every system below was designed, built, deployed and is maintained by this team. Most of them run companies we own — dispatch, printing, engraving, apparel, 3D printing, vehicle wraps, murals — which is a very direct form of quality control.
In production
Smart Haul TMS
A transportation management system built around the third-party dispatch model — where the agency earns a percentage and every load has two invoice paths: agency to carrier, and carrier to broker. Off-the-shelf TMS software assumes an asset-based carrier, so it fights you on day one. We built the one that doesn't.
Loads, carriers, settlements, driver pay, IFTA, safety and maintenance in one schema
Carrier self-service portal — onboarding, documents, fleet and payment history without a phone call
An eight-stage sales CRM and a staff chat/texting suite built directly into the platform
AI document reading for rate confirmations, BOLs, PODs and invoices — with a free OCR path so the AI bill stays optional
Node.js / ExpressPostgreSQLServer-renderedDocker ComposeClaude API
Scale of the codebase today: 56 tables, 100 migrations, ~20 route modules. Self-hosted on a private VPS — no per-seat SaaS bill, no vendor holding the data. Its own product site is live at smarthaul.tech.
A TMS with real accounting underneath it, built for a working trucking company and running their operation. Most transport software treats the books as an export; this one treats them as the source of truth — a double-entry, append-only ledger that the database itself refuses to let anyone quietly edit.
Double-entry, append-only ledger enforced by a database trigger — corrections are entries, never edits
Roles with permissions enforced server-side, and mandatory 2FA for admin and accountant accounts
Plaid bank feed for reconciliation, so the books match the account without manual entry
A Telegram bot for drivers — the workflow lives in an app they already had open
Double-entry ledgerPlaid2FADockerTelegram Bot API
Built jointly with a second developer, deployed by git and Docker to a private VPS. Live at tms.svvtrucking.com.
Ledger — August
1,842Entries
0Out of balance
2FAEnforced
Posted
Reconciled
Awaiting doc
In production
Smart Haul Driver App
The companion mobile app on the same backend: drivers see their loads, upload proof of delivery from the cab, and check pay without calling dispatch. One React Native codebase, both stores, its own token-based auth so a lost phone never touches the office system.
Photo capture straight to the load record — no email chains for paperwork
Separate auth boundary from the web platform
Shipped under our developer accounts — we handle review, signing and releases
React NativeExpoiOS + Android
Driver — today
Pickup
Upload POD
In production
Unified CRM
Built for the owner of several businesses, not one sales team. Contacts live in one place; each brand sees only its own pipeline; email marketing sends from the right domain with the right signature. Priced like software you own rather than per seat, per brand, per month, forever.
Per-brand access control — a salesperson on one brand can't see another's book
Multi-domain email marketing with per-brand sending identities
Deal stages, tasks and activity history that match how the business really sells
Dispatchers were guessing at toll costs, which meant quoting lanes badly. This puts three real options in front of them — cheapest, fastest with tolls, and toll-free — over a national interstate graph, and it does it in the browser with no login and no account.
A 104-node national interstate corridor graph with Dijkstra routing in three modes
At least two genuine route options on 98.9% of roughly 2,575 tested lanes
Static hosting behind a CDN — fast, free to run, nothing to keep patched
Hold your inventory once and sell it everywhere. Uscore syncs products across Etsy, eBay, TikTok Shop and more, schedules listings to go live on a date the marketplace itself doesn't support, and exposes a read-only partner API with signed webhooks so other systems can react to a new product or order.
Marketplace OAuth, rate-limit-aware sync and a job runner that survives API outages
Scheduled publishing implemented as draft-then-activate where platforms have no native scheduler
Public partner API with bearer keys, plus product.created and order.created webhooks
Sign, print and apparel shops run a job through four different systems and a whiteboard. Shop OS runs it through one record — quote, production, install, invoice — and keeps the history append-only, so nobody can quietly rewrite what a job cost after the fact.
One job record from quote to invoice, with production, install and costing attached to it
Strict multi-tenant isolation, with an automated test suite proving pricing never leaks between shops
Artwork proofing locked to a specific file version, so "which proof did they approve" stops being an argument
Job costing from historical stock snapshots rather than today's catalogue price
A partner network letting shops subcontract to each other without exposing customers or pricing
Next.js 16React 19PostgreSQL + DrizzleTailwind 4TOTP 2FAClaude API
AI reads incoming customer enquiries and suggests a quote — but the price always comes from the shop's own pricing engine, never from the model.
Job #4471 — banner run
Quote
Production
Install
Proof approved
Awaiting install
Live with a club
TeamOps
Youth sports clubs run a season out of a group chat, and families quietly disappear without anyone noticing until they're gone. TeamOps puts schedules, attendance, rosters and announcements in one place — and watches for the families who are drifting, before they leave.
Trainings, meets and meetings with recurrence, cancellations and automatic notifications
Attendance tracked per athlete — present, late, excused, absent — with history and reporting
Drop-off Radar: flags families whose attendance is fading so a coach can reach out while it still matters
Role-based views — a parent sees only their own children, never the whole club
RSVPs, volunteer sign-ups that can't be oversubscribed, and a private calendar feed per member
Social scheduling for people managing many accounts, not one. Eight networks behind a single calendar, a queue that retries when a platform throws a 500 at 2am, and per-post performance you can actually compare across channels. Designed to be sold to strangers — the integration with our own catalogue software is one optional adapter, not a dependency.
A cloud phone system for small businesses tired of paying enterprise prices for a ring group. The site, the brand and the legal pack are built; what stands between it and launch is telecom regulation, not code — which is its own kind of portfolio piece.
Business numbers, IVR menus and routing rules a non-technical owner can change
Calls and texts logged against the customer record, not lost on someone's cell
Presales under way into a trucking-consulting network of roughly 300 potential seats
Brand, marketing site, terms, privacy, AUP and VoIP service terms all drafted and built
Telecom compliance groundwork mapped: Robocall Mitigation Database filing plan, an E911 build spec and the FCC registration sequence
Nine live sites, all of them ours, all of them selling.
Each one is a real business with real orders — which is why they're built for catalogue depth, search indexing and speed rather than for a portfolio screenshot. Click any of them; they're all live.
The unglamorous work that makes the rest possible.
Nobody puts these on a homepage. They're also the reason the sites above have live catalogues instead of stale spreadsheets.
JDS proxy worker
A supplier's catalogue API returned 403 to our servers for weeks. Three independent tests proved the block was a geographic/ASN rule on their Cloudflare, not our IP or user agent. We routed the calls through a Cloudflare Worker on a US edge and a 25,000-SKU integration came back to life — one shared key, two sites, $0/month.
Cloudflare WorkersDiagnosis
Freight document pipeline
Rate confirmations, BOLs, PODs and invoices read automatically into the TMS. Free OCR handles the standard path; the AI model handles the hard ones, with batch processing and prompt caching keeping the per-document cost down — and the Batch API adopted specifically for resilience after we hit overload errors in production.
Claude APIOCRBatch + caching
Supplier catalogue connectors
S&S Activewear and JDS Industries wired into WordPress as live search rather than nightly imports: 5,653 apparel styles across 102 brands, 25,000+ wholesale blanks, an 18,693-file image cache, and rate-limit handling so a busy afternoon doesn't get us throttled.
REST APIsCachingWordPress
Client work
Most of what we build never gets a public page.
Internal tools, quoting systems, customer portals and integrations tend to live behind a login and under an NDA. We're happy to walk you through the relevant ones on a call, with the client's permission and the sensitive parts blurred.
What we'll show you: the actual architecture decisions, what we'd do differently now, and roughly what a system that size costs to build and to run per month. Estimates you can hold us to, not ranges with a 10× spread.
Want something like these, for your business?
Bring the messy version — the spreadsheet, the whiteboard photo, the process only one employee understands. That's the right starting point.