WealthLens is software for mortgage advisors. The unusual part is the company behind the product: a solo founder plus a digital workforce that handles onboarding, leads, support, marketing, and operations, twenty four hours a day.
Imagine a small company. Now imagine each role is filled by a software specialist that never takes a day off.

Screens new leads from ads or web forms. Quick filter: real loan officer, target customer, worth talking to.

Answers new leads in under a minute. Asks four qualifying questions. Routes the keepers to the calendar.

Welcomes new paying customers with a 30-day feature tour, shares a new feature every week, and reaches out when someone stops using the product.

Thanks customers who refer other customers. Sends a weekly recap with real numbers.

Customer service. Answers billing and account questions by email, teaches features from a how-to library, and picks up the phone when a lead calls in.

The manager. Reads everything, posts a daily briefing. You can chat with her: “Dana, ask Max to draft an email about X.”

Runs the CRM. Once a week, proposes new initiatives the team should work on next.

Watches how customers use the product. Flags anyone going dark before they cancel.

The on-call engineer. Diagnoses problems at 3am, suppresses noise, only wakes the human if it really matters.

Tracks the bills. Knows where every dollar goes across providers.

Keeps the email list clean. Checks every message before it goes out, so the team never emails anyone who bounced, complained, or unsubscribed.

The quality inspector. Reads the product’s AI conversations after the fact and catches slip-ups nobody reported. An AI whose whole job is auditing the other AIs.

Writes ad copy, social posts, email drafts. Every piece runs through human approval before going live.

Generates the images that go with what Max writes. Makes two candidates, picks the better one.
“A normal AI tool is one chatbot trying to do everything. This is a workforce of fourteen specialists with one boss and a shared notebook.”
Three things separate this from a typical AI tool.
When Larry qualifies a lead, Pete updates the CRM. When Alex notices a customer going quiet, Nadia sends a check-in. They share one notebook, so nothing falls through.
Dana is the supervisor. She reads the notebook, posts a daily briefing, and you can talk to her like a person. She figures out who should do what.
Once a week, Pete writes up three to five things the team should work on. The human reviews, approves the good ones, and the team gets to work.
Every project finished is logged with what changed and what was learned. The next session reads what happened last time. Institutional memory, in software.
When a person corrects something an agent wrote, that correction is saved and the agent does better next time. It learns from feedback, and a human still approves every change before it goes live.
The thing that ties the team together, that one place every agent reads and writes, is an idea called Open Brain. It’s an open-source pattern by an engineer named Nate B. Jones: instead of every AI tool having its own separate memory, you give them one shared database with vector search and a common protocol, and they all plug into it.
We took that core idea and built it out for a real SaaS company. The agents don’t just remember things individually. They share an event log, a workstream tracker, an approval queue, and a vector memory of past conversations. When Larry talks to a new lead, Pete sees it. When Alex spots a quiet customer, Nadia knows. That’s Open Brain, adapted.
Source pattern: github.com/NateBJones-Projects/OB1
Some of this is live, some is on the way. The faded items below are scoped but not built yet.
Today she lives in Slack. Soon: a chat widget on the WealthLens dashboard so customers and the human can talk to her there too.
Pete is the first. Mike, Alex, and Edith are next. Eventually the whole team is proposing initiatives weekly.
Today the team posts updates to Slack. Soon the WealthLens dashboard itself will be the home base, with phone-style notifications.
Imagine asking your dashboard “how are my customers doing this week?” and getting a real spoken answer.
Today, agents pass work to each other through CRM tags. Soon: a first-class log of every cross-agent handoff, easy to audit.
The chat widget gives suggestions today. The next step is testing it against a graded set so it can run on auto-pilot.
Two more docs sit behind a quick request form. I review every request myself and reply within a day.
Architecture, stack, agent inventory, coordination model. For engineers who want the technical picture.
Read itEnd-to-end picture. Origin, substrate, agents, coordination, novel patterns, where it’s heading. The full story.
The hard-won lessons behind a live multi-agent fleet: what to automate, what to gate, and the trade-offs that aren’t obvious until you’ve run one.
A few quick details and I’ll send it your way personally.