Flowlytics starts by grounding the project before anything else opens up. This setup guide explains how discovery works, what gets saved if you stop, and how documents help the platform build a stronger project foundation from the start.
Every new project begins in discovery. Flowlytics keeps the project in an in-discovery state until there is enough grounded information to support research properly. That means the platform is not just collecting labels. It is building the context that later methods, evidence, and strategy outputs depend on.
The discovery session adapts to the kind of project you are setting up. A new product idea, a redesign, and a churn problem do not need the same follow-up questions, so the platform keeps probing until the answers are useful enough to guide real work.
Flowlytics needs the product name, a clear description, direct competitors, the decision objective, and the main constraints shaping the work.
The platform also needs to understand who is affected, where the workflow breaks today, and what success needs to look like before research begins.
If setup is interrupted, discovery can pause without turning the project into a low-quality live workspace. Progress is saved exactly where it was left, and when you come back, Flowlytics reopens discovery at the right point instead of pretending the foundation is already finished.
Discovery uploads are optional, but they are useful when you already have source material such as briefs, notes, decks, transcripts, or internal context documents. Flowlytics can pull structured setup context from those files, reduce repeated manual input, and still ask for clarification if something important is missing.
Once the project is grounded, you can move into the next help-centre guides depending on what you need to do next inside Flowlytics.