The customer
A Texas promotional-products company makes branded merchandise - uniforms, name tags, badges, custom goods for clients who order the same items again and again, plus bigger custom projects where the creative work actually matters.
The operation ran on a legacy ERP the team used maybe 25% of, Sage for accounting, a set of Google Sheets that functioned as the order tracker, and email. A lot of email.
An order would arrive in an inbox, get forwarded to the right customer service rep, get typed into a spreadsheet, get handed to the design team through a second spreadsheet, and come back as a proof and a quote. Every order got the same treatment. During one working session, the owner pulled up a $48 badge order and pointed out that his team would spend the same time proofing and quoting it as they would a $4,800 order.
Automation
- Order intake automated
- Email routed into a ticketed system
- Automated nudges on stalled requests
- Drafted responses, human-reviewed before sending
Instrumentation
- Centralizing toward one source of truth
- Response-latency measurement
The wound
The owner had already run the numbers before we ever measured anything. Repeatable uniform orders were about 35% of the company's volume, and his CSR lead estimated that automating them would save roughly 80% of the team's time on that work. Skilled, creative people were spending their days re-keying orders that never change, while the big custom projects - the ones that needed their attention - waited.
What nobody had was measurement. No one knew how long a request sat before someone responded, or where an order stalled between inbox and proof. The cost was real; it just wasn't visible.
The conversation
The first real discovery call was 45 minutes of tracing money through systems - how does an order in the ERP show up in Sage, how does it show up in the sheet, who touches it and when. The owner later said he came away from that first conversation with a list of 67 things worth fixing.
He also floated replacing the ERP outright. The answer was the opposite of a consultant's answer:
"I definitely wouldn't start there."
There were front-of-house problems that could return profit immediately, and fixing those first would make an eventual ERP swap easier, not harder. The scope shrank instead of growing.
The deal didn't close on a deck. It closed over a coffee in Austin and a kickoff lunch at a restaurant in Salado.
The work
Two tracks ran in parallel.
The automation track went after the uniform orders first: order intake automated, email traffic pulled into a ticketized system instead of a shared inbox, automated nudges so a stalled request gets bumped without a human remembering to chase it, and drafted responses a rep reviews before anything goes out. The system does the repetition; a person keeps the right of refusal.
The instrumentation track built the eyes. Order data lived in spreadsheets, Dropbox folders, the accounting system, and shipping tools - none of it in one place. We began centralizing it toward a single source of truth and, for the first time, measuring request-to-response cycles, so "we're slow on Mondays" could become a number someone can act on.
The efficiency went exactly where the owner said he wanted it: nobody was let go. The CSR and design teams got their time back and moved it to the bigger custom orders - the work they were hired to be good at.
Where it went
The goal at kickoff was to automate around the old ERP. Within weeks it became replacing it - a system used at 25% doesn't earn its keep. From there the engagement kept compounding: a multi-store e-commerce rollout so uniform clients order the way they order everything else online, and AI tooling for the production side, including logo redraw and proof generation.
The through-line never changed:
"you're either keeping more profit in your company from existing revenue, or you're enabling your ability to go get more revenue."
The company got both.
The kicker
The results and the trust ran deep enough that the company didn't renew a vendor relationship - they became our business partner in a new venture. That story belongs to another part of Inventive. But you don't co-found something with a vendor who didn't deliver. Looking at what the work had become, the owner put it plainly: "that's the billion-dollar idea, honestly... It's real." The reply: "it's about to be."
If any of this sounds like your operation - orders arriving by email, spreadsheets as the system of record, good people buried in repeatable work - the first step is a conversation, not a contract. We'll trace the money through your systems and hand you a map of what we find. You correct it, and you decide whether there's a next step.