The platform decision was made before the process was mapped
Tier, add-ons and seat count committed on a demo. Then the operation turns out to need routing rules and a recipient matrix nobody scoped, and the project is renegotiating in month two.
Salesforce · Mortgage CRM Advisory
Before you configure anything, somebody should map the operation.
Most Jungo projects that go wrong were decided badly, not built badly — the wrong tier, an unscoped recipient matrix, a sync cadence nobody confirmed, a licence bought for capability nobody uses. We assess what you have, price buy against build with the arithmetic shown, and hand you an architecture you can execute with anyone. We do not resell the licence, so the answer can go either way.
2–4 wks
0
500+
12+
Trusted by 500+ organizations — including mortgage lenders, brokerages and loan-officer teams running their pipeline on Salesforce with Twopir Consulting.
Built for Mortgage Operations
- Salesforce Partner
- HubSpot Partner
- Jungo — The Mortgage App
- Encompass LOS Sync
- Calyx Point · Byte · LendingPad
- Floify · DocsBar
- Optimal Blue · Mortgage Coach
- Salesforce Flow Automation
Six decisions that cost more than the software
Almost every troubled Jungo rollout we are called into went wrong before anyone configured anything. The expensive mistakes are decisions, not builds.
Nobody has done the licence maths
Seats, tier, setup fee, texting, lead distribution, the origination sync, the minimum one-year term. Each line looks small. The three-year total rarely gets written down before signature.
The org is live but nobody can say what is in it
Flows built by three different people, picklists that drifted from the origination system, reports that contradict each other. Every change request starts with an archaeology dig.
Buy-versus-build is argued, never calculated
One side wants the add-on, the other wants to build it. Without effort ranges and a per-seat multiplier on the table it stays a matter of opinion, and the loudest voice wins.
Adoption is treated as a training problem
It is usually a design problem. Loan officers abandon a system that asks for data they do not have at the moment it asks, and no amount of training fixes a layout built for the wrong role.
There is no measurable definition of success
Without a baseline for cycle time, pull-through or source profitability, the project cannot be judged and the next investment cannot be justified.
Advisory work that ends in a decision you can defend
A clean definition, because "consulting" is the vaguest word on any partner site.
Jungo consulting is the work that happens before, or instead of, a build. It answers four questions: what do we actually have, what should we buy versus configure versus build, what should the architecture look like, and in what order should we do it.
The product it advises on is Jungo — The Mortgage App — a mortgage CRM sold by the seat and listed on the Salesforce AppExchange since 2008. It adds a Loan record, shipped milestone alerts, a referral-partner programme and a maintained loan-origination-system sync on top of Salesforce. Everything underneath stays stock: Flow, reports, tasks, events and cases are used as-is. That matters for advisory work, because it means most of what you might want is reachable either by licensing the layer or by building on the platform — and the choice is genuinely open.
We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. The engagement ends with an assessment, a platform-fit decision with the licence maths, an architecture blueprint and a sequenced roadmap. If you then want it built, that is a separate implementation engagement. If you would rather your own team built it, the documents work just as well.
The three capabilities buyers assume are core are not in the entry tier
This is the single most common surprise in a Jungo purchase, and it is entirely avoidable with a seat-count model built before signature.
| Capability | Where it sits | Why it matters to the decision |
|---|---|---|
| Marketing library & templates | Entry tier | Available from the bottom tier, so it rarely drives the decision either way. |
| Property listings & print co-marketing | Entry tier | Useful for purchase-heavy teams; not a reason to move up a tier on its own. |
| Agent portal for referral partners | Entry tier | Strong capability at the entry price — worth weighing if partner self-service is the main driver. |
| Loan origination system sync | Bundle tier | The capability most buyers assume is core. Without it the CRM and the loan file are reconciled by hand. |
| Lead distribution (Leads App) | Bundle tier, plus its own setup and annual fee | Also runs on your own Zapier plan, so lead volume drives a third bill nobody forecasts. |
| Business texting | Separately licensed, on your own Twilio account | Two different price models appear on the vendor’s own pages. Get yours in writing before you budget it. |
Six deliverables that make the next decision an easy one
Every item here is a document or a decision you keep, independent of who builds what comes next.
Current-State Assessment
What you actually have, documented — whether that is a five-year-old org or a process that has never touched a CRM.
- Org inventory: objects, fields, Flows, layouts, report types
- Origination system field map and sync health
- Process walk-through with intake, processing and leadership
- Data quality, duplicates and record-ownership review
- Adoption diagnosis by role, not by training-hours delivered
Platform-Fit & Licence Analysis
The buy, configure or build decision for each capability, with the arithmetic shown rather than asserted.
- Capability-by-capability buy / configure / build call
- Tier and add-on fit against your real seat count
- Three-year cost model including the minimum term
- Where Jungo is genuinely the shortcut, and where it is not
- Independent — we hold no reseller margin either way
Architecture Blueprint
The design document a build team can execute from, and a principal can actually read.
- Data model: contacts, loans, referrals and partner records
- Routing logic including licensing and round-robin rules
- Milestone matrix — which party receives which alert
- Integration boundaries and system-of-record decisions
- Reporting structure and the metrics leadership will run on
Roadmap & Sequencing
What to do first, what to defer, and what to decline — with effort ranges attached so the plan can be budgeted.
- Phased plan with dependencies made explicit
- Effort ranges per workstream, not a single false number
- Quick wins separated from structural work
- Risk register: sync cadence, history, licensing, ownership
- Success baselines so the next investment can be justified
Governance & Ownership Design
Who owns the system after go-live, in writing. This is the single most common gap we find in a struggling org.
- Admin ownership model: internal, partner or blended
- Change-control and release process for Flow work
- Permission, sharing and record-visibility design
- Consent and opt-out handling for email and texting
- Documentation standards so the next admin is not archaeologist
Vendor & Contract Advisory
What to ask Jungo before you sign, and which published answers are worth pinning down in writing.
- The field dictionary and supported editions
- Which of the two published SMS price models applies to you
- The real sync cadence for your tenant
- Whether a Salesforce licence is included or separate
- Migration support for the history the live sync will not backfill
Five stages, two to four weeks
Longer for multi-branch lenders or orgs with years of undocumented automation. We give you the range after the scoping call, not after the invoice.
Scope & Access
We agree what the assessment has to answer, get read access to the org and the origination system, and book time with the people who actually run the process.
Discover
Org inventory, field-map review, data profiling and role-by-role process walk-throughs. We watch the work happen rather than relying on how it is described.
Analyse
Findings against the operation: what is costing time, what is costing loans, what is costing licence fees for capability nobody uses.
Decide
The buy / configure / build call per capability, with cost models and effort ranges, worked through with your team rather than presented to it.
Blueprint & Roadmap
Architecture document, sequenced plan, risk register and success baselines — yours to execute with us, with another partner, or internally.
What the work looks like once the decisions are right
Two engagements that began exactly here — with an assessment of how leads were reaching people, and what the systems underneath were really doing.
★★★★★
Twopir rebuilt how leads reach an agent and how a deal becomes a signed contract. Contract turnaround dropped from two or three days to under four hours, and the error rate on documents went to near-zero because the data was coming straight out of the CRM instead of being re-keyed.
Operations Director Luxury real estate conglomerate · 250+ agents Lead-to-Contract
Real Estate Group — 250+ Agents
Sales operations and lead management rebuilt on Salesforce, from lead routing through to contract generation and commissions.
4 hrs Contract turnaround, from 2–3 days
~0 Document error rate after CRM-sourced data
250+ Agents on one routing model
★★★★★
The enrichment and scoring work changed which leads our reps saw first. They identified high-value leads about 30% faster, and lead-scoring accuracy improved around 25% once the rules were built on real engagement and firmographic signals rather than guesswork.
Revenue Operations Lead Mid-market FinTech · 250 employees · North America Lead Scoring
Mid-Market FinTech — 250 Employees
Salesforce CPQ with Apollo.io enrichment, Outreach sequences and Zapier workflow automation across one connected sales stack.
30% Faster high-value lead identification
25% Improvement in lead-scoring accuracy
1 Connected stack, not four disconnected tools
Advice you can act on without buying anything from us
The value of an assessment is proportional to how free the assessor is to reach an inconvenient conclusion.
We hold no reseller margin, so the advice can go either way
We implement Jungo and we build on core Salesforce. Nothing in our commercial model prefers one answer, which is the only condition under which a platform-fit assessment is worth reading.
We assess the operation, not just the org
An org inventory tells you what was built. It does not tell you why loans stall. We map intake, routing, processing and post-close alongside the metadata, because the answer is usually in the gap between them.
We show the arithmetic
Seat counts, tier deltas, add-on pricing, the minimum term, and the configuration hours that would replace an add-on. Buy-versus-build stops being a debate the moment both columns have numbers in them.
We know where this product is thin, not just where it is strong
Non-retroactive origination sync. A conflicting published sync cadence. Documents that attach to the contact rather than the loan. Recipient matrices that are configuration on every rollout. These shape a plan, and they are not in a demo.
The deliverable is yours
Assessment, blueprint and roadmap are written to be executed by whoever you choose. A consulting engagement that only makes sense if you also buy the build is not consulting.
Answers before the first call
Four deliverables. A current-state assessment of your org or your process. A platform-fit decision with the licence maths written down — which capabilities you buy, which you configure and which you build. An architecture blueprint covering the data model, routing, milestone matrix and reporting. And a sequenced roadmap with effort ranges. You can hand all four to another partner if you want to. Most clients do not, but the work is yours either way.
Usually neither, in our experience. An org can be live and still operationally weak — shipped milestone templates nobody re-pointed at the right recipients, routing rules that never encoded the licensing logic, a field map that drifted from the origination system, reports nobody built. That is recoverable configuration work, not a rebuild. We assess first precisely so you do not pay for a rebuild you do not need.
That is one of the questions the assessment settles, and the answer is frequently not the one on the AppExchange listing. The entry tier carries the marketing library, property listings and the agent portal. The three capabilities most buyers assume are core — the loan origination system sync, lead distribution and texting — sit in the bundle above it. We price your real seat count against the capabilities you will genuinely use, including the add-ons that bill separately.
No. We implement Jungo, we build on core Salesforce, and we have no reseller margin riding on which one you choose. That is deliberate. It is also why our assessments sometimes conclude that a capability you were about to license is forty hours of configuration on the platform you already pay for.
Two to four weeks depending on org size and how many branches are involved. From you we need read access to the org, your origination system and its field map, a walk-through with the people who actually run intake and processing, and your current reporting. We do not need a tidy environment — the mess is the data.
Then we say so, and the assessment is the whole engagement. A two-loan-officer shop with one referral source and no licensing complexity does not need a lending architecture programme, and telling you that is worth more than selling you one.
That is the arrangement we prefer. An internal admin who knows the business plus an outside team that knows the platform and the mortgage layer is a stronger combination than either alone. We scope the split explicitly so nobody is guessing who owns what after go-live.
Next Step
If the platform decision is still open, this is the cheapest hour you will spend
An assessment costs a fraction of a rollout and routinely changes what gets bought. Bring us the org, the process and the quote — we will tell you what we would actually do.
Related: Jungo & Salesforce overview · Salesforce for mortgage lending · All Jungo services · Salesforce integration services
Independent advisory — we implement Jungo and build on core Salesforce, and resell neither
