Progressive profiling
Collecting a few profile details now and asking for more later, so each form stays short and never repeats a known question.
See it
What it is
Progressive profiling collects a small amount of user information at first, then asks for different details during later visits or moments of value. A first form might request only an email; a later download can ask for role, and a sales handoff can ask for company size. HubSpot ships the idea as progressive fields on its forms, which swap in the next unanswered question for a known contact.
Reach for it when a long form blocks signup but the business still needs richer qualification data. Store each answer on one profile, hide questions already answered, and ask only for information that changes the next experience or action.
Gotcha: breaking one interrogation into five interruptions is not an improvement. Explain why each new detail is useful, let people skip nonessential questions, and do not treat inferred or stale data as a fresh answer. Sensitive data still needs a legitimate purpose and appropriate consent no matter how gradually it is collected.
Ask AI for it
Build a progressive-profiling flow for [journey] using these approved fields and purposes: [fields]. Ask only for email at first conversion, then choose at most one unanswered field at each later value moment. Persist answers on the authenticated server-side profile, prefill known values, and use the HTML `autocomplete` tokens `email`, `name`, `organization`, and `tel` where they match the field. Return the field sequence, decision rules, form copy, data model, validation, skip behavior, and tests for anonymous-to-known profile merging. Never ask again for a confirmed answer or collect a field without its supplied purpose.