Every problem gets quoted as the same project
Assessment, build, integration, migration and support are five different engagements with five different risk profiles. Quoted as one lump they are impossible to compare and easy to overrun.
Salesforce · Jungo Service Lines
Five different projects. One number on the quote.
Assessment, build, integration, migration and support are separate engagements with separate risks — and quoting them as one lump is how programmes overrun. We name all six, price them separately, and run them under one architect so nobody re-explains your operation at a handoff. Take the first phase, or take all of it.
6
500+
40+
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 ways a Jungo programme quietly stops paying for itself
These are the patterns we are called in to fix, and every one of them traces back to a service that was never scoped as its own piece of work.
The build finishes and ownership does not start
Go-live is treated as the finish line. Six months later the Flows nobody maintained are the reason loan officers stopped trusting the pipeline.
History is discovered late
The origination sync does not backfill closed loans. Teams find this out after cutover, when the reporting that justified the project has nothing behind it.
Integrations are scoped as logos, not as data flows
"We integrate with Encompass" is not a scope. Which fields, in which direction, at what cadence, and who owns the mapping when the origination system changes — that is a scope.
Customization accumulates without governance
Three people build Flows on the same object over two years. Nothing is documented, nothing is tested, and every new request takes longer than the last.
Support means training, not fixing
Teams discover that the help they bought explains how to do it rather than doing it — which is fine, unless nobody on staff has the time or the platform skill to act on the explanation.
Six services, one accountable architect
Named separately because they are genuinely different engagements — different skills, different risks, different prices.
Jungo — The Mortgage App is a mortgage CRM built on Salesforce, sold by the seat and listed on the AppExchange since 2008. It supplies a Loan record that carries the transaction separately from the borrower contact, shipped milestone alerts, a referral-partner programme with an agent portal, borrower document collection, and a maintained sync to five loan origination systems. Underneath it, everything is stock Salesforce: Flow, reports, tasks, events and cases are used as they ship.
That architecture is why service boundaries matter here. Because the platform underneath is standard, most capability is reachable two ways — by licensing the mortgage layer or by building on Salesforce. Which way you go is a consulting decision. Making it work is implementation. Pushing it past the shipped behaviour is customization. Connecting it to the loan file is integration. Bringing history across is migration. Keeping it alive is support.
We work with growing, mid-market, and enterprise organizations that need help with complex CRM implementations, integrations, and business system challenges. We implement Jungo and we build on core Salesforce; we resell neither, so nothing in our commercial model prefers one answer over the other.
The six engagements, and what each one actually buys
Each links through to its own page with scope, process and pricing shape. Most clients take two or three, not all six.
Consulting & Assessment
What you have, what to buy versus build, what the architecture should be and in what order — with the licence arithmetic written down.
- Current-state org and process assessment
- Platform-fit and three-year licence modelling
- Architecture blueprint and sequenced roadmap
- Governance and admin-ownership design
- See Jungo consulting in detail →
Implementation
The build: data model, routing, milestone matrix, origination sync, reporting and a rollout your loan officers actually adopt.
- Contact, Loan and referral data-model configuration
- Routing rules including licensing and round robin
- Milestone alerts and recipient matrices per party
- Phased rollout with parallel running and role training
- See Jungo implementation in detail →
Customization
Where configuration runs out and real development starts — with the boundary named before the work is quoted.
- Custom objects, fields and record types
- Flow automation beyond the shipped templates
- Apex and Lightning Web Components where warranted
- Agent portal and pre-approval letter extensions
- See Jungo customization in detail →
Integrations
The origination system, pricing engines, document portals, texting and everything reached through the API — scoped as data flows, not logos.
- Encompass over ICE Partner Connect, with persona setup
- Calyx Point, Byte, LendingPad and Velocity
- Floify, DocsBar, Optimal Blue, Mortgage Coach, Homebot
- Twilio texting, dialers and email or calendar sync
- See Jungo integrations in detail →
Data Migration
Contacts, loans, partners, activity and documents brought across and reconciled — including the history the live sync will never backfill.
- Legacy CRM extraction and profiling
- Closed-loan history the origination sync does not cover
- Duplicate resolution and record-owner mapping
- Parallel-run validation and reconciliation reporting
- See Jungo migration in detail →
Support & Managed Services
Somebody has to own a Flow-driven system. Where that is not an internal admin, it is us — at whatever level matches your change volume.
- Fractional or fully managed Salesforce administration
- Milestone, routing and automation change requests
- Release monitoring and sync-health checks
- User onboarding, permissions and adoption support
- See Jungo support in detail →
Three ways to work with us, and when each one fits
The commercial shape matters as much as the scope. Picking the wrong one is how good projects end up feeling expensive.
| Fixed-scope project | Phased programme | Retained capacity | |
|---|---|---|---|
| Shape | One defined outcome, fixed scope, fixed range. | A sequence of scoped phases, each re-baselined from the last. | A standing allocation of architect and admin time each month. |
| Best for | An assessment, a single integration, a defined migration. | A full implementation, or a multi-branch rollout. | Life after go-live, and teams with no internal admin. |
| You get | A deliverable and a date. | Working software at the end of each phase, not only at the end. | Change requests, monitoring and a named person who knows your org. |
| Watch for | Genuinely new requirements mid-flight need a change order. | Phase one has to be scoped well enough to inform phase two. | Capacity is only worth buying where change volume is real. |
| Typical duration | Two to eight weeks. | Three to five months for a multi-branch lender. | Monthly, rolling, cancellable. |
From first call to a system somebody owns
Five stages. The second one is short, written and cheap on purpose — it is what makes everything after it accurate.
Scoping Call
Thirty minutes to establish which of the six services you actually need, and in which order. Frequently it is fewer than you arrived expecting.
Assessment
Short and written. What exists, what it is costing, and what the options are — the input every other engagement is scoped from.
Statement of Work
Each workstream priced separately with its own effort range and risk notes, so you can take all of it, some of it, or the first phase only.
Deliver
Build, integrate, migrate, test and roll out — in phases, against the baselines the assessment set, with a named architect throughout.
Operate
Documented handover and, where you want it, ongoing admin capacity. Go-live is a milestone, not the end of the engagement.
What the work actually produces
Two engagements from the same discipline: rebuild how leads reach a person, and make every channel that produces them measurable.
★★★★★
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
★★★★★
Phone was our biggest channel and our blindest one. Once call data landed against the right record in Salesforce we could finally attribute 100% of inbound calls to a source, and the marketing spend conversation changed completely.
Marketing Operations Manager High-volume inbound-call practice Call Attribution
Inbound-Call Driven Firm
Invoca connected to Salesforce so every inbound call is attributed to its source and scored alongside digital channels.
100% Inbound call attribution
1 View across call and digital channels
0 Manual call logging by the team
Not a reseller. An architectural partner.
We are a Salesforce Partner and a HubSpot Partner. We implement Jungo. We hold no reseller margin on the mortgage layer, and that shapes the advice.
Six named services, priced separately
You can see what each engagement is, what it costs and what it depends on. A single undivided number is convenient for a vendor and impossible for a buyer to evaluate.
We build, we do not only advise
The vendor’s support function trains rather than builds — its published position is that the user stays in control of the mouse. That is a legitimate model, and it is not the one most lending teams need when the Flow is broken on a Friday.
We work the whole estate, not only the mortgage layer
Marketing automation, document generation, dialers, accounting, HubSpot on the demand side. When the right answer sits outside Jungo, we are not structurally unable to say so.
We design for whoever owns it next
Documented architecture, named ownership, change control on Flow work. The measure of a good build is whether the person who inherits it can safely change it.
One accountable architect across every service
Assessment, build, integration, migration and support run under the same architect. Nobody re-explains the operation at each handoff, because there is no handoff.
Answers before the first call
Six, and they are genuinely different engagements: consulting and assessment, implementation, customization, integrations, data migration, and ongoing support. Most clients start with one and add others. The commonest sequence is assessment, then implementation with migration folded in, then support once the system is live and somebody has to own it.
Neither. We implement Jungo — we are a Salesforce Partner and a HubSpot Partner, and we hold no reseller agreement for the mortgage layer. You buy the licence from the vendor at the vendor’s price. That is what lets an assessment conclude you do not need it.
Different scope and a different posture. The vendor’s services are billed hourly and its support function trains rather than builds — the published position is that the user will be in control of the mouse. We build, and we work across the whole Salesforce estate rather than only the mortgage layer, which matters when the answer involves core platform work, another system, or deciding not to use a Jungo module at all.
Yes, and for a lot of lending teams that is the realistic model. Jungo automation is Salesforce Flow, which means anything can be built and someone has to own it. We provide that capacity on a retained basis, at whatever level matches your change volume, and we document as we go so you are never locked in.
Regularly. We begin with a short assessment rather than by continuing blind — an inherited org usually contains decisions we would not have made, and some of them are load-bearing. You get a written picture of what exists and what it would cost to finish, continue or redirect, before anyone commits to a plan.
If the platform decision is still open, consulting. If it is settled and nothing is built, implementation. If it is built and underperforming, an assessment first — a struggling org is far more often a configuration and ownership problem than a rebuild. If it is working and nobody owns it, support.
We deliver across the US, Canada, the UK, the UAE, Australia and New Zealand. The mortgage layer and its origination-system integrations are strongly US-oriented, so outside the US the work more often lands on core Salesforce with a lending data model we design rather than licence.
Next Step
Tell us which part is broken, and we will tell you which service fixes it
Frequently that is a shorter engagement than the one you came in expecting. The scoping call is thirty minutes and costs nothing.
Related: Jungo & Salesforce overview · Salesforce for mortgage lending · Jungo consulting · Salesforce integration services
Six named services · one accountable architect · no reseller margin
