A customer completes a form, uploads evidence, and chooses a date. Staff then identify the account, check entitlement, and ask for missing information. The form was submitted successfully; the request still was not ready to process.
Our recommendation: compare Typeform and Jotform on the complete intake process, then build only the part that needs live business state. A custom application can be valuable when it prevents repeated staff repair. A custom form that merely copies vendor fields can add maintenance without improving the outcome.
Compare response capture with usable intake
Primary documentation checked September 26, 2026. Numeric price headlines are omitted because the public Typeform page exposes multiple price presentations; confirm the selected plan, currency, and billing cadence in checkout. The capabilities below are not claims that every plan includes every feature.
| Criterion | Typeform | Jotform | Build your own intake application |
|---|---|---|---|
| Basic model | Interactive forms with response allowances. Typeform plans | Forms with submission and storage limits. Jotform plans | An authenticated or public request process tied to domain records. |
| Conditional questions | Conditional logic is listed in the plan overview. Typeform plans | Show/hide fields, conditional messages, and emails. Jotform conditional logic and form features | Validate branches against live account and policy data. |
| Form count vs volume | Unlimited forms can coexist with capped responses. Typeform plans | Form, submission, storage, and other limits need separate review. Jotform plans | Capacity depends on database, traffic, file storage, and abuse controls. |
| Team access | User allowances and enterprise identity features vary. Typeform plans | Pricing FAQ identifies Enterprise as the multiuser plan. Jotform plans | Implement reviewer roles and least-privilege access. |
| Document output | Scope the needed document workflow separately. | PDF generation and fillable-PDF features are documented. Jotform conditional logic and form features | Generate a versioned record after server-side validation. |
| Approval workflow | Integrate a downstream process through APIs or webhooks. Typeform webhooks | Approval and group-approval features documented. Jotform conditional logic and form features | Own assignment, escalation, decision reasons, and audit history. |
| Offline intake | Prove offline requirements separately. | Mobile offline forms are documented. Jotform conditional logic and form features | Implement synchronization and resolve conflicting edits. |
| Immediate handoff | Webhooks push submissions to an endpoint. Typeform webhooks | API supports custom integrations. Jotform API | Queue accepted submissions and make downstream writes idempotent. |
| Historical retrieval | Responses API returns JSON; very recent responses may lag. Typeform Responses API | API includes forms and submission operations. Jotform API | Export normalized requests and original attachments. |
| Best fit, our assessment | Teams prioritizing a guided response experience. | Teams needing broader form-centered operations. | Intake whose correctness depends on existing business records. |
Branching is useful; live validation is a different requirement
Both products can adapt a form. Jotform also documents conversational cards, so “one question at a time” should not be treated as an exclusive capability without testing. Choose the interaction by whether the intended respondent can complete it accurately, not by a generic claim that one format always converts better. Jotform conditional logic and form features.
Live entitlement is a different problem. If a requester must be an active customer on a qualifying contract, a hidden field or prefilled URL is not proof of authorization. A trusted server needs to associate the request with the authenticated person and check the current contract. A custom validation endpoint can perform that check while a hosted form still collects the remaining information.
Measure the proportion of submissions that become valid work without manual correction. Include mismatched account names, unreadable uploads, missing evidence, duplicates, and requests that use an expired policy. Those examples reveal whether the improvement belongs in the form, the validation service, or the staff review screen.
| Intake test | What to measure | Consequence for buy or build |
|---|---|---|
| Existing customer with a similar name | Correct account association | Build trusted identity matching if manual selection remains error-prone. |
| Changed answer changes eligibility | Hidden-field behavior and final server validation | Branching must not retain invalid stale data. |
| Large or invalid attachment | Upload feedback, quarantine, and reviewer access | Storage limits and safe file handling affect the real scope. |
| Duplicate submission | One request or a clearly linked revision | Deduplication is a business rule, not just a UI message. |
| Reviewer requests more evidence | Request state and complete response history | A long-running application may be more suitable than a one-time form. |
| Integration endpoint is unavailable | Submission retained, retried, and reconciled | Hosted capture still needs reliable downstream delivery. |
Model quotas and retained services
For Typeform, a large number of forms does not imply unlimited responses. For Jotform, evaluate more than the monthly submission number: storage and payment-related or document limits can matter to the actual workflow. Budget for the tier that satisfies collaboration and security needs, not only the volume estimate. Typeform plans; Jotform plans.
The custom path still uses hosting, a database, object storage, authentication where needed, transactional email, and possibly a payment processor. Include abuse prevention, file scanning, observability, accessibility work, and the time to change business rules. Avoid storing payment-card data simply because a custom interface gives you more control over fields.
Do not assume polling is immediate delivery. Typeform's Responses API documentation warns that very recent submissions may be absent, giving roughly 30 minutes as an example. Use webhooks for timely handling and historical retrieval for reconciliation, with a durable record keyed by the submission identifier. Typeform Responses API; Typeform webhooks.
Build a request lifecycle, not a second spreadsheet
A useful first version might include a submitted request, validation results, a review queue, a request-for-information state, and a final decision. Save the policy version used to make the decision. Separate the original answers from corrections made by staff so the history remains explainable. If a customer returns later, show exactly what is missing rather than asking for the whole form again.
Permissions should cover individual requests and files. A reviewer assigned to one customer must not gain access to every uploaded document by guessing a URL. A removed teammate should lose access both in the portal and in any integration used to retrieve data. Export a sample completed request with its attachment references, decisions, and timestamps before treating portability as solved.
Run a pilot through actual review and completion, not just submission. Test keyboard and mobile use, slow connections, integration failure, and a second maintainer's ability to change a rule. Buy if the hosted workflow produces clean intake. Extend if one validation or approval service closes the gap. Build the full application when the continuing request lifecycle is the essential product.
Frequently asked questions
Is a custom form enough to replace an intake platform?
Only if the requirement is genuinely limited to the form. For an operational intake, the valuable custom work is often validation, routing, status, and correction after the initial submission.
What would a first custom intake application include?
Create a guided intake connected to the current account and request model. Validate information on the server, show only relevant questions, store attachments with controlled access, and create a request with a stable reference. Give customers a way to correct a submission without creating a duplicate.
How should we compare the cost of Typeform, Jotform, and a custom build?
Include the labor after submission, not just response volume. For custom intake, budget ongoing accessibility checks and maintenance of account and file integrations. Compare the same scope and planning horizon, including implementation, retained services, maintenance, and support. A lower subscription bill alone does not establish a lower total cost.