Fast fit check.
If you are screening quickly, start with the Head of Finance CV, confirm the US-hours setup, then scan the four proof points above.
Open my default CVRemote US-hours finance systems operator
Decision-grade finance.
Built to survive review.
I help lean companies turn close, cash, reporting, and finance systems into one controlled operating picture. My work spans FP&A, controllership, treasury, tax/vendor cleanup, dashboards, crypto accounting, and board reporting.
Evidence over assertion
Controls before automation
Human ownership stays explicit
Start Here
I know different people are reading this for different reasons. Recruiters need fit fast. Founders and CFOs need judgment. Technical finance people need to know the work survives review.
Can I carry the messy middle?
Start with the First 30 Days Diagnostic, then read the Close Rebuild and Tax/Logistics case studies. That is closest to how I actually work.
Open the first artifactWill this survive review?
Read the Claim Support Matrix. I separate what I can publish, what stays private, and what I can walk through live.
Open the support matrixWhere I Help
I'm strongest in Seed to Series B environments where finance is too important to stay messy, but the company is still too lean to solve it with layers of people.
Finance Ownership
I can own FP&A, close, cash/runway, investor support, accounting operations, treasury, tax workflows, payroll, and reporting cadence.
Systems And Data
I'm comfortable in the messy tool layer: QBO, Bill.com, Rho, Stripe, Shopify, BigQuery, Fivetran, Looker, Metabase, SQL, Python, Apps Script, and automation workflows.
Operating Discipline
I care about the boring things that keep companies alive: vendor discipline, cost control, inventory/logistics visibility, department budgets, workforce planning, and board-ready metrics.
Selected Systems
These are working finance systems, not concept mockups. Each case study separates what was built, what was verified, and where human review or deployment boundaries remain.
Finance operations control plane
FinanceOps Warehouse
A client-isolated finance operations system that turns provider data into canonical facts, close controls, work queues, evidence, and explicit next decisions.
QBO / Stripe / Shopify / ShipBob / Bill.com
BigQuery raw to canonical to agent layers
Fail-closed release and close-state controls
Verified July 12, 2026
838 automated tests passed in this workspace.
Read the case study
QBOStripeShopifyBill.com
Client-isolated warehouse
Source trust / canonical facts / controls / evidence
Close gatesWork queuesHuman decisions
Close operations platform
Howard Finance Platform
Three tools on one stack: missing-bill detection before close, explainable GL coding review/prediction, and owner-statement review with an attributed audit trail.
Next.js / FastAPI / PostgreSQL
Deterministic + explainable semantic review
Client-scoped workflows and downloadable workpapers
Retested July 10 / built July 12, 2026
Four scoped runs with zero cross-client suggestions; TypeScript and the production frontend build passed.
Read the case study
01A/P ProactivityExpected-but-missing bills
02GL Coding ReviewReview / predict / explain
03Owner StatementsReview / revise / approve / pay
How I Think
I built these memos so you don't have to guess how I would approach the work. They're not pretty theory decks; they're the kind of operating artifacts I would want in front of me before making decisions.
First 30 Days Finance Diagnostic
Start here for founder-led Head of Finance roles.
Runway, Burn, And Cash Visibility
For cash discipline, restructuring, and runway ownership.
Monthly Close Rebuild
For close, controls, audit readiness, and controller-heavy work.
Finance Data Stack Architecture
For systems, AI FP&A, BI, and finance transformation work.
Board Finance Pack Template
For investor reporting and executive finance conversations.
Crypto Treasury Reconciliation
For crypto-native finance, treasury, and digital asset work.
Dashboard Operating Layer
For dashboard, BI, finance systems, and decision cadence proof.
Evidence, Without Leaking Private Work
These case studies are based on real workpapers. I sanitized them because wallet data, invoices, system exports, and company records do not belong in a public portfolio. The point is to show judgment, workflow, and proof standards without exposing private material.
Close Rebuild & Reporting Control
How I turn fragmented finance systems into a controlled reporting cadence.
Tax / Logistics Correction
Accounting judgment across tax/logistics treatment, vendors, periods, and ledger movement.
Crypto Accounting & Treasury Controls
Wallet, exchange, transaction, FMV, cost-basis, and JE workflow discipline.
Finance Data Stack Evidence Map
How accounting and operating systems become executive visibility.
Claim Support Matrix
What I can show publicly, what stays private, and what I can demonstrate live.
Dashboard Operating Layer
Sanitized dashboard recreations, inventory, and reporting logic.
What I can publish
Sanitized case studies, methods, outputs, and hiring-relevant claims.
What stays private
Raw workpapers, internal folders, wallet labels, hashes, vendor support, QBO exports, dashboard details, payroll/customer/investor records.
What I can walk through
The logic, assumptions, controls, decision points, and what I intentionally didn't publish.
Dashboard Layer
The old portfolio had two public dashboard links that are worth keeping. I am separating those original public links from the sanitized recreations below, because they prove different things.
Actual screenshot + public link
Looker Studio Sales Dashboard
Public dashboard from the old portfolio. Stronger for BI/systems roles because it shows the reporting surface directly.
Actual screenshot + public link
DIMO Protocol Dune Dashboard
Public protocol dashboard from the old portfolio. Useful signal for Web3, treasury, token, and on-chain data conversations.
Sanitized Dashboard Recreations
I am not publishing private operating dashboards. These recreated views show the dashboard families I worked around: finance, growth/product, and ops. The point is to show how I think about visibility, definitions, and decision cadence without exposing company data.
Executive Finance
Cash, runway, burn, close status, revenue, and decision notes.
Growth / Product
Connected vehicles, app conversion, retention, attribution, lifecycle funnel.
Ops / Fulfillment
Inventory, shipping cost, fulfillment flow, support signals, tax/logistics blockers.
Why recreated?
Because raw dashboards can expose user metrics, vendor data, wallet/treasury details, and internal performance. I can walk through the real logic live; the public version is intentionally sanitized.
Proof Walkthrough
The strongest version of the proof is a short screen-share where I walk through one artifact and explain what I would do, what I would ignore, and where the risk usually hides.
Planned format: 2-3 minutes, camera plus screen share, embedded here with Loom or an unlisted video link.
2-3 minute walkthrough
Use the role-specific artifact below, then explain the operating logic directly.
General startup finance
First 30 Days Finance Diagnostic. Best for founder-led Head of Finance roles.
Controller / accounting depth
Tax / Logistics Correction. Best for messy close, controls, and operating-accounting judgment.
Crypto / treasury
Crypto Accounting Controls. Best for wallet, exchange, token, FMV, and JE conversations.
Pick The Right CV
I keep separate CVs because different roles care about different signals. The Head of Finance version is the default unless the role is clearly Controller, FP&A, systems-heavy, or crypto-specific.
Head of Finance
Default for founder-led startup finance roles.
Senior Controller
For SMEs/startups needing close, controls, reconciliations, and audit/tax readiness.
Strategic Finance / FP&A
For SaaS, fintech, GTM, Finance & Strategy.
Finance Systems / AI FP&A
For CFO tools, BI-heavy finance, and automation.
Crypto Controller / Treasury
For Web3, digital assets, and treasury operations.
My Proof Standard
Trust is mostly about making it easy to distinguish evidence, scope, and limits. I use the same standard here that I use in finance work.
01
Claims have a source
CV outcomes point to artifacts, tested systems, public dashboards, or redacted operational evidence.
02
Private data stays private
Raw company records, credentials, payroll, customer data, and transaction detail are excluded or redacted.
03
Limits stay visible
I label review tools as review tools, release snapshots as snapshots, and undeployed work as undeployed.
04
Verification is dated
Build and test statements include the verification date so they do not quietly become permanent claims.
Contact
I'm based in Argentina, work US-compatible hours, and can work as a contractor or through EOR. I don't need US visa sponsorship.