Nashville, Tennessee

AI Consultant in Nashville, Tennessee

Based in East Nashville, working with operations leaders across Middle Tennessee in person and with companies anywhere remotely.

Book a 30-minute callTake the 2-minute scorecard

No pitch. If I can’t find a workflow worth automating, I’ll tell you on the call.

Why Nashville

Nashville is an operations town: healthcare services, logistics, hospitality, and a fast-growing group of technology companies that run large support and back-office teams here. Lyft built one of its best support operations in Nashville, and I ran the platforms behind it for seven years. Checkr, where I lead strategic operations today, has a hub here too.

How I work with local companies

Working sessions on site, with the people who do the work, are the fastest way to map a workflow honestly. For Middle Tennessee companies I do the assessment and rollout work in person where it helps and remotely where it does not. For everyone else, the whole engagement runs remotely and has for years.

  • AI Operations Assessment, two to three weeks
  • Pilot to Production, six to twelve weeks
  • Fractional AI Operations Lead, a few days a month

The name

Session Player Studio takes its name from Nashville's session players: the musicians who walk in, learn the song fast, play exactly what it needs, and make the record better without needing to be the star. That is the job.

Questions

What people ask first.

Do you work on site in Nashville?

Yes, for assessments and rollouts in Middle Tennessee where being in the room speeds things up. Ongoing fractional work is mostly remote with periodic visits.

Do you work with companies outside Tennessee?

Most of my work is remote and always has been. Location only matters for the on-site option.

Which AI tools and vendors do you work with?

I am vendor neutral. I have bought and implemented platforms such as Zendesk, Twilio Flex, and 8x8 at Lyft scale, and I build with Claude, OpenAI, and current agent tooling every week. The recommendation follows the workflow, not the other way around.

Do we need engineers for this to work?

Usually not for the first wins. Most operations automation comes from well-defined workflows and off-the-shelf tooling configured carefully. When a build is needed, I write the first version or a spec your engineers can act on.

We are in a regulated industry. Is that a problem?

It is the normal case for me. I run operations under FCRA today, and at Lyft I worked through regulatory programs that required careful tradeoffs. Compliance is designed into the workflow with audit trails and human review, not bolted on afterward.

Further reading
AI & Operations

Eliminate, Automate, Too Late: How to Sort Support Work Before You Automate It

The EAT framework (Eliminate, Automate, Too Late) for deciding which customer support work to remove, which to automate with AI, and which to leave to people, plus how to classify customer pain at scale with an LLM.

Let’s find the first workflow.

Thirty minutes. Bring the process that eats the most time. You leave with a view on whether AI can help and what it would take.

Book a 30-minute call