Customer interviews for people who hate jargon

Why this comes up

Every month a client asks us about customer interviews. The short answer is: start smaller than you think.

If you only read the checklist near the bottom, that is fine. It carries most of the value.

Working out a budget? See mobile app development cost.

Where things usually break

Budget attention, not just money. Customer interviews works when one person owns it and reviews it weekly for a month. After that it mostly runs itself.

Almost every failure we have seen with customer interviews traces back to skipping the boring middle: naming things clearly, writing the confirmation message, testing on a real phone with real thumbs.

Measuring whether it worked

Price it end to end. A cheap start plus a year of patching is rarely cheaper than getting customer interviews right the first time, and the patching arrives when you are busiest.

Pick one number to watch. For customer interviews it is usually completed actions — bookings, orders, replies — not visits. Visits flatter you; completions pay you.

The parts people skip

The best examples of customer interviews are boring on purpose. Clear words, obvious next step, nothing blinking. Personality lives in the copy and the photography, not in animation for its own sake.

Write for the person who is tired, on a bus, on a cracked screen. If customer interviews works for them it works for everyone else too.

• ✓Load time under three seconds on cellular
• ✓A price or a range, in plain numbers
• ✓A backup and a way to restore it
• ✓Proof: reviews, photos, real names
• ✓An owner's name next to each task
• ✓The single action you want from a visitor
• ✓A support path that answers within a day

Making it easy for the customer

Customers judge customer interviews in about five seconds. They are asking three silent questions: what is this, is it for me, what happens if I tap the button. Answer them above the fold.

Keep a short log of what you changed and what happened. Six months of notes about customer interviews is worth more than any course.

What we would do differently

Plan the second month while you are planning launch week. Customer interviews that nobody owns after launch decays quietly, and decay is harder to sell to your team than a fresh build.

Write down the single outcome you want from customer interviews before touching a tool. One sentence. If you cannot write it, the project is not ready — and no amount of design will rescue a fuzzy goal.

Questions people ask

Do I need to be technical to handle customer interviews?

No. You need to make decisions and supply real information. We handle domains, hosting, deployment and the technical maintenance.

Can we change things later?

Yes. Every build ships with revisions, and you own the domain, the content and the finished product outright.

How long does customer interviews usually take?

For a small business, expect one to three weeks of real work once content is ready. The waiting is almost always content, not build time.