Tenant #001 · Live
Escapod Trailers runs every order from deposit to delivery on Main Street Foundry.
Escapod builds the TOPO2 — a Red Dot and IF Design Award–winning overland teardrop camper — in Coalville, Utah. Every trailer is handcrafted. Every order is custom. And until recently, every customer update lived in the back of Chris’s head.
9
Stage build workflow
28
Tracked TOPO2 part SKUs
5
Personas on one tenant
0
Custom code per tenant
The Problem
Five months from deposit to delivery is a long time to leave your customer in the dark.
A TOPO2 Voyager takes around five months to build. In that time, Escapod’s customers are living with the most expensive purchase of their year — and most of them had no idea what stage their trailer was in unless they emailed. Chris H. was answering the same two questions on repeat: “What’s happening this week?” and “When can I come pick it up?”
Internally, it wasn’t much better. Marco tracked parts in a spreadsheet that went stale on Friday. Dana and Mike wandered the shop asking which build they were on today. Every major supplier had a different system. No single view of a customer.
The Fix
One tenant. Every role. Every part. Every customer.
Before
Customers calling every two weeks to ask “where’s my trailer?”
After
A live portal they check themselves. Milestone SMS when paint goes on.
Before
Parts inventory tracked in a spreadsheet that nobody trusted by Friday.
After
28-part catalog wired to real stock, auto-allocation to builds, reorder alerts.
Before
Marco scribbling shipment receipts on the back of packing slips at the dock.
After
iPhone scans the tracking barcode, photographs the slip, signs off with a tap.
Before
Five different tools to look at one customer (CRM, shop notes, email, files).
After
Customer 360 page with every order, warranty, note, contact log in one view.
Five roles, one login page
Everyone sees what they need. Nobody sees what they don’t.
The platform is role-aware. Chris H. logs in and sees the whole shop. Dana logs in and sees only the two builds she’s assigned to. Tim logs into his portal and sees his trailer’s paint photo the moment it’s taken. No custom code per role — it’s a config.
| Role | Person | Sees |
|---|---|---|
| Owner | Chris H. | Everything. Dashboard, reports, customer 360, inventory, billing. |
| Manager | Sarah M. / Chris T. | Orders, customers, inventory summary, pipeline reports. |
| Floor Lead | Marco T. | Full production pipeline. Worker assignments. Every part on every rack. |
| Worker | Dana K. / Mike P. | Only their assigned builds. Part checklists. Photo upload. |
| Customer | Tim, Rachel, Derek, Jess | Their portal. Their order. Their milestones. |
Phone-first receiving
A UPS truck backs up to the dock. Marco has sixty seconds.
Old way: Marco signs a slip. Takes it inside. Types into a spreadsheet later, if he remembers. Chris finds out parts arrived when he trips over a box.
New way: Marco opens escapod.mainstreetfoundry.io/ops/receiving on his iPhone. Scans the tracking barcode with the camera. Photographs the packing slip. Confirms quantities. Marks anything damaged. Signs off with QC. Good parts hit In Stock immediately. The system auto-allocates them to waiting builds and notifies the worker assigned to that trailer.
When his phone loses wifi (it’s an old metal shop), the steps queue in the browser and sync when he’s back in range. No lost receipts, no end-of-day catch-up.
The customer side
Five meaningful touches instead of fifteen cold ones.
Escapod picked five of the nine build stages as customer-visible milestones: Order Confirmed, Frame Fabrication, Interior Fit-Out, Paint & Finish (with a photo, always), and Ready for Pickup. Everything else is internal. The result is that every SMS Tim gets matters — so he reads it, shows his wife, shares it at work. That’s the whole point.
SMS · Thursday 2:14 PM · From Escapod
“Paint day. Your TOPO2 is getting its color — we grabbed a photo for you. See it: 🔗”
For the technical reader
The whole thing is configuration, not code.
Escapod’s tenant is one folder of configuration — stages, milestones, brand tokens, parts catalog, staff roster. Core engine is React + Node + DynamoDB on AWS, multi-tenant pool model. Auth0 handles login with a custom claim for tenant and role.
When Chris wants a change — “add a QA photo step before Paint” — he can either describe it to the Foundry Copilot in the ops dashboard and watch it ship, or it becomes a five-minute config edit. No engineering team on retainer. No bespoke deploy.
If this sounds like your shop — let’s talk.
We’re onboarding a handful of small manufacturers into this cohort. If you build something custom and your customers want to know where it is, we should probably meet.