Vicquant is open for beta testers: pick a frontend design, run four short tasks, and tell me exactly what feels wrong.
The problem with asking "What do you think?"
When I first put Vicquant in front of beta testers, I asked the question every builder asks:
"What do you think?" The answers I got back were polite and vague. "Looks good." "Nice app."
Not one of them told me where someone got stuck, what confused them, or what they expected to happen and didn't.
That is my mistake, not theirs. Open-ended questions produce open-ended politeness.
So this time I am doing it differently: I am giving you specific things to do, a short way to report what
happened, and a say in how the app looks. If you have ever wanted to shape a product while it is still early, this is that chance.
What is Vicquant?
Vicquant is an AI-assisted personal finance and market-analysis app. It started as a small local chatbot that helped people plan debt repayment and savings, and it has grown into something much bigger. One rule shaped it from day one: the AI never does the arithmetic. All the
money math (balances, payoffs, risk numbers) is computed by normal, testable code, and the language model only explains the results. That way a language model's confident guess cannot quietly become your budget.
What you can try in the beta:
• AI Advisor and Budget: ask questions about debt, savings and spending in plain language.
• RAG Vault: upload your own financial documents and get answers with citations back to the source, so you can check the answer instead of trusting it.
• Stocks and Portfolio: track holdings and see risk measures such as Sharpe, Sortino, VaR and CVaR, without needing a finance degree to read them.
• Market regime detection and alerts: a statistical model that tries to tell calm markets from turbulent ones.
• Proof ledger: trading signals are recorded in a tamper-evident, hash-chained log with fixed rules set in advance, so results cannot be quietly rewritten after the fact. No win rate is shown until at least 30 signals have been resolved, because a handful of lucky calls proves
nothing.
Honest status: what is rough right now
A beta invitation is only useful if it is honest, so here is where things stand:
• The AI currently runs through a hosted model service rather than fully on your own device.
Running it locally again is on the roadmap, but it is not the current setup.
• The mobile web experience is not good enough. A native Android and iOS app is planned, so please judge the layout with that in mind.
• Vicquant gives information and analysis. It is not licensed financial advice, and nothing in it is a guarantee of returns.
• Some features are still being tuned, and speed can vary. If something feels slow, I want to know exactly when it happened.
• The frontend UI and UX design also needs working on. This is my first time on working on something of this scale.
Please, I need your honest review and contribution, so i can improve on it
Please use sample numbers. During the beta, enter made-up balances and debts rather than real account details.You can test everything that matters without exposing anything
personal.
Help me choose the design
I have three frontend designs and I do not want to choose alone. The feedback I got earlier was that the interface needs to feel easier for someone who is not a finance expert, so this is where your eyes matter most. The UI design is okay for laptop size screen but for the mobile, i am still working on it.
When you vote, do not only tell me which one you like. Tell me which one you understood fastest. In a finance app, "pretty" matters less than "I knew what to tap."
Your 15-minute mission
Four tasks. Do them in order, and write down anywhere you hesitated, even for a second.
How to send feedback (it takes two minutes)
After the four tasks, answer these five questions in the feedback form:
• Which design did you pick, and which one did you understand fastest?
• Where did you get stuck or confused? Name the screen.
• What did you expect to happen that did not?
• Did any AI answer feel wrong, vague or untrustworthy? Paste it if you can.
• Would you use this again? What single change would make you say yes?
Bug reports are gold. A screenshot, your device and browser, and one sentence about what you were doing is all I need.
Join the beta
If you are a developer, a student, a finance enthusiast, or simply someone who gets confused by money apps, you are exactly who I need. Beginners are especially welcome, because they
find the problems experts forgive.
• Beta link: https://budget-planner-advisor-rho.vercel.app/
• Reply here or message me with questions.
Thank you for reading, and for being willing to break something so it can be built better. Tell me what is wrong with it, and I will make sure the next version is better because of you.
Top comments (1)
The "no win rate until 30 resolved signals" rule is a good instinct, but 30 is still a thin sample, so I'd show the interval next to the number. I computed Wilson 95% intervals for n=30: 18 wins (60%) gives 42%-75%, and 20 wins (67%) gives 49%-81%. The chance of 20 or more wins out of 30 from a coin-flip strategy is 4.9%, and 21 or more is 2.1%. So a tester can see a 67% "win rate" at the first moment it is displayed and it still can't rule out luck once you have tried more than a few rules. To pin the half-width at about 5 points around 55% you'd need roughly 380 resolved signals.
Two things that would make the proof ledger stronger: record the rule version in each hash-chained entry (so changing a threshold later is visible), and show the count of rules or parameter sets tried before this one went live, since that count is what inflates the best one.
Also worth saying on the Sharpe/Sortino side of the app: with a few months of daily returns those ratios have wide error bars as well, so a "no finance degree" display should probably carry the same caveat. I built canli-mcp (free, MIT, no key),
npx -y canli-mcp, and github.com/arhancanli/canlicapital has the free overfitting checks if you want something to test the ledger against.