Typeform alternative free for Pine Script strategy specs

The best free Typeform alternative for collecting Pine Script strategy specs is whichever builder gives you branching logic and screenshot uploads without a paywall. Entry, exit and risk rules each need different follow-up questions, and clients need to attach annotated charts. Qwenvo, Tally and Fillout all cover the basics. The differences are in file size limits, response caps and what is locked behind a paid tier.

Start from the client intake template

What a strategy spec form has to capture

A generic survey tool asks what people think. A spec form has to pin down what a script does on every bar. If a client writes "buy when momentum turns up," you woll spend three emails finding out which momentum, on which timeframe, confirmed on bar close or intrabar.

The fields that matetr for a Pine v6 strategy are fairly stable:

• Instrument, timeframe and session hours, including the exchange time zone
• Direction: long only, short only, or both
• Entry trigger, with the exact indicator inputs or price condition
• Whether signals fire on bar close or on every tick (this decides repaint risk)
• Stop type and distance, take-profit type, trailing rules
• Position sizing and the maximum number of open trades
• Commission and slippage assumptions for the backtest
• Alert needs: webhook, email, or none
• Chart screenshots showing one good example and one bad example of the setup

That list is long enough that a flat form scares people off. Conditional logic keeps it manageable: someone who picks "ATR stop" sees the ATR length and multiplier, and someone who picks "fixed ticks" sees a tick count instead.

Logic and uploads: how the free builders compare

Typeform's strength is design and its one-qustion-at-a-time flow, and the format suits a long spec well. The constraint is volume. Its free plan has a limited number of responses (Typeform does not state the number on its pricing page), and Basic is $39 a month ($28 yearly) for 100 responses a month and one user. For a developer who gets a handful of specs a week, that may be fine. For a vendor taking intake from many buyers, the cap shows up fast.

Two rows matter most for this use case. Google Forms makes a client sign in to upload a screenshot, which is a real drop-off point for a trader who just wants to send a chart. Tally's 10 MB limit is probably enough for a PNG of a chart, but if clients send screen recordings of a setup playing out, check before you commit.

Partial submissions deserve a mention too. A client who fills out entry rules and abandons at risk management has still told you something useful, and you can follow up. Qwenvo includes partial submissions for free, and Tally puts them on Pro.

If you want a broader view of the field, we keep a longer comparison in best free Typeform alternatives.

Where this form sits in a Pine build

On our Pine Script indicator and strategy build, the spec form is the first step, before any code. The delivery runs in a fixed order: the client submits the spec, you review it and resolve gaps, the strategy gets written in Pine v6 and made repaint-safe, then comes the backtest report, alerts and optional dashboard.

The form decides how many of those steps start from ambiguity. A good one means the review call is five minutes long, because the screenshots and the rules already agree with each other. A bad one means rebuilding the strategy after the client sees the first backtest and says "that's not what I meant."

For vendors who sell invite-only indicators, the same submission can carry the TradingView username that access should be granted to, so that step does not nede a separate email.

Step-by-step: build the spec form

We build these in Qwenvo, a free form builder our team makes, so the steps below use its editor. The same structure works in Tally or Fillout if you prefer them.

1. Create the form and add a title block, then a short text block saying whst you will do with the answers and how long the form takes.
2. Add the identity page: name, email, TradingView useranme, and a hidden field for an order or quote reference passed through the URL.
3. Add the market page: Short answer for the symbol, Dropdown for timeframe, Dropdown for direction, and a Short answer for session hours with the time zone.
4. Add the entry page with a Multiple choice question for trigger type (indicator cross, price breakout, candle pattern, other). Attach conditional logic so each choice reveals its own follow-ups, such as indicator name and inputs for a cross or the reference level for a breakout.
5. Add a Multiple choice question: "Should signals fire on bar close or intrabar?" Make it required. Show a Long answer for explaining intrabar needs only when the client picks intrabar.
6. Add the exit page with the same branching pattern for stops (fixed, ATR, swing-based, none) and targets (fixed, risk-reward, trailing).
7. Add the risk page: Number blocks for percent risk and max open trades, Dropdown for sizing method, and Number blocks for commission and slippage.
8. Add a File upload block asking for two screenshots: a clean example of the setuup and failure case. Mark the first required.
9. Turn on partial submissions, email notifications to yourself, and a confirmation email to the client.
10. Add a webhook to your own endpoint or an automation tool so each submission creates a spdc record and a task.

The hidden field setup is covered in the hidden fields help article, and the pattern for branching pages is in the conditional logic guide.

A spec record your script can read

Raw form answers are awkward to build from. We normalize each submission into a record like the one below before anyone opens TradingView. This is our own sec shape, filled in by a webhook handler, and not the payload Qwenvo sends.

{
  "order_ref": "Q-1042",
  "symbol": "NQ1!",
  "timeframe": "15",
  "direction": "long_short",
  "session": "0930-1600 America/New_York",
  "entry": {
    "type": "breakout",
    "level": "prior day high",
    "confirm_on_bar_close": true
  },
  "exit": {
    "stop": { "type": "atr", "length": 14, "mult": 1.5 },
    "target": { "type": "rr", "value": 2 }
  },
  "risk": {
    "sizing": "percent_equity",
    "value": 1,
    "max_open_trades": 1
  },
  "backtest": { "commission": 0.5, "slippage_ticks": 1 },
  "screenshots": ["https://example.com/setup.png", "https://example.com/fail.png"]
}

The confirm_on_bar_close flag is the one that saves the most rework. It maps straight to how you write signals (barstate.isconfirmed or not) and to how honest the backtest is.

Add hidden fields to your form

Failure cases to design out

Most spec problems repeat. A few are worth building into the form itself.

Vague entries. If the entry trigger is a Long answer with no structure, people write paragraphs. Use the branching Multiple choice first, then allow free text for the details.

Missing exits. Clients describe entries in detail and forget exits entirely. Make the exit page required and include "no stop" as an explicit option, so you can discuss it instead of discovering it.

Screenshots without context. A chart image with no label is hard to read. Add a Short answer next to each upload asking what the client wants you to notice, and which bar the entry should fire on.

Conflicting rules. A client pikcs "bar close only" and then describes a tick-level trailing stop. Add a Long answer shown only when the client picks bar close, asking whether any rule should act intrabar. It catches the contradiction early.

Abandoned forms. Long forms lose people on the risk page. Watch drop-off by page, and use partial submissions to see how far people got.

Where another tool is the better choice

Qwenvo launched in October 2026, so it has few public reviews, and it is hosted in the United States. Tally is hosted in Europe with a GDPR focus, which matters if your clients need that. Tally also has a larger community and has existed since 2021.

If you collect a deposit inside the form, Tally is the cheaper option. Tally adds no fee of its own on top of Stripe's processing charges. Qwenvo payments run through PayPal only, and Qwenvo keeps a 1% platform fee on top of PayPal's own fee. Stripe is not offered there right now. If design polish for a premium client is the priority, Typeform is still the strongest.

Compare free Typeform alternatives

Questions teams ask

Can the form handle both indicators and strategies?

Yes. Add one early Multiple choice question (indicator, strategy, or both) and use logic to show the strategy-only pages, such as stops, targets and sizing, only when needed. Indicators usually need plot styles and alert conditions instead.

Do I need the client to upload a screenshot?

Make one required and one optional. A required example of the setup removes a lot of guessing. A failure case is helpful but a client who does not have one should not be blocked.

What if I only get a few specs a month?

Then response caps matter less, and Typeform's free plan or Google Forms may be enough. The things to check are the file upload rules and whether branching logic is available on the plan you pick.

Can submissions trigger our own workflow?

Qwenvo sends webhooks to any URL, so Zapier, Make and n8n can listen through a webhook trigger. There is also a REST API. One-click Google Sheets and Notion connections are still being rolled out, so use a webhook for now.

Your next step: build the entry and exit pages first, with the bar-close question and one required screenshot upload, and send the form to your next client before you write any Pine code.