How I work

I put the help into the work you already do. People still approve the decisions that matter, especially anything that changes the books.

How an engagement actually runs

Same path whether it’s books help, job-flow cleanup, or something custom for your shop.

Discover

I start with a short call about what’s broken, what you’ve tried, and what a written job would look like. Glimpse walks you through the first part of that conversation.
Put it in writing

A simple engagement letter names who’s responsible, how I handle your data, and what “good” looks like in your words.
Write down the job

A written list names what I build, what you pay, and when it is done. You know the finish line before I dig in.
Deliver

I build it, plug it into your real tools, train your people, and stay long enough that it survives a real workday. You own everything I build. Ongoing support is optional.

Everything else can flex for your shop.

Bigger jobs get more homework: how your trade works and where time and money leak. Smaller jobs stay lean. Both stay written.

I wire the workflow and leave the crew something they can run on their own, so the hours they spent retyping go back into billable work.

The software can draft, suggest, and sort. A person still approves the ledger, the filings, and the contract.

The people who signed the agreement make the go-live calls. See who works with you. Weighing a weekend build first? Read the Grok Bot field note.

I use your data only for the job you hired me to do.
Only the people on the job can open the files.
The books, the job system, and the official record stay in the shop’s tools.
I use tighter setups when the job calls for them. The agreement says the work product is yours.

I will tell you what a written engagement would look like.