Proof, not promises.
Before a lender can make a decision, someone has to gather the records, check the details, and assemble the paperwork. MARCUS prepares that work at B:Side Capital. Here is what was built, what the team reported, and what still belongs to a person.
The useful starting point is one handoff: records in several places become a prepared package a person can check.
A contractor preparing billing or a service firm assembling a client file may recognize that pattern. The records, rules, and approvals will differ. Your workflow needs its own baseline, tests, and business case; B:Side Capital’s results cannot establish yours.
Related-company deployment: Christopher Myers is Founder & Chairman of Main & Machine and CEO of B:Side Capital.
One prepared package. A person accountable for the decision.
Christopher Myers leads both B:Side Capital and Main & Machine. This related-company deployment gives us direct operating experience; it is not independent validation or a forecast for your business. The full system spans several departments. A standard sprint starts with one agreed workflow.
Prep ate the days.
B:Side Capital is a regulated SBA 504 and CDFI lender. Before anyone decides anything, someone gathers the documents, pulls the reports, and drafts the paperwork. The same steps, over and over, across seven departments. The team needed a controlled boundary around borrower documents and a record of how the system used them.
Fourteen agents, in-house.
We read roughly 840 of B:Side’s own process documents and built fourteen AI agents across seven departments. Borrower documents are processed locally; selected tasks can use external reasoning on filtered text. The system prepares work against B:Side’s procedures, with human approval for consequential actions.
A person signs off. Always.
MARCUS does the gathering, checking, and drafting, then hands finished work to a person who says yes, sends it back, or escalates. Staff still check the prepared work, correct errors, and resolve exceptions. Those steps count when evaluating the time a workflow actually returns. Judgment stays with the people accountable for it.
MARCUS: a private AI back office for a regulated lender
The brief was one line: take the prep off our people’s plate, without ever taking them out of control. Walk the whole build: the seven departments, the fourteen agents, and the four surfaces the team already uses.
Read the full teardown →Client work goes up the same way: verified, and signed off.
We publish a client story only when its figures are verified and the client signs off in writing. The figures below are B:Side Capital’s first-party reports, including estimates from initial workflow studies. They describe that operation and measurement window, not results promised to another business.
Estimated staff preparation hours returned during June–August 2026, calculated from B:Side’s initial workflow studies. This is operating capacity, not measured payroll savings.
Reported weekly use by week six, across a staff of 45 employees. The percentage is rounded; an exact active-user count is not published.
Borrower identifiers reported as sent to outside models during the measurement window. Filtering is required; detection is not guaranteed to be perfect.
Of consequential actions approved by a person during the reported window, before sending, filing, posting, or paying.
What might work in your operation? Describe one recurring task and get a free written first step. Your plan names what to investigate before deciding whether a build makes sense.
The guarantee: If a scoped workflow is not live in your operation within 90 days, we keep building at no charge until it is.
The credit: Your audit fee can be credited toward a sprint signed within 60 days, up to 25% of the sprint price.
We reply within 24 hours. A fixed quote follows an agreed scope, before paid work begins.
— Christopher Myers, Founder