When the work touches money, it has to be right.

I'm Rob Neville, CPA. I build the finance automations and customer systems small businesses run on — close and reporting, booking, payments, follow-up. Every system ships with the control, the owner, and the number it is supposed to improve.

Selected work

Three systems you can inspect

What shipped, and the numbers I stand behind. Client names are published only with permission; the numbers are real either way.

A close pipeline that refuses bad numbers

A multi-entity, international insurance company closed its books through a manual cycle: export the general ledger, convert currencies, stage, load, and hope nothing slipped. The hard part wasn't the automation. It was that the output feeds audited financials, so a fast pipeline that could load a wrong number would be worse than a slow one.

I replaced the cycle with a single command, then built the part that matters: a tie-out gate that blocks any load off by more than $10,000 per entity, and vendor classification where a person approves or rejects every new mapping before the system learns it.

The control: the pipeline stops itself. Bad loads are blocked, they don't wait for someone to notice. The company's name stays private; the figures were checked against its books.

A wellness practice, moved onto a real platform

A Greater Cincinnati wellness practice needed off its old website builder. I designed and built the new site, set up online booking across sixteen appointment types with the right payment rule for each, switched her payment processor, migrated her newsletter and subscriber list, and cut the domain over with no downtime.

She got a plain-language owner guide, her annual software spend went down, and the site now runs on a monthly care plan — hosting, upkeep, and email included.

A service site that became a revenue system

A healing-arts studio had a site that could describe her practice but couldn't sell anything. The new one books five appointment types with waivers and payment built in, signs members in with their own accounts, and sells a ten-session practice library that unlocks the moment a purchase clears — no manual handoff, no "check your email for a link."

Her newsletter moved platforms with an auto-sync from the website, old inquiries were pulled into the same follow-up workflow as new ones, and there are real purchases in production.

Also shipped: a new site for a 40-year gym serving 500+ monthly members — real gym-floor photography, and the vendor switch that moved its member system onto a modern platform. A practitioner site the owner edits and publishes herself. And RenewalGuard, a free vendor-contract audit that's live now, grown from an internal contract process that saved a company $30k+ in its first year; the subscription product is still in development.

The operator

I've run the work I now automate

I'm Rob Neville, a CPA in Cincinnati. I started at EY, spent 15 years in FP&A, and most recently led finance at a venture-backed tech company through $100M+ raises, board reporting, and close after close.

Then AI happened to me. I'm not a trained engineer; I'm a finance operator who got obsessed with the new AI tools and used them to learn to ship real software. Nights and weekends I built whatever was in front of me: software that ran a full season for a local baseball program, our wedding website, a pick'em league for friends, the dashboard my own week runs on.

Neville Ops is where that obsession meets the day-job judgment. I know what happens downstream when a number is wrong, because I've been the person it happened to.

More about me on LinkedIn

  • CPA, ex-EY. I know what evidence looks like, what has to tie, and what an auditor will ask.
  • 15 years in FP&A. I've run the close, the forecast, and the board pack myself, on deadline.
  • Finance leadership at scale. Review and consequence are familiar. I build for the day something breaks, and I say what breaks first.
  • I ship working software. You get the running system, the documentation, and the keys. A slide deck about the system is free elsewhere.

What I build

Three kinds of system

Close, reporting, and controls

Reconciliations, recurring journals, reporting packs, data pipelines, and the approval gates that keep them honest.

See: the close pipeline

Money-in and money-out

Booking, payments, invoicing, AP/AR, reminders, and the membership or customer handoffs that follow the money.

See: the platform move

Owner visibility and memory

Dashboards, cash scenarios, contract and renewal tracking, documented workflows, and a handoff you can actually run.

See: RenewalGuard

How engagements work

A decision sequence, in the open

  1. We map one workflow and put a number on it: the hours it eats and what those hours cost.
  2. I show you the build, the control, who owns it, and the estimated payback, in writing.
  3. You decide whether it's worth shipping. If the math doesn't work, the document says so.
  4. If it ships, I run it: monitored, maintained, and documented, including how to reverse it.

The first mapping session is free and the shortlist is yours to keep, whoever builds it. Everything I build stays in your accounts, under your logins.

No testimonials here yet, on purpose. Early engagements are still running, and I won't publish invented quotes or quote myself. References are available for serious conversations — ask, and I'll connect you with a client directly.

Start with one workflow.

Thirty minutes on how the work actually runs today. You get a shortlist of what's worth automating, with estimated hours and payback for each. It's free, and the shortlist is yours either way.

The button opens an email to me — that's the whole mechanism, no scheduler and no funnel. I reply within one business day. Greater Cincinnati and Northern Kentucky in person, anywhere remotely.