How to conduct user interviews and turn them into posts

How to conduct user interviews and keep what you learn: a consent form, a debrief form, and a rule that routes quotes into your weekly post queue.

To conduct user interviews that pay off, ask about specific past behavior, record with consent, and write a debrief within an hour of hanging up. The step most founders skip is the last one. This guide shows how to use a short scheduling and consent form before each call and a debrief form after it, so quotes and themes land in your weekly post queue.

Start from the interview template

Why interview insights die in notes

You probably already talk to customers. The call goes well, you scribble a few lines in a doc, and two weeks later you cannot say which customer used the phrase that explained your whole onboarding problem. Three things usually go wrong.

The notes have no structure, so nothing can be searched or counted. Nobody asked the customer whether you could quote them, so a good line is stuck in a private doc. And the debrief happens "later," which in practice means never.

Fix those three and every interview becomes raw material. The same quote can drive a product decision on Monday and a LinkedIn post on Thursday.

Send every interviewee a short form instead of a calendar link alone. It books the slot, asks one warm-up question so the call starts mid-story, and records two permissions you will need later.

Field	Block type	Why it is there
Name, email, role and company	Short answer, Email	Lets you match the call to a customer record
Time slot	Embed anything (Calendly)	Scheduling stays in the tool you already use
"What were you trying to get done the last time you dealt with this?"	Long answer	Gives you a real story to open with
May we record the call?	Multiple choice	Recording needs a clear yes, not an assumption
How may we use what you say?	Multiple choice	Name and company, anonymous only, or do not quote
interview_id	Hidden field	Ties the booking to the debrief later

Use conditional logic on the recording question. If someone answers no, show a line saying you will take written notes only. It removes any awkwardness on the call itself.

The quote permission field is the one that matters for content. Three options are enough, and "do not quote" must be a normal, easy choice. This is a product decision, not legal advice, so check the consent rules where you and your interviewees live.

Running the interview itself

You do not need a long script. You need a few habits.

Ask about the last time something happened, not what they would do in theory. "Walk me through the last time you onboarded a new client" produces a story. "Would you use a dashboard like this?" produces politeness.

Do not pitch. If you start explaining your product, the interview becomes a sales call and the customer starts managing your feelings. Let silences run a few seconds longer than feels comfortable; people fill them with the useful part.

Follow the emoton. When someone says "honestly, that was a nightmare," stop and ask what happened next. The sentences you will want to publish tend to come right after a sigh or a laugh.

Keep one line open in your notes labeled "quotable." Whenever the customer says something sharp, write it down word for word. You will be glad of it in the next section.

Capture within an hour: the debrief form

Right after the call, spend two minutes on a second form. It is for you, not the customer, and every field exists so the output can be sorted later.

interview_id, passed in as a hidden field so it matches the booking
The single best quote, word for word (long answer)
Theme (dropdown with your running list, such as pricing cnfusion, onboarding friction, switching trigger)
A one-line post angle in your own words
Quote permission, repeated from the booking so you cannot forget it
Anything that needs action tis week (short answer)

A dropdown for theme feels restrictive and is the right call. Free-text themes drift ("pricing," "price," "cost worries") and you end up unable to count anything. Add a new option when a call genuinely surfaces one.

Qwenvo's AI triage also reads each submission and assigns a category, priority, sentiment and a short summary, which is useful when you run several calls a week and want the sharpest ones surfaced first.

Step-by-step setup

Our team builds Qwenvo, a free form builder, and it is what we would use for both forms. The steps below take under an hour.

Open the user interview scheduling template and duplicate it. Rename it to something your interviewees will recognize.
Add your Calendly link with the Embed anything block. Qwenvo has no built-in scheduling, so this is the way to do it.
Add the recording and quote permission questions as Multiple choice blocks. Put the conditional logic on the recording answer.
Add a hidden field called interview_id. Pass it in the link you send, for example ?interview_id=int-0142.
In the Settings drawer, turn on confirmation emails to respondents and email notifications to yourself. Switch off the Qwenvo branding badge.
Optional but nice: on the Domains page add a subdomain such as forms.yourbusiness.com, add the CNAME and TXT records, click Verify, and pick it on the Share tab.
Build the debrief form the same way, using the field list above. Keep it to one page.
In the debrief form's Settings, add a webhook pointing at your automation tool (Zapier, Make and n8n all accept a webhook trigger). The webhooks help article covers the details.
Submit a test of each form and confirm the row reaches your automation with interview_id intact.

All of that is free on Qwenvo: webhooks, the REST API, the MCP server, AI triage with routing, partial submissions, a custom domain, badge removal, unlimited teammates, and custom design and CSS. Several of those sit behind Tally's paid Pro plan at $29 a month, such as custom domains, teammates, partial submissions and custom CSS, so it is worth comparing if you are choosing now.

Two honest caveats. Qwenvo launched in October 2026, so there are few reviews yet. And a bare scheduling form like this one does not replace a real calendar tool; Calendly does the booking, the form does the consent and context.

Build your interview form free

Routing quotes and themes into the weekly post queue

This is where the interview stops being a note. Once the debrief webhook fires, your automation maps the fields into one record and drops it in the queue that feeds your content.

In the Founder Content Engine, a weekly system that turns a 30-minute founder call into LinkedIn posts, a newsletter, short clips and cross-posted social content in your voice, this debrief is a second input next to the weekly call. The call supplies your opinions. The interviews supply evidence and customer language. Everything still passes through the approval step before anything is published.

A mapped record can be as simple as this (the field names are ours, set in your automation, not a fixed Qwenvo format):

{
  "interview_id": "int-0142",
  "quote": "I spent more time explaining the report than reading it.",
  "theme": "reporting friction",
  "post_angle": "Why your dashboard needs one sentence on top",
  "quote_permission": "anonymous_only",
  "priority": "high"
}

The routing rules then look like this:

Condition	Where it goes	What happens
quote_permission = do_not_quote	Insights doc only	Never enters the post queue
quote_permission = anonymous_only	Post queue, flagged	Drafts must strip name and company
quote_permission = named	Post queue	Eligible to use with attribution, after your approval
AI triage priority = high or urgent	Slack incoming webhook	Quick ping so the strongest quote is used this week
Theme count reaches 3 in a month	Newsletter topic list	A recurring theme becomes a longer piece

Qwenvo's triage routing can send matching submissions to up to five email addresses or a Slack incoming webhook, so the Slack ping needs no extra tool. If you also want the raw data in a spreadsheet, send the same webhook there; Qwenvo's one-click Google Sheets connection is still being rolled out.

Check the permission field before every draft goes out, and message the customer first if a quote is going out under their name. A flag in the queue helps, but it does not replace asking.

Measuring whether it works

Track three things per month: interviews completed, debriefs filed within 24 hours of the call, and posts or newsletter sections that used an interview quote. If debriefs lag behind interviews, the form is too long. If quotes pile up unused, the angle line is too vague.

Partial submissions are handy on the booking form. If someone opens it and leaves halfway, that shows up as an incomplete row, whcih is a prompt for a polite follow-up.

Questions teams ask

How many user interviews should I run?

There is no magic number. Keep going until new calls stop changing your list of themes. If the fifth call still surprises you, schedule more.

Do I have to record the call?

No. Written notes work, and the booking form should make that an easy answer. If you do record, get the yes in writing on the form so you can find it later.

Can I use a customer's words in public posts?

Only as far as their quote permission allows, and it is cuorteous to show tjem the exact wording before it goes out under their name. The form records what they agreed to; it does not remove the need to check.

Do I need Qwenvo for this?

No. Any form builder that can post to a webhook will do the job. We recommend Qwenvo here because the webhooks, triage routing and custom domain are free, which keeps a two-form setup at zero cost.

Your next step

Open the user interview scheduling template, duplicate it, add the quote permission question, and send it to whoever you are speaking with next. Fill in the debrief form straight after that call and see whether the quote reaches your queue.