Olivebank LC is the operating charter I work under. Most people building marketing automation have never sold anything. I spent about a decade in the seat the software is supposed to serve: auto retail, bank customer service, licensed insurance telesales, hotel reservations, and sales in residential leasing. Quotas, scripts, CRMs that got in the way, and follow-up that lived in somebody's head. That is why the systems I build survive contact with the people who have to use them.
How I work
Domain fluency, fast
Strategist by default. Pick up the product, the pricing, the regs, the customer language. Then make real calls, not safe ones.
Research and synthesis
When the call depends on what specs, regulations, contracts, or source documents actually say, go to the source. Verbatim quotes, ambiguity preserved, conclusions earned, not guessed.
Calm over theater
The work should feel steady, direct, and usable. No performance, no jargon padding.
Boring can be valuable
If a process only works on a good day, it is not solved.
Clear ownership
Recurring work should have a name, a place, and a person.
Ten years of carrying a number teaches the part that is not in any documentation: where a process quietly breaks, what a person actually does when the CRM is in the way, and how a customer sounds right before they go quiet. I build for that person because I was that person.
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 regs, 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.
I have carried a number
Worked a quota, been the top closer on a sales floor, and sat in the weekly reviews reading bottlenecks, slow-season patterns, pricing, and lead quality. So when I build a pipeline I know which stage people actually stall in, because I stalled there.
I have taken the calls
Years of high-volume voice and written contact under load. Hotel reservations across US chains, licensed life and health telesales in New Hampshire and Maine, and retention work where the conversation starts angry. That is where the follow-up copy comes from, not from a swipe file.
I have built the thing and left
The follow-up system a sales team now runs on: templates, message flows, CTAs, and timing rules, with notes, recaps, and coaching automated through the CRM. It lifted engagement and cut ghosting, and it kept working after I stopped watching it.
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.
Credentials
Pedigree across sales platforms, paid media, regulated-vertical compliance, data protection, and state-issued insurance licensure. Each one earned in a context where what it protected was real.
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.
Understand the moving parts
Start with the actual business, the offer, and the points where communication, visibility, or consistency begin to break down.
Set the working shape
Decide what should happen regularly, where the information lives, and how the work should look when it is being carried well.
Reduce the drag
Tighten the records, improve the handoff, and use automation or sequences where they make the system lighter instead of busier.
Keep it usable
The goal is a business rhythm that still works during a normal week, not just when someone is trying very hard.
Email is the simplest place to start. A service, a project, anything that belongs under Olivebank LC. A short note is enough. I read everything.
xavi@olivebanklc.com
Email reaches me directly and is the fastest way in.