The jdwin map is a place-selection instrument, not a results dashboard. Analysis does not start until you confirm the resolved place by its real name.
Selection only, no early run
After sign-in, the map sets place and spatial context for the decision you are about to request. It does not host operational feasibility outputs as a substitute for the report. That separation keeps the path legible: select → confirm → analyze → report. Marketing and documentation pages do not open the operational map before authentication; “Start analysis” calls to action lead to register or login, then into the app surface. Visitors stay in the public story; decision-makers work inside an account that can own the verdict.
Mandatory confirmation
Smart search may propose a place close to your intent. Confirmation protects you from repeated place names across cities, from a pin that drifted away from the address you meant, and from running analysis on coordinates you never reviewed. For location-dependent ventures the rule is product doctrine, not a soft hint: no analysis without confirm. Digital and online projects (an app, a SaaS platform, an online store) are the one exception: jdwin detects them from your wording and studies them market-first, with no pin and no confirmation step. Side-by-side site comparison with live context is listed among Max package benefits when you need to weigh two locations inside the same decision culture.
No analysis without confirm, a product rule, not an optional hint.
Operating flow
1Set the placeBy text, voice, or map click. The shown name must match the real place you intend.
2Review contextSector and model come from the query text. There is no separate mode key for digital projects.
3Confirm, then analyzeAfter confirm, analysis begins and progress appears inside the report, the only results surface.
Loading your page… 
