Don't start from blank.
Start from proven.

A general-purpose 'get in touch' form for a website, footer, or email signature.

Collecting what a prospect wants to see so the sales team can tailor the product demonstration.

A light first-touch form for companies interested in exploring a partnership.

Converting website and campaign visitors into identifiable leads: who they are, what they're after, and how they want to be followed up with.

Qualifying inbound prospects against your ideal customer profile: firmographics, the real business problem, urgency, budget, authority, and timeline.

Prospective clients requesting a consultation with a consultancy, agency, or professional services firm.

Collecting what a business needs to estimate the cost of a product, project, or service, without a back-and-forth email thread.

Capturing structured requirements from an organization that wants a proposal: objectives, scope, deliverables, constraints, and how the decision will be made.

Evaluating applicants for a partner program: market reach, capabilities, capacity, and what they want the partnership to become.

Capturing signups and light segmentation ahead of a launch.

Growing an email list with an explicit frequency preference.

An interactive self-assessment for content marketing and lead engagement.

Internal teams formally requesting marketing support for a launch, campaign, or promotion.

Collecting everything a creative, design, content, or video team needs before starting work on an asset.

The front door for customer problems and help requests. Branching asks technical, billing, and account questions only when they apply, and severity is captured up front so urgent issues surface first.

An open-ended relationship check-in that captures what customers value and where you fall short, in their own words.

The classic three-question NPS pulse, styled to hold attention.

A lightweight satisfaction pulse after an interaction or purchase.

A structured satisfaction read across product quality, support, and ease of doing business.

Capturing the buying experience while it's fresh: satisfaction, friction, and repurchase intent.

Sent after a purchase, an interaction, or a project wraps. Captures a clean satisfaction score, then the interviewer draws out what drove it, and a low score routes straight into what went wrong.

The relationship-level loyalty question, asked properly. Every band gets a different conversation: detractors are asked what to fix, passives what's missing, promoters what they'd say when recommending you.

Sent after a customer completes a task: setup, a purchase, a return, a support request. Scores the effort involved, then locates the exact obstacles, detours, and wasted steps.

Sent when a support conversation ends. Confirms whether the issue is truly resolved, scores the experience, and rates speed, ease, competence, and communication, with unresolved cases routed straight back.

The formal channel for a customer who wants a problem escalated. Captures the complete account: what happened, when, who was involved, what's been tried, the impact, and the resolution they expect, ready for management review.

Sent when a customer cancels, downgrades, or fails to renew. The interviewer digs past the polite answer to the specific moment, comparison, or unmet expectation that drove the decision.

Sent right after the contract is signed or the purchase is made. Collects the facts onboarding needs, then gets the customer talking about goals and success criteria while motivation is at its peak.

Sent a week or two after a customer starts using the product. Measures setup progress and early confidence, and gets specific about anywhere the experience hasn't matched the pitch.

Sent to happy customers when marketing needs testimonials, case studies, or reference stories. The interviewer works like a feature writer: before and after, measurable results, and the line worth quoting.

Letting users and internal teams propose product improvements, in a way that yields the underlying user problem and its cost rather than a bare feature spec.

A periodic deep-dive with users of a product, feature, or experience: satisfaction, real usage, likes, dislikes, friction, and gaps, ending with where they'd spend your next improvement cycle.

Collecting actionable bug reports from customers or internal testers: what broke, how to make it happen again, how bad it is, and the environment it happened in.

A general-purpose qualitative interview about how users actually work, grounded in recent concrete examples.

A jobs-to-be-done discovery interview run before you build: the situation that triggers the need, how people cope today, what they've tried, and the forces that would govern a switch.

A structured market-research survey showcasing the full question-type palette.

Screening volunteers for usability tests, interviews, diary studies, or beta programs: role, experience, real behaviors, tools, availability, and contact details, all in filterable structured answers.

The follow-up conversation after a participant attempts tasks in a product or prototype: completion, difficulty, confidence, and a deep dig into every confusing moment while it's still fresh.

Testing a product, feature, or business concept with target users: comprehension, perceived value, fit, concerns, and honest likelihood of use, with the reasoning behind every judgment.

Willingness-to-pay research in the Van Westendorp style: current spend, perceived value, the four price anchors from suspiciously cheap to out of the question, and the reasoning behind each.

A short, recurring check-in on morale, workload, and blockers between full engagement surveys.

Collecting job applications in one consistent structure: contact details, work history, education, skills, links, availability, and work authorization, ready for side-by-side review.

A short screen sent before interviews: experience level, core skills, availability, work preference, and compensation fit, plus the motivation behind the application.

Collecting the practical details before a new employee starts: contact info, equipment and access needs, work location, emergency contact, and welcome-kit preferences.

The annual or twice-yearly engagement survey: structured scores across motivation, belonging, trust, workload, recognition, communication, and growth, plus a conversation about whatever is most strained.

Collecting structured peer, report, and manager feedback about one person during review cycles, in a way that yields examples rather than adjectives.

Measuring a training, workshop, or enablement session: relevance, clarity, instructor effectiveness, the confidence shift, and whether any of it will get used.

Sent when an employee resigns. The interviewer digs past the polite answer to the moments, relationships, and unmet expectations that actually drove the decision.

A standardized request form for new projects, analysis, development, and design work, so every ask arrives with the problem, the stakes, and the definition of done.

The internal front door for technical problems. Category and severity route each request, and branching asks hardware, access, and network questions only when they apply.

Employees reporting anything the office needs fixed: repairs, cleaning, equipment, temperature, and safety hazards, with hazards flagged and secured first.

Employees requesting access to a system, tool, or dataset, captured with the permission level, business justification, duration, and approver that a least-privilege review needs.

Documenting a proposed change to a system, process, policy, or production environment before it happens, with enough context for a change review to approve and schedule it.

Recording workplace accidents, injuries, near misses, property damage, and safety concerns while the details are fresh, in neutral language that establishes facts rather than fault.

Employees submitting out-of-pocket business expenses for reimbursement.

Employees requesting approval to buy a product, service, subscription, or piece of equipment.

Requesting new or additional budget for a project, department, initiative, or event.

Gathering operational details from a new supplier before the relationship goes live: contacts, services, compliance posture, invoicing, and support.

Run before a selection, renewal, or periodic review. The internal owner of the vendor relationship rates it, and the interviewer digs into the concrete incidents behind each score.

Selling tiered passes and add-ons for a conference or paid event.

Letting customers or prospects request a meeting slot without a scheduling tool.

General-purpose registration for a conference, webinar, workshop, or meetup, with in-person needs asked only of in-person attendees.

Sent after a conference, webinar, workshop, or meetup to capture attendee reactions while they're fresh, and to shape the next agenda.

The way employees report suspected phishing, compromised accounts, data exposure, unauthorized access, and lost devices, tuned so people report fast instead of hiding mistakes.

Recording that an employee reviewed and accepted a policy, code of conduct, or security standard, with questions and compliance concerns routed to follow-up instead of lost.

Audience-building content. The result is the thing people post, and every share carries your brand.

Newsletters, events, community engagement. A graded quiz with a score people compare.

Top-of-funnel marketing. The result is a recommendation, so the share is also an ad.

Pricing pages and paid landing pages. Replaces a pricing table nobody reads with an answer.

Lead magnets and consulting intake. A score people want, in exchange for knowing who they are.

Onboarding and compliance training. A pass mark, with the explanations shown after.

Inbound qualification. Routes a scored outcome to your CRM while the prospect gets a genuine answer.

Community and technical audiences. A difficult quiz is a credibility signal, and the explanations are the content.

Deciding what stays on a small food or retail menu: which items customers would actually keep, why the favourite is worth the shelf space, and how the range compares with what they can buy elsewhere.

Post-play feedback after a playtest, demo, or early-access build: how someone played, whether they'd come back tomorrow, what stuck with them, and the moment that nearly ended the session.