>
Home Experience Clients Studio Products Skills Get in touch
Available for hire

Experience in depth

The work behind the roles.

My experience grouped by the kind of work I do, from regulated financial operations to executive support, project delivery, and building software. Real tools, real reporting, real automation, the problems I solved, and the language of each domain. Tap any highlighted term to see what it means and how I used it.

10+years across finance, ops, and delivery
4domains of work
5roles and ventures
70+tools, frameworks, and terms

Domain 01

Financial operations and compliance

Seven years across the regulated end of customer finance: escalations, identity and fraud checks, disputes, credit, and collections, plus the compliance guardrails that protect both the customer and the company.

Subject Matter Expert and Escalation Manager
Intuit · Financial Products
Feb 2013 - Jan 2018 · 5 years

ScopeHigh-volume US fintech support across the Quicken, QuickBooks, and TurboTax ecosystems, owning tier-2 and tier-3 escalations and acting as the floor's subject-matter expert.

What I did

I owned the cases nobody else could close: money movement gone wrong, identity and fraud checks, disputes, billing failures, and anything with regulatory weight. I resolved escalations end to end, set the standard for compliant handling, coached agents, and fed recurring problems back to policy and product so they stopped recurring.

Representative work

  • Resolved account-takeover and identity cases requiring KYC re-validation and careful PII handling.
  • Owned payment disputes and chargeback escalations, balancing customer outcome against GLBA and company policy.
  • Acted as SME reviewer and approver for tier-2 agents on money-movement resolutions.
  • De-escalated high-emotion, high-value customers while protecting the company's position.
  • Ran root-cause analysis on repeat escalation drivers and wrote it up for policy and product.
  • Maintained and improved the escalation playbooks the wider floor relied on.

Problems I solved

A stuck refund-then-rebill loop

A cohort of customers were trapped bouncing between refund and rebill, and agents kept reopening the cases. I traced it to a billing-flag mismatch, documented the pattern, and handed policy a repeatable fix that closed the loop for good.

Identity versus access

Locked-out customers wanted instant access while compliance wanted proof. I standardized a re-validation path that satisfied KYC without stranding legitimate users, cutting resolution time while staying inside the rules.

Tier-2 overload

Cases that should never have reached tier-2 were flooding it. I tightened the escalation matrix and playbooks so agents could self-resolve, and escalation volume dropped.

Tools and software

SalesforceCase-management systemsGenesys telephonyKnowledge-base toolingExcelGoogle Sheets

Reporting

Weekly escalation-trend and root-cause reports, QA scorecards, and SLA, CSAT, and first-contact-resolution tracking, plus case-aging summaries surfacing systemic issues.

Automation

Reusable response templates, case-tagging conventions, and standardized escalation playbooks that cut repeat-handling time.

Deliverables

Escalation playbooks, root-cause writeups, QA scorecards, agent coaching notes, and policy-feedback summaries.

Frameworks and terms

KYCAMLGLBAPII handlingChargebacksDisputesSLACSATNPSFCRRoot-cause analysisEscalation matrix

Worked withFront-line agents, team leads, QA, policy, and product, plus direct contact with high-value customers.

Outcomes

  • Five years of tenure with progression into an SME and escalation-lead role
  • Trusted with the most compliance-sensitive and high-value accounts
  • Mentored front-line agents on regulated, money-movement cases
  • Reduced escalation handling time and repeat volume through playbooks and root-cause fixes
Credit and Collections
City View Blinds
Feb 2018 - Dec 2019 · 2 years

ScopeOwned the credit and collections function end to end: credit assessment, receivables, recovery, and reconciliation.

What I did

I ran the full order-to-cash back end: assessing customer credit, keeping receivables current, chasing overdue balances, negotiating payment plans, and reconciling accounts, all while protecting the relationship so recovery did not cost future business.

Representative work

  • Managed aging receivables and prioritized collections by risk and value.
  • Negotiated payment plans that recovered balances without losing the customer.
  • Ran dunning sequences and escalation for seriously overdue accounts.
  • Reconciled accounts and applied cash correctly, flagging discrepancies for correction.
  • Assessed credit for new and existing customers to limit exposure.

Problems I solved

A ballooning 90-plus bucket

The oldest receivables were growing faster than they were being collected. I re-sequenced collections to hit the highest-value, oldest accounts first and brought the 90-plus bucket back under control.

Recovery versus relationship

Aggressive collection risked losing good customers. I built tiered payment plans that recovered the money and kept the relationship, so recovery did not become churn.

Tools and software

QuickBooksExcelAccounting and ERP toolsEmailPhone

Reporting

Aging reports, collections status, cash-application summaries, and DSO tracking for management.

Automation

Standardized dunning sequences and payment-reminder templates for consistent, timely follow-up.

Deliverables

Aging reports, collections trackers, payment-plan agreements, and reconciliation summaries.

Frameworks and terms

Accounts receivableAgingDSODunningCredit assessmentReconciliationCash applicationWrite-offs

Worked withSales, finance, and customers directly.

Outcomes

  • Kept receivables current and reduced overdue balances
  • Recovered outstanding accounts while preserving customer relationships
  • Brought consistency to credit decisions and collections follow-up

Why it matters for your team

If you are hiring for financial operations, this is someone who already works fluently in the regulated, money-movement world, KYC, AML, GLBA, disputes, credit, collections, and reconciliation, without needing the language explained.

Domain 02

Executive and operations support

Senior EA to C-level leadership at a US digital agency, plus the operations project manager who built the systems behind the work, calendars and inboxes on one side, utilization reporting and automation on the other.

Senior Executive Assistant and Operations Project Manager
Plan Left LLC · Nashville, remote
Jan 2024 - Apr 2026 · 28 months

ScopeSole EA and operations project manager for a US digital agency's leadership team, across time zones.

What I did

I supported founders and senior leaders across the full EA surface, calendar, inbox, meeting and board prep, travel, and expenses, and I owned the operations layer underneath: SOPs, utilization and capacity reporting, resourcing, and the automations that replaced hours of manual work every week. I was the person who made leadership's week run and the operation legible.

Representative work

  • Managed calendars, inboxes, travel, and expenses for multiple senior stakeholders across time zones.
  • Ran board and leadership meeting prep: agendas, decks, follow-ups, and action tracking.
  • Built a live utilization dashboard from Jira and Tempo that replaced a manual weekly export.
  • Stood up SOPs for recurring operations so the work did not depend on any one person.
  • Produced monthly financial and operational summaries for the founder.
  • Coordinated resourcing and capacity across the team's project load.

Problems I solved

Reporting ate every Monday

Utilization reporting was a manual export that consumed hours weekly. I wrote Apps Script to roll it up automatically into a live dashboard, and Monday mornings got their hours back.

Tribal knowledge

Key processes lived only in people's heads. I documented them as SOPs so onboarding, coverage, and handoffs stopped being risky.

Leadership flying blind on capacity

No one had a clear view of who was overbooked. I turned utilization into a capacity view that flagged overload before it burned people out.

Tools and software

Google WorkspaceJiraTempoSlackNotionQuickBooksGoogle Apps ScriptZapier

Reporting

Weekly team-utilization and billable-hours reports, capacity-planning views for resourcing, and monthly financial and operational summaries for the founder.

Automation

Google Apps Script to auto-roll-up timesheets and utilization into a live dashboard, automated recurring report generation, and Zapier connections to remove copy-paste steps.

Deliverables

Utilization dashboard, SOP library, meeting and board packs, resourcing views, and monthly summaries.

Frameworks and terms

Executive supportChief-of-Staff functionsUtilization rateBillable hoursCapacity planningSOPsOKRsStakeholder managementResourcing

Worked withFounders, senior leaders, project managers, and the whole delivery team.

Outcomes

  • 28 months supporting C-level leadership at a US digital agency
  • Automated weekly reporting that previously consumed hours of manual work
  • Built SOPs and reporting systems that outlived any single project
  • Ran the utilization and financial reporting leadership relied on

Why it matters for your team

For an EA, Chief of Staff, or operations role, you get someone who does the assistant work and builds the systems underneath it, so the operation runs better after they arrive.

Domain 03

Project and production management

Producer and project manager for QA on campaigns for some of the biggest names in media and tech, more than 30 projects delivered across Agile and waterfall teams.

Producer and Project Manager
Foxhole QA
Jan 2020 - Dec 2023 · 4 years

ScopeProducer and PM across more than 30 QA engagements for major media and technology brands, in both Agile and waterfall.

What I did

I produced and project-managed QA for campaigns and product launches, coordinating designers, engineers, and QA across timelines, scope, and client expectations for clients including Google, HBO, and Coachella. I ran the delivery cadence, owned defect triage and release readiness, and was the single point the client trusted for status and decisions.

Representative work

  • Ran QA production for campaign and product launches under fixed client deadlines.
  • Coordinated designers, engineers, and QA across Agile sprints and waterfall milestones.
  • Ran sprint planning, standups, and retrospectives, keeping scope and capacity aligned.
  • Owned defect triage, prioritization, and release-readiness calls.
  • Managed client-facing status, expectation-setting, and scope negotiation.
  • Standardized kickoffs and QA cycles into repeatable templates.

Problems I solved

A launch at risk

A campaign was tracking to miss go-live. I re-cut scope into must-have versus nice-to-have, re-sequenced the QA cycles, and it shipped on date with the critical path clean.

Noisy bug reports

Inconsistent reports slowed triage. I standardized the bug-reporting format so defects were reproducible and prioritizable on sight, and triage sped up.

A nervous client

One client wanted constant updates. I set a predictable status cadence and a single source of truth, which replaced anxiety with confidence.

Tools and software

JiraAsanaTrelloSlackGoogle WorkspaceBug and defect trackersFigma

Reporting

Project status and milestone reports, QA test and defect reports, sprint burndown and velocity, and release-readiness summaries.

Automation

Templated project kickoffs and QA cycles, standardized bug-reporting formats, and recurring status roll-ups.

Deliverables

Project plans, QA test reports, defect logs, release-readiness summaries, and client status decks.

Frameworks and terms

AgileScrumWaterfallSprint planningBacklog groomingStandupsRetrospectivesUATRegressionDefect densityRelease management

Worked withDesigners, engineers, QA testers, and client stakeholders at major brands.

Outcomes

  • More than 30 projects delivered for brands including Google, HBO, and Coachella
  • Coordinated distributed, cross-functional teams end to end
  • Balanced scope, timeline, and quality under real client deadlines
  • Ran both Agile and waterfall delivery depending on the engagement

Why it matters for your team

For a project or delivery manager role, this is proven multi-project delivery at brand scale, in both Agile and waterfall, with real clients and real deadlines.

Domain 04

Systems and automation building

The founder side. I build production fintech software solo, using AI-assisted development to ship what most people only spec. This is where operations meets engineering.

Founder and Solo Builder
Kabuhayan I.T. Services · DTI-registered
2024 - present

ScopeDesign, build, and operate a family of production fintech products, solo, using AI-assisted development with real engineering discipline.

What I did

I take products from idea to live: architecture, database design and security, financial-model logic, regulatory disclosure, testing, and deployment. As a non-developer founder I work through AI-assisted development but hold the line on rigor: row-level security, automated tests on the money paths, deployment gates, and regulatory disclosure that stands up to scrutiny.

Representative work

  • Architected multi-tenant systems with row-level security across 80-plus tables.
  • Implemented loan, fee, and interest logic with regulatory disclosure such as effective interest rate and APR.
  • Built booking and billing with PayMongo webhooks and ledger reconciliation.
  • Guarded the money paths with 565-plus automated tests and deployment gates.
  • Designed data-privacy controls aligned to the Philippine Data Privacy Act.
  • Shipped four distinct products from schema to live UI.

Problems I solved

Tenants sharing one database

Partners needed isolation but I wanted one system to maintain. I enforced row-level security on every table so each partner sees only their own data, with no cross-tenant leak.

Disclosure that has to be right

Lending disclosure is legal exposure, not a formatting choice. I locked the interest and fee math and the effective-interest-rate disclosure behind tests so a wrong number cannot ship.

Solo, but not sloppy

Building alone invites shortcuts. I put deployment gates, probe-before-edit discipline, and 565-plus tests in place so speed never costs safety on the money paths.

Tools and software

SupabasePostgresNext.jsReactTypeScriptPayMongoVercelCloudflareAnthropic APIGitVitest

Reporting

Financial models for loan and fee computation, commit and delivery analytics, and regulatory disclosure outputs.

Automation

CI and deployment gates, agent-based development workflows, 565-plus automated tests, and billing webhooks with reconciliation.

Deliverables

Four live products, database schemas, financial models, regulatory disclosure logic, test suites, and deployment runbooks.

Frameworks and terms

Multi-tenant architectureRow-level securityREST APIsWebhooksMigrationsADRsRA 9474 and 8556RA 3765RA 10173AMLROSCASaaS

Worked withSolo build, with regulatory counsel input on lending and data-privacy disclosure.

Outcomes

  • 2,331 commits shipped across the product suite in roughly three months
  • 80+ database tables secured with row-level tenant isolation
  • 565+ automated tests protecting financial calculations
  • Four production products taken from idea to live, solo
Kabuhayan

B2B lending-operations SaaS. Multi-tenant, row-level security, EIR and APR disclosure, 1,986 commits.

Paluwagan

No-custody rotating-savings app. KYC pipeline, dispute resolution, Taglish localization, PWA.

Poster

AI marketing content SaaS. Brand-voice generation and PayMongo subscription billing.

EA Copilot

Executive-assistant decision-support. Gmail OAuth, calendar, and safe email rendering.

Why it matters for your team

If you want someone who understands product and engineering from the inside, this is operations thinking applied to shipping real software, with security, compliance, and testing built in.


How I work

The operating principles behind all of it

The habits that carry across every role, from escalations to shipping software.

Document so it outlives me

Playbooks, SOPs, and runbooks, so the work does not depend on any one person being in the room.

Automate the manual

If it happens every week by hand, it gets a script. Reporting and roll-ups should run themselves.

Protect the money paths

Where money or compliance is involved, tests and gates come before speed. A wrong number should not be able to ship.

Translate for the audience

The same work, explained in the language of the person reading it, whether that is a founder, a client, or an auditor.

Own the hard cases

Escalations, disputes, and the things others avoid. The messy end is where the value is.

Probe before I change

Understand why something exists before touching it. Investigate intent first, then act.


Reference

Tools, frameworks, and terminology

A full index of what I have worked with across all four domains. Highlighted terms are tappable for a plain-English explanation, a visual, and how I used it.

SalesforceGenesysJiraTempoAsanaTrelloNotionSlackGoogle WorkspaceGoogle Apps ScriptZapierQuickBooksExcelFigmaSupabasePostgresNext.jsReactTypeScriptPayMongoVercelCloudflareAnthropic APIGitVitestAgileScrumWaterfallSprint planningBacklog groomingStandupsRetrospectivesUATRegressionRelease managementDefect densityKYCAMLGLBAPII handlingChargebacksDisputesSLACSATNPSFCRRoot-cause analysisEscalation matrixAccounts receivableAgingDSODunningCredit assessmentReconciliationCash applicationWrite-offsExecutive supportChief-of-Staff functionsUtilization rateBillable hoursCapacity planningSOPsOKRsStakeholder managementResourcingMulti-tenant architectureRow-level securityREST APIsWebhooksMigrationsADRsRA 9474 and 8556RA 3765RA 10173ROSCASaaS

Want the version tailored to your role?

Tell me the kind of work you are hiring for and I will walk you through the parts of this that matter most to you.