Companies we have built, run or grown
Ours first. Then the ones who asked for the same thing.
The row grows as the work does. Every one of these is a real business; ask on the first call and we will walk you through the systems behind it.
Read one install, start to finish →
- Wasatch CleanersService company: quote engine, hiring funnel, lead sentinel, care plans, local search
- AkovexOperations platform: briefing, tasks, meetings that assign work, e-sign, finance
- TidumoVertical software for cleaning companies, licensed to other operators
- Ekot GroupProperty management: owners, tenants, vendors and turnovers on one screen
- The Broker's TableMedia brand with a store: production pipeline, syncing episodes, product ladder
- Esther StowellFounder brand and speaking site, built to be maintained without a developer
- And more as we scaleClient work joins this list as it goes live
Notes on each company
What was broken, what we installed, what still runs.
We hold a stake in each of these, which is why the notes are blunt. One system per note, one thing that failed, and what is different when the company is not ours.
wasatch-cleaners.comrunning
Wasatch Cleaners
Cleaning company, Salt Lake City. Ours.
- Broken
- Leads from two platforms arrived masked and were discarded. Quotes priced by memory. Over a hundred applications unread.
- Installed
- Lead sentinel with recovery and a text to the owner, quote engine with a floor, hiring funnel with scoring and slot booking, care plans, local search pages.
- What failed first
- The first lead parser threw away anything with a masked email. Found by a customer who called to ask why nobody replied. Fixed, then monitored.
- If it were not ours
- Two weeks longer. We would spend them in shadow mode so your office checks every recovered contact before it goes live.
akovex.comrunning
Akovex
The operating platform itself. Ours.
- Broken
- Six inboxes, four logins, and a founder reading all of them to know what happened yesterday.
- Installed
- The morning briefing, tasks with owners and dates, meetings transcribed into assignments, e-sign, finance, and an AI layer routed per task that cut model cost by roughly three quarters.
- What failed first
- A database migration left a dozen queries pointing at the old store. Caught by an audit, not by a user. Now every deploy has a rollback that has been rehearsed.
- If it were not ours
- You would get it as an install, one module at a time, starting with the briefing.
tidumo.comrunning
Tidumo
Vertical software for cleaning companies. Ours, licensed to others.
- Broken
- Every cleaning operator we met was rebuilding the same booking, dispatch and payment flow by hand.
- Installed
- One codebase, many tenants, each company's data walled off at the database layer, so an operator can run it without a developer.
- What failed first
- Two brands with the same slug collided in the first multi-tenant build. Now names are checked before anything is created.
- If it were not ours
- This is the two-week vertical install on the pricing page. It is what we would put into your cleaning company.
ekotgroup.comrunning
Ekot Group
Property management. Ours.
- Broken
- Owners, tenants, vendors and turnovers lived in a property system and three spreadsheets that disagreed.
- Installed
- A live connection to the property management system, several hundred vendors on one screen, turnover boards with a cost strip, move-out to make-ready as one tracked flow.
- What failed first
- The first vendor sync trusted the source data. It had duplicates. Now imports are deduplicated and reviewed before they land.
- If it were not ours
- The connect-not-replace pattern: we keep your property system and put the operating layer around it.
thebrokerstable.comrunning
The Broker's Table
Media brand with a store. Ours.
- Broken
- Episodes published by hand, a contact form that silently lost leads, products announced before they existed.
- Installed
- Episodes sync from the host automatically, a store with a product ladder and live payments, a clip pipeline from long episodes to shorts.
- What failed first
- A caching layer swallowed form submissions for weeks. Found by testing the form end to end, which is now a standing rule for every form we ship.
- If it were not ours
- The content engine on the services page: podcast in, shorts, captions, covers and a schedule out.
estherstowell.comrunning
Esther Stowell
Founder brand and speaking site. Ours.
- Broken
- A site that needed a developer for every change, so it never changed.
- Installed
- A site the owner maintains alone, with a recurring audit that reports what drifted.
- What failed first
- Typography choices the owner disliked and told us so. We changed them. The rule that came out of it applies to every site we build now.
- If it were not ours
- The smallest engagement we do. Usually part of a larger install, sometimes on its own.
What an engagement produces
Not a deliverable. A running system, and the people who keep it running.
StrategyA written blueprint: what to install, what it earns, the date, the price. Pricing and scale plans built on real unit economics.
SystemsIntake, quoting, scheduling, hiring, dashboards, portals, stores, platforms. Configured to the business, live in stages.
MarketingSearch including the AI answer box, paid, email, referral programs, films and reels from our own pipeline, all attributed.
OperationWe stay. Errors reach us first, restores are rehearsed, the numbers arrive monthly with the next thing worth building.
Try it instead of reading about it
Six pieces of this, running in your browser.
Descriptions of software are worth very little. So we cut six working pieces out of the systems above and put them on a page you can touch: take a shift answering leads and then watch the operating layer take the same shift, price a job against a floor it refuses to go below, turn a meeting into owned tasks, score an applicant and read every reason, write four openings for a post. Nothing you type is sent anywhere.
Open the playground →