You have maybe fifteen minutes at a stand before the queue behind you gets restless. Spending it on a feature tour is a waste, because every vendor at the show has the same feature list on the same pull-up banner. Spend it on the questions where answers actually diverge.
What follows is the list we would use ourselves if we were buying rather than building. It works on any trading platform, CRM or risk vendor, and it is deliberately blunt.
Pricing: what is the second invoice
The first number is the one on the banner. The second number is the one that ends contracts. Ask for the full structure: setup fee, monthly licence, per-account or per-user charges, per-server costs, data feed, support tiers, and what triggers a jump to the next price band. Then ask what a firm with 2,000 funded accounts pays versus a firm with 200, in the same sentence.
Ask specifically about volume-linked pricing. A percentage of client deposits or a per-lot charge means the vendor's bill grows exactly when your margin is thinnest. Ask whether the price changes if you switch liquidity providers or add a second brand. Our CRM pricing guide sets out the models you are likely to meet.
Ownership: whose licence, whose data, whose brand
Three separate questions that vendors often blur together. Who holds the platform licence, you or them. Where does client data live and who can read it. And whose name appears on the trader's screen, in the emails and in the app store listing.
The white label word is used loosely enough to be meaningless on a show floor, so ask for specifics rather than the label. Some arrangements brand everything down to the terminal. Others brand the portal and emails while the trading application stays under the vendor's name. Both can be reasonable. Being surprised after signing is not. We wrote about the gap between the promise and the arrangement in white label licence myths.
Ask for the exit terms while you are still being courted. Notice period, data export format, whether you get your client records and trading history in a usable file, and what happens to open positions during a migration. The answer is far harder to obtain after you have signed.
Operations: what breaks, and who answers at 3am
Ask about the last outage. A vendor with real clients has had one, and how they describe it tells you more than any uptime figure on a banner. What failed, how long, what changed afterwards. A vendor who claims never to have had an incident is either very new or not being straight with you.
Then support. Which hours, in which languages, through which channel, and what counts as an emergency. Weekend cover matters for a firm with clients trading crypto or in Asian time zones. Ask who you actually reach: a shared inbox, a named account manager, or an engineer. Ask how a bug reported on Friday afternoon reaches a developer.
Ask about deployment too. Shared infrastructure or a dedicated instance, where the servers sit, and what the latency story is for your main client regions. If they cannot name the data centre regions, they do not run the infrastructure themselves.
Roadmap and lock-in
Two questions do most of the work. What shipped in the last ninety days, and what is next. A vendor that cannot list recent releases in specific terms has a product in maintenance mode, whatever the roadmap slide says. Ask whether feature requests from clients ever get built, and ask for an example with a name attached.
On lock-in, ask about the API. Every setting a client can change in the interface should exist as a documented route, because that is what lets you automate later and what lets you leave without retyping your business. Ask to see the documentation on the stand. It takes thirty seconds and it is remarkably revealing.
Compliance questions the sales staff often cannot answer
Ask who holds the data processing agreement, how long records are retained, and whether audit logs are immutable or editable by an administrator. For a firm serving European clients, ask where personal data is stored and processed, and ask it while somebody technical is standing there. Sales staff frequently guess at these, and a guess in a stand conversation becomes an expensive misunderstanding later.
Ask about access control too. Whether staff permissions are per area or one blanket admin role, whether a support agent can see full client documents, and whether the system records who viewed what. Firms discover the importance of that question during their first audit, which is a bad time to find out the answer.
References and the awkward final question
Ask for two references: one client who has been with them over two years, and one who left. The second request is uncomfortable, which is why it works. A confident vendor will give you a name and tell you honestly why the relationship ended.
Finally, ask who built the product and whether those people are still there. Trading software carries a lot of accumulated knowledge about edge cases, and a team that has been replaced twice tends to rediscover the same bugs. We answer that one directly: the people behind SINGUARD's products are named on the site. If you are shortlisting, the vendor comparison is a reasonable starting map, and the Prop Firm CRM page carries our own answers to most of the questions above.
"Ask what happens when we stop working together. A vendor who has never thought about that question has never had a client leave, or has never let one."
— Alex Onta, Executive Director, SINGUARD
Key Takeaways
- Ask for the full price structure including setup, per-account and per-server charges, and what a firm ten times your size pays.
- Separate the three ownership questions: who holds the licence, where client data lives, and whose brand appears on the trader's screen.
- Ask about the last outage and about weekend support hours, then ask to see the API documentation on the stand.
- Request two references, one long-standing client and one who left, and get the exit terms in writing before you sign anything.
Frequently Asked Questions
What is the single most useful question to ask a trading software vendor?
What happens when the contract ends. Notice period, data export format and migration handling reveal how the vendor treats clients, and the answer is far harder to get once you have signed.
How do I check whether a vendor's product is actively developed?
Ask what shipped in the last ninety days and what is next, in specific terms. A vendor who can only describe a roadmap slide rather than recent releases is likely running the product in maintenance mode.
Should I ask for client references at an expo?
Yes, and ask for two: a client of more than two years and one who left. The second request is uncomfortable, which is exactly why the answer is informative.
About the Author
Alex Onta is an Executive Director at SINGUARD. He built eTrader, the terminal, the mobile apps, eTrader Broker, Copytrading, Business and Community, along with the worldwide clustered-server infrastructure it all runs on, with his brother Roman Onta helping on the design, and he leads that division today. Together with Roman he builds the Prop Firm CRM, the Broker CRM, Scalegram and CopySignals, and the two of them carry worldwide compliance, payment processing and international business structuring side by side. He lives and works in Dubai for most of the year. Meet the executive duo leading Singuard's five divisions.