Technology & innovation executive · People builder · Operator · CPA · Veteran
I built my career by questioning accepted answers, looking beyond the boundaries of my role, and refusing to let hierarchy, politics, or bureaucracy stand between a meaningful problem and a better solution.
Technology is moving faster than traditional organizations can respond. I help close that gap — modernizing systems, aligning people, and creating the conditions for ideas to move, decisions to be made, and impact to scale.
Expertise becomes systems. Systems create impact. Impact happens through people.
For thirty years the person who saw the problem and the person who could build the fix were two different people, and everything got lost in translation. That gap is closing. The new innovator is the domain expert who can build — and the constraint is no longer capability. It's judgment.
01
Most companies are solving the wrong problems faster. AI didn't fix that — it accelerated it. The first question is never can we build this. It's whether this is the problem that deserves the next six months.
02
Time doesn't disappear; it gets reallocated. The real question is what caliber of quality the team operates at afterward. Not working less — operating differently, and smarter.
03
Everyone asks whether AI can do the work. The better question is whether we can prove it did it right — the difference between a system people adopt and one they quietly work around.
04
Organizations don't outperform because they obsess over customers. They outperform because they invest in the people serving them. As AI absorbs execution, that becomes more of the job, not less.
As AI takes on more of the what and the how, leadership becomes even more about the why and the who.
The reach
Two decades in office-of-the-CFO technology — audit, advisory, and enterprise SaaS — across every industry, working with some of the largest and most complex organizations in the world. The last four years have been focused on AI-native architecture and orchestration — building the systems, not just directing them.
Every seat in the lifecycle
Customer success, solutions consulting, product and business transformation, platform strategy, building, release, and enablement — including ownership of a new product line from idea to scale. Betting a company's transformation on software means knowing exactly where plans meet reality.
The spine
U.S. Air Force — mission first, people always. PwC and Deloitte. Founded a CPA firm serving real estate investors and small businesses, and ran a rental portfolio for a decade. Every chapter required learning something new from zero.
Beyond the day job
Serving as an advocate for the LGBTQ+ community and a respected presence among women entrepreneurs and founders. Serving on the board of an organization providing resources to domestic violence victims.
CPA (VA) · M.S. Accounting, Liberty University · B.S. Accounting & Computer Science, University of Maryland · Veteran · Los Angeles, CA
Code ships → the content keeps up
Release readiness. When engineers ship a change, the help articles, release notes, training video and sales briefing it needs are written to match. Nothing goes out until a person approves it.
The problem
Organizations now ship technology faster than their customers can absorb it. Documentation, release notes and training arrive late and uneven, so customers are left to work out a product that has already moved on — and support absorbs the difference.
The value in solving it
Customers get timely, clear, high-quality guidance the moment a release lands, so they can actually adopt what was built. Release velocity stops outrunning the customer, and the field walks in prepared instead of catching up.
Capability comparison · survivor calls · migration plan
For an acquisitive software company: compare capabilities across every acquired technology, flag which implementation survives and which retires, and build the migration plan that folds the acquisition into one unified platform.
The problem
Growth through acquisition is a sound strategy — but only if the acquired technology gets folded into the existing stack quickly. Miss that window and you accumulate an arsenal of disconnected parts that never turns into customer expansion.
The value in solving it
The acquisition becomes part of one platform instead of another product to maintain: the surviving capability chosen on evidence, duplicates retired on purpose, and the migration sequenced so the deal compounds into expansion rather than fragmenting the portfolio.
Intake → process analysis → auto-configuration → ROI
It starts with the problem the customer is trying to solve. The engine maps that problem to the technology that solves it, analyzes their actual process, translates it into implementation data, writes the configuration files, configures the system to their requirements — and tracks the ROI they were promised the whole way.
The problem
Customers arrive with a specific problem, shaped by everything unique about their business. Translating that into the technology is done by hand, so implementations run long, the original problem gets lost in the build, and nobody can quantify the return they came for.
The value in solving it
Quicker time to value, traceable value, and an accountability system: the configuration reflects how this business actually works, every step ties back to the problem they came to solve, and the return is measured against the numbers they walked in with.
Due diligence · prioritization · allocation
Which problem deserves the next six months. Candidates are scored on impact, strategic fit, feasibility and signal, weighted by confidence, then re-ranked as evidence arrives — the judgment call, made in the open.
The problem
What to build next gets decided emotionally, or on a half-baked case, rather than on what will actually drive value. The people building are usually a step removed from the problems they are solving — and from how customers use the collection of products together.
The value in solving it
The decision gets made on evidence: every candidate scored on the same dimensions, grounded in how customers actually use the portfolio, re-ranked as new signal arrives — and defensible enough to walk a board through.
Citable retrieval · provenance · re-verifiable
Atomic rules that carry their own citations. Ask a question, get the governing rule and the policy that overrides it — not a paraphrase. The same retrieval pattern runs the company, domain and industry corpora.
The problem
An AI answer nobody can trace back to a rule is unusable where being wrong is a reportable event — and company policy sits in people’s heads, not in the model.
The value in solving it
Every answer walks back to the standard and the internal policy it came from, so an expert who does not trust the model can still verify it and sign off.
Registry routing · fail-closed authority · memory
The layer every other system runs on. Work arrives from any direction — a support case, a use case, a code change, a product area — and lands in the same governed path: classified, routed from a live registry, checked against authority before it can act, verified against evidence after.
The problem
Agents that can act without governance are a liability, work arrives from four different directions, and every new specialist means another rewrite.
The value in solving it
One governed path for all of it: routed from a live registry, fail-closed on authority, verified against evidence — and a new specialist is a config entry, not a project.
Verified figures are a checked, versioned snapshot of the engineering record. The build rejects blank, zero, partial, or regressed totals, so the last known-good numbers stay visible. Attested figures are career facts no script can check.
Signature talks
Innovation Is Choosing the Right Problem
Most companies are solving the wrong problems faster. AI didn't fix that — it accelerated it.
Trust Is the Real Moat in AI
Everyone's asking "can AI do this?" The better question: "can we prove it did it right?"
People First: The True Responsibility of Leadership
Organizations outperform because they invest in the people serving the customer.
Built, Not Born: What Resilience Actually Requires
Resilience isn't a personality trait. It's a practice.
The Chapters You Don't Put on Your Résumé
Your most important career chapter is probably the one you're embarrassed to talk about.
Presentations
Articles
Recorded & featured
Podcasts & media
Interviews, commentary, and stories on leadership, innovation, AI, finance, and the future of work.
Consulting & advisory
Strategy, systems, and transformation to modernize, simplify, and drive meaningful outcomes.
Network & community
Connection, mentorship, and shared learning with leaders, builders, and thinkers driving change.
Speaking & events
Keynotes, panels, and roundtables that challenge thinking and inspire action.
Subject-matter expert
Deep expertise in finance, accounting, product, technology, operations, leadership, and AI.
Builds & portfolio
Products, prototypes, and operating systems turning insight and expertise into scalable solutions.