Controller Software — Custom Built for Financial Ops, North County San Diego
I'm PJ, in Encinitas. I build custom software for controllers who are tired of duct-taping spreadsheets between their ERP, close checklist, and the reports the CFO actually wants.
Quick answer for controllers
- Yes, I build custom — not another SaaS subscription you have to fight IT to approve.
- Close cycle, reconciliations, variance reports, flux analysis — the boring stuff that eats your month.
- One text, real answer. Not a discovery call disguised as a sales pitch.
- Local North County San Diego — Encinitas / Solana Beach. Work with clients nationwide.
→ See what a financial ops build actually looks like
FAQ — what controllers actually ask me
Can you automate our month-end close without replacing NetSuite / Sage / our ERP?
Yes. I build layers that sit on top of what you already have. Pull data out, run the logic, push results back or into a report. Nothing gets ripped out.
We have reconciliations done in 40 Excel tabs. Can that become software?
That's the most common thing I build. Those tabs are a specification — they tell me exactly what the tool needs to do. Usually 2–4 weeks to a working version.
How do you handle audit trail and SOX concerns?
Every action logged, every change timestamped with user. I've built for teams that get audited by Big 4 — the audit trail requirements are baked in from day one, not bolted on.
What's the realistic cost vs. buying FloQast or BlackLine?
If you need the full platform, buy the platform. If you need three specific workflows fixed, custom is often cheaper in year one and you own it. I'll tell you honestly which fits.
Who maintains it after you build it?
Me, if you want. Or your IT team — I write clean code with docs. No lock-in. I've had clients take builds fully in-house after a year.
Do you work with our CFO / FP&A team too, or just controllers?
Both. A lot of my work bridges controller-owned data (the true numbers) with FP&A-owned models (what-ifs). That handoff is usually where things break.
Useful things to know before we talk
Start with the painful spreadsheet
The one that takes 6 hours every month and someone always breaks. That's your highest-ROI build. Not the fancy dashboard the CFO wants.
Don't automate a broken process
If the reconciliation logic is wrong, software just makes it wrong faster. We fix the logic first, then automate.
Data out of the ERP is usually the easy part
The hard part is the exceptions — the manual adjustments, the one-off entries. Map those first.
Flux analysis can be automated
Variance commentary is 80% pattern-matching on the GL. Real software can draft it; your team approves and refines.
Intercompany is not as hard as vendors claim
It's mostly matching + FX + timing. Custom tools handle it cleanly without a six-figure platform.
Your close checklist is a workflow engine
Turn it into software with dependencies, owners, and status. Suddenly the close runs itself and you see bottlenecks in real time.
Straight from PJ
I've spent enough time inside finance teams to know a controller doesn't need another demo. You need one honest conversation with someone who codes. Text me or check my background.
View LinkedIn →One text. Real answer.
Tell me the spreadsheet that's killing your close. I'll tell you if it's a 2-week build, a 2-month build, or if you should just buy something off the shelf.
📱 Text 858-461-8054