What it does
I run two Pink's Windows locations and my wife runs a The Designery franchise. Titan is what we actually use to run them day to day: the dashboard we check each morning, the report that lands in the inbox twice a day so nobody has to go looking, the customized agents the teams use to improve their work ad hoc, and the workflows that massively cut our recruiting, invoicing and collections costs.
The whole system is built and accelerated by AI coding agents. It can be stood up as an MVP for another operating brand in a week, and made operational within a month once blockers are cleared.
The 6pm email. The same numbers come to us — every visit from that day, and which ones still need invoicing or still need paying. This is the lever that shortened our cash cycle.
| Friendliness | ★★★ |
| Hustle | ★★☆ |
| Quality | ★★★ |
No red flags
Summary: Strong candidate in the right town, with years of relevant outdoor work. Clear communication and a well-thought-out answer to the customer-service scenario. All requirements met, no concerns identified.
Assistant Thanks for reaching out. A few quick screening questions before our GM sets up a time to meet — where are you located?
Candidate I'm about ten minutes from the yard.
★★★ — right by the van parking spot
What it changed
The franchisor licensed it
Pink's licensed what we built and rolled it out across the network, with individual locations able to subscribe to additional reports and workflows on top. It's the same system in every location, which is the part that matters: these results are reproducible, not a one-off.
How it's built
Every piece of work travels the same circuit — asked for, planned, or turned up by the overnight run. Scroll to run it.
In at the top. Back to whoever needed it.
Agents work in parallel. Merges don't.
One screen for all of it. They email when they're stuck.
It checks itself, and fixes what it can.
A coordinator keeps it moving. You come in for the calls that matter.
What the circuit changes
The dev team shrank to one. The work didn't.
A conventional build puts a team between the person who understands the business and the code that runs it. This one doesn't. The work runs in parallel and the operator drops in periodically — which moves velocity, cost and review in the same direction at once.
Velocity usually costs you review. Here it buys more of it — the lenses run in parallel too, so every one of those 752 merged pull requests got a harder look than a rushed team would give it.
Overnight three jobs run on their own: reconcile our data against Jobber and BigQuery and backfill whatever's missing, scan for errors, and draft the next day's plan. The next step is a coordinator that keeps the sessions moving without me, and only surfaces when a decision actually needs a human.
Getting it running
The question I get most: what would it take to point this at a different business?
That conversation is about finding the highest-leverage number in your business. For Pink's it was labor as a share of margin — we knew we were overspending on labor per job, so that's what we built toward first. Yours will be something else, and it's worth an hour to find out what.
Two ways to run it
One business
Build fee + usage-based license
A custom implementation pointed at your operation, your data sources and your numbers. A build fee to stand it up, then a license scaled to the functionality you turn on.
A franchise network
Build fee + per-location monthly
The Pink's model. One build, deployed multi-tenant, then a monthly per-location license tiered by functionality — with ongoing improvements and new workflows as they earn their place.
We start with a scoped proposal, or a working demo on your own data, so you can judge it before committing to anything. If you'd rather just see it, the base tier is free — connect your field-service system and the dashboard and the daily reports run on your own numbers.