A pitch artifact meant to show how I think: research the market signal, pick a real accounting target, and build around blocked API access instead of waiting for perfect conditions.
Demo
This walkthrough shows the research path, the dummy Slash API, the sync flow, and the Odoo-side validation.
Problem
The integration replaces a manual accounting handoff with an automated path from card spend to expense records.
The workflow is simple: turn Slash-style card spend into accounting-ready records without CSV exports, manual re-entry, or a broken audit trail.
The target came from research, not convenience: conversations pointed to vertical expansion, healthcare stood out, and Slash’s own healthcare accounting content led me to Odoo after ruling out QuickBooks as already covered by a native integration.
What I built
Research depth, implementation judgment, and bias for action.
I built a Slash-to-Odoo sync that replaces a manual CSV handoff with an automated path: fetch transactions, map expenses, create Odoo records, and write a trace back to Slash.
The constraint was access. With no sandbox key, I used public docs and SDK shape to recreate enough of the Slash API to keep building.
Docs, SDKs, hiring signals, and market research narrowed the prototype into one workflow worth building.
AI helped me move faster, while the product judgment stayed grounded in the workflow.
I recreated enough of the transaction and note-update surface to keep implementation unblocked.
Odoo came from the healthcare accounting research path, then gave me a real system to test locally.
The sync is conservative by design: safe to rerun and hard to duplicate.
The prototype also clarified what the public API does not expose yet.
How it works
Transaction data in, Odoo expense out, source trace written back.
1. Simulate Slash
Public docs and SDK types filled the sandbox gap.
2. Create the expense
Transactions are filtered, mapped, deduped, and created in Odoo.
3. Close the loop
The Odoo record ID is written back as the available sync trail.
Selected proof points
From sales calls and architecture to shipped systems and measurable fintech scale.
$768M+ in annual Ramp bill pay and card spend across 15 customers.$768M+
Annual Ramp bill pay + card spend supported through integrations I architected and delivered.
Across 15 customer deployments.
15 Customers
Built and launched integrations across diverse financial workflows, customer environments, and operational constraints.
0 -> 1 Ownership
Took projects from sales call and technical scoping through architecture, implementation, and production delivery.
Business -> Build
Translated customer pain into architecture, developer execution, and shipped client-facing systems.
Contact
This draft keeps the contact surface intentionally light.
If this project resonates, I would love to walk through the research path and prototype decisions.