Skip to main content

What I've built

The businesses I run, the systems underneath them, and the client work that came with them.

Project Parabellum

Active

Founder·2024 – Present

The market data layer for firearms dealers.

A subscription platform for licensed FFL dealers. It ingests wholesale inventory and pricing from 17 distributors, normalizes wildly different CSV, API, and FTP feeds into one catalog, and puts search, price watches, daily deals, and analytics in front of dealers on both web and mobile.

  • 17 distributor integrations, each its own parser and fetcher, normalized into a single product schema, a catalog on the order of 360,000 products.
  • A Convex and Postgres hybrid: Convex holds the reactive application state, Postgres carries the high-volume catalog behind 748 idempotent migrations.
  • Onboarding gates on real FFL verification: ATF database lookup, license upload, then admin approval driven from a Slack Socket Mode sidecar running inside the ECS task.
  • Codegen-driven type safety end to end, with generated hooks and typed API wrappers, plus pre-commit binaries that enforce validation and test coverage.
  • A React Native app built on the same generated data layer as the web client, so a dealer can check pricing and price watches from the counter without a second implementation to keep in sync.
  • Convex
  • Go
  • Next.js
  • React Native
  • Expo
  • Postgres
  • AWS ECS
  • Terraform
  • Stripe

Mile High Ideas

Active

Founder·2019 – Present

A Colorado web studio for local service businesses.

Design, build, and hosting for small service businesses around Parker, Colorado, plus the custom applications a few of them outgrew their websites for. The interesting part is the delivery system underneath it.

  • A 13-site WordPress fleet living in one monorepo on one server. CI diffs each push, extracts the client sites that actually changed into a build matrix, and fans out parallel zero-downtime Ansible deploys. A shared-asset change triggers the whole fleet.
  • DNS and servers as code: a reusable per-site Terraform module declares each client's zone, and preserves their real mail and verification records rather than flattening them.
  • An operations platform behind it all, running companies, projects, time tracking, retainer drawdown, Stripe invoicing, and contract e-signature with a per-recipient audit trail. Built to replace a purchased tool.
  • Billing runs on staggered crons: agreement reminders at 9am MT, Stripe milestone invoices thirty minutes later, deliberately separated to keep two bursts of API traffic out of the same minute.

Selected client work

CAMCOAsphalt & concrete paving

An operations platform for a paving contractor: estimating for seal-coat, mill-overlay, and concrete work, plus crews, fleet, time clock, QC, and documents. 227 tables across twelve domain modules, a custom IAM layer with its own policies, groups, and audit log, and QuickBooks Online sync. I built both clients against one backend and one shared data layer: a Next.js office portal, and a React Native app that crews use in the field for time clock, quality checks, and photos, released together with health checks and automatic rollback.

portal.camconow.com
Trofeo Motoring SocietyMotorsport events

Rally registration and payments: Stripe embedded checkout with a verified webhook, transactional email on React Email, and a Three.js hero.

trofeomotoringsociety.com
CCMGInsurance claim advocacy & construction management

Claims & Construction Management Group represents property owners from insurance settlement through construction closeout. The engagement spans a family of brands, a marketplace product, and the Google Workspace identity behind all of them, nine repositories in total.

  • Saga is the substantial one: a marketplace connecting HOAs with independent community managers, rebuilt off an Airtable and Softr stack. 23 tables across 13 schema modules, a public site and a staff console sharing one backend and one session cookie, and a resumable 15-module import engine. Every table keeps its source record id and an index to match, so a re-import is idempotent rather than duplicating.
  • Authorization there is deliberate rather than role-table shaped: a membership join plus helper guards, with the viewer query documented as render-only and explicitly not the security boundary.
  • Stripe for a single subscription tier, R2 over built-in storage so document links expire, rate limiting on the two unauthenticated mail paths, four crons, and 30 transactional email templates.
  • Google Workspace as Terraform across six tenant domains: one shared module for users, groups, and memberships, called almost identically by each tenant, with remote state isolated per tenant and lifecycle rules that keep imported accounts from drifting on every plan.
  • A build runner defined but gated off by default, so the infrastructure exists in code and costs nothing when idle. One tenant generates its own credentials because it was created fresh rather than imported.
  • A shared marketing template across the brands, the strongest of which carries a typed content layer with 42 posts and eight service pages.
ccmgpro.com
Simply Auto GroupAutomotive repair

A headless reporting pipeline with no web UI at all: FastAPI and pandas pull shop data through to a live scorecard, wired into payroll and shop-management webhooks.

  • Next.js
  • Convex
  • Terraform
  • Ansible
  • Trellis
  • Cloudflare
  • Stripe

Dashtag Platforms

Past

Co-founder & Technical Lead·Feb 2025 – Aug 2026

A digital identity for every vehicle.

Co-founded a vehicle-enthusiast platform and led its engineering from empty repository to apps in both stores. The premise: every vehicle gets a persistent digital identity. QR codes were minted and printed onto stickers before the vehicle existed in the system, handed out at car meets and shops, then claimed to a profile carrying albums, glovebox documents, maintenance history, modifications, ownership records, valuation, and NHTSA recall data. Around that grew ticketed event management, a repair-shop CRM, a marketplace, and a gamified passport with badges and leaderboards.

  • A TypeScript monorepo of 14 applications and 26 shared packages over a reactive backend of roughly 150 schema modules. Next.js on the web, React Native on mobile, Go and Python services behind them.
  • Published a Terraform provider for vehicles: ten resources generated from an OpenAPI spec that was itself generated from the backend schema, so one source of truth produced the provider and the multi-language SDKs alike. It ships publicly alongside five modules covering garages, vehicles, album sets, maintenance, and modifications. A garage became declarative infrastructure.
  • Dogfooded that provider against my own five-vehicle garage, 26 imported resources under version control, which is a strange but very effective way to find the gaps in your own API.
  • Self-hosted routing on ECS Fargate Spot, launched on demand by a private Lambda router and self-terminating when idle, so it cost nothing at rest. The organization was Control Tower governed with a policy denying anonymous Lambda URLs, so the backend reached it over scoped IAM rather than a public endpoint.
  • Six DNS zones under Terraform driven from YAML rather than hand-written HCL, alongside R2 buckets, CORS rules, and redirect rulesets, with keyless CI throughout via GitHub OIDC.
  • Built the React Native app and shipped it to the App Store and Play Store across 38 minor releases, carrying the QR claim flow, vehicle profiles, event tickets, and wallet passes.
  • Ticketing that had to survive real event days: tiers, waivers, waitlists, coupons, and refunds, with wallet passes issued to attendees.
  • Codegen-enforced type flow from schema through to UI, with pre-commit gates that rejected stub tests. A test whose every assertion was trivially true failed the commit.
  • Print automation nobody expects to write: Python driving Illustrator to lay generated QR codes into sticker templates while keeping them natively editable.
  • Weekly production error triage against real traffic, including an O(log n) rewrite of leaderboard ranking and throttled write paths that had become contention points under load.
  • Convex
  • Next.js
  • React Native
  • Expo
  • Go
  • Python
  • Terraform
  • AWS
  • Cloudflare
  • Stripe

Let's connect

Whether it's a cloud architecture problem, a platform that needs building, or something in between, I'm glad to talk it through.

Résumé

Parker, Colorado

© 2026 Brandon Shutter