What we built, and how it is put together.
Ten systems, each told the same way: what it is made of, the checks around it, how it runs, and only the results we can show. Some are client work, named with permission. Some we built to run MUVES itself.
LabelBot: the invoice prints its own shipping label
Carlos Ceramics Dental Lab, a family-run dental lab in North Miami Beach
A virtual printer, a parser that reads by position, a service-area check, a ledger with a lock and the courier API turn each printed invoice into exactly one label.
628labels in its first four weeks
A CRM sync that wrote 3,244 fields and overwrote none
Carlos Ceramics Dental Lab, syncing its practice history into Go High Level
0existing values overwritten
A WordPress rebuild that keeps all 88 old links
Carlos Ceramics Dental Lab, replacing a slow site dentists used every week
19 to 92phone speed score
A bilingual site where customers build their own print quote
Conception Design, a sign, print and apparel shop in North Miami Beach
EN / ESevery page, both languages
A five-kit store with Stripe checkout, built into an existing site
Custom Dental Solutions, selling bur kits to dental offices
5kits, one checkout
MUVES OS: 34 agents, one review gate, nothing sent on its own
Built in-house at MUVES, the system we run our own company on
34agents in 9 departments
A monitor with no model, and the tests that fixed our agents
Built in-house at MUVES, watching MUVES OS
12 of 12routing benchmark, about 1 s each
A voice assistant that knows a cough from an interruption
Built in-house at MUVES, the voice of our own assistant
52automated voice checks
Company books in Google Sheets that check themselves every morning
Built in-house at MUVES, running our own books
6 amcalendar rebuilt every day
A read-only audit that measured every page, click and redirect
Carlos Ceramics Dental Lab, before its website was rebuilt
88old addresses checked
The system first, the client second.
Every case page opens with the same five facts: what was built, the stack, the timeline, where it stands and the scale. Here they are side by side.
| System | Built for | Made with | Where it stands |
|---|---|---|---|
| Invoice-to-label automation | A dental lab | Python, a courier API, a Windows scheduled task | In daily use since September 2026 |
| CRM sync with an audit trail | A dental lab | Python, the Go High Level API, a CSV audit log | Delivered in August 2026 |
| A measured website audit | A dental lab | Python, Node.js, headless Chrome, Lighthouse | Delivered in October 2026 |
| Website rebuild with every link kept | A dental lab | A WordPress block theme and plugin, Blender, Remotion | Built, replacing the old site when the lab switches over |
| Online store with Stripe checkout | A dental supply seller | A WordPress plugin, Stripe Checkout | Built, launching once payments are set up |
| Bilingual site with a quote builder | A sign and print shop | A static site on Netlify, Netlify Forms | Live since September 2026, with monthly care |
| A multi-agent operating system | MUVES | Node.js, SQLite, local and cloud models | In daily use |
| Agent monitoring and testing | MUVES | Read-only SQL rules, evaluation scripts | Running beside MUVES OS |
| A voice assistant you can interrupt | MUVES | Local Whisper, Web Audio, echo cancelling | Built, real-microphone retest due |
| Books that check themselves | MUVES | Google Sheets, Apps Script, Gmail, Calendar | In daily use |
WordPress
Stripe Checkout
Google Sheets
Gmail
Google CalendarGo High LevelNetlifyPythonNode.jsBlenderThree trades, and our own company.
A family dental lab
Labels, records, an audit and a rebuilt site.
Its sister supply company
A five-kit store with card checkout.
A sign, print and apparel shop
A bilingual site with a quote builder.
MUVES itself
Agents, monitoring, voice and our own books.
Our client work so far sits in three different trades: a family-run dental lab in North Miami Beach, its sister company selling dental supplies, and a sign, print and apparel shop down the road. None of these systems is really about teeth or t-shirts. Each one is a pattern: a document that triggers an action, two systems that should agree, a site that takes the request. Every case page ends with where the same pattern fits in other kinds of business.
The in-house systems are the ones we run MUVES on every day. We count them as proof because we depend on them, and we say plainly that they are ours. For the problems they solve in your trade, see industries, or start from what we build.
Your business could be the next case on this page.
Tell us which step eats your week. The first call is free, and we will tell you plainly whether it is worth building.