One source of truth
See lead source, applications, disclosures, conversion, and pipeline movement in one leadership view—without stitching together exports or guessing whether the numbers are complete.
Ongoing services proposal · July 2026
Protect what works. Build what’s next.
A flexible partnership for the team reAlpha has today—with the support, visibility, and build capacity to welcome 51 more LOs without creating 51 new versions of the business.
What we heard on July 14
The next phase is about visibility, accountability, and scale.
reAlpha has already made the hard move to a more organized operating model. The opportunity now is to turn that foundation into clearer leadership reporting, easier day-to-day execution, and a consistent experience for every LO.
Context where work happens
Give processors the borrower history and LO communication context they need without repeatedly opening individual LO accounts.
Visible LO activity
Make outreach, follow-up, tasks, and activity easier to coach and manage with daily reporting now and richer leader oversight over time.
A repeatable LO command hub
Bring tasks, licensing, cross-sell visibility, marketing resources, and company links into one consistent starting point for the field.
Smarter operating workflows
Improve call routing, referral-partner visibility, lead follow-up, and exception handling before higher volume turns today’s workarounds into tomorrow’s bottlenecks.
Acquisition-ready onboarding
Start with the LOs active today, then add the Instamortgage cohort through a controlled, repeatable onboarding and rollout process.
Three ways to engage
Start at today’s adoption. Scale when the team does.
Every option includes up to 20 active LOs. Above 20, the recurring fee increases by $50 per active LO per month. An LO becomes billable when their HighLevel user is created; the activation month is prorated.
Option 1
Essential Support
$2,500 / month
Help for current LOs, Broker Toolkit access, troubleshooting, and quarterly leadership guidance.
Option 2Recommended
Managed Growth Partnership
$5,700 / month
Essential Support plus ongoing system care, company-wide snapshot management, and continuous HighLevel request fulfillment.
Option 3
Managed Growth + Build Capacity
$9,400 / month
The recommended partnership plus two simultaneous HighLevel requests and prepaid capacity for reporting, portal, and integration work.
The recommended baseline
Pay for ongoing ownership—not for fixes already promised.
The recommended partnership separates three different needs: correcting an original defect, caring for a live operating environment, and creating something new. That keeps the agreement fair, predictable, and easy to use.
Essential Support
Up to 20 active LOs
Up to 20 active LOs
$2,500
+
Ongoing System &
Snapshot Care
Snapshot Care
$2,000
+
Continuous HighLevel Requests
One active at a time
One active at a time
$1,200
=
Managed Growth Partnership
Current recurring total
Current recurring total
$5,700
Warranty: we stand behind the original build
If Empower-delivered functionality does not perform as accepted—and reAlpha or a third party did not materially change it—Empower corrects the defect at no charge during the applicable six-month warranty period.
Managed Care: we own continuity after launch
The paid module provides proactive attention, recovery, vendor-change triage, ongoing upkeep, and controlled snapshot administration as the live environment evolves.
New work: choose the right fulfillment path
New HighLevel functionality moves through the Request Board. Reporting, portals, integrations, data work, and other cross-system changes use the Development Bank or an approved project scope.
$2,000 ongoing-care module
Managed Care keeps the connected operating environment dependable after launch. It covers ongoing attention, first response, supported recovery, routine upkeep, vendor-change assessment, and the administration required to keep one approved LO experience current.
Build the change through the Request Board. Test it once. Managed Care rolls the approved version out to the right LOs and keeps the master version current.
- 01reAlpha Ops PortalKeeps the operations workspace available, secure, and supported for the people who rely on it.
- 02Connected HighLevel environmentKeeps approved account, user, workflow, contact, message, and note information moving to the right places.
- 03Arive loan updatesKeeps loan milestones and key borrower information flowing into the appropriate Leads, LO, and Ops experiences.
- 04Byte loan updatesProvides continuity for Byte-connected loan data, producer assignment, and supported recovery.
- 05Consumer Direct lead operationsProtects the existing lead-to-appointment journey, including handoffs, dispositions, reminders, and follow-up entry.
- 06Lead routing & licensing controlsHelps each lead reach an eligible LO using the approved roster, state rules, availability, and fallback paths.
- 07Hot-lead claiming & iConnect handoffKeeps time-sensitive leads moving from offer to claim to live follow-up.
- 08reAlpha website & app activityPreserves the approved flow of digital activity into the appropriate customer and operating records.
- 09Production continuity & recoveryMaintains the scheduled work, alerts, operating history, and recovery procedures behind the experience.
- 10One approved LO snapshotMaintains the master LO experience, tests updates, distributes approved changes, and keeps future onboardings current.
How the Request Board works
Unlimited requests in sequence. One active build per lane.
There is no monthly request-count limit. reAlpha can keep a continuously prioritized queue of ready HighLevel work. Empower completes the top ready request, then moves directly to the next. One lane means one request actively in fulfillment; each additional $700 monthly lane adds another request that can move at the same time.
Build the queue
reAlpha can submit and prioritize as many eligible HighLevel requests as needed.
Keep the next item ready
Empower confirms the outcome, required inputs, and whether the work belongs in HighLevel.
Fulfill continuously
One approved request is active per lane. When it finishes, the next ready request starts.
Add speed when needed
Purchase another lane for $700 per month when two priorities need to move concurrently.
Examples from reAlpha’s roadmap
Good Request Board work
- Daily task and activity reminders for the Leads Team
- A native HighLevel version of Ashley’s LO command hub
- Referral-partner fields, views, and follow-up workflows
- Smarter native AI call-routing and failover rules
- Dashboards, campaigns, forms, calendars, fields, and workflows
- Build in the Playground account before approved snapshot rollout
Development Bank or project
Work that crosses systems
- Consolidated reporting across lead, loan, and activity data
- Mirroring LO conversations into the Ops account
- New Ops Portal experiences or custom leader dashboards
- Arive, Byte, reAlpha website/app, or other outside-system changes
- Historical migrations, reconciliation, or acquisition data work
- Anything requiring an integration, database change, or custom application
Throughput depends on the size and readiness of each request and the speed of reAlpha review. A request waiting on copy, access, decisions, or approval steps aside so the next ready item can keep the lane moving.
Service-level expectations
When something needs attention, everyone knows what happens next.
These are response and communication targets during regular business hours—not promises that every issue will be fully resolved inside a fixed window. Resolution depends on diagnosis, access, approvals, vendor dependencies, and the type of work required.
| Priority | When to use it | Initial response target | Communication commitment |
|---|---|---|---|
| Critical (P1) | A covered production service is unavailable; there is a material data or security risk; or company-wide lead flow is stopped with no practical workaround. | Within 2 business hours | Every 4 business hours until the service is stable or a recovery plan is agreed. |
| High (P2) | Significant degradation or multiple-user impact, but the business has a reasonable workaround. | Within 1 business day | At meaningful status changes, and at least daily while actively worked. |
| Standard (P3) | An individual issue, access question, how-to request, or noncritical defect. | Within 2 business days | At classification, when a dependency arises, and when the issue is complete. |
| New request | A desired change or new outcome—not an incident. | Classified within 2 business days | Clear routing to warranty, Managed Care, Request Board, Development Bank, or a separate project scope. |
Hours and intake
Standard Business Hours are Monday through Thursday, 8:00 a.m.–4:00 p.m. Mountain Time. reAlpha may use Empower HQ or the designated support intake channel. A named reAlpha administrator approves production changes and sets request priority.
What pauses the clock
Response and update targets pause while Empower is waiting on required access, information, approvals, reAlpha review, or a third-party vendor. Friday, evening, weekend, and 24/7 coverage are available only under a separately priced on-call arrangement.
Grow without paying early
The relationship grows when reAlpha does.
Today’s price reflects approximately 10 active LOs—not a future acquisition population. reAlpha pays the baseline through 20 active LOs, then adds $50 per LO only when each new HighLevel user is created. The activation month is prorated.
10
Current active LOs
$5,700 / month recommended partnership
$5,700 / month recommended partnership
20
Included active LOs
$5,700 / month recommended partnership
$5,700 / month recommended partnership
50
Illustrative active LOs
$7,200 / month recommended partnership
$7,200 / month recommended partnership
60
Illustrative active LOs
$7,700 / month recommended partnership
$7,700 / month recommended partnership
| Contracted recurring fees | Included operating advisory & governance |
|---|---|
| $2,500–$5,999 / month | One 60-minute operating advisory session each quarter |
| $6,000–$9,999 / month | One 60-minute operating advisory session each month |
| $10,000+ / month | Two 60-minute operating advisory sessions each month, plus a quarterly roadmap review |
Concrete next-step opportunities
Two high-value projects are already taking shape.
These working ranges translate the July 14 conversation into decisions leadership can evaluate. They are directional—not fixed quotes—and will be finalized after requirements, data sources, and acceptance criteria are confirmed.
Consolidated performance reporting
Create one leadership view of company-generated versus self-sourced leads, applications, disclosures, conversion, LO activity, and pipeline movement. The goal is a trusted operating picture without manual exports or account-by-account investigation.
$6,000–$8,000
Standard estimated value before prepaid discount · approximately $4,600–$6,200 from the Development Bank
Conversation context in the Ops account
Bring relevant LO and borrower communication history into the processor experience so the team can understand what has already been discussed, reduce duplicate requests, and spend less time switching between accounts.
$4,000–$6,000
Standard estimated value before prepaid discount · approximately $3,100–$4,600 from the Development Bank
The prepaid illustrations apply the same estimated effort at $250 per blended hour instead of the standard $325 rate. Projects expected to exceed $1,500 still receive an individual scope and approval before work begins, and approved work may draw from accumulated bank balance.
Option 3 · Development Bank
Build more for less—with one simple client-facing rate.
A $3,000 monthly Development Bank reserves 12 blended hours for reporting, portal, integration, and other approved work. The same effort purchased as needed is $325 per hour; prepaid work is $250 per hour. reAlpha sees the outcome, estimate, and savings—not a confusing mix of developer rates.
Standard · pay as needed
$325 / hour
12 blended hours carry a standard value of $3,900.
Prepaid Development Bank
$250 / hour
$3,000 reserves 12 hours with one client-facing rate.
$900 savings · approximately 23%Simple client accounting
Every delivery developer counts one-for-one. Estimates show expected blended hours, standard value, prepaid allocation, and dollar savings. The bank is charged only for actual time worked, never above the approved cap without additional approval.
Bank mechanics
- Unused hours roll through the agreement term
- Written estimate approved before work begins
- Actual time posted at completion or weekly for longer work
- Cancellation before start: no deduction
- Cancellation after start: actual time worked only
- Work over six hours / $1,500 receives an individual scope
- Individually scoped work may draw from available bank balance
One-time LO onboarding
Onboard one LO—or welcome the whole team.
Onboarding is priced separately so reAlpha pays only when people are ready to launch. Every standard onboarding includes account creation, the approved reAlpha setup, phone and email compliance configuration, validation, and the applicable live session.
| Onboarding format | Price | Live sessions | Delivery structure |
|---|---|---|---|
| Individual LO | $200 / LO | 1:1 session | Standard setup, guided configuration, and completion check |
| 2–4 LOs | $500 | 1 shared session | $500 group-program minimum applies at two people |
| 5–10 LOs | $1,000 | 2 shared sessions | Five LOs begins the two-session band |
| 11–19 LOs | $1,500 | 2 shared sessions | Standardized cohort delivery |
| 20–49 LOs | $3,000 | 4 shared sessions | Two tracks, with two sessions per track |
| 50+ LOs | Custom cohort plan | Defined with rollout | Session tracks, roster coordination, and dependencies scoped together |
An LO becomes billable for recurring support when their HighLevel user is created. The activation month is prorated. The monthly fee does not increase merely because an acquisition is announced or a cohort is scheduled.
Carrier approvals, DNS propagation, and third-party review timing are outside Empower’s control. Empower corrects its own submission or configuration errors; nonstandard structures or repeated client-directed changes may require separate approval.
Clear expectations
Know what is covered before the request is made.
What we are protecting
The agreement records what is live, what it is expected to do, known limitations, and the handoff date. Warranty and Managed Care decisions are measured against that shared starting point.
When a vendor changes something
Managed Care includes first response, diagnosis, and a clear impact assessment. Any redesign, migration, or new workaround is estimated before implementation.
How LO-wide updates work
Approved HighLevel changes are tested, released to the appropriate standardized LO accounts, and added to the master template for future onboardings.
Project discount
The SOW project discount is separate consideration. It is not credited against or recovered through monthly service fees. Options 2 and 3 exceed the SOW’s $2,500 threshold.
Initial term
The initial service term is 12 months, matching the term stated in the final reAlpha SOW’s ongoing-services discount trigger. Renewal terms are set in the definitive agreement.
Larger initiatives
New applications, major migrations, new integrations, acquisition transitions, and other multi-system initiatives receive discovery and a separate written scope.
Review selection
Choose the level of partnership that fits the next phase.
This selection is for proposal review and does not replace the definitive service agreement, baseline schedule, or authorized signature.
Current selection
Managed Growth Partnership
Ongoing system care, company-wide snapshot management, and continuous HighLevel request fulfillment with one active request at a time.
$5,700 / month
Pricing shown in USD. Each option includes up to 20 active LOs; additional active LOs are $50 each per month. One-time onboarding, pass-through expenses, third-party usage, and separately approved work are excluded unless expressly shown.
Commercial proposal prepared July 14, 2026. Final scope, service levels, effective dates, renewal, termination, and legal terms are governed by the executed agreement and its accepted production-baseline schedule.