A form is not a job

What Typeform, Tally and Google Forms do perfectly, and the four things a form structurally cannot do for a client job.

Published on August 19, 2026Written by Kalepio7 minute read

A brief form is already a huge step up from a three-minute voice note. If you have one, you are ahead of half the freelancers out there, and nothing in this article says otherwise.

There is still a ceiling, and it is not a missing feature. A form collects one submission. A job is what happens over the six weeks after it.

What a form does better than anything

For asking somebody twenty questions and getting twenty answers back, Typeform and Tally are excellent. One question at a time, conditional logic, the way it behaves on a phone, resuming halfway through: that is their trade and they do it better than most of the tools claiming to replace them.

And for anything that is not a job, they are the right choice, no argument. A contact form, a waiting list, a workshop signup, a survey of your clients: putting a job-management tool behind any of those would be absurd.

The ceiling arrives at the exact moment the submission stops being the end of the story.

One: there is no second round

This is the most expensive limit and the least visible at the start, because it does not show up until your third job.

You forgot a question. Or rather: you could not have asked it before reading the answers, which is the normal case. Now you need the logo as a vector, or the mock-up signed off, or the copy for three pages.

You have two options and both are bad.

Edit the form. You add the question and resend the link. Except the form is the same object: the answers already submitted no longer match the questions asked, and if the client resubmits you have two sets of answers for one job with no way of knowing which is current.

Make a second form. Now you have two links, two response tables, and nothing saying they are about the same job. By your fifth job you have twelve forms and no idea which pairs with what.

What you actually need is a second round on the same job: new questions, without touching what has already been answered. That is precisely what a form cannot be.

Two: there are only two states, and the missing one matters

To a form, a response is submitted or it is not.

To you, a job is in one of two very different states: it is waiting on you, or it is waiting on the client. That is not a nuance, it is two different kinds of work. The first is your day's work. The second is your chasing, which takes five minutes and unblocks days.

A form does not know that distinction, so you hold it by hand, in your head or in a spreadsheet on the side. That is the subject of where every job stands, without a spreadsheet, and it is where this gets paid for.

Three: the client has no address after submitting

They click Submit, the page says thank you, and that is that. From that second on, they have nothing.

They cannot reread what they answered, which they will need in three weeks when you are discussing a colour. They cannot see whether their third file went through. They do not know whether you are waiting on them. They do not know where things stand.

So they write to you, and everything after the submission happens in your inbox. The form solved the first half hour of the job and none of the rest.

Four: nothing connects to payment or delivery

A form does not take a deposit, and it cannot hold a file back until it is paid for. That is two more tools, two more links, and two more manual steps on every job.

That last point is the most underrated, because it does not take long. It just has to be done every time, and it is the one you forget on a Friday evening. On the order to ask for money in, there is deposit, balance, delivery.

The table, with no adjectives

A form A job
Asking twenty questions elegantly Excellent Adequate
Fine-grained conditional logic Excellent Simpler
Asking a question you forgot A second form A second round, same job
What the client answered stays frozen No, the form moves on Yes, by construction
Knowing who is waiting on whom Submitted or not Two distinct states
What the client sees after submitting A thank-you page The job, through to delivery
Deposit and delivery Elsewhere On the same page

The first two rows are not politeness. If what you need is a good-looking questionnaire and nothing else, take Tally and stop thinking about it.

Stay with a form if

What you are collecting is not a job: contact, survey, signup, waiting list.

Your jobs settle in one submission and one delivery, with no back and forth at all. That exists, mostly on tightly defined, repetitive work.

You already have a tool that handles the aftermath and the form is only the front door. That is a perfectly sound architecture.

Change on the day

You make a second form for the same job. That is the clearest signal there is.

You find yourself wondering which of a client's two responses is the real one.

A client asks you what they had answered, and you have to go digging in a spreadsheet to tell them.

You have a spreadsheet next to the form, and it is no longer up to date.

If you want to see what questions already written for your trade look like, before you think about tools at all: they are here, trade by trade.

Frequently asked questions

Are Typeform or Tally enough for a client brief?

For the brief itself, yes, and they do it very well. What they do not do is what comes after the submit: a second round of questions without rewriting the first answers, a state that says who is waiting on whom, and an address the client can come back to.

How do you ask a question you forgot after a form has been filled in?

With a form, by making a second form, which leaves you two sets of answers with no link between them. What you need is a second round on the same job, adding questions without touching what has already been answered.

Can you take a deposit from a form?

Some of them allow it, but the payment stays separate from the delivery: nothing holds a file back until it clears. That is the manual step you forget on a Friday evening, not the missing feature.

Is a form a bad choice for a freelancer?

No, it is a very good first step and far better than nothing. The ceiling arrives when a job has several rounds, a state to follow, and a client who needs to see what they said.

What is the real difference between a form and a job tool?

A form collects one submission. A job tool follows the six weeks after that submission: the later rounds, who is waiting on whom, the payment, and what the client can check on their own.

Kalepio asks these questions for you

You send one link, your client answers once, and you start with everything you need.

Read next