A shop that size already runs good tools. QuickBooks holds the money. Field software schedules the crews. What neither shows the owner is the layer in between: what every job actually made, which invoices are stuck waiting for a signature, and who owes what for how long. That layer is usually a person working nights, or a hire the shop is not sure it can justify. RunHank is that layer as software.
RunHank reads QuickBooks and the field software, keeps one honest set of numbers, walks every invoice from draft through approval to created in QuickBooks and emailed, and keeps a collections list a person works with a log of every contact and every promise. It is deliberately not an all-in-one platform: dispatch, scheduling, and the truck-cab app belong to the field software the crews already use. RunHank ships narrow and deep on the back office.
The disciplines
The platform handles money records, so a few rules are built into the architecture rather than promised in copy. Nothing moves money on its own; a person approves anything that changes an invoice, contacts a customer, or records a payment. Every action lands in an append-only audit log. Each company's data is isolated at the database layer, enforced by the database itself and tested on every code change. And the data belongs to the shop: exportable at any time, deleted on a stated timeline if the engagement ends. The security page covers these in more detail.
The company
RunHank is a product of Division1 Capital LLC. It is built the way the guides on this site recommend running a shop: narrow scope, honest numbers, and nothing shipped that cannot be stood behind. Engagements start with a demo on real numbers, onboarding is included and measured in days, and pricing is part of that conversation; the arithmetic it competes against is worked out on the math page.