Case study 01 · M&B Consortium Corp · Decatur, Illinois
We are our own first client. Before GoldenHammer installed anything for anyone else, M&B Consortium ran its entity work, finance, tax research, and daily operations on the same setup. This is what it replaced, what it did not, and what carried into the install kit we now sell.
M&B Consortium Corp is a family-owned Illinois holding company with four owners and a handful of operating subsidiaries. The people who own it also hold other jobs, and for most of the year the company's administration has to fit into the hours left over after those jobs are done.
The work does not shrink to fit. Entity filings, real estate and tax matters across two states, finance reconciliation, and the meeting agendas and minutes a multi-owner corporation is required to keep were all landing on one person. The choice was a part-time administrator or a system, and we built the system.
Everything below was built between other work, by one operator, on tools any small business can subscribe to. None of it required a developer on staff, and all of it is documented well enough that someone else could run it, which was the point.
Six systems, in roughly the order they arrived. Each one started as a specific pain and ended as a written procedure.
VICKY is a documented set of AI-run workflows for the paperwork a small corporation generates: entity formation packages, board and owner meeting agendas, resolutions, and the standing records that have to exist whether or not anyone enjoys writing them. Version 1.0 exists as an operating manual so that the system survives the operator, which is the difference between a tool and a habit.
VICKY reads the company's accounts through the Monarch finance platform's Python interface, so reconciliation and reporting start from live numbers rather than a spreadsheet someone remembered to export. Credentials are rotated on a schedule, and the integration sits behind a set of hardening checks that have to pass before it is allowed to run unattended.
Illinois estate planning material, tax strategy references, and our own entity documents are ingested into a searchable corpus, so questions get answered against the actual sources with citations before they go to the CPA or the attorney. The corpus makes the question faster and better prepared. The professionals still own the answer, and we have never found a reason to change that.
Tasks are captured into a shared list from a sentence spoken into a phone, which matters more than it sounds when the operator is in a tractor cab. A work journal is written automatically into the calendar at the end of each session. Standing instructions tell every tool how we want answers, including an explicit rule to push back when we are wrong.
ATHENA is an agent running on a small NVIDIA Jetson board with a sensitivity gate, a request router, a fact store, and a messaging front end. It is not a product and it is not for sale. It is where we learn what agents actually do when nobody is watching, before we would ever put one near a client's books.
When people in our own company needed job-specific study material, we built and hosted it ourselves: a gas control operations course, an Illinois food-safety certification guide, a grain cart operator's manual, two personal AI manuals, and a certification study plan, with read-aloud and reading accommodations built in. Same tooling as the rest, and a turnaround measured in afternoons rather than weeks. That work became the custom academies we now build for clients.
Entity formation packages that were drafted by hand or paid out to a filing service are now generated from VICKY and reviewed by the attorney. Monthly reconciliation that started from exported spreadsheets now starts from live numbers pulled from the finance platform. Tax and entity questions that used to be researched from scratch are answered against the corpus with citations and sent to the CPA already framed.
Meeting agendas and minutes that were written whenever someone found the time are drafted from the running task list before each meeting. Session notes that lived in one person's head are written to the calendar automatically at the end of every working session. Each of those used to cost the operator an evening. Each now costs a review.
The CPA. The attorney. The owners' judgment about which entity does what and why. Every one of those became faster to reach and better prepared, and none of them became cheaper to skip. Early on we let the tools carry more of the substance than they should have, and we pulled it back. That experience is why the rule sits at the top of every proposal we write.
It also did not replace the need for someone to notice when a tool changes. Vendors ship monthly. Running a business on AI includes a standing habit of checking what drifted, which is exactly the job the operator retainer exists to do for clients.
Write the memory structure first: people, entities, properties, vendors. Everything else gets easier once the tools stop guessing which office "the Brown office" refers to. Give every tool standing instructions with a pushback clause, because the default setting is agreement and agreement is expensive.
Build inside the owner's own accounts, wire the tools into the calendar and inbox the owner already checks, and keep an operating manual. VICKY 1.0 exists as a document because a system nobody else can run is not a system, it is a person.
Start with the half-day assessment. You leave with a map of your paperwork and a fixed quote, and we will tell you plainly if an install would not pay for itself.