Skip to main content
Logan Leiter

CX Studio · Customer experience consulting

Customer experience that somebody actually owns.

I help industrial and B2B companies fix the survey that dies in an inbox, the quote nobody owns, and the system that went live and took the old confusion with it.

  1. 01

    Problem

    Customers waiting on a quote, an email, or an answer nobody owns. A survey that comes back and dies in an inbox. A system that went live and took the old confusion with it.

  2. 02

    Approach

    I sit with the queue, the survey, and the people who own the handoff. Then I build the route, the follow-up, the report, and the tool the team will actually open.

  3. 03

    Outcome

    Something the operation can run without a project manager in the middle of every ticket. A front door. A closed loop. A reply target people can see.

Where I help

Where customer work usually breaks.

The labels change by company. The failure is familiar: the customer can feel it, and the operation cannot see it clearly enough to fix it.

01

Voice of customer, made runnable

Problem
The survey comes back, the detractors are real, and nothing in the operation is required to move.
Approach
Design the listening system — relationship NPS, transactional CSAT and CES, field service and chat — and the closed loop under it: owners, clocks, a dashboard, and a review leadership will not skip.
Outcome
A program someone can run on a Tuesday. Feedback has an owner. Unhappy customers get a follow-up. The score is no longer the end of the story.
02

Customer operations and responsiveness

Problem
Quotes, email, and order confirmations sit because nobody can see the queue, or everyone assumes someone else has it.
Approach
Give the work a front door, a route, and a reply target the team can manage. A first-reply target, like 24 hours, is the kind of goal I set. It's a target until you can show the interval.
Outcome
Cleaner handoffs, a visible backlog, and a front line that can tell what they own.
03

The system after go-live

Problem
The platform went live. The workarounds came with it. Reporting still depends on whoever exports the spreadsheet.
Approach
Design the workflow the system should support, then build the small joints around it: a CX dashboard, a service or procurement path, the integration that lands a survey where follow-up happens.
Outcome
A system people use because it matches the job, and a report that does not require a hero to assemble.
04

Customer portals and digital intake

Problem
Every large account brought its own portal, punchout, or inbox, and the team is babysitting them by hand.
Approach
Define the first-door path, pick a pilot that can actually finish, and stay until the exception process is visible.
Outcome
One way in, a short list of live connections, and a written definition of done before anyone talks about scale.

See the three engagements. Short notes on surveys, go-live, and the front door are in Insights.

The approach

How I take the work on.

I start in the operation, I build something the team can repeat, and I leave when they can run it without me in the middle.

01

I start with the week as it is

A sentence an operator can use on Monday. Who owns the work, what good looks like, and by when. Not a vision statement.

02

I read the queue and the survey

Response rate, aging, reply time, sentiment, quote turnaround. If a number is not trustworthy yet, it does not go on a slide. We mark the gap and go get it.

03

I find the missing handoff

Usually not “people don’t care.” Ownership is fuzzy, the handoff lives in someone’s head, or the system does not match how the work actually moves.

04

I leave a route the team can run

The smallest change that will still be here next quarter: a route, a follow-up, a target, a report, a tool. Then a cadence that keeps it honest.

Selected work

What the work looks like up close.

Operating work I lead in-house at a global industrial manufacturer. Here's the situation I walked into, what I did, and what changed.

VoCAnalyticsCX Ops

Feedback with an owner

Built a voice-of-customer program that treats the annual relationship survey and monthly transactional CSAT as a management system, not a report.

Problem
Survey results were not consistently tied to an owner or a follow-up.
Approach
A short transactional survey, a detractor workflow, and a review leaders cannot treat as optional.
Outcome
Replies have an owner, and detractors get a follow-up instead of dying in an inbox.

In-house project · global industrial manufacturer · 2025 – Present

PlatformsDigital TransformationCX Ops

Responsiveness after the system went live

Worked the post-go-live responsiveness problem — quotes, email, and order confirmations — and gave those intervals a target the operation can manage.

Problem
After go-live, quotes, email, and confirmations still moved on a mix of old habits and the new system.
Approach
One target, one view of aging, and a workflow in the system of record instead of a side spreadsheet.
Outcome
Quote turnaround and first replies have a visible target and a view of aging.

In-house project · global industrial manufacturer · 2025 – Present

CX OpsChange MgmtOperating Model

A front door, instead of a pile of inboxes

Designed the intake and routing model for a formal CX function so a request has an owner, a handoff, and a path.

Problem
Requests entered everywhere, and ownership changed with the person who saw them.
Approach
Team-based routing, a front-line ownership model, and a status people can see.
Outcome
Requests have an owner, and supervisors can see the age of unassigned work.

In-house project · global industrial manufacturer · 2025 – Present

ToolsPlatformsAnalytics

Tools that match a Tuesday

Built the joints of the CX system: a dashboard for the review, a survey-to-task integration, and a service portal that matches how requests arrive.

Problem
The signal, the queue, and the follow-up lived in different places.
Approach
Build the joints: a review dashboard, a survey-to-task integration, and a service portal.
Outcome
The review runs off a dashboard, and a survey reply can become a follow-up task without an export.

In-house project · global industrial manufacturer · 2025 – Present

PlatformsDigital TransformationCX Ops

One path instead of a pile of portals

Started replacing a pile of customer procurement portals and manual PO checks with a single integration path, beginning with a small pilot.

Problem
Staff were babysitting customer portals instead of running exceptions.
Approach
One integration path, a small pilot, and a written definition of done.
Outcome
A small pilot uses one connection instead of a pile of portals. I am not claiming the whole landscape is done.

In-house project · global industrial manufacturer · 2026 – Present

AnalyticsCX OpsOperating Model

A single definition of on-time

Helped the operation agree what “on-time” means and put promise-date adherence in a weekly review customers can actually feel.

Problem
“On-time” depended on which report you opened.
Approach
One definition, a dashboard, and a weekly exception review.
Outcome
The teams share one meaning of on-time, and exceptions have a weekly review.

In-house project · global industrial manufacturer · 2025 – 2026

What I watch

What this kind of work is trying to move.

These are the intervals I pay attention to. I don't publish numbers from this work, and I don't name the company.

Qualitative

Follow-up

Survey replies

Unhappy customers get an owner and a call back instead of sitting in an inbox.

Qualitative

Quote turnaround

Quotes

I made quote turnaround something the team could see and manage.

Qualitative

First reply

Reply target

A reply target the team can see and manage. A target isn't a result until you can show the interval.

Qualitative

Ownership

Requests

Every request lands with a named owner instead of sitting unassigned.

How an engagement runs

Close to the work, not above it.

Strategy that nobody can operate is a slide. I stay near intake, follow-up, and the report long enough to know whether the change is holding.

Three ways to work together: a CX audit, a voice of customer and NPS program build, or a website and CX build that covers intake, your portal, and your site. Each is scoped in writing first, and I quote after I've seen the problem.

  1. 01Every significant request enters through a defined channel with an owner. Ambiguity is not a queueing strategy.

  2. 02The week has a cadence: the review, the 1:1, the cross-functional sync. Each one ends with a written outcome.

  3. 03What good looks like is agreed before the build.

  4. 04Escalation is written down.

  5. 05The work closes with a retrospective. That is a requirement, not a celebration.

Tell me where customers are waiting.

Pick a time for an intro call and we'll talk through what's breaking, what you've already tried, and what a good month would look like. I'll tell you honestly whether I'm the right person to help. I reply to every request within one business day.

The intro call is free: 30 minutes on video. Book at least a day ahead.