DiliPilot
I took an acquisition-diligence problem from research and product definition into a working demonstration: organize the seller’s records, make proposed adjustments reviewable, and show how financing assumptions change the picture.
My role
Co-Founder, Product & Strategy. Built the first MVP solo. I own product and customers. I lead product direction, research, financial-review workflow design, and GTM coordination.
Status
Pre-revenue · Synthetic demo
Capabilities
Financial analysis · Product ownership · Workflow design
The problem
A seller package can contain financial statements, tax records, exports, and explanations that do not immediately agree. The useful work is not simply producing a summary. It is deciding which figures tie, which adjustments have support, and which questions remain unresolved.
What I worked on
I designed the review flow from document intake through financial spreading, reconciliation, earnings adjustments, and financing scenarios. The aim was to make the analysis inspectable: keep source references close to figures, distinguish records from assumptions, and surface missing support instead of burying it in prose.
Decisions and tradeoffs
Narrow the output
Early customer discovery showed that the product was trying to serve too many users. I narrowed the workflow around a source-linked financial package that a reviewer can inspect.
Keep AI away from financial math
Models can extract, classify, and propose. Deterministic code performs the calculations, and a human approves work that moves into a report.
Draw hard lines on claims
The product does not claim lender approval, CPA verification, guaranteed financing, or replacement of a formal quality of earnings report.
What I learned
- About 15 pitch-first LinkedIn messages produced no replies. A question focused on who cleans up seller financials before they reach a lender received a reply within 30 minutes on day one.
- I shifted outreach toward SBA lender-side roles for research and product feedback after that change in response quality.
Evidence and scope
A public synthetic demonstration and a developed diligence workflow. DiliPilot is pre-revenue; the portfolio does not present the demonstration as evidence of paying customers, completed live engagements, or validated adoption.
What this shows
My contribution connects financial analysis, product decisions, coordination, and practical implementation. It is an example of taking a broad business problem and defining a specific, reviewable output.
See the work
