Delivery LeadershipEngagement ManagementCustomer Success

Delivery that holds

I take over enterprise engagements that have started to drift and make them predictable again.

Scope, margin, delivery and the renewal —
held together rather than traded off.

Dallas, TX
Open to Dallas & remote

Currently Client Success Lead
at a technology consultancy

$20M+Portfolio owned
25+Engagements directed
92%Renewal rate
+1.1ptsGross margin gain
32.3% → 33.4% in one year
2×Company recognitions
15+ accounts across 3 segments · 2026 President’s Club and 2025 Q3 Customer Success Business Impact Award · A national technology staffing & services firm, 2022–2026
01 — Work

A rescue, a build, and a book at scale

A program I inherited already flagged red, a delivery capability stood up inside a client that had never used one, and the scope of the account I carried while it grew.

Rescue: a modernization program flagged red by the client

Problem

A two-workstream modernization program at a Fortune 100 financial services firm, flagged red by the client’s own domain review before I took it over. No delivery methodology, no governance plan, no documented commitments, and nobody on either side owning requirements — which were being reverse-engineered out of legacy code. Fourteen engineers, a hard seasonal freeze I could not move, and an executive sponsor who had already lost confidence.

Approach

Led as primary delivery owner, from delivery lead through executive sponsor. Had the client define milestones rather than inherit a date, and put one named owner on each. Narrowed three parallel batch jobs to one, and front-end scope from five transaction types to one proven end to end — a repeatable pattern beats five half-finished ones. Rejected: holding the original date and pushing harder. Closed volume against work in flight said it would not land, and a missed date after a death march costs more credibility than a renegotiated one.

Outcome

Nine milestones defined where there were none; first two demoed sixteen days after I landed — the first working increment the engagement had produced. On the batch side, specification approved first pass, stories the same day, build four days later, and my engineer promoted to technical lead with the client’s backing. Both workstreams now target delivery ahead of the October freeze. In flight.

ReflectionI moved on governance before requirements ownership, and requirements was the more expensive gap by a wide margin. Where a client-side expert owned the specification, the work moved within days. Where nobody would take that seat, it did not.

Build from zero: standing up nearshore delivery inside a new client

Problem

A major airline’s people-data organization needed more delivery capacity than its onshore budget allowed. My firm had run nearshore teams elsewhere, but nobody in this organization had worked that way before — so no internal precedent, a real working-style adjustment on both sides, equipment to ship across borders, knowledge transfer from client employees to consultants who had never seen the platform, and an expectation of immediate delivery from a team still onboarding.

Approach

Led the engagement design as a fully managed service rather than staff augmentation, starting with four nearshore data engineers and one onshore lead. Brought our practice leadership into scoping before the work was sold, so staffing was right up front instead of corrected later. Always placed a team with a lead on it, never an individual, so someone from the practice was accountable for holding junior engineers to the client’s bar. Rejected: staff augmentation, which puts every quality problem on the client’s desk instead of mine.

Outcome

Grew from 4 nearshore consultants to 22 in eighteen months, and expanded to 4 pods across 3 additional portfolios in the same technology organization. That second number is the one that matters: those leaders had no obligation to use us. Performance travelled by word of mouth and they chose to trust the model on the strength of it.

ReflectionThe whole thing turned on the kickoff. Early practice involvement made the staffing right; a lead on every team made the quality hold. Those leads went on to carry business-review content and propose how to reach value faster. I would formalize that role from day one rather than discover how load-bearing it was.

Scope: 25+ engagements owned inside a 45+ engagement book

The remit

I directly managed 25+ engagements inside an account carrying 45+ — a $20M+ portfolio with 90+ consultants deployed. Accountable for the whole account’s delivery including engagements I did not own, for two direct reports and their growth, for every consultant performing to the client’s bar rather than only mine, and for growing the account while all of that ran. Onsite with the client three days a week.

How I ran it

Split the book by complexity: my two direct reports took the simpler engagements with real ownership rather than shadowing me, and I held the complex, milestone-based and nearshore work myself. Made myself the escalation owner rather than the escalation router. Used the three days onsite as a governance instrument rather than a courtesy — risk surfaced in a hallway a week early is cheaper than risk surfaced in a status meeting.

Results

92% renewal rate, and gross margin up 1.1 points in a year — 32.3% to 33.4% on $20M+ of revenue, which on a book that size is where the commercial work shows. Both direct reports took on more scope, and the account grew while I carried it.

ReflectionSplitting the book by complexity was right. Splitting the relationship would have been better — I held the client-facing side too tightly for too long, which made me the bottleneck on my own account and slowed how fast my direct reports could grow.

Each of these in full — the constraints I could not change, what I led versus influenced, the options I rejected and why, and a longer reflection on each.

Read the detailed case studies →
02 — Tools

Four things I built that other people used to make decisions

None were asked for. Each replaced something done by hand, or a decision made without the numbers in front of it.

Client footprint & forecast dashboard

One view of our position inside a client’s technology organization: active engagement count, revenue forecast for the year, client spend across each of their portfolios, and investment by capability we provided.

Used by account teams and delivery leadership

SOW lifecycle tracker

Flags every SOW ending within three months — owner, portfolio, current value, and a forecast extension value derived from contract length and team size. Renewals stopped being reactive.

Turned renewals from reactive to planned

Pay / bill rate margin calculator

Lets a recruiter or account manager model gross margin live — change the pay rate against a given bill rate and watch the margin move. It put the commercial consequence in front of the person making the offer, at the moment they made it.

Margin decisions moved to the point of decision

Automated monthly SOW report

A survey to every consultant, auto-assembled into the exact client template: accomplishments, value delivered, the consultant’s own recommendations, issues and risks with mitigation, financial summary. A contractual deliverable on every SOW, previously built by hand every month.

Removed manual assembly from every SOW

No client data, figures or screenshots leave the client.

03 — Leadership

One team, or none of it works

Seven years took me from change control in a regulated plant, through project coordination and engagement management, to running delivery portfolios. The technical content changed completely. One thing did not: the work only goes well when the people doing it are set up to succeed — consultants, internal partners, and the client, who is a teammate rather than an audience.

The best outcomes were always achieved when people came together, supported one another, and worked toward a shared goal. Written on four years at a national technology staffing & services firm, 2026

Build a team, never place an individual

An individual placed into a client is a resource. A team with a lead on it is a capability — someone from our practice accountable for holding the bar, mentoring the engineers below them, carrying business-review content, and proposing how to reach value faster without trading away quality. I also bring practice leadership into scoping before the work is sold, so the people are right the first time instead of corrected later.

Promote the person already doing the job

Titles should follow capability, not seniority or tenure. I have moved people up over more senior peers because they were already performing at the higher level, and carried the awkward conversation with the peer rather than avoid the decision. The alternative — handing someone a title and hoping they grow into it — costs the team more than it costs me.

Two cultures, both respected

When I stood up a nearshore team inside a client that had never used one, it worked because the team built our practice culture inside the client while genuinely adopting the client’s. Inclusion was not a value statement there, it was the delivery mechanism. A distributed team that does not believe it belongs will not tell you what is going wrong.

None of this is soft, and it is not charity. A four-person nearshore team became twenty-two and expanded into three more portfolios whose leaders had no obligation to use us — because the engineers were held to a high bar and trusted enough to say when something was broken, and because word of that travelled further than any pitch I could have made. Looking after the people is the growth strategy, not a trade against it.

Three more of the principles I lead by — on recognition, on feedback running in both directions, and on why people come before delivery rather than after it.

Read the full leadership approach →
04 — People

What the people I worked with say

I am so grateful to have worked alongside you! You have an incredible ability to solve complex problems, stay proactive, and bring people together around a common goal. Without a doubt, you left the team better than where we started. Thank you for being such a wonderful partner and friend.
Cynthia Phillips (Villegas)
Enterprise Solution Sales Executive
You’ve taught me so much, and I’m incredibly grateful that our paths have crossed. There is genuinely no one quite like you — your positivity, professionalism, and the kindness you bring to every interaction are rare. You have such a good heart, and your impact on this account and the people around you goes far beyond the work itself. Thank you for all the support, encouragement, and positivity you’ve shared over the years.
Karla Monge
Solution Sales Executive
05 — Contact

Let’s talk about your portfolio.

Delivery Director → Engagement Manager → Project Coordinator at a national technology staffing and services firm, 2022–2026. Now Client Success Lead at a technology consultancy.