Audit the drag
Statement assembly, production summaries, meeting follow up, file hunts, and status chasing.
Find the repeated handwork.The Buyback Principle, applied to your practice
The systems are in place. The hours are still manual. Power Automate prepares the work inside your Microsoft 365 so your people can spend more time on clients, cases, and relationships.
What you are actually buying
Dan Martell's Buyback Loop is simple: audit the work, transfer what does not need your unique ability, then deliberately fill the recovered time. Here is that loop for this round table.
Statement assembly, production summaries, meeting follow up, file hunts, and status chasing.
Find the repeated handwork.A flow reads your own sources, prepares the draft, and stops for a person inside your tenant.
Move the task, not the judgment.More households ready for review, faster case progress, stronger follow through, and more client conversations.
Reinvest the hour where it compounds.The book's 10–80–10 delegation pattern, adapted as an operating model, not a promised automation percentage.
The DRIP Matrix
Every task has two costs: the time it consumes and the energy it takes. The first workflows should target repeatable work that drains both.
Mentoring, learning, and improving the client experience.
Schedule and protectAdvice, plan design, trust, referrals, and relationships.
Keep this humanFile hunts, tracker updates, reminders, and data assembly.
Automate firstRecurring analysis packaging and complex prep assembly.
Standardize and assistFor advisors
Hunting context · packaging data · chasing status
Planning judgment · client trust · referrals · leadership
For the support bench
Copying fields · building summaries · manual reminders
Review readiness · case progress · proactive client service
Run it on your numbers
The book's rule of thumb starts with your Effective Hourly Rate: annual economic value divided by 2,000. One quarter of that is the Buyback Rate.
Uses 133 working days, a $45 loaded support rate, and assumes the workflows prepare 80% of the modeled assembly time. Change the sliders; nothing leaves this page.
Effective Hourly Rate
$300/hr$600.0K ÷ 2,000 hoursYour Buyback Rate
$75/hrEffective Hourly Rate ÷ 4$5.6Keach month
$7.5Kper staff seat
$202.0Kover three years
At these inputs, the selected stack’s highest modeled first year cost per hour is below your Buyback Rate. It clears the book’s first financial screen.
Capacity model, not a revenue or savings forecast. The working assumptions are confirmed against your own volume during the pilot.
The build
Phase 1 creates the governed pattern inside your tenant. Each later module switches on independently when its own access or approval is ready.
A working pilot, not a strategy deck. We map your approved sources, field names, and review rules; build and test the flows; then install and document them in your Microsoft environment. Typically live in 2–3 weeks after provisioning.
Phase 2 · Pick your stack
Typical rollout after each gate clears
These are build estimates, not fixed dates. Each module starts when its own requirement is ready, so the longest approval does not hold up the rest.
Deployment, licensing, and portability
The workflows are built with sample data, installed in your approved Microsoft environment, and connected to client controlled accounts only after your team authorizes access.
Live client records are not used unless you separately approve it.
Use a Power Platform solution where the client environment supports it.
Your team authorizes client controlled connections inside the tenant.
Draft output, access limits, and failure handling are checked.
Your team approves the release and receives a restore path.
Architecture map, connection matrix, configuration list, test record, release notes, and handoff guide.
A solution package is used when Dataverse and solution aware flows are available. Otherwise, the same approved logic is built directly in the client environment.
Production runs in your approved Microsoft environment using access your team can grant, limit, audit, and revoke.
What we need from you
Stated plainly
Built for this building
Buying back time never means buying away supervision. The flow prepares; your people retain the decision.
Microsoft 365 only. Your identity, data, and audit trail.
Nothing sends until a person reviews and sends it.
No writes into the CRM or any Northwestern Mutual system.
The pilot never places or executes a trade.
IT and compliance clear each later module before it starts.
Your service account, data, credentials, and revocable access.
Work uses a named vendor account with the minimum access your team approves. Actions remain in your audit trail, and sample data is used before a live client record is introduced.
Access is limited to the engagement and revocable by you.Drafts stay in your mailbox. Any index or tracker stays in your SharePoint or Excel, inside the retention and archiving your firm already applies to Microsoft 365.
No separate recordkeeping system is introduced.Your data, tenant, credentials, drafts, and documentation remain yours. Stanford Systems retains its reusable automation framework and licenses it to the practice during the active subscription.
A separately quoted perpetual conversion can make the use license permanent.The decision
The pilot does not promise fewer people. It gives the same people more room to carry the work that grows and protects the practice.
Then $3.5k/month for the license and managed care.
At the assumptions currently selected in the model.
The right to use the Stanford Systems automation framework for one practice, plus monitoring, fixes, minor iterations, updates, and a monthly view of the capacity prepared in your tenant. Each additional practice is $5,000 to activate and $1,250 per month.
The build is typically half at the start and half on delivery. The subscription begins at launch with a 12 month initial term. Microsoft, DocuSign, YCharts, and other platform licenses are separate.
Support and updates stop, vendor access is removed, and the use license expires at the end of the term. The practice keeps its data, records, drafts, and documentation, but must stop running the licensed automation unless it renews or purchases a separately quoted perpetual conversion.
The next step is simple
A contained pilot removes the assembly work while your people keep every decision, approval, and send. We sign a short engagement, your team provisions a named vendor account, and the first buyback loop begins.