DATA SHEET
REV. 2026.05 / PUBLIC

PART NO.
KJ01
Kevin Jordan
Technical Founder / Operator
STATUS
SHIPPING / Springfield, OR
AVAILABILITY
ACCEPTING WORK / AI WORKFLOW BUILDS
LISTING
KDJORDAN LLC / est. 2026
kevinjordan.dev
ABSTRACT

I build systems for
operational messes
that should not still exist.

I look for the workflows companies have learned to tolerate: rejected flows, manual exceptions, reconciliation messes, proofing queues, internal handoffs, and data nobody trusts. Based in Springfield, Oregon; working locally, across Lane County and the Pacific Northwest, and remotely with operators who have workflows worth fixing.

YR. SHIPPING
25+
1998 -> 2026
AGENTS RUNNING
24/7
multi-model, persistent
COMPANIES BUILT
07
zero -> market
FIRST STEP
15m
workflow audit
§01 / OPERATING THESIS

The weirdest thing about broken workflows is how normal they become.

DIAGNOSE / BUILD / MEASURE

At first, everyone knows the process is stupid. Then someone builds a spreadsheet, one experienced person becomes the translation layer, and the business starts depending on the workaround. A few years later nobody calls it broken anymore. They call it how we do it.

That is where I look first: not the clean dashboard, not the strategy deck, but the operational corner where time, money, risk, and tribal knowledge are leaking out of the business. Different industries. Same pattern.

§02 / CURRENTLY

What's on the bench.

UPDATED / 2026.05.27

Leading U.S. operations at BTS, one of the largest wholesale VoIP carriers in the world. Telecom is the current proving ground, not the box. The bigger thesis is finding the weird operational corners every industry normalizes, then building systems around the value leaking out. I am based in Springfield, Oregon, next door to Eugene, and work with operators locally, across the Pacific Northwest, and remotely.

[01]
Broken workflow replacement
Find the process everyone tolerates, quantify the drag, and build the smallest system that removes hours.
[02]
Operational waste streams
Rejected flow, rate chaos, CDR disputes, routing exceptions, and the ugly data paths where telecom proves the pattern.
[03]
Persistent agent infrastructure
Research, email, memory, scheduling, and tool access stitched into one operating layer instead of scattered context.
§03 / PROOF SYSTEMS

Selected systems, not shelfware.

03 SYSTEMS / 01 OFFER

No.SystemDomainProofStatus
01Apparel Proofing System
A proofing queue everyone learned to tolerate: garment templates, artwork placement, customer signoff, and production-artist review buried in hours of manual setup.
Manual Production Bottleneck4-8 hr path -> 15-30 min targetPILOT
02Telecom Operator Tools
Carrier workflows full of rejected flow, rate chaos, CDR disputes, routing exceptions, and data nobody fully trusts until an operator touches it.
Operational Waste StreamsVOIPAccelerator / ReconcileCDR / TelcoOSLIVE
03Always-On Agent Infrastructure
Context that used to be scattered across chat, files, email, memory, schedules, and tools, pulled into a persistent operating layer.
Context / LeverageHermes / agents / memory / automationsRUNNING
§04 / SERVICES

Start with one normalized mess.

01
Broken Workflow Fit Check
Bring one workflow your team has normalized but probably should not. I will tell you if it is a real automation candidate, where the ROI might be, and what I would look at first.
02
Workflow Map / AI Audit
Paid diagnostic for serious workflows: current-state map, bottlenecks, failure points, AI/software fit, ROI/risk read, and the first practical build path.
03
Bottleneck-to-System Sprint
Build the smallest working system around a real process: ingestion, automation, human review, reporting, and handoff into the existing operation.
04
Operator-Build Partner
Ongoing support for teams that need someone practical in the room: systems maintenance, new workflow discovery, vendor sanity checks, and roadmap execution.