Every prop firm that claims to be “the best,” “the leader of the crowd,” or “the top of the food chain.” Those words are actually the first warning sign: only one firm can genuinely be the best, and the one that is doesn’t need to tell you.
The real question is “the best in what?” Making the firm money, making traders money, or hopefully both?
Every prop firm review on this site starts the same unglamorous way.
Firms that don’t meet our transparency standard are still shown, but get no backlink and aren’t included in the comparison lists. The information we find is presented as neutrally as possible, so you can make up your own mind. We don’t recommend using any specific firm, that choice is yours to make. The aim here is just to make that choice easier.
The order things are actually checked in
Published website content first, directly compared with legal representations (website vs. actual TOS and contracts published), then rules and terms. Help-center articles next, since firms tend to be more specific there than in the Terms of Service, which is usually written broadly enough to cover almost anything. Only after that do I go to support chat or write an email, and only to confirm something the documentation left ambiguous, not to ask something I could have found myself. If support gives an answer that contradicts the documentation, I don’t just take either side, I go find a third source, or test it directly.
A single rule is almost never “a problem”: the combination is.
Pretty much all firms run some variation of the same rules. They just call them different names, weight them differently, or combine them differently, that’s just how internal risk management works for each firm. The problems start when these rules are designed or combined in a way that makes your journey deliberately harder.
As an example, requiring Consistency (even when low) is not really a problem, but demanding a low consistency and having “profitable days” defined at a significant gain puts the trader in a virtual cage. The rules appear to be the same between firms, but one has them designed to make the payout harder while the other just manages risk properly.
Spotting that difference on paper is one thing, getting a firm to admit which one they’re actually running is another.
Support chat is also where the process stops being tidy.
Boilerplate is the default answer, not the exception
Ask a support agent something specific enough and the honest, useful answer would be “we don’t disclose that” or “let me check with someone who knows.” What you get instead, most of the time, is the same paragraph from the help center, pasted back to you, sometimes word for word, as if the question was “please repeat the policy” rather than “what does the policy actually mean for my account.” Ask again and you get the same paragraph again. It’s not a conversation, it’s a very polite loop.
The only way through it, in my experience, is to keep pushing until either you get escalated to someone who actually knows, or the loop itself becomes the finding. Both outcomes are useful. A firm’s risk team telling you plainly “we can’t disclose our internal criteria” is a real, citable answer, it just also tells you something about the firm. A support rep with no idea repeating a paragraph tells you something else entirely: that the front line isn’t equipped to actually answer questions, which is a different problem from the firm hiding something.
Why that matters more than it sounds like it should
That’s why it’s hard to vet firms from the outside. A refusal to answer looks identical whether it comes from a policy of deliberate opacity or from an agent who’s never read past the first paragraph of the script in front of them. AquaFunded’s risk team, for comparison, gave a real answer when pushed hard enough: they can’t disclose their internal review criteria, full stop, a policy-level admission, not a support script failing to find the right paragraph. Both situations end in “no answer,” but only one of them is actually about the firm’s intentions. Support incompetence is annoying. A trained refusal to disclose anything, even under direct pressure, from someone who clearly knows the answer, is the finding.
What this means for reading our reviews
When a review here says support gave a vague or evasive answer, that’s reported as exactly that: an evasive answer, not proof of bad intent. Where it matters, we try to push past the front line and get an answer from someone who actually knows, or find the same fact stated plainly somewhere the firm already published it. The distinction between “support couldn’t tell me” and “the firm won’t tell anyone” is worth the extra round of messages, even when it means sitting in a chat window repeating the same question for the third time, or following up across multiple emails with different teams.
