The operator behind the surface.

Olivebank LC is the operating charter I work under. About a decade across auto retail, banking customer service, licensed insurance telesales, hotel reservations, and now senior sales and client operations in residential leasing. Layered with operational and technical fluency that lets me move faster than the team that usually does the same work.

Experience across sales, support, and operations.

Reservations, insurance, leasing, and support-heavy roles each sharpened a different part of the same skill set: commercial awareness, careful communication, and keeping the next step visible when a lot is moving.

The work sits at the intersection of sales, customer communication, operations, and systems. What holds it together is the habit of going deep into whatever domain the contract is in.

The pattern I bring: drop into a regulated, technical product domain cold. A few months later, I'm fluent in the product, the pricing, the regulations, and the customer language at the level a real strategy call requires. I build the operating tooling the team didn't have and write the documentation that lets the system survive without me in the room. The skill underneath is domain absorption plus operational synthesis. The deliverables are downstream of that.

I work as if it's my own business. The point isn't to leave a stack of files behind. It's to leave something the next person can actually run.

Tools follow the business logic, not the other way around.

Tools follow the business logic, not the other way around. The fit is strongest where the logic is clear and the system needs to be made usable.

CRM: HubSpot (Sales Hub certified) and Pipedrive most often; the same operating logic carries into adjacent platforms.

Workflow and automation: n8n, HubSpot workflows, REST APIs, and sequence design, including AI-assisted drafting and recap loops that run unattended.

Custom builds when off-the-shelf doesn't fit: landing pages and small apps in the modern static-rendered stack, lightweight servers, data pipelines, and AI-in-the-loop tooling on a local model.

Paid-media instrumentation across the major analytics and server-side event surfaces, with clean attribution back to the spend that earned it.

Contact-center exposure from enterprise voice-agent work and virtual-desktop telesales environments earned across licensed insurance roles.

The point isn't 'I know one app.' It's knowing how sales, reporting, notes, follow-through, and automation should behave inside whatever system is in place, and building the missing piece when there isn't one.

One surface for the work I take on now, and the work that may follow.

Olivebank LC holds the direct work and the current services. Anything that matures into a distinct offer can earn its own page later.

I want the site to stay stable, clear, and useful as the business expands.