Make something better out of what's there.
Your systems already hold what your customers need to know. The work is getting them to answer as one business.
Where AI fits.
Customers are starting to show up through their own AI (that's the last box on the top row up there), asking it to find a price or check on a repair or move an appointment. It only works if the context underneath is right. An AI reading from the system that never heard about the plan change is going to give the same wrong answer a stale account page would, just faster and with a lot more confidence. The layer that lets your site and your people answer as one business is the same one that lets an AI answer for you, the customer's own AI and any you put to work on your side.
Four steps, starting from what you have.
Characterize
I start by mapping what exists and how it behaves today, including the workarounds your team built to cover the gaps. Nothing disappears without a decision.
Connect
Then I build a thin context layer over the systems you already run, with one identity for each customer and one meaning for each term (so "active" means the same thing in billing as it does in scheduling), and data read where it lives.
Design the interaction
With that in place, I design around the jobs your customers are trying to get done, at the right depth for each person, from the customer who wants to handle everything on their own (more and more often by asking their own AI) to the one who wants somebody to handle it for them.
Prove it
I measure what customers finish and what your team stops doing by hand, which is how you find out whether any of it worked.
The approach works the same way when the person trying to get something done sits on your own team (in finance or operations, or answering the phone).
Every customer sits somewhere on the scale.
Self-serve and managed service are two points on the same line, and most customers move along it depending on what they're doing that day, so I design the blend on purpose. Buying sits on the same line (some customers want to build their own quote, some want a person to walk them through it, and most do a bit of both, starting online and picking up the phone when the price gets real).
The same customer, at every stage.
-
Explore
Whoever's shopping, sometimes for a whole companyCan you serve me, and what will it cost?
-
Buy
Whoever signs, and whoever approves the spendSigning up and getting the price they were quoted.
-
Deliver
The people on site waiting for itGetting set up and knowing when it'll happen.
-
Run
The people using it, and the people paying for itUsing it and paying for it, and getting help when something breaks.
-
Change
Whoever owns the account by thenMoving, upgrading, adding a location, or leaving.
When the customer is a company, a different person usually shows up at each stage. The office manager who asked for the quote hands off to whoever signs the contract, and months later it's someone in accounts payable calling about an invoice they've never seen the quote for. Each stage should pick up from what the business promised the last person, whoever that was.
What good looks like.
- Can your customers get it done without friction?
- Where self-serve ends, does your person pick up with the full picture?
- Does each term mean the same thing in every system and every conversation?
- Are you measuring what customers got done, along with what you shipped?
What I steer clear of.
Each of these moves the work back onto the customer.
- Pushing customers into a channel because it's cheaper for you.
- A separate experience for each system the same customer happens to touch.
- Handoffs where the customer has to explain it all again.
- Copying data into yet another store when it can be read where it lives.
The first step is a conversation.
Send a message. No pitch. Bring the question your customers keep calling about.
Send a message