C
Client Master Plan

Ruben Cruz

Crulliance
Team: ~10 Since: ~2020 Last Updated: February 13, 2026

GPS

Trajectory
Execution phase fully underway. SOP V3 drafted and in final review — 15 steps across three phases, flow diagram, role assignments, escalation protocol, and Founder Snapshot integrated as recurring checkpoint. Pooja oriented via intro call (Feb 13) — she hasn't been through a single close yet, so the SOP is her primary guide. Weekly check-ins scheduled for next 5 weeks. Blueprint and project plan rebranded to Crulliance, aligned to SOP. Key correction from walkthrough interview (Feb 12): Pooja reviews every month, CPA advisors add quarterly strategic lens. Sariah removed from escalation entirely — Pooja sends via Liscio, CPA advisor approves. Team roster clarified with bookkeeper names and assignments. February close is 2 weeks out — first live test of the system.
Updated: February 13, 2026 (SOP V3 + Pooja intro + cross-document alignment)
Position Changed
SOP V3 drafted — 15 steps, three-phase continuous cycle (Active Close → Review & Delivery → Set Up Next Month). Pooja oriented but hasn't run a close yet. Weekly check-ins with Kathryn starting Feb 19. Blueprint and project plan rebranded to Crulliance light theme and cross-calibrated. Sariah removed from escalation — Pooja owns client communication via Liscio with CPA advisor approval. Bookkeeper roster confirmed: Sarah (20–25), Anas (20–25), Jheanifer (onboarding), Patty (2–3). Founder Snapshot designed as recurring checkpoint. February close = first live test. Still mid-tax-season.
Direction Consistent
80–90% of client financials delivered by promise date. 100% completion where Crulliance controls all variables. Visibility without involvement. Team ownership of processes. Repeatable systems that don't rely on Ruben. 40 new clients in 2026 with 100% retention. 95% existing client renewal. Sell the firm in 1–3 years. Wants to do more advisory and less compliance.
Speed Consistent
Maximum urgency maintained. Kathryn building at pace — SOP, blueprint, project plan all produced and aligned in one week. Pooja intro completed same day as walkthrough interview. February close deadline creating natural forcing function. No deceleration despite tax season pressure.
February 9, 2026
Position
Mid-tax-season. Books not ready for reviews. Month-end close improvised monthly — no defined workflow. Pooja onboarded and trained but has no operating system to run. Team absorbs client delays quietly with no protocol. Projects in Financial Cents not set up properly, workflow templates dated. Ruben mentally orchestrating everything. CEO memo process working (2 consecutive weeks). Committed to expanded $1,500/month Advisory OS implementation engagement as of 2-9-2026. Kathryn now working directly with Pooja.
Direction
80–90% of client financials delivered by promise date. 100% completion where Crulliance controls all variables. Visibility without involvement. Team ownership of processes. Repeatable systems that don't rely on Ruben. 40 new clients in 2026 with 100% retention. 95% existing client renewal. Sell the firm in 1–3 years. Wants to do more advisory and less compliance.
Speed
Ready to move immediately. Agreed to expanded engagement on the call — "Let's do it. I'm ready to swing for the fences." Wants February month-end as first live run. Pooja has capacity RIGHT NOW. Tax season compressing bandwidth but urgency at maximum — "I just want to hit pause on everything and figure things out." Every month without the system compounds.
February 2, 2026
Position
Growing rapidly, bringing on new clients while training and hiring simultaneously. Book is closed personally — not taking new clients. New Accounting Manager (Pooja) started but hasn't fully taken ownership yet. SOPs nearly complete. Two AI processes deployed (CEO Memo, Constraint Identifier). Team is stretched — bookkeepers at capacity, standardization still in progress.
Direction
40 new clients in 2026 with 100% retention. 95% retention of existing clients. Goal to sell the firm in 1-3 years. Wants to run the business more efficiently with less dependency on Ruben. Wants to do more advisory and less compliance.
Speed
Wants to go fast — doesn't want to wait until October to figure things out. Concerned about losing good clients or prospects and team turnover. Open to accelerated deployment through Advisory OS.
January 26, 2026
Position
In tax season, wrapping up 2025 books for Crulliance. SOPs in progress but not fully installed. Monday meetings going over time. Team growing. Still reactive and doing admin work that should be systematized.
Direction
40 new clients in 2026, 100% retention of new clients, 95% retention of existing clients. Goal to sell the firm in 1-3 years.
Speed
Feeling reactive, trying to catch up. Bandwidth constrained during tax season. Recognizes need to solve constraints faster before they compound.

Weekly Rhythm

Friday
Constraint brief arrives from Ruben
Read and note what to probe Monday. No matrix update yet — brief is prep, not input.
Monday
Session with Ruben
Informed by brief + master plan. After session: transcript + brief → constraint priority matrix → master plan update.
Wednesday
Check-in with Pooja
Calibrate on SOP execution, surface what she's seeing live. Update master plan if anything shifted.
Between Sessions
Build deliverables
SOPs, templates, workflow configurations, whatever the current build requires. Deploy to Pooja for live testing.

Recurring Themes

Ruben as the Bottleneck — Now a Formal Constraint Updated Evidence
Elevated from theme to formal constraint (C9) in the updated matrix. The most persistent pattern across every data source. Ruben is reviewer of last resort, blocker remover, admin worker, mental orchestrator. In the 2-9 session: "I just want to hit pause on everything" and "I always feel like we're treading water." The matrix classifies C9 as downstream of C1, C2, C3, and C4 — meaning it resolves progressively as upstream systems deploy. Not solvable directly. Track as leading indicator of system effectiveness. His signing the expanded engagement is the first concrete action to transfer operational load to a system.
Matrix C9 (formal) GPS Position × 3 Quotes × 5 All sessions
Right People, Lagging Systems Updated Evidence
System now being built. Pooja is the clearest instance — she has the skills and capacity but had no system to run. As of Feb 13, the SOP V3 gives her that system. Weekly check-ins with Kathryn start Feb 19. The expanded engagement is the mechanism — Kathryn builds the system directly with Pooja. First live test: February close. The reusable system template means the next hire comes with a playbook from day one.
Matrix C1 (primary) Matrix Pattern 🔁 × 3 Constraint Briefs × 2 Feb 13 Pooja Intro Feb 9 Session
Month-End Close as Systemic Failure Updated Evidence
System designed. SOP V3 drafted and in final review. Updated from 7 to 9 constraints in the matrix, all in Operational Systems. C2 is co-primary with C1. The walkthrough interview (Feb 12) produced the source transcript — Ruben walked through every step, tag, escalation path, and deliverable. SOP V3 defines the three-phase continuous cycle: Active Close (Day 1→7-8), Review & Delivery (7-8→15th), Set Up Next Month (15th→EOM). February close is the first live test.
Matrix 9/9 Operational Systems Constraint Briefs × 2 Feb 12 Walkthrough Feb 13 SOP V3 All sessions
Single Capability — Same Root Cause — Everything Is Operational Systems Updated
Updated from 7/7 to 9/9. Two new constraints surfaced in the 2-9 session (C4: Financial Cents Workflows, C8: Bookkeeper Capacity) and one elevated from theme (C9: Ruben as Bottleneck). All remain in Operational Systems. Zero constraints in any other capability category. This confirms the engagement is a single-track solve. Once the Operational Systems root cause is resolved, the next category to surface will likely be Pipeline Infrastructure (40-client goal) or Visibility Engine (95% renewals).
Matrix Pattern: 📦 Same Root Cause Matrix All 9 Constraints GPS Direction
Financial Cents as Infrastructure Gap New Theme Detected
Newly surfaced in the 2-9 session. Ruben flagged it as a "big one" — projects not set up properly in Financial Cents, workflow templates dated, assignees wrong for new team structure. "What is not front and center, nobody knows about." The matrix flags C4 as needing to be solved together with C3 (Client Accountability Protocol) — the data layer and communication layer amplify each other. This is the infrastructure foundation that C1, C2, and C3 all depend on. Needs investigation before building the month-end OS on top of it.
Matrix C4 (new) Feb 9 Session ↔️ Solve Together with C3
Simplify Instinct — Right Direction, Wrong Target
Ruben's instinct to simplify is sound: "How do we stop adding and just maybe subtracting?" But what he subtracts matters. The risk is cutting client-facing visibility when the real move is subtracting internal production effort. The expanded engagement channels this instinct correctly — Kathryn builds the system, Pooja runs it, Ruben reads the snapshot. This is subtraction of Ruben's effort, not client value.
Quotes × 2 GPS Direction Subtract/Add Framework Feb 2

Relationship

Entry Point
Your Scalable Offer Suite
Duration
Active since 2025
Meeting Cadence
Weekly Mondays
Communication Style
Direct, action-oriented

Current Engagement

Active Initiatives
Accounting Manager Operating System
Tier 1 · In Progress · Build 1 SOP V3 in final review. Blueprint + project plan aligned. Pooja oriented. Feb close = first live test.
Project Plan ↗ Client Blueprint ↗

Seeds Planted

Accounting Manager Operating System Implementation
Six-month engagement to build SOPs, founder snapshots, client communication templates, and onboarding procedures. Working directly with Pooja on implementation. $1,500/month (half standard rate). Resolves or reduces 5+ of 9 constraints.
Active
Next: Deploy SOP V3 with Pooja. First live test: February close (March 1 start). Weekly check-ins begin Feb 19.
Project Plan ↗ Client Blueprint ↗
Client Roadmap Visualizers
Visual roadmaps showing clients where they are in accounting, tax, and advisory cycles. Ruben sees this as a "want" after operational "needs" are met.
Seed
Next: Revisit after core operational constraints are resolved
Sales Conversation AI Agent
Record Nick's sales calls, feed transcript to agent that extracts proposals, work instructions, and client setup information.
Seed
Next: Build after core operational systems are established

Constraints Diagnosed

Source: Constraint Priority Matrix — Feb 9, 2026 (Updated)
⬆️ Upstream
⬇️ Downstream
🔁 Recurring
📈 Escalating
📦 Same Root Cause
↔️ Solve Together
⬆️ Upstream · Operational Systems · Tier 1
Active Solve In Progress
C1 — Accounting Manager Operating System Not Defined
SOP V3 drafted — 15 steps, three-phase continuous cycle, role assignments, escalation protocol, Founder Snapshot integrated. Pooja oriented (Feb 13 intro call) but hasn't run a close yet. Weekly check-ins scheduled. Blueprint and project plan aligned. February close = first live test. Solving this resolves or reduces C5, C7, C9.
Blocks: All Direction goals
🔁 Recurring 📈 Escalating 📦 Same Root Cause 9/9
Project Plan ↗ Client Blueprint ↗
⬆️ Upstream · Operational Systems · Tier 1
In Progress
C2 — Month-End Close Process Not Designed
Co-primary with C1. SOP V3 defines three-phase continuous cycle: Active Close (Day 1→7-8), Review & Delivery (Day 7-8→15th), Set Up Next Month (15th→EOM). 80% of 55–60 clients submitted by Day 7–8. Pooja reviews every month; CPA advisors add quarterly strategic lens. February close = first live run.
Blocks: 80–90% on-time delivery, 95% renewals
🔁 Monthly 📈 Escalating
⬆️ Upstream · Operational Systems · Tier 1
↔️ Solve Together C4 Open
C3 — Client Accountability Protocol Missing
Team absorbs delays silently. No consequences for clients. Pooja sends delay notifications via Liscio, CPA advisor approves wording. Should be solved together with C4 — accountability needs project data to reference.
Blocks: 80–90% on-time delivery, team ownership
📈 Escalating
⬆️ Upstream · Operational Systems · Tier 1
↔️ Solve Together C3 Open
C4 — Financial Cents Workflow Configuration Outdated
Projects not set up properly, assignees wrong, templates dated. "What is not front and center, nobody knows about." Infrastructure that C1, C2, C3 depend on. First surfaced 2-9 session.
Blocks: Team ownership, visibility, 100% on controlled variables
⬇️ Downstream of C1 · Operational Systems · Tier 2
Designed
C5 — Founder Visibility Gap (No Reporting Snapshot)
Founder Snapshot designed and integrated into SOP as recurring checkpoint spanning all three phases. Pooja produces weekly during close — pace toward 80% target, delayed clients with plans, items needing Ruben's attention. V1 is manual; V2 (Build 4) upgrades to structured data from Financial Cents. Questions for Ruben: what level of detail, every client or just exceptions.
⬆️ Upstream (separate) · Operational Systems · Tier 3 — Queue
Open
C6 — New Client Onboarding → Close Readiness Gap
Every new client = potential surprise on first close. Escalating as pipeline delivers. Queue after C1/C2/C3/C4 deployed.
📈 Escalating
⬇️ Downstream of C1 · Operational Systems · Tier 4 — May Self-Resolve
In Progress via C1
C7 — Review Ownership Fragmentation
Corrected: Pooja reviews every month — this is her core responsibility. CPA advisors (Ruben, Kevin) add a quarterly strategic lens (tax opportunities, planning implications). Both reviews happen on quarter months. Fragmentation resolves as Pooja becomes the consistent operational reviewer.
⬇️ Downstream (partially of C2) · Operational Systems · Tier 4 — May Self-Resolve
Open
C8 — Bookkeeper Capacity
~15 clients per bookkeeper sweet spot. Currently stretched. Solving C2 may recapture enough capacity to delay or right-size a new hire. Reassess after February close.
⬇️ Downstream of C1, C2, C3, C4 · Operational Systems · Tier 4 — Will Self-Resolve
Open
C9 — Ruben as Operational Bottleneck
The master symptom. Resolves progressively as upstream systems deploy. Not solvable directly. Track as leading indicator.
🔁 Recurring 📈 Escalating
✅ Solved Constraints
Meeting Structure / Async Communication
Solved: CEO Memo process (ChatGPT voice → Slack) · Feb 2, 2026 · Holding — 2 consecutive weeks, team engaged
Constraint Identifier Process
Solved: ChatGPT project, Friday voice ritual · Feb 2, 2026 · Holding — 2 consecutive weeks
Daily Report Template / Time Entry
Solved: New template, full team adoption · Feb 2, 2026 · Holding
Matrix Insight
9 active constraints + 3 solved. All 9 in Operational Systems — one missing system, nine expressions. Highest-leverage move: solve C1+C2 (co-primary), which resolves or reduces 5 of 9. Feb 13 status: C1+C2 SOP V3 drafted and in final review. C3 escalation protocol designed (Pooja sends, CPA approves). C5 Founder Snapshot designed and integrated into SOP. C7 review ownership clarified in SOP. Linked pair C3 ↔️ C4 confirmed — solve together, combined build planned. Three solved constraints holding.

Recommendations

Accounting Manager Operating System — Full Design & Deploy
Linked: Matrix C1–C5, C7, C9 · Highest-leverage intervention
Accepted — Engagement Signed
Implement three-phase month-end rhythm (Active Close, Review & Delivery, Set Up Next Month) with Pooja owning the process
Linked: C1 + C2 · SOP V3 drafted, in final review
In Progress
Create weekly Founder Snapshot: pace toward goal, delayed clients with notes, game plans
Linked: C5 · Designed and integrated into SOP V3 as recurring checkpoint
Designed
Build pre-approved client communication templates — Pooja sends via Liscio, CPA advisor approves wording
Linked: C3 · Escalation protocol designed in SOP V3. Templates = Build 3 deliverable.
Protocol Designed
Set success metric: 80% of client financials by promise date (working toward 90%), 100% for controlled variables
Linked: C1 + C2 · Build tracking into Founder Snapshot
Accepted
Examine vetting/prospecting process for clients who consistently don't provide required documents
Linked: C3 upstream · Revisit after month-end systems in place
Suggested
Restructure Monday meeting: pre-record announcements in Friday CEO memo
Linked: Meeting Structure
Implemented
Weekly CEO memo via ChatGPT project with voice input, posted to Slack on Fridays
Linked: Meeting Structure, Team Communication
Implemented
Weekly constraint identifier via ChatGPT project with voice input
Linked: Coaching Effectiveness
Implemented
Use running bank balances instead of waiting for statements (except quarter-end)
Linked: C2
Suggested
Record all sales conversations and use AI agent to extract proposals
Linked: Sales Documentation Gap
Suggested
Structure tax team meetings as 30-min blocks: 15 min team updates + 15 min Q&A
Linked: Capacity
Implemented

Key Quotes

"I just want to hit pause on everything and be like, guys, like, no new clients. Let's just like, we gotta figure things out to get things better. Like, there's no reason why people have to ask where things are at."
Expressing frustration about lack of systems visibility — February 9, 2026
"I always feel like we're treading water."
Describing the current state of operations — February 9, 2026
"Let's do it. I mean, that's, that's, I'm ready to swing for the fences."
Agreeing to the expanded engagement — February 9, 2026
"How do we stop adding and just maybe subtracting? Because what we're finding is we're getting the wins in certain areas, and some of this other stuff is getting in the way with no wins."
On simplifying and focusing — February 2, 2026
"These things that I talk about have to get buttoned up, because my book is closed... it's just running this business that's where I need to be spending a lot of time."
On priorities — February 2, 2026
"It feels doable, which is very important... It's something that I know that I could consistently do week over week."
After completing the CEO memo process test — February 2, 2026
"My goal is to sell the firm in 1, 2, 3 years. We'll see how that goes."
On exit timeline — January 26, 2026
"My real concern is like creating the space to be able to, like, review it and get the value out of it. I feel like everything is still reactive."
On the scorecard — January 26, 2026
"Sometimes I feel that way. I'm like, are we just wasting our time?"
On the Monday meeting structure — January 26, 2026
"I do admin work and try to figure this out. I'm like, Oh man, I'm tired."
On manual work combing through client lists — January 26, 2026

Latest Wins

SOP V3 drafted — full month-end close operating system
15 steps, three-phase continuous cycle, flow diagram, role assignments, escalation protocol, Founder Snapshot integrated. Built from source interview. Ready for Ruben's review.
February 13, 2026
Working relationship established with Pooja
Intro call completed. Weekly check-ins scheduled for 5 weeks starting Feb 19. Pooja oriented on the engagement and her central role in the system.
February 13, 2026
All engagement documents cross-calibrated
Blueprint, project plan, SOP, and client reference data aligned on phase names, team roster, role assignments, and Crulliance branding. Single source of truth across all deliverables.
February 13, 2026
Full month-end process documented from source
Walkthrough interview with Ruben produced comprehensive transcript — every step, tool, tag, escalation path, and team assignment captured directly from the person running it.
February 12, 2026
Committed to expanded systems implementation engagement
Agreed to six-month commitment at $1,500/month for hands-on systems implementation. Significant investment in building scalable operations.
February 9, 2026
CEO Memo: 2 consecutive weeks completed
Successfully completed Constraint Identifier and CEO memo for two weeks in a row, proving the process is sustainable.
February 9, 2026
Team meetings more productive
Removed company announcements and policy updates from meetings by moving to async CEO memo. Team came prepared, one person had a question about memo content.
February 9, 2026
New Accounting Manager: Pooja started
Full-time hire to own accounting department — reviewing books, answering bookkeeper questions, overseeing projects, ensuring quality reporting
February 2, 2026
Daily report template and time entry rolled out
Full team adoption — fulfillment team, accountants, bookkeepers, tax staff, and front end
February 2, 2026
Client praise for onboarding experience
Newer client told Nick the onboarding surpassed expectations. Kevin Garcia recognized.
February 2, 2026
Ashwin ahead on tax season
Described as "an all star" — ahead in tax prep, receiving team-wide shout-outs
February 2, 2026
SOPs progressing with team
Krisha and Sariah completed SOP reviews. Ashwin next.
January 26, 2026

Action Items

Mine
Client
From February 12–13, 2026
Present SOP V3 to Ruben for review (Monday call)
Mine Source: Feb 13
Ask Ruben Founder Snapshot questions: what level of detail, every client or just exceptions, what tells him Pooja is doing a great job
Mine Source: Feb 13
Get February client list by readiness category from Ruben
Mine Source: Feb 13
Confirm with Ruben: does Financial Cents tag literally say "Non-BAD" or "Non-Vet" — need to match SOP to what team is using
Mine Source: Feb 13
Define 30-day warning language and consequences with Ruben (escalation protocol step 5)
Mine Source: Feb 12
First weekly check-in with Pooja — walk through SOP, prep for February close
Mine Source: Feb 13 · Due: Feb 19
From February 9, 2026
Send updated payment link for the new engagement structure
Mine Source: Feb 9 · ✓ Done
Pause the current one-to-one payment
Mine Source: Feb 9 · ✓ Done
Reach out to Pooja to schedule SOP development time
Mine Source: Feb 9 · ✓ Intro call completed Feb 13
Draft the Month-End Close SOP with Pooja
Mine Source: Feb 9 · ✓ V3 in final review
Prepare Founder Snapshot framework for next week's session
Mine Source: Feb 9 · ✓ Designed, integrated into SOP
Send follow-up questions from today's discovery conversation
Mine Source: Feb 9
Send Pooja's email to Kathryn via chat
Client Source: Feb 9 · ✓ Done
Communicate to Pooja that Kathryn will be reaching out
Client Source: Feb 9 · ✓ Done
Watch for payment link email and initiate recurring payment
Client Source: Feb 9 · ✓ Done
Provide access to existing month-end workbook template
Client Source: Feb 9 · ✓ Received
Provide copy of Financial Cents workflow templates for review
Client Source: Feb 9
From Previous Sessions
Build AI agent for Friday CEO memo in ChatGPT
Mine Source: Jan 26
Complete Friday CEO memo voice recording and post to Slack
Client Source: Feb 2 — Weekly
Complete Friday constraint identifier and email to Kathryn
Client Source: Feb 2 — Weekly

Recent Conversations

February 13, 2026 Working Session — Pooja Intro
Kathryn's first direct call with Pooja. Covered her background, current understanding of the role, what she's seen so far. Established the working relationship and set weekly check-in cadence for the next 5 weeks (Wednesdays 1pm ET / 11:30pm IST starting Feb 19).
Outcomes: Working relationship established; weekly cadence set; confirmed Pooja hasn't been through a close yet — SOP is her primary guide; background in accounting with team management experience
View Full Recap →
February 12, 2026 Working Session — Month-End Walkthrough
Deep-dive interview with Ruben walking through the entire month-end close process. Source transcript for SOP V3. Covered every step from the 1st through financial delivery, team roles, tool usage, status tag system, escalation approach, and client communication workflow.
Outcomes: Full process documented; status tags defined (Expected On Time, In Review, Push — Waiting on Client, Push — Info Received Late, Push — Non-Vet); escalation protocol clarified; team roster confirmed with bookkeeper names and assignments; deliverable format confirmed (balance sheet + P&L as PDF from QuickBooks, Excel exceptions for consultant clients)
View Full Recap →
February 9, 2026 Coaching Call
Ruben expressed overwhelming frustration with tax season + lack of systems. Kathryn presented systems maturity framework and Accounting Manager OS plan. Ruben committed to expanded 6-month engagement at $1,500/month. Deep-dive on month-end close design — pre-work questions answered live. CEO memo updated with "save for later" feature.
Outcomes: Expanded engagement signed; SOP development starting with Pooja this week; success metrics defined (80-90% on-time, 100% controlled); Founder Snapshot design next week
View Full Recap →
February 2, 2026 Coaching Call
Walked Ruben through setting up CEO Memo and Constraint Identifier ChatGPT projects. Tested both live. Focused on month-end close as priority constraint. Introduced Advisory OS concept.
Outcomes: Two ChatGPT projects created and tested; month-end close identified as priority; Advisory OS introduced
View Full Recap →
January 26, 2026 Coaching Call
Restructured Monday meeting — moved announcements to async Friday CEO memo. Established upstream/downstream constraint framework. Reviewed SOP progress.
Outcomes: Agreed to restructure Monday meeting; Kathryn will build CEO memo agent; constraint identification framework established
View Full Recap →