nCino Pricing Explained: Licenses, Implementation Fees and a Worked Example
The nCino subscription is usually the smallest number you'll negotiate. This piece adds up licenses, Salesforce add-ons, partner fees and modules for a hypothetical 60-user commercial lending team.
What an nCino Quote Covers and What It Leaves Out
Your first nCino quote will make the platform look simpler than it is. nCino pricing starts with a recurring subscription, but the full cost has four layers: the nCino license, the Salesforce platform it runs on, the implementation partner who configures it, and the add-on modules you'll want by year two. Banks that budget only for the first layer usually end up asking the board for more money about a year into the project.
For most of its history, nCino priced its loan origination software per user, and the price depended on the user's role. A relationship manager or credit analyst who works in the system all day costs more than an executive who only approves deals or reads dashboards. More recently nCino has also offered platform-style pricing on some new contracts, based on things like asset size or loan volume rather than headcount. Which model you're offered depends on your region, your segment (community bank, regional bank, enterprise, credit union) and when you sign. Ask which model you'll be quoted before the first workshop. Seat-based pricing grows with hiring. Platform pricing grows with the balance sheet, and that changes how you forecast costs.
A commercial lending subscription typically includes:
- Core origination workflow: pipeline management, credit memo and approval routing, document collection and closing checklists.
- Relationship and entity data: borrower, guarantor and collateral records linked across deals.
- Embedded platform license: many contracts bundle the Salesforce runtime license each user needs into the nCino fee. Not all do, so check the order form.
- Standard support and regular releases: nCino ships updates on a recurring cycle, and your team has to regression-test each one.
These are usually priced separately: automated financial spreading, portfolio and covenant monitoring, digital onboarding and account opening, borrower portals, analytics, extra sandboxes, extra data storage and integration middleware. Get each one quoted as its own line item, including the ones you don't plan to buy yet. Once you've signed, you lose the leverage to get a good price on them.
The Salesforce Layer: Platform Costs That Show Up on the Invoice
nCino runs natively on Salesforce. That has real benefits: a mature security model, a large pool of administrators and developers in most markets, and the option to put lending and CRM in one data model. It also means part of your bill follows Salesforce's price list, not nCino's.
These are the platform items buyers miss most often:
- Data and file storage. Commercial lending produces a lot of documents: financial statements, appraisals, legal agreements. Base storage runs out quickly once you migrate historical loan files. Extra storage is sold in blocks. For a mid-sized lender it can add a five-figure annual cost unless documents go to an external content management system.
- Encryption and event monitoring. Many banks require field-level encryption with customer-managed keys and detailed audit logs. On Salesforce that usually means Shield or a comparable add-on, typically priced as an uplift on your underlying platform spend.
- Full-copy sandboxes. A test environment that mirrors production data often costs extra. You need at least one for user acceptance testing and release regression.
- CRM licenses for non-lending users. If treasury, deposits or wealth teams need the same relationship data, they may need separate Financial Services Cloud or Sales Cloud licenses.
- Integration tooling. Links to the core banking system, credit bureaus, document generation and e-signature often run through middleware such as MuleSoft or another iPaaS, which is priced separately.
Data residency rules differ by region. Salesforce runs local infrastructure in a number of jurisdictions, including the EU, the UK, Canada, Australia, India and Japan. Banks subject to GDPR, UK outsourcing and operational resilience rules, the Reserve Bank of India's outsourcing and data storage expectations, or Gulf regulators' cloud frameworks should confirm where the instance will be hosted. They should also ask whether that choice changes the price or limits any features. Your compliance team and outside counsel should check any outsourcing or cloud notification your regulator requires. The vendor's assurance alone isn't enough.
nCino Implementation Cost: Partners, Timelines and Where Budgets Break
On most commercial lending projects, implementation costs as much as the first two or three years of subscription, and often more. nCino has its own professional services team and also works with systems integrators. These range from global consultancies such as Accenture, Deloitte and KPMG to specialist Salesforce-and-banking firms. The partner you pick affects total cost more than almost any other decision.
Day rates depend heavily on region and delivery model. Onshore senior consultants in North America, the UK, Western Europe and Australia typically bill about $1,200 to $2,200 a day. Blended teams, with onshore leads and delivery staff in India, Eastern Europe or Latin America, often come in around $500 to $1,000 a day. These are typical 2026 market ranges and vary by contract.
A commercial lending rollout for 40 to 100 users typically takes 9 to 15 months. The main cost drivers:
- Loan products and approval paths. Ten credit policies, each with its own authority matrix, cost far more to configure than three.
- Core banking integration. Two-way booking into a modern core with documented APIs is much cheaper than batch files into a legacy mainframe.
- Data migration. This is the workstream teams most often underestimate: moving active loans, relationships, collateral and covenants, and cleaning them up first.
- Credit memo and document templates. Every template has to be designed, reviewed and tested.
- Regulatory reporting fields. Local requirements add fields and validation rules. Examples include AnaCredit-style loan data in the eurozone, IFRS 9 staging inputs and Basel risk-weighting data.
Overruns tend to happen in the same three places. Scope is still open when the build starts. Data migration is estimated before anyone has profiled the legacy data. And the bank doesn't free up enough of its own subject-matter experts. A partner can configure workflows, but only your credit team knows what the approval policy really is. Plan to backfill two to four senior lending and credit staff for most of the project. If you can't release them, push the start date back. Starting without them almost always costs more.
Worked Example: Costing a Hypothetical 60-User Commercial Lending Team
This example is hypothetical. All figures are illustrative, typical 2026 market ranges that vary by contract, region and negotiation. Confirm every line with nCino and your shortlisted partners.
Say a regional bank with a mid-market commercial lending business is replacing spreadsheets, a legacy origination tool and approvals done by email. Its 60 users:
- 20 relationship managers
- 12 credit analysts
- 6 credit officers and approvers
- 10 loan operations and closing staff
- 6 portfolio monitoring staff
- 6 executives, auditors and read-only users
Treat 48 as full users at an assumed $200 to $300 per user per month, and 12 as light users at $50 to $100. The bank also buys automated spreading and portfolio monitoring, plus Salesforce storage, encryption and one full sandbox.
| Cost line | Year 1 (USD, indicative) | Recurring annual (USD, indicative) |
|---|---|---|
| Full-user subscriptions (48) | $115,000 – $173,000 | $115,000 – $173,000 |
| Light-user subscriptions (12) | $7,000 – $14,000 | $7,000 – $14,000 |
| Add-on modules (spreading, portfolio monitoring) | $35,000 – $80,000 | $35,000 – $80,000 |
| Salesforce storage, encryption, sandbox | $15,000 – $40,000 | $15,000 – $40,000 |
| Integration middleware | $20,000 – $60,000 | $20,000 – $60,000 |
| Implementation partner fees | $600,000 – $1,400,000 | – |
| Data migration and clean-up | $75,000 – $200,000 | – |
| Internal backfill and project team | $250,000 – $500,000 | – |
| Ongoing admin and development (1.5–2 FTE or managed service) | $75,000 – $175,000 (half year) | $150,000 – $350,000 |
| Total | $1.19M – $2.64M | $342,000 – $717,000 |
Assume the software lines go up about 5% a year. Over five years, total cost of ownership comes to roughly $2.7 million to $5.7 million. With implementation spread over the term, that's about $9,000 to $19,000 per user per year. Admin salaries are a big part of the recurring line. They're much lower in India, Southeast Asia or Eastern Europe than in London, Sydney or New York, so banks in those markets should adjust that line first.
The example shows two things. First, the subscription usually starts at signing, not at go-live. With a 12-month build, the bank pays a full year of licenses before it books a single loan through the system. That's why ramped licensing (covered below) is worth fighting for. Second, software is only about half of the recurring cost. The rest is the people who keep the platform running. That's the biggest difference between Salesforce-based systems and more tightly packaged alternatives, and it's the line most business cases leave out.
Loan Origination System Pricing: nCino Against the Alternatives
nCino rarely wins on price. It wins when a bank wants one configurable platform for origination, onboarding and relationship data, and is comfortable committing to Salesforce. A typical commercial lending shortlist includes several other approaches, and each one costs money in different places.
| Option | Typical pricing model | Indicative annual software cost, 60 users (USD) | Typical implementation | Best fit |
|---|---|---|---|---|
| nCino | Per user by role, or platform-based on some contracts | $190,000 – $370,000 | $600,000 – $1.5M; 9–15 months | Banks wanting a broad, configurable lending and onboarding platform |
| Moody's CreditLens | Per user or enterprise license, often with spreading and risk-rating modules | $150,000 – $350,000 | $300,000 – $1M; 6–12 months | Credit-risk-led teams where spreading and rating matter most |
| Finastra commercial lending suite | Subscription or term license; varies widely by product | $150,000 – $400,000 | $400,000 – $1.2M; 9–18 months | Institutions already running other Finastra products |
| Temenos, Oracle or other core-vendor lending modules | Often bundled with core or priced by volume and asset size | $100,000 – $350,000 incremental | Varies; often part of a wider core program | Banks consolidating vendors around a core replacement |
| Low-code build (Pega, Appian, Newgen and similar) | Platform license plus users or cases | $120,000 – $300,000 | $500,000 – $1.5M; 9–18 months | Banks with unusual workflows and strong internal engineering |
| Regional or segment specialists | Per user or per loan, often lower minimums | $60,000 – $200,000 | $100,000 – $500,000; 4–9 months | Smaller lenders or single-market institutions |
All figures are typical 2026 market ranges and vary by contract, region and scope. Local pricing differs, so confirm with vendors.
Where a vendor can actually deliver matters as much as price. nCino is strongest in North America, the UK and Ireland, parts of continental Europe, Australia and New Zealand, and Japan. In the Middle East, Africa, Latin America and much of Southeast Asia, find out how many qualified local partners exist before you shortlist. A strong platform with two capable partners in your market is riskier than a weaker one with ten, because you can't run a competitive bid with only two partners and you can't easily replace one that underdelivers. Some vendors, such as Abrigo, are serious options for US community banks but have limited reach elsewhere.
For a 60-user commercial lending team that already uses Salesforce for CRM, nCino's higher upfront cost is usually justified, because you avoid running a second platform with a second admin team. If your bank doesn't use Salesforce and your main problem is credit analysis rather than workflow, a credit-risk-focused tool will usually cost less over five years.
Negotiation Levers and Red Flags Before You Sign
You have the most leverage before the order form is signed, while the vendor still has competitors in the deal. These levers move the numbers:
- Ramped licensing. Have subscriptions grow as users go live. For example, pay 25% during the build, 75% at pilot and 100% at full rollout. On a 12-month build, this can cut a large share of first-year license spend.
- Renewal price caps. Cap annual increases, commonly somewhere in the 3% to 7% range, in the master agreement itself, not in a side letter.
- Written role definitions. Define full and light users in the contract, so a portfolio monitor who edits one field isn't reclassified as a full user at true-up.
- Locked module pricing. Fix today's price for modules you might add in years two and three.
- Fixed-fee or capped partner work. Put well-defined workstreams, such as template build and standard integrations, on fixed fees. Keep time-and-materials for work that's genuinely open.
Stop and push back if you see any of these:
- A partner estimate produced before anyone has seen your credit policy, product list or legacy data.
- No named lead consultant, or a lead with no commercial lending go-lives in your region.
- Storage, encryption and sandbox costs marked "to be confirmed."
- Multi-year commitments with termination fees but no service-level credits.
- Nothing in writing on data residency, exit assistance or data export formats.
Rules on liability, data protection and regulatory audit rights differ by jurisdiction. Have your legal team or outside counsel check the contract against your local outsourcing rules before you sign.
Use this rule. Rebuild the worked example table for your own bank, have the vendor and partner fill in every line in writing, and compare five-year totals rather than annual subscriptions. If more than two lines are still blank or marked as estimates at final negotiation, you aren't ready to sign. Send the quote back and ask for firm numbers.
Frequently asked questions
How much does nCino cost per user?
For commercial lending, full users typically fall somewhere around $150 to $300 per user per month (a typical 2026 market range), and light or read-only users cost much less. Some newer contracts use platform pricing tied to asset size or loan volume instead of seats. Prices vary by contract, region and negotiation, so ask nCino for a written quote that includes role definitions.
Do I need to buy Salesforce licenses separately to use nCino?
Many contracts bundle the Salesforce runtime license for nCino users into the nCino subscription. Extra storage, encryption add-ons, full-copy sandboxes, integration middleware and CRM licenses for non-lending staff are often priced separately. Go through the order form line by line to confirm what's included.
How long does an nCino implementation take, and what does it cost?
A commercial lending rollout for 40 to 100 users typically takes 9 to 15 months. Partner fees often fall somewhere between about $600,000 and $1.5 million, plus data migration and internal staffing. The main drivers are the number of loan products, how complex the core integration is, and the quality of your legacy data. These are typical 2026 market ranges, so get firm quotes from partners.
Does nCino's subscription start at signing or at go-live?
Under many contracts the subscription starts at signing, so with a long build you could pay up to a year of licenses before any loans go through the system. Negotiate ramped licensing that increases as users go live, and get the schedule written into the order form.
Written by the Adviser Hub Cloud editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.