Top 3: form builders for a useful client enquiry

Choose a form builder by working backwards from the enquiry you need to act on. Tally is worth considering when conditional logic or calculations are central; Typeform when reporting and integrations are part of the brief; and Jotform when drag-and-drop setup and answer-dependent fields fit the task. These are starting points, not exclusive strengths or a ranking. The useful choice is the one that collects enough context for your next reply without creating unnecessary work for either person.

Start with the reply you want to send

Example: a solo designer needs an enquiry form for prospective client projects. Before choosing a tool, they draft the reply they would like to send: acknowledge the requested service, explain the deadline and suggest the next conversation. Working backwards, the form needs contact details, project type, timing and a short description. Questions that would not change that reply can wait.

This keeps the comparison focused. A long feature list matters less than whether the builder supports the necessary questions and a manageable handover. Decide which answers are essential, which are optional and which should appear only for a relevant project type. Do not collect sensitive background information simply because a form makes it easy to ask.

Tally: consider it for branching questions or calculations

Tally’s official features page describes conditional logic and calculations. Its published summary also states that free use is subject to fair-use rules, with additional paid features. For the designer example, a useful trial would be whether selecting a service can lead to relevant follow-up questions without making the form difficult to maintain.

Calculations deserve a separate decision: does this enquiry actually need them? If the goal is simply to arrange a conversation, adding calculated values could introduce rules you must later update. If a calculation is genuinely useful, test ordinary inputs and awkward edge cases. Check the applicable fair-use terms, paid-feature scope and data handling rather than assuming a free starting point covers the intended workflow.

Typeform: consider the work after submission

Typeform’s official platform overview describes no-code forms, surveys and quizzes with logic, reporting and integrations. Advanced capabilities and response limits vary by plan. Its fit for your workflow therefore depends partly on what you need to do with enquiries after people submit them, not just on the questions themselves.

For example, the designer might want to review enquiry categories regularly or pass details into an existing working process. First specify the actual report or destination needed; “has integrations” is not enough to establish that fit. Then check the precise connection, available fields and plan requirements. If enquiries are reviewed individually, decide whether reporting adds useful context or simply another layer to configure.

Jotform: consider layout and answer-dependent follow-up

Jotform’s official drag-and-drop features page describes templates, widgets, integrations and conditional logic. Forms can show or hide fields and change follow-up behaviour based on answers. This makes it a candidate to investigate when different enquiry types need different details.

For the designer, an identity project and a website project might call for different background questions. A template could provide a starting structure, but the editorial work remains yours: remove irrelevant questions and check every branch. Treat widgets as possible solutions to specific needs, not items to add by default. More moving parts mean more cases to review whenever you change the form.

Run one small trial before committing

Build the same short enquiry in each shortlisted tool, using invented project details rather than real customer data. Keep the wording consistent so you are comparing setup and workflow rather than three different questionnaires. Try a straightforward enquiry, one that takes an alternative branch and one with missing optional information. Read the resulting submissions as if you had to reply immediately.

Then make one realistic change, such as adding a service category. Note which questions, rules and downstream steps need attention. This exposes maintenance work that an initial build can hide. Choose only after checking the relevant plan scope and data-handling arrangements. The published product details do not establish comparative completion rates, setup times or a universal winner; your trial should establish fit for this specific task.

Strengths

• All three supplied summaries describe logic for shaping a form around answers.
• The options offer different starting points for evaluating construction, output and follow-up needs.
• A short, consistent enquiry brief provides a useful basis for comparison.

Limitations

• Check submission limits, storage and integration access against your expected use.
• Test conditional branches and confirm where responses are stored and who can read them.
• No comparative completion-rate or usability test is claimed.

The details, side by side

Compare capabilities, setup and the work each option needs.

Swipe or scroll sideways to compare all products →

Editorial comparison. Confirm the current variant and suitability before buying.

What matters to you	TallyA small intake form with conditional questions or calculations	TypeformAn intake journey where question order and response review matter	JotformA service enquiry with different paths for different requests
A good fit for	Collect a brief and show follow-up fields when an answer calls for them.	Guide a prospect through relevant questions and inspect the submissions.	Build a form visually and route fields or follow-up according to answers.
Key capabilities	Tally provides conditional logic, calculations and forms under its free tier, subject to fair-use guidelines. It also lists integrations and a choice of paid features for more advanced requirements.	Typeform supports no-code forms, surveys and quizzes, with logic, reporting and integrations. Its platform overview distinguishes plan allowances for response volume and more advanced capabilities.	Jotform offers a drag-and-drop form builder with templates and widgets. Conditional logic can show or hide fields, vary thank-you messages and send emails according to the submitted answers.
Before choosing	Review fair use, upload needs, branding and the integration required by your process.	Check response allowances and the exact reporting or integration capability you need.	Verify submission and storage allowances, integrations and required permissions.
The trade-off	Test both branches of every condition and verify where responses arrive.	Keep question branches aligned when the service or eligibility criteria change.	Retest hidden fields and recipient rules after changing the form.
Take a closer look	Read the full review	Read the full review	Read the full review

Before you decide

• Build the same enquiry and test every relevant answer path with invented data.
• Check whether each resulting submission contains enough context for a useful reply.
• Confirm the required features, response allowances and intended usage under the chosen plan.
• Verify data handling and any exact integration needed for follow-up.
• Change one question or service category and review the maintenance required.