From Firefighting to Operating System

The Situation

United Robotics is a 20-person ABB-authorized robotic welding integrator headquartered in Springdale, Arkansas. They build precision welding cells for OEM manufacturers, scaling demand from a deep technical reputation and a tight set of client relationships. Their work is hard to do well -- robot path programming, fixture design, weld parameter tuning, and customer integration on a shop floor that doesn't stop running.

By any reasonable measure, the technical side of the business was working. The operational side had grown without ever being designed. Quotes were assembled by hand from scattered sources, with each one taking 45 minutes or more to produce. Inbound communications -- prospect inquiries, partner updates, customer changes, vendor pricing -- all lived in individual inboxes, lost the moment someone closed a tab. Sales prospecting was driven by gut and territory familiarity, not data. Leadership had no consolidated weekly view of what was happening across the business, which meant problems surfaced as crises instead of early warnings.

It's the same pattern visible in nearly every growing manufacturer: the technical work is sharp, the people are good, and the operational nervous system simply hasn't kept up with the body it's attached to.

The Engagement Model

United Robotics didn't need a software vendor, a one-time audit, or a generic implementation playbook. They needed someone embedded in the business -- with operator-level context, not just consulting frameworks -- who could see what was actually broken and build the connective tissue to fix it.

Kre8ive Studio dropped in as a fractional operational intelligence layer. Not in the org chart. Not running a department. Sitting one level above the daily fight, with enough access to see the whole system and enough technical capability to actually build the missing parts.

Six workstreams emerged. They weren't a fixed scope of work; they surfaced as the system became visible. Each one solved a specific problem. Together, they shifted the business from operating on memory and reaction to operating on a structured, queryable picture of itself.

The Six Workstreams

Workstream 01 · Quoting

Custom quoting tool: 45 minutes to under 10

Quoting was the most visible bottleneck and the easiest to feel. Every proposal pulled specifications, pricing, and part data from multiple disconnected sources. Format drift was constant. A single typo in a part number meant a revision cycle.

Built a structured quoting tool that pulls the right specs, applies the right pricing logic, and produces a clean, consistent quote in under 10 minutes -- with the option to customize where it matters and standardize where it doesn't.

78% time reduction · deployed to sales team

Workstream 02 · Email Intelligence

Inbound communications, structured

Critical context -- new opportunities, partner shifts, customer requirements, problems forming -- was buried in email. A single VP could be sitting on three weeks of information that nobody else in the company could see.

Built an automated pipeline that captures inbound mail, summarizes it, classifies it, and logs it to a centralized intelligence database. Leadership now has a structured, searchable record of what the business is hearing -- and an attention layer that flags what shouldn't be ignored. The pipeline runs unattended on a managed cron, with a watermark checkpoint so nothing is lost or duplicated.

Operational, processing daily · 70+ summaries logged

Workstream 03 · Sales Territory Intelligence

TripTrack: route-based prospect scoring

Sales travel was high-cost time. Customer visits clustered geographically, but prospect targeting between them was driven by familiarity and luck. The team was driving past high-value manufacturers without knowing they were there.

Built TripTrack, a route enrichment app that ingests a planned itinerary, identifies high-volume manufacturers along the corridor, scores them against URI's ICP, and surfaces 15-25 pre-qualified stops per route. Sales reps now arrive at known territory with a prioritized list backed by real industrial data instead of a paper map and a hunch.

Deployed on Google Cloud Run · in active use

Workstream 04 · Leadership Visibility

The weekly operational update

Before the engagement, there was no consolidated weekly view of the business. Leadership relied on standup meetings, hallway conversations, and whatever was front-of-mind for whoever was talking. Patterns were invisible. Drift went unnoticed until it was a fire.

Built a weekly update workflow triggered by a single command: a two-gate approval process that produces three artifacts every Monday -- a PDF dashboard with the operational snapshot, a Notion page formatted as an internal email update, and a Gmail draft ready for distribution. Leadership now opens the week with a structured picture instead of assembling one from fragments.

First structured weekly leadership view in company history

Workstream 05 · Phone & Communication Hygiene

Spam analysis and phone system management

The company's toll-free line was being hammered by spam calls -- routine, ignorable, and quietly eroding signal-to-noise on legitimate inbound. Beyond the nuisance, the underlying phone system (UniTel) was a black box: nobody owned it, nobody understood the configuration, nobody had visibility into call patterns.

Performed a full spam pattern analysis, restructured the phone system management, and brought UniTel into the same operational visibility envelope as the rest of the inbound stack. Inbound noise reduced; legitimate calls more reliably reach the right person.

Spam pattern reduced · phone system under active management

Workstream 06 · Strategy & Talent

Growth intelligence, succession planning, and the talent brief

Beyond systems, leadership needed structured thinking partners on the strategic questions. Where is the business going? What does the next hire need to look like? How does succession actually work in a 20-person shop with deep founder knowledge concentrated in a few people?

Produced a Growth Intelligence Brief mapping market position and adjacent opportunity. Drafted a talent acquisition brief for the next critical role. Facilitated succession planning preparation. Built strategic context documents that leadership could use as reference, not artifacts that would sit on a shelf.

Three strategic documents in active use

The Outcome

The visible wins are easy to count: 78% off quote time, an email pipeline that runs unattended, a territory tool that pre-qualifies prospects, a weekly view that didn't exist before. But the deeper shift is the one that matters.

United Robotics now operates with a structured layer underneath the daily fight. Information that used to disappear into inboxes is captured. Decisions that used to depend on memory have data behind them. Leadership opens Monday with a picture, not a question. The system is no longer running them; it's running for them.

And critically: this layer compounds. Every additional week of email captured deepens the searchable record. Every additional route run improves the targeting model. Every additional weekly update establishes more pattern recognition. The investment doesn't depreciate -- it accrues.

Why It Worked

Three things made this engagement different from a typical consulting project.

Embedded, not advisory. Most consulting produces a deck and a recommendation. This produced working systems. The fractional model meant operating in the business, not consulting at it.

Operator context, not framework context. 18 years inside a manufacturer that scaled from 38 to 600 employees produces a different read on operational pain than an MBA case study. The diagnoses landed faster because the patterns were familiar from lived experience.

Compounding builds, not point solutions. Each workstream was designed to feed the next. The email intelligence layer makes the weekly update richer. The territory tool feeds the growth brief. The quoting tool surfaces patterns that inform pricing strategy. Nothing was a one-off.