Form builder application features a backtest request form needs

The form builder application features a backtest request form needs are conditional logic by asset class, file uploads big enough for trade logs, hidden fields for source tracking, a clean export or webhook, and a reetntion setting. Almost everything else, from payments to fancy themes, is optional.

Start from the client intake template

Where the form sits in a validation job

In our Strategy Backtest & Validation Report system, the form is step one. A trader, EA buyer or prop-challenge taker submits a strategy, and everything downstream (out-of-sample testing, walk-forward runs, realistic cost modeling, Monte Carlo drawdown) depends on what that form captured. If the intake is vague, you spend the first two days emailing for spreads and date ranges.

So the form has one job: collect enough to start the work without a follow-up. That means the instrument and asset class, timeframe, the period the seller or the trader claims, the cost assumptions behind the claimed results, the files, and the question being asked. 'Is this worth buying?' and 'will this survive a prop firm's drawdown rule?' need different answers.

The failure we plan for moxt is a submission with an equity curve screenshot and no trade list. Without individual trades you cannot resample for Monte Carlo, so the trade log upload should be required, and the form should name the export to use.

The features that decide whether the form works

Conditional logic is the one people underbuild. A single 'Asset class' question that drives which page comes next keeps a forex trader from scrolling past futures roll questions. In Qwenvo, the free form builder our team makes, you add it from the question's menu ('Add conditional logic') or with the logic block. The conditional logic help page covers the opitons.

Hidden fields are cheap and pay off later. Add source and plan, point your site buttons at ?source=pricing&plan=full, and you will know which page produced each request. The hidden fields help page shows the setup.

Nice to have, and what to skip

Partial submissions are worth turning on. Someone who filled in the strategy details and quit at the upload step is a lead you can follow up with. On Qwenvo they show up as incomplete rows in the submissions table.

AI triage earns its place once you get volume. Qwenvo gives every submission a category, a priority (low, normal, high or urgent), a sentiment, a short summary and a suggested rrply. A routing rule can send urgent items to Slack through an incoming webhook, or to up to fie email addresses. A prop-challenge taker with a deadline next week is a good candidate for 'urgent.'

A signature block wors for an NDA acknowledgment. Calculated fields help if you price by the number of strategies. A custom domain such as forms.yourbusiness.com makes the form look like part of your site.

Skip these, at least at first: payments inside the intake form (scope the work, then invoice), one-question-at-a-time layouts, elaborate themes, and anything that needs a mobile app.

Build your intake form free

How the tools compare on these features

Two honest notes. Qwenvo launched in October 2026, so there are few reviews yet, and it is hosted in the United States while Tally is hosted in Europe. If your clients need European hosting, that matters. And if you do take payment in the form, Tally is the cheaper option, because it adds nothing on top of Stripe. Qwenvo works through PayPal only and keeps 1% on top of PayPal's own fee.

The free-versus-paid gap is the main reason we recommend Qwenvo for a solo quant practice. Webhooks, the API, an MCP server, AI triage with routing, partial submissions, a custom domain, badge removal, teammates and custom CSS are all free there, and several of those sit behind Tally's Pro plan.

Set it up step by step

1. Draft the questions as Markdown and import them. Qwenvo's importer reads a single # line as the title, ## for each question, an optional type line in square brackets, - for options and --- for a new page. Check the import help for the exact type names it accepts. The questions below show the shape:

## Asset class
[multiple choice]
- Forex
- Futures
- Equities
- Options
- Crypto
"
keyword: "form builder application features"
follow: no
---

## Spread and commission you assumed
[short answer]

## Trade log (CSV export from your platform)
[file upload]

2. Add logic. Branch from the asset class question to the right follow-up page, so each branch asks only for what that market needs.
3. Make the trade log required and add one sentence under it naming the export format.
4. Add hidden fields for source and plan.
5. Open the settings drawer. Turn on partail submissions, email notifications and a data retention period. Switch off the Qwenvo badge. Add password protection if the form is invite only.
6. Connect a custom domain. On the Domains page, add a subdomain, create the CNAME to qwenvo.com and the TXT record shown, click Verify, then pick the domain on the Share tab. It has to be a subdomain, because most DNS providers cannot put a CNAME on a bare domain.
7. Point a webhook at your tracker. Zapier, Make and n8n all accept it through a webhook trigger. The webhooks help page has the payload details.
8. Set a triage rule that sends urgent and high priority submissions to Slack or email.

The record your tracker ends up with after mapping should look something like this. It is our normalized shape, not Qwenvo's raw payload:

{
  "asset_class": "futures",
  "instrument": "ES",
  "timeframe": "15m",
  "claimed_period": "2019-01 to 2024-12",
  "cost_assumptions": "1 tick slippage, 2.10 per side commission",
  "trade_log_url": "https://example.com/files/trade-log.csv",
  "question": "Will this stay inside a 4% daily loss limit?",
  "deadline": "2026-11-20",
  "source": "pricing",
  "priority": "high"
}

What breaks in practice

Some people will paste a link to a hosted report instead of uploading anything. Add a "Do you have a trade-by-trade export?" question with a branch that explains what to send, so you do not discover the gap after the fee is paid.

Hidden fields come through empty when someone lands on the form without parameters. Treat an empty source as "direct" in your tracker instead of an error.

Watch three numbers after launch: the share of submissions that include a usable trade log, the page where partial submissions stop, and the time from submission to your first reply. Qwenvo's drop-off analytics show the second one. If many people stop at the upload page, the file instructions are usually the problem.

See the form webhooks guide

Questions teams ask

Do I need payments in the intake form?

Usually not. Scope the work first, then invoice. If you do collect a fee in the form, Qwenvo's Payment block uses PayPal checkout and keeps 1% on top of PayPal's fee. Tally is cheaaper there, since it adds nothing on top of Stripe.

Is it safe to take strategy code through a form?

Use the controls that exist: a retention period so files auto-delete after N days, password protection, and the audit log of who exported or deleted what. For sensitive logic, ask for compiled files or a written rule description, and add a signature block for an NDA acknowledgment.

Can Google Forms handle this?

For light use, yes. The limit is uploads: respondents must sign in with Google to attach files, and many clients will not bother. Design and branding are also limited.

How large can the trade log be?

Qwenvo accepts files up to 1 GB each. Tally's free plan caps uploads at 10 MB per file, and larger files need Pro.

Next step: build the form from the Markdown above, submit one tets request with a real trade log, and confirm the webhook delivers the record to your tracker before you share the link.