I figured my application could introduce itself.

Built with LiveKit to answer questions about my experience, tools I've built, how I'd approach the role, and where I'd still have some learning to do.

AI fluencyEducates C-suite execs on AIConceived & Prototyped3D Cloud's first sold AI product0 → 1Built the enablement functionHands-onA Claude Code nativeRetention110% net revenueIPNamed patent inventor

Prefer to read?

A few things you might be wondering.

Why should we even talk?

I've already done the part of this role that sounds most familiar: building an enablement function from scratch inside a technical SaaS company, without an existing playbook.

What makes LiveKit especially interesting is the chance to do it with a team that already values enablement, and in a category where the sales motion is still being invented.

Why leave 3D Cloud?

I'm proud of what we've built here. 3D Cloud has been an incredible experience.

Now I'm looking for the next blank page: a deeply technical product, a fast-moving category, and a team where enablement can help shape sales from the beginning.

Technical enough for an infra product?

I'm not a career engineer, and I won't pretend to be.

But I do build working tools, integrate APIs and SDKs, and learn technical systems well enough to turn them into things sellers can use. I know how to ask the right questions, explain difficult ideas with clarity, and recognize when to let the expert take the lead.

What would you do first?

I'm a firm believer in learning from experience. In their first week, every AE would build a basic agent from LiveKit's docs.

The goal is for them to run into latency, turn detection, interruptions, and model choices firsthand, so deploying these tools stops feeling abstract. That's an experience we can turn into stronger discovery questions, demos, talk tracks, and coaching.

A few examples of how I work

Demo Forge

A retailer's product page → a working 3D demo, in minutes.

To sell at 3D Cloud, a prospect needs to see the product under their own branding, not a generic demo. That used to mean rebuilding a product page by hand. So I built a pipeline that captures the page, interprets its design, generates an SDK-integrated demo, and verifies everything loads, then hands off to a rep or solutions engineer to fine-tune it with natural language instructions. What took hours now takes minutes, without removing the human quality check.

ROI Calculator

Business cases built to survive a CFO.

The ROI tooling we use in live enterprise deals: modeling conversion lift, order value, and return reduction against a prospect's own numbers. I pushed hardest on making it defensible rather than impressive: incremental lift, not total volume; margin, not revenue. An ROI model that overstates is worse than none.

Sales Operating System

The AI-assisted portal our team runs on.

One place for account coverage, automated research, coaching, and sales assets.

The research workflow includes a claim-verification gate so unsupported information doesn't make it into a customer conversation. The AI coach is grounded in our own content, and the asset library automatically checks link health before reps send a demo. Built on the AI-friendly stack of Next.js, Supabase, Vercel, Railway and Claude.

AI Room Planner

3D Cloud's first AI product to reach the market.

3D Cloud builds 3D visualization, not AI. But once the models felt ready for it, I put together a prototype on my own time, mostly to see if it would work. It turns a photo of a real room into a styled, shoppable version of itself. I pitched it, and it became the first AI product the company brought to market and sold.

I built this because the role sounds unusually close to the work I do best: learning hard products, making useful things, and helping sellers become more credible.

I'd love to talk about what that could look like at LiveKit. And, on a human level, I think I'd love being part of the team.

— Jeff

Résumé (PDF)Email me