The CRM mortgage branch managers run a branch, not a borrower, in.
A mortgage branch manager runs 5 to 15 loan officers against a monthly branch funded-unit target, a recruiting pipeline, a comp plan with ladder tiers, and the ever-present risk that a producing LO walks across the street to a competitor. Strkr collapses the branch dashboard, the LO ramp view, the comp plan audit, and the recruiter queue into one workspace shaped around the branch manager week.
The mortgage branch manager job splits across four jobs across the same week: lead the LO pipeline reviews, run the branch funded-unit forecast, recruit the next three LOs, and run the comp plan audit on the back half of the month. The common stack is Encompass or Byte for the LOS, Jungo or Surefire for the CRM, a Google Sheet for the branch forecast, a spreadsheet for the comp plan, an email thread with the regional manager, and a LinkedIn window for the recruiter outreach. Nothing in the stack holds the branch funded-unit forecast against LO submission with manager override, the LO ramp view against the comp plan ladder, or the LO retention signals against the recruiter queue. The sections below show how Strkr collapses the branch manager workflow into one workspace with the branch forecast on a hierarchical rollup, the LO ramp dashboard on every rep, the comp plan on the LO record, and the recruiter queue as a parallel pipeline.
Branch forecast by Sheet
The branch funded-unit forecast lives in a Google Sheet.
Every month the branch manager pulls Encompass pipeline into a Sheet, applies gut-feel haircuts on 60 files across 10 LOs, sums commit and best-case, pastes the number into a reply email to the regional manager. The next month the whole ritual starts over. Strkr runs a native hierarchical forecast: LOs submit category calls per file (commit, best-case, pipeline, omit), the branch manager overrides where the manager read differs, and the branch number rolls up to the regional manager automatically. The Sheet retires on week two.
LO ramp without signals
A new LO ramps or does not and nobody sees it until month 4.
A new loan officer rolls into the branch and the branch manager watches the first 90 days against ambition instead of a dashboard. The LO is at 2 pre-quals a week in month 2 when the ramp curve says 6 and nobody flags it until the month 4 review when the comp plan already stung. Strkr runs an LO ramp dashboard that shows pre-quals created, applications taken, submitted-to-underwriting, and funded units per week since start, with the ramp curve as the baseline and the gap visible every Monday morning.
Comp plan ladder opaque
The comp plan ladder tier is invisible to the LO and the manager.
The branch comp plan ladders basis points by funded unit count or funded volume with a per-tier BPS lift. The LO closes a deal that nudges them into the next tier and the comp plan recalculates on the back half of the month in a spreadsheet nobody audits. Strkr holds the comp plan ladder on the LO record with the current tier, the funded units year-to-date, the units to the next tier, and the projected tier at the end of the month. The LO sees the number without asking.
Recruiter time split
Half the branch manager week disappears into recruiting.
The branch manager spends 15 to 25 hours a week on recruiting: sourcing LO candidates, phone interviews, team lunch demos, offer package building, and the departing-LO exit interview. The time disappears into LinkedIn tabs and email threads and the branch manager cannot answer "where did the week go" by Friday. Strkr runs the recruiter queue as a parallel pipeline with every candidate on a stage board (sourced, phone screen, team lunch, offer, signed, declined) and the time logged against each stage so the Friday retrospective runs off a number.
LO retention blind spot
The producing LO walks across the street and nobody saw it coming.
The branch manager loses one producing LO per year to a competitor and the departure usually surprises the branch. The signals are there: funded-unit drop over the trailing 60 days, a sudden drop in Realtor partner touches, a comp plan tier that stalled below expectation, a backchannel LinkedIn message pattern. Strkr runs an LO retention signals view that flags the three LOs most likely to leave in the next 90 days against those signals so the branch manager runs the retention conversation two months before the two-week notice lands.
Branch comp audit by hand
The month-end comp audit eats a weekend.
The branch manager and the office manager spend the first weekend of every month on the branch comp audit: pulling Encompass funded loans, matching to LO records, recalculating the ladder tier, applying referral splits, applying mentor fees, and reconciling against the Sheet. Strkr holds every pricing scenario, every ladder tier change, and every funded unit on the LO record with a timestamped audit trail so the month-end audit runs off the record in two hours instead of a weekend. Strkr does not provide regulatory advice; firm compliance leadership should confirm policy configuration.
How Strkr fits the branch manager week
The primitives mortgage branch managers actually run a branch on.
Strkr for mortgage branch managers ships the same CRM every other role at the branch runs, with manager-tier views layered on top for branch rollup, LO ramp, comp plan audit, and recruiter queue. The primitives below line up with the branch manager week: Monday pipeline review across LOs, mid-week recruiter outreach, Wednesday LO ramp coaching, Thursday branch forecast submit, Friday comp plan projection and retention signal review.
Hierarchical branch forecast
LOs submit, branch manager overrides, number rolls up.
LOs submit weekly category calls per file (commit, best-case, pipeline, omit) through a Thursday workflow with a submit-lock. The branch manager sees every LO submission on one screen, overrides where the manager read differs, and submits the branch number to the regional manager. The regional sees the branch rollup the same way. One source of truth, no spreadsheet, no copy-paste moment where numbers drift between tools.
LO ramp dashboard
New hire first 90 days, visualized by week.
A new LO ramp dashboard shows pre-quals created, applications taken, submitted-to-underwriting, funded units, and Realtor partner touches by week since start with the ramp curve baseline and the gap visible. The branch manager coaches on specifics (pre-qual response time, Realtor partner outreach cadence, condition clearance pace) rather than vague "you need to make more calls." Ramp time shortens because the gaps are visible.
Comp plan on the record
Ladder tier, year-to-date, projected tier on the LO record.
The branch comp plan ladder lives on the LO record with the current tier, the funded units and funded volume year-to-date, the units to the next tier, the projected tier at end of month, and the audit trail on every tier change. The LO sees the number without asking and the branch manager sees the comp exposure before the ladder tier shift lands on the Friday payroll run.
Recruiter queue
LO candidates on a parallel pipeline.
The recruiter queue runs as a parallel pipeline with every candidate on a stage board (sourced, phone screen, team lunch, offer, signed, declined). Each candidate carries the sourcing channel, the current branch, the funded-unit history where known, the comp expectation, and the next-step task. The branch manager sees the Friday retrospective on time logged per stage so the recruiter time split is a number instead of a feeling.
LO retention signals
The three LOs most likely to leave surfaced monthly.
Strkr runs an LO retention signals view that flags the three LOs most likely to leave in the next 90 days against signals: funded-unit drop over trailing 60 days versus trailing 180, Realtor partner touch cadence drop, comp plan tier stall below expectation, pipeline age climbing without closes, LinkedIn visibility pattern where available. The branch manager runs the retention conversation before the two-week notice lands.
Branch dashboard
Funded units, applications taken, pipeline, one page.
The branch dashboard ships with funded units month-to-date, applications taken trailing 30 days, submitted-to-underwriting trailing 30 days, pipeline value at commit, and LO ranking on the leaderboard. Each tile filters by LO, loan product, lender, Realtor partner source, and timeframe. The Monday branch meeting runs off the dashboard in 15 minutes instead of a Friday afternoon email from the ops manager.
1:1 prep view
Every LO 1:1, context already loaded.
Open the LO record, see the 1:1 workspace: pipeline moves this week, applications taken, submitted-to-underwriting, funded units month-to-date, condition clearance pace, Realtor partner touches, ramp curve gap for new LOs. The branch manager walks in with the questions already surfaced and spends the hour coaching, not pulling reports.
Comp audit trail
Every pricing scenario and tier change on the record.
Every pricing scenario, every fee concession request, every ladder tier change, and every LO comp line item carries a timestamped audit trail on the LO record and the file record. The month-end audit runs off the record in two hours instead of a weekend reconciliation against a Sheet. Strkr does not provide regulatory advice; firm compliance leadership should confirm policy configuration.
Flows for the branch manager motion
Automations across forecast, ramp, comp, and recruiter.
The best mortgage branch managers automate the administrative drag between weekly motions and spend their hours on the three conversations that compound: the LO 1:1, the recruiter phone screen, and the retention check-in. Strkr Flows cover the automations every branch manager should run as native triggers with no webhook plumbing. The pattern below compounds into a cleaner branch forecast, a tighter LO ramp cadence, a comp plan audit that runs off the record, and a recruiter queue that moves faster than the regional peer branch.
Forecast submit-lock
Thursday 5 PM, LO submissions lock.
A weekly flow opens the branch forecast on Monday, nudges LOs on Wednesday if they have not submitted, locks submissions on Thursday 5 PM branch-local, and rolls the branch number to the regional queue. LOs who miss the lock escalate to the branch manager automatically. Nobody chases anyone and the number that lands upstream is the number the branch actually agreed on.
LO ramp curve gap
Weekly ramp gap digest to the branch manager.
Monday 7 AM email to the branch manager: every new LO inside the ramp window with the week-by-week ramp curve, the actual against the curve, and the specific gap (pre-qual intake pace, Realtor partner outreach cadence, application-taken rate). The branch manager walks into the Monday 1:1 with the ramp gap in hand.
Comp plan tier change
A funded unit that lifts a tier fires the comp alert.
A funded loan that nudges the LO into the next ladder tier fires a flow that posts the tier change to the LO record, pings the LO with a congrats, pings the branch manager with the comp exposure delta, and queues the office manager for the month-end comp audit entry. The audit runs off a stream of logged events instead of a weekend Sheet reconciliation.
Retention signal flag
Trailing 60 day drop fires the retention alert.
A daily flow checks funded-unit pace, Realtor partner touch cadence, and pipeline age against each LO baseline. An LO who drops below the retention threshold fires an alert on the branch manager retention queue with the specific signal and a drafted check-in message. The branch manager runs the retention conversation two months before the two-week notice.
Recruiter outreach cadence
Sourced candidate pushes a cadence.
A candidate lands on the recruiter queue at Sourced and the flow drafts the first-touch LinkedIn or email through Strkr AI, logs the touch, and schedules a 72 hour follow-up. Non-response at 7 days fires a nudge; non-response at 14 days surfaces for a drafted second-touch. The recruiter outreach runs on cadence instead of memory.
Branch funded milestone
Branch funded-unit threshold fires the regional report.
The branch hits the monthly funded-unit threshold and the flow fires the regional report with the units funded, the LO leaderboard, the Realtor partner source mix, and the lender product mix. The regional meeting runs off the generated report instead of a late-Thursday Sheet rebuild.
LO 1:1 action items
Items captured in the 1:1 become tasks for Monday.
Action items captured during an LO 1:1 ("call the Realtor again by Thursday", "catch up on the three stuck conditions") turn into tasks owned by the LO with a due date and a reference back to the 1:1 timeline. Next week's 1:1 opens with the item status at the top of the agenda, which closes the loop that most 1:1 notes never close.
Compliance review cadence
Monthly compliance review runs off the record.
The month-end compliance review runs off the LO record audit trail: pricing scenarios, fee concessions, ladder tier changes, LO comp lines, and co-marketing agreement renewals. The firm compliance leadership runs the review in the Strkr record view instead of a weekend reconciliation. Strkr does not provide regulatory advice; firm compliance leadership should confirm policy configuration against the firm policy manual.
What a branch manager sees that LOs do not
Manager-tier views that stay out of the LO workspace.
A manager tier that creates a parallel UI is a tier LOs resent. Strkr keeps the LO workspace identical for LO and branch manager, then adds a manager-only overlay for branch rollup, private 1:1 notes, retention signals, and comp plan audit that LOs do not see. The result is a shared source of truth where LOs trust that what they see is what the manager sees, with no shadow view running on top. The surfaces below are what gets added at the manager tier, not what gets taken away from the LO.
Branch rollup
Every LO pipeline in one scrollable view.
The branch rollup shows every LO pipeline on a single screen, grouped by LO, sorted by stage and funding date. Filter by lender, loan product, Realtor partner source, deal size, or ramp status to find the 15 files that matter this week across the branch. Collapse per LO when running branch-wide reviews and expand per LO when running a 1:1.
Private 1:1 notes
Manager notes that LOs do not see.
Notes captured during an LO 1:1 can be marked private to the branch manager or shared with the LO. Private notes feed into the quarterly review view and the ramp dashboard so the branch manager has running context on each LO across the year. Shared notes become visible to the LO on Monday with the related action items queued.
Submit-lock override
The branch read beats the LO read when it has to.
LOs submit their weekly category calls through the Thursday workflow. The branch manager overrides the LO call per file where the manager read differs, and the override carries a one-line reason the LO sees on Friday. The branch number that rolls up is the manager-adjusted number, with the LO submission preserved as an audit trail for the quarterly review.
Retention signal inbox
The three LOs most likely to leave, in one list.
Every LO retention signal flag lands in a manager-only retention inbox. The branch manager triages each flag in two clicks: dismiss (false positive, carries a reason), schedule retention conversation (creates a task tied to the LO), or escalate (routes to the regional with the signal history attached). The inbox clears to zero on a disciplined month, and dismissals train the model.
Comp plan setting
Per-LO ladder, per period, with tier curves.
The branch manager sets the comp plan ladder per LO per period with the per-tier BPS lift. The ladder rolls into pacing dashboards for the LO and the branch manager without a quarterly sync meeting. Change a ladder mid-period and the comp recalculates automatically. The audit trail per LO is preserved so the compensation conversation at period end is grounded in a shared history.
Recruiter candidate detail
Candidate record visible to the branch manager only.
Candidate records on the recruiter pipeline are visible to the branch manager and the regional recruiter only. The candidate funded-unit history where known, the comp expectation, the current branch, and the signed offer package stay out of the LO workspace. The branch manager runs the recruiter motion without broadcasting the pipeline to the current team.
Branch benchmark
LO against branch, branch against region.
Every LO metric (pre-qual pace, application pace, submitted-to-underwriting pace, funded units, cycle time) renders against the branch average and the regional average on the same tile. The branch manager spots the LO a quarter outside the branch on cycle time and runs a specific coaching session instead of a generic "we need to close faster" talk.
Head-to-head
Strkr for branch managers vs the Encompass + Jungo + Sheets + LinkedIn stack.
A typical mortgage branch manager stack runs Encompass or Byte for the LOS, Jungo (Salesforce for mortgage) or Surefire for the CRM, a Google Sheet for the branch forecast, a spreadsheet for the comp plan, an email thread with the regional manager, and a LinkedIn window for the recruiter outreach. Nothing in the stack holds the branch rollup, the LO ramp view, the comp plan audit, or the retention signal. Strkr collapses the branch workflow into one workspace with the branch forecast as a hierarchical rollup, the LO ramp dashboard on every rep, and the recruiter queue as a parallel pipeline.
What matters
Strkr
Encompass + Jungo + Sheets + LinkedIn
Number of surfaces the branch manager opens weekly
1 (Strkr)
5 to 6 (LOS, CRM, forecast sheet, comp sheet, LinkedIn)
Branch forecast
Native hierarchical rollup with LO submit-lock and manager override
Google Sheet rebuilt monthly
LO ramp dashboard
Native per-week ramp curve with gap visibility
Branch manager eyeballs funded units at month 4 review
Comp plan ladder on the record
Native ladder tier, year-to-date, projected tier on LO record
Comp spreadsheet reconciled on the first weekend of the month
Recruiter queue
Parallel pipeline with stage board, cadence, and candidate detail
LinkedIn tabs and an email thread
LO retention signals
Three-LOs-most-likely-to-leave view flagged against signals
Record audit trail for pricing, fee concession, ladder change
LO memory and sticky notes
Admin burden
Self-serve for branch manager and ops manager
Salesforce admin for Jungo, LOS admin for Encompass, separate
Monthly cost per LO (manager stack)
One per-seat line, see pricing page
Four to five per-seat lines stacked
See the CRM mortgage branch managers run a branch in.
Start a trial with the full mortgage branch manager stack enabled: hierarchical branch forecast with submit-lock, LO ramp dashboard, comp plan ladder on the record, recruiter queue, LO retention signals, 1:1 prep view, and Flows for every weekly motion. Migrate from the Encompass plus Jungo plus Sheets stack in an afternoon and keep every record, forecast submission, and LO 1:1 action item intact on the way in. The pricing page lays out the per-seat line in full so there is no mystery before the trial starts.
Can Strkr replace the Encompass plus Jungo plus Google Sheet forecast our branch runs today?
For most branch managers running 5 to 15 LOs, yes, on the forecast and manager-tier views. Strkr ships a native hierarchical forecast with per-LO category submission (commit, best-case, pipeline, omit), manager-tier overrides with an audit trail, a submit-lock on a weekly cadence, and rollup to the regional level. The forecast Sheet retires in week two. The LOS continues to hold the regulated loan file; Strkr integrates with Encompass and Byte so key dates, stages, and conditions sync. For branches running Jungo today, Strkr covers the common cases and migrates the Jungo custom fields into Strkr custom fields on setup.
How does Strkr handle LO ramp for a new hire?
A new LO ramp dashboard shows pre-quals created, applications taken, submitted-to-underwriting, funded units, and Realtor partner touches by week since start with the ramp curve baseline and the gap visible. The branch manager walks into the Monday 1:1 with the specific gap (pre-qual intake pace, Realtor partner outreach cadence, application-taken rate) instead of a vague "you need to pick up the pace" talk. Ramp curves are tunable per branch so an inside-sales LO ramp and a referral-partner LO ramp can run the same dashboard with different baselines. The ramp dashboard retires at the 180 day mark and the LO rolls into the standard pipeline view.
Does Strkr handle the comp plan ladder tier math on an LO record?
Yes. The branch comp plan ladder lives on the LO record with the current tier, the funded units and funded volume year-to-date, the units to the next tier, the projected tier at end of month, the per-tier BPS lift, and the audit trail on every tier change. A funded loan that nudges the LO into the next tier fires a flow that posts the tier change, pings the LO, pings the branch manager with the comp exposure delta, and queues the office manager for the month-end audit entry. The audit runs off a stream of logged events instead of a weekend Sheet reconciliation. For branches running multi-dimensional comp (volume tier plus retention bonus plus mentor fee), the ladder supports multiple parallel axes.
How does Strkr flag an LO at risk of leaving the branch?
Strkr runs an LO retention signals view that flags the three LOs most likely to leave in the next 90 days against signals: funded-unit drop over trailing 60 days versus trailing 180, Realtor partner touch cadence drop, comp plan tier stall below expectation, pipeline age climbing without closes, and LinkedIn visibility pattern where available. The branch manager runs the retention conversation before the two-week notice. The signals are tunable per branch so a branch running a high-tenure team and a branch running a mix of senior and new LOs can both run the same view with branch-appropriate weights. The retention conversation is manager-led; Strkr does not auto-send messaging to the flagged LO.
Can a branch manager customize the branch configuration without a corporate CRM admin?
Yes, for the manager-tier levers. The branch manager can tune per-stage pipeline criteria, LO ramp curves, comp plan ladder tiers, 1:1 note templates, retention-signal cadence, and recruiter queue stages without a corporate ticket. Deeper schema changes (new custom objects, API-level integrations with the regional LOS instance, flow logic that writes to external systems) still route through a corporate RevOps admin by design, so branch configuration stays local but shared architecture stays coherent. The branch manager customizations roll up to the regional view without a copy-paste moment.
How does the recruiter queue work alongside the branch manager day-to-day?
The recruiter queue runs as a parallel pipeline with every LO candidate on a stage board (sourced, phone screen, team lunch, offer, signed, declined). Each candidate carries the sourcing channel, the current branch, the funded-unit history where known, the comp expectation, and the next-step task. The branch manager spends 15 to 25 hours a week on recruiting and the time logged against each stage lands on the Friday retrospective so the recruiter time split is a number instead of a feeling. For branches with a regional recruiter supporting the branch, the regional recruiter sees the branch queue from the regional view and takes handoffs on specific candidates at stage transitions. The candidate records stay out of the LO workspace so the branch manager runs the recruiter motion without broadcasting the pipeline to the current team.
No sales call, no migration consultant, no four-month implementation. Enter your card, get 14 days of the full Pro tier, cancel any time before day 14 with zero charge. Spin up a workspace, import your CSV, and have something useful before lunch.
We use cookies.
Essential cookies keep the site working. If you accept, we also enable Google Analytics
so we can see which pages help and which don't. Reject to opt out entirely. Details in our
Privacy Policy.
