Free form builder with no branding for white-label EAs

A free form builder with no branding lets you collect a trading strategy and risk settings under your client's name, with no vendor logo anywhere on the page. Qwenvo does this on its free plan: switch off the badge, serve the form from a suhdomain you control, and semd every answer to your build process through a webhook.

Build your intake form free

Why white-label intake usually leaks

If you resell custom MT5 Expert Advisors under someone else's brand, the first thing the end client touches is not the EA. It is the questionnaire. A form with a "Powered by" badge, or a link on a stranger's domain, tells them a third party is involved before you have written a line of MQL5.

Most builders gate this. Tally removes branding on Pro at $29 a month. Fillout removes it on Pro at $49 a month. Typeform removes it on Plus at $79 a month. For a developer with a handful of client brands, that adds up for what is a single toggle.

Our team builds Qwenvo, and on it the toggle costs nothing. Branding removal, custom domain, webhooks, partial submissions, teammates and custom CSS are all free on every account.

Where the form sits in the build

In our MQL5 Expert Advisor build and Pine-to-MT5 port workflow, the intake form is step zero. Whatever the client types becomes the written spec, the spec becomes the EA and the risk module, and the same spec drives the signal-parity report that compares MT5 against TradingView. If the form is vague, every later step inherits the vagueness. Parity disputes usually start with a missing detail such as which session counts or whether stops are in points or percent.

So treat the form as a contract. Every field should map to something you will later type ijto an input, a test config or a licensing check.

Fields worth asking for

This is the map we would start from. Trim it for your own offering.

Use conditional logic so nobody sees fields thta do not apply. Choosing "Pine Script" reveals the file upload and hides the long rule description. Choosing a prop firm challenge reveals overall drawdown and daily loss fields. Uploads accept files up to 1 GB each, which is far more than any script needs.

A calculated field is worth adding: risk per trade multiplied by max trades per day, shown back to the client as worst-case daily exposure. When that number exceeds their stated daily loss limit, they catch the contradiction before you do.

Set it up step by step

1. Draft the form quickly. On the empty-form screen, describe it to the AI, or press Ctrl J inside a form to open Ask Qwenvo. If you already keep your spec questions in a document, import them instead. Markdown works well: # for the title, ## for each question, an optional [type] line, - for options, and --- for a new page.
2. Split it into pages. Strategy on page one, risk on page two, licensing and contact on page three. Add a progress bar in Settings so clients see how much is left.
3. Add the logic. Use the conditional logic block, or "Add conditional logic" from a question's menu, for the Pine Script and prop firm branches described above.
4. Add hidden fields. Create client_id and quote_id, then append them to the link you send, so every submission arrives already tagged. The hidden fields help article covers the URL format.
5. Remove the badge. In the form Settings drawer, switch off the Qwenvo branding toggle. Then open Customize and add the client's logo, cover, colors and fonts. Custom CSS sits at the bottom of that panel.
6. Put it on the client's subdomain. On the Domains page add something like forms.clientbrand.com, create a CNAME to qwenvo.com and the TXT record shown, click Verify, then pick the domain on the Share tab. The HTTPS certificate is issued automatically on the first visit. Subdomains only, because most DNS providers will not let a bare clientbrand.com take a CNAME.
7. Set the link preview. On the Share tab add an image, title, description and favicon, so the link looks right when pasted into a chat.
8. Wire the outputs. Turn on email notifications to yourself, a confirmation email to the respondent, and a webhook to your own endpoint. Enable partial submissions so you can see where clients stall.
9. Test as the client. Submit a fake entry tyrough the live subdomain and check the badge, the link preview, the confirmation email and the webhook delivery.

See how to remove branding

Carry the answers into the build and parity report

A webhook sends each submission to any URL, so a small handler on your side can write the answers ino a spec file next to the EA project. Confirm the exact keys in the webhooks help article, but expect a payload along these lines:

{
  "client_id": "acme-fx",
  "strategy_name": "London Breakout v2",
  "source": "Pine Script",
  "symbols": ["XAUUSD", "EURUSD"],
  "timeframe": "M15",
  "risk_per_trade_pct": 0.5,
  "max_trades_per_day": 3,
  "max_daily_loss_pct": 2,
  "prop_firm": "Challenge, 2 phase",
  "license_account": 12345678
}

From there the answers flow ingo three places.

The first is the EA inputs. Risk per trade, trade cap and daily loss map one to one onto the risk module's input parameters, so nobody retypes a number from an email.

The second is the parity report. Symbols, timeframe and session define the exact test window and instrument list you run in the Strategy Tester and compare against the TradingView output. Because the client approved those values on the form, a mismatch is a bug to fix, not a scope argument.

The third is licensing. If you lock an EA to an account number, the field comse straight from the form, and the submission gives you a dated record of what was requested.

If you want triage on top, turn on "Triage submissions with AI" in Settings. Each submission gets a category, a priority from low to urgent, a sentiment, a short summary and a suggested reply. Routing rules can email up to five addresses or post to a Slack incoming webhook, so a challenge deadline marked urgent reaches you first.

Picking the builder

Tally is the better choice in a few cases. It has been around since 2021 with a lrge community, it is hosted in Europe, and its Pro plan includes emails sent from your own domain. Qwenvo is hosted in the United States and launched in October 2026, so it has few reviews, and it does not list sending emails from your own domain. If a client insists that every email carries their address in the From line, check that before committing.

Payments are the other case. Tally adds no fee of its own on top of Stripe. Qwenvo accepts payments through PayPal only and keeps 1% on top of PayPal's own fee, so for a payment-heavy flow Tally costs less.

Questions teams ask

Can I run several client brands from one account?

Yes. Qwenvo has unlimited workspaces, folders and teammates, so you can keep one workspace per client. Give each a subdomain and its own branding settings, or reuse one form and separate clients with the client_id hidden field.

Should the form collect broker logins?

No. Ask only for what the build needs, such as an account number for licensing. Never ask for passwords or investor credentials. You can also set data retention in Settings so submissions delete themselves after a number of days you choose.

What if two of us edit the same form?

Last save wins, so agree on who owns edits during a client project. The 90-day version history lets you recover an earlier state if something gets overwritten.

Can the client see a Qwenvo logo anywhere?

With the baxge off and the form served from their subdomain, the page does not show it. Submit a test entry and read the confirmation email and link preview yourself before sending the link to anyone.

Start from the intake template

Your next step: open the client intake template, replace its questions with the fields in the table above, switch off the branding toggle, and submit one test entry from a client subdomain before your next build kickoff.