mysherpas

Name: mysherpas
Brand: mysherpas

AI Native

Pioneering the new era in lending technology.

Est 2021

LinkedIn 2K|Website|Web traffic 2K|FTEs 17|HQ Salt Lake City, Utah, US

Published Jul 15, 2026

01Common complaints

- Organizations that require a large volume of independent third-party reviews (G2, TrustRadius, Gartner Peer Insights) as part of procurement may find limited public review coverage. - If a full LOS replacement is required rather than a collaboration and workflow overlay, vendors that provide end-to-end commercial origination and booking suites may be more appropriate. - If procurement requires a publicly accessible security portal with downloadable SOC reports, subprocessor lists, hosting-region details, encryption specifications, and penetration test summaries, expect to request such materials directly from the vendor and allow additional time for diligence. - For highly bespoke workflows that demand deep configurability at every origination and servicing step, confirm that the vendor’s configuration model meets requirements before committing.

Deal disqualifiers (poor fit)

Organizations that require extensive public security documentation before initiating diligence
Buyers seeking a purely self-service SaaS with published pricing and minimal vendor engagement
Institutions with a well-adopted, deeply integrated LOS and document portal that are unwilling to change existing workflows

Publicly acknowledged limitations

No formal public limitations list was found in the materials reviewed.

Roadmap / future features

Vendor blog content references an evolving product roadmap and ambitions for lead-generation features; public descriptions did not include detailed delivery dates or commitments.

Scale limitations

No documented throughput or user-scale ceilings were found publicly.

Security/compliance gaps (public documentation)

While SOC claims appear in vendor social media and company summaries, detailed security documentation (hosting regions, encryption specifics, penetration test disclosures, and subprocessor lists) was not readily available publicly.

API/integration constraints

An open API is described in vendor materials, but no publicly accessible API documentation, rate limits, authentication model, or webhook/eventing documentation was found in reviewed sources. Buyers should request API documentation, SLA terms, and integration support details.

Negative reviews (low-rating) and churn reasons

No substantive negative reviews or churn narratives were identified in public review platforms in the sources reviewed.

02Why they buy

Differentiators observed in vendor materials

The vendor positions the product as a workflow overlay that consolidates documents, communications, and task lists into a lending-specific workspace intended to complement existing LOS and core systems.
A defined implementation and adoption methodology is emphasized as part of the vendor’s customer engagement model.
The vendor has announced issued patents related to its technology; the specific patent claims were not analyzed in this report.

Areas where competitors may have the advantage

Broader ecosystems, more extensive integrations, and more visible market references with larger incumbents (for example, nCino or Abrigo).

03Field reports

What was found (and not found)

No substantive product review pages were located on mainstream third-party review platforms in the accessible material reviewed (G2, TrustRadius, Gartner Peer Insights).
Community forums (Reddit, Hacker News) did not surface substantive discussions about the product in accessible searches.

This indicates that many publicly available testimonial items are vendor-selected quotes, press releases, and partner write-ups rather than independent review volumes.

Positive testimonials (vendor/PR/association sourced)

Examples of published customer quotes in vendor and PR materials include: - A customer leader describing a switch from a competitor, praising the vendor’s support and strategic alignment. - A COO from a customer stating the platform "streamlines every step" and assists with focusing on closing deals (vendor-provided quote). - A press release describing a short implementation period and training of a large customer team. These are vendor- or PR-supplied quotes and should be treated as selected testimonials.

What customers appear to value (from available sources)

Consolidation of documents and communications into a single shared workspace, reducing friction associated with email and multiple document stores.
Emphasis on guided implementation and adoption methodologies rather than self-serve onboarding.
Reported reductions in manual document handling and improvements in turnaround times in selected customer narratives.

Buyer caution on testimonial quality

Because many quotes originate from vendor materials and PR, they are subject to selection bias and may over-represent successful deployments. Independent, unprompted review volume appears low or absent publicly.

Case study: InterMountain Business Lending (IMBL) — association write-up

Reported outcomes in the association article include: - Reported reduction in manual document handling (vendor- or customer-reported large reduction). - Reported improvement in application-to-close time by a modest, vendor-reported amount. - A team projection to increase loan volume over a multi-year horizon. Critical evaluation: - These metrics are not independently audited and appear to come from a vendor-promoted case study or webinar. - Baseline definitions (what counts as manual handling, loan cohorts, time windows) are not disclosed. - The figures are useful prompts for diligence questions: ask for methodology, sample size, and measurement windows.

Case study: Mountain America Credit Union (MACU) — press release

Claims in press materials include: - Implementation completed in a short, vendor-marketed timeframe and training of a sizable lending staff. - Migration of certain workflows away from existing document stores as part of consolidation. Critical evaluation: - This content is distributed via a press release and contains vendor-aligned framing. "Industry standard" benchmarks in the release are broad and may not be comparable to full LOS implementations. - Buyers should confirm scope of capabilities implemented in the initial deployment versus subsequent phases.

Engineering/DevOps case study: SPK & Associates

A vendor-to-vendor case study describes work performed to improve deployment automation and DevOps processes, including reported reductions in deployment time and a DevSecOps emphasis.

Critical evaluation:

This is a services-provider case study about internal delivery processes and does not directly evidence uptime, security posture, or end-customer support quality.

04Best fit

Company sizes

Based on vendor positioning and cited implementations:

Likely fit: mid-sized credit unions and community banks, specialized commercial/SBA lenders, and broker shops.
Vendor-provided examples reference deployments with teams of varying sizes; these are single-case examples and should be validated for broader scope.

Industries/verticals

Financial services: commercial lending, SBA lending, private lending, and certain auto finance segments.

Roles and personas

Economic buyers: heads of commercial lending, senior lending executives, COOs, CIOs (for security and integration approvals)
Champions: loan operations managers, SBA operations leads, credit administration
End users: relationship managers, loan officers, processors, underwriters, and borrower coordinators

Qualification criteria (fit indicators)

High email/document friction and dispersed borrower communication workflows
Desire to standardize needs lists and increase transparency of loan status across stakeholders
Organizations prepared to adopt a new workspace tool and retire or consolidate legacy document-sharing workflows

05The pitch

What the product does (objective core value proposition)

mysherpas is a cloud-based commercial lending workflow and collaboration platform. The vendor describes it as a centralized repository for loan teams and borrowers by consolidating loan document collection, communications, task management, and pipeline visibility into one shared workspace. Vendor materials indicate goals of reducing fragmented email and attachment workflows, standardizing needs lists, and decreasing application-to-approval time using automation and AI-assisted tasking. A key vendor positioning is that mysherpas is intended to operate alongside an institution’s existing Loan Origination System (LOS) or core banking platform—serving as a workflow and collaboration layer that centralizes work performed across tools such as email, Teams, SharePoint, Box/Dropbox, Slack, and CRM.

Target market and market positioning

**Target buyers/users (based on vendor and association listings):** - Credit unions, community banks, and non-bank financial institutions (NBFIs) - SBA 7(a) / SBA 504 lenders, CDCs, and commercial loan brokers - Private lenders and certain auto/captive finance players **Positioning:** - The vendor describes the product as a lending collaboration and workflow platform supported by issued patents and a defined implementation approach focused on operational adoption. - The company emphasizes an implementation and adoption methodology (branded in vendor materials) as a differentiator in addition to product features.

Get a comprehensive analysis of mysherpas including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →

Published Jul 15, 2026

01Common complaints

Organizations that require a large volume of independent third-party reviews (G2, TrustRadius, Gartner Peer Insights) as part of procurement may find limited public review coverage.
If a full LOS replacement is required rather than a collaboration and workflow overlay, vendors that provide end-to-end commercial origination and booking suites may be more appropriate.
If procurement requires a publicly accessible security portal with downloadable SOC reports, subprocessor lists, hosting-region details, encryption specifications, and penetration test summaries, expect to request such materials directly from the vendor and allow additional time for diligence.
For highly bespoke workflows that demand deep configurability at every origination and servicing step, confirm that the vendor’s configuration model meets requirements before committing.

Deal disqualifiers (poor fit)

Organizations that require extensive public security documentation before initiating diligence
Buyers seeking a purely self-service SaaS with published pricing and minimal vendor engagement
Institutions with a well-adopted, deeply integrated LOS and document portal that are unwilling to change existing workflows

Publicly acknowledged limitations

No formal public limitations list was found in the materials reviewed.

Roadmap / future features

Vendor blog content references an evolving product roadmap and ambitions for lead-generation features; public descriptions did not include detailed delivery dates or commitments.

Scale limitations

No documented throughput or user-scale ceilings were found publicly.

Security/compliance gaps (public documentation)

While SOC claims appear in vendor social media and company summaries, detailed security documentation (hosting regions, encryption specifics, penetration test disclosures, and subprocessor lists) was not readily available publicly.

API/integration constraints

An open API is described in vendor materials, but no publicly accessible API documentation, rate limits, authentication model, or webhook/eventing documentation was found in reviewed sources. Buyers should request API documentation, SLA terms, and integration support details.

Negative reviews (low-rating) and churn reasons

No substantive negative reviews or churn narratives were identified in public review platforms in the sources reviewed.

02Why they buy

Differentiators observed in vendor materials

The vendor positions the product as a workflow overlay that consolidates documents, communications, and task lists into a lending-specific workspace intended to complement existing LOS and core systems.
A defined implementation and adoption methodology is emphasized as part of the vendor’s customer engagement model.
The vendor has announced issued patents related to its technology; the specific patent claims were not analyzed in this report.

Areas where competitors may have the advantage

Broader ecosystems, more extensive integrations, and more visible market references with larger incumbents (for example, nCino or Abrigo).

03Field reports

What was found (and not found)

No substantive product review pages were located on mainstream third-party review platforms in the accessible material reviewed (G2, TrustRadius, Gartner Peer Insights).
Community forums (Reddit, Hacker News) did not surface substantive discussions about the product in accessible searches.

This indicates that many publicly available testimonial items are vendor-selected quotes, press releases, and partner write-ups rather than independent review volumes.

Positive testimonials (vendor/PR/association sourced)

Examples of published customer quotes in vendor and PR materials include:

A customer leader describing a switch from a competitor, praising the vendor’s support and strategic alignment.
A COO from a customer stating the platform "streamlines every step" and assists with focusing on closing deals (vendor-provided quote).
A press release describing a short implementation period and training of a large customer team.

These are vendor- or PR-supplied quotes and should be treated as selected testimonials.

What customers appear to value (from available sources)

Consolidation of documents and communications into a single shared workspace, reducing friction associated with email and multiple document stores.
Emphasis on guided implementation and adoption methodologies rather than self-serve onboarding.
Reported reductions in manual document handling and improvements in turnaround times in selected customer narratives.

Buyer caution on testimonial quality

Case study: InterMountain Business Lending (IMBL) — association write-up

Reported outcomes in the association article include:

Reported reduction in manual document handling (vendor- or customer-reported large reduction).
Reported improvement in application-to-close time by a modest, vendor-reported amount.
A team projection to increase loan volume over a multi-year horizon.

Critical evaluation:

These metrics are not independently audited and appear to come from a vendor-promoted case study or webinar.
Baseline definitions (what counts as manual handling, loan cohorts, time windows) are not disclosed.
The figures are useful prompts for diligence questions: ask for methodology, sample size, and measurement windows.

Case study: Mountain America Credit Union (MACU) — press release

Claims in press materials include:

Implementation completed in a short, vendor-marketed timeframe and training of a sizable lending staff.
Migration of certain workflows away from existing document stores as part of consolidation.

Critical evaluation:

This content is distributed via a press release and contains vendor-aligned framing. "Industry standard" benchmarks in the release are broad and may not be comparable to full LOS implementations.
Buyers should confirm scope of capabilities implemented in the initial deployment versus subsequent phases.

Engineering/DevOps case study: SPK & Associates

A vendor-to-vendor case study describes work performed to improve deployment automation and DevOps processes, including reported reductions in deployment time and a DevSecOps emphasis.

Critical evaluation:

This is a services-provider case study about internal delivery processes and does not directly evidence uptime, security posture, or end-customer support quality.

04Best fit

Company sizes

Based on vendor positioning and cited implementations:

Likely fit: mid-sized credit unions and community banks, specialized commercial/SBA lenders, and broker shops.
Vendor-provided examples reference deployments with teams of varying sizes; these are single-case examples and should be validated for broader scope.

Industries/verticals

Financial services: commercial lending, SBA lending, private lending, and certain auto finance segments.

Roles and personas

Economic buyers: heads of commercial lending, senior lending executives, COOs, CIOs (for security and integration approvals)
Champions: loan operations managers, SBA operations leads, credit administration
End users: relationship managers, loan officers, processors, underwriters, and borrower coordinators

Qualification criteria (fit indicators)

High email/document friction and dispersed borrower communication workflows
Desire to standardize needs lists and increase transparency of loan status across stakeholders
Organizations prepared to adopt a new workspace tool and retire or consolidate legacy document-sharing workflows

05The pitch

What the product does (objective core value proposition)

A key vendor positioning is that mysherpas is intended to operate alongside an institution’s existing Loan Origination System (LOS) or core banking platform—serving as a workflow and collaboration layer that centralizes work performed across tools such as email, Teams, SharePoint, Box/Dropbox, Slack, and CRM.

Target market and market positioning

Target buyers/users (based on vendor and association listings):

Credit unions, community banks, and non-bank financial institutions (NBFIs)
SBA 7(a) / SBA 504 lenders, CDCs, and commercial loan brokers
Private lenders and certain auto/captive finance players

Positioning:

The vendor describes the product as a lending collaboration and workflow platform supported by issued patents and a defined implementation approach focused on operational adoption.
The company emphasizes an implementation and adoption methodology (branded in vendor materials) as a differentiator in addition to product features.

Get a comprehensive analysis of mysherpas including market position, competitive landscape, adoption trends, and peer benchmarks.

Download full report →