SkaleCRM industry provider profile

SkaleCRM supplies staff CRM, back-office administration, a branded client area and partner management for brokers and prop firms. Sales activity, account administration, referral commissions and customer communications form its operational role. Trading execution and other specialist functions remain with the relevant connected services.[1]

The prop product connects challenge settings, verification, progress and results to the trader’s record, with segmentation and communications around it. That manages an evaluation’s lifecycle beyond ordinary account creation. The product description does not make Skale the supplier of trading capital, the author of a firm’s commercial challenge rules or the obligor for an eventual payout.[3]

Spotware’s integration directory describes the wider suite as CRM, cashier, back office, affiliate platform, IB portal and marketplace. That breadth is meaningful for a broker seeking fewer disconnected administrative screens. It should still be scoped at the workflow level: a cashier interface, for example, is the place where payment functions appear to a customer; it does not by itself identify the entity processing or holding the funds.[8]

Skale’s current integration page lists MT4, MT5, cTrader SSO, TradeLocker, CMC Markets, DXtrade, X Open Hub and Match-Trader. It also describes click-to-call, automatic connection of answered calls to agents and access to recordings and call analytics within the CRM. These are operational connections with different permissions and dependencies. A platform login connection, a trading-account action and a telephony recording are separate capabilities even when they are available from one staff interface.[4]

The Match-Trader announcement describes a configurable CRM arrangement around the selected trading server, with customer onboarding, account management and payment processes linked into the broker’s operation. It is a dated confirmation of an integration, not a promise that every Match-Trader deployment has identical configuration or entitlements. The platform’s own mobile and web delivery characteristics should also remain distinct from the services purchased from Skale.[9]

Skale advertises an Open API together with connections to ERP, data-warehouse and business-intelligence systems. That supports the prospect of external reporting and reconciliation, but the inspected public product page does not supply a full endpoint reference or establish which writes and exports are available under a specific subscription. A technical evaluation should distinguish a supplied connector from a buyer-maintained API integration.[2]

No numeric Skale subscription tariff, setup price or standard capacity schedule was established from the inspected current official pages. The website directs prospective customers to a commercial enquiry and demo. The pricing status here is therefore quote-only. A quotation needs to identify the forex or prop product, client and partner areas, connected platforms, branding, implementation and support actually being purchased.[7]

The contract should separate the initial project from recurring use and later changes. Current public material did not establish a standard minimum term, renewal mechanism, cancellation notice or charge for leaving the service. Those omissions matter most for a broker transferring a live client base: the commercial discussion needs to include the duration and cost of transition assistance, not just the subscription after launch.

Skale describes cloud delivery using AWS, with backups, multiple availability zones and security monitoring. The compliance page also presents configurable flows across brands and jurisdictions. These are vendor descriptions of the service design; they do not identify the region or account architecture assigned to a particular broker. An implementation plan should tie the selected brands, legal entities and onboarding rules to the actual environment and administrator roles.[5]

Challenge purchase, configuration, progress and final result need to describe the same evaluation, distinguishable from ordinary live or demo accounts. The product page does not establish automatic migration of a historic challenge book.[3]

No detailed current migration specification was located. The useful handover therefore needs an agreed record inventory: customer identifiers and documents, platform-account links, payment records, partner relationships, commission balances, activity history and reports. Reconciliation should identify records that cannot be imported and preserve their external archive. This is an implementation requirement arising from the data involved, not a claim that Skale advertises a particular migration tool.

A NetShop ISP page from January 2022 describes a hosting partnership around Skale’s marketplace and brokerage infrastructure. It is evidence of that historical partner arrangement. It should not be used to infer where today’s default Skale CRM is hosted, or to replace the AWS description on the current site. The actual hosting and support chain belongs in the current order and data-processing terms.[13]

Skale advertises a private Slack channel with 24/7 support and a dedicated service team. Public severity definitions, guaranteed response times and escalation responsibility across connected services were not established.[1]

The contact page is the verified public route in this profile. A support telephone number or direct support email was not established from that page. Existing customers should use their contracted channel and escalation contacts rather than treat a sales-demo form as an emergency support route.[7]

Skale’s compliance page uses regulator names and logos to describe the jurisdictions its workflows aim to accommodate. That is not a register entry showing that Skale is authorised by those regulators, nor evidence that a brokerage becomes compliant by adopting the CRM. The evidenced role is operational technology: configurable onboarding, reporting and access controls supporting the buyer’s processes.[5]

The inspected current site did not provide a readable production SaaS agreement or full data-processing schedule. Customer-data ownership, subprocessor access, residency, retention, deletion and export rights consequently remain unestablished in this profile. A broad security claim cannot settle those terms. They need to describe the specific environment holding identity documents, customer communications and financial records before those records are transferred.

Skale’s current company page says David Nussbaum founded the business in 2008 and identifies him as CEO. It lists Adam Raboch as chief commercial officer, Antony Gelberg as chief technology officer and Neal Daskal as chief financial officer, alongside other management roles. These are current company statements about history and leadership; they do not establish a legal-entity structure or ownership percentages.[6]

An FDCTech issuer announcement dated 11 June 2021 describes SkaleCRM as powered by Fintech Solutions Limited, based in Herzliya, Israel, when reporting its Condor FX Pro integration. That provides a concrete historical operator reference. The inspected current Skale pages did not establish that this remains the contracting entity in October 2026, so the profile preserves that uncertainty rather than presenting the older release as a current contract. FDCTech’s integration announcement is not evidence that it owns Skale.[14]

Operator

SkaleCRM; current contracting entity not publicly established

Service scope

Forex and prop CRM, client portals, back-office and partner workflows, with external trading, payment, identity and investment-allocation integrations.

Customer types

FX and CFD brokerages; Prop trading firms; Multi-brand brokerage groups

Delivery

SaaS; API

Pricing publication

Quote only

Pricing scope

Current numeric subscription and implementation rates were not established; commercial enquiries are directed to the provider.

Implementation

Cloud delivery with configurable workflows and third-party integrations. Public migration and data-exit specifications remain unestablished.

Support

Private Slack support advertised 24/7; contractual response and escalation commitments require confirmation.

Permissions and regulatory scope

Broker operations software. Compliance workflow claims and regulator logos do not establish financial authorisation or a customer’s compliance.

Provider metadata checked 20 Oct 2026Source 1Source 2Source 3Source 5Source 7Source 14

The PAMM connector merits particular care when defining account views. Brokeree describes investor statistics, manager-related records and rating functions alongside the integration. An IB earning acquisition commission and an investor allocating money to a strategy are different relationships, even if both appear in one branded portal. Keeping those roles and balances separate improves the clarity of customer statements and operational reconciliation.[11]

The current source set supports workflow automation, reporting and integrations. It did not establish a named Skale AI agent, a model that approves customers autonomously or a documented generative-AI action policy. Automated challenge verification and CRM task handling should therefore be described as their documented functions, without adding an unsupported AI product claim.

The most consequential remaining document is the current customer agreement. It should identify the actual supplier and the broker’s rights to obtain usable customer, account and partner data during service and at exit. This is especially important where the selected portal, challenge workflow and commission model make the CRM a central operational record rather than merely a sales contact list.