Prompthon-IO Business Data Analysis
Own Analyze in Lesson 4. Read safety, persistence and the runnable README before executing the selected workflow.
Workflow
- Select one local CSV/XLSX/clean.json or a canonical course dataset with rows. Confirm what one row means, date range, population and denominator. If the remote record has metadata only, ask for its explicitly selected local artifact; do not invent rows.
- Profile shape, column types, nulls, exact duplicates and parse problems. For CSV/XLSX, reuse Structure's reader without applying a rewrite. A schema can clarify dates/currencies, but analysis does not modify input.
- Summarize categorical counts and numeric min/max/sum/mean/median by unit. Keep contact identifiers out of categorical values in stored reports. Flag invalid, negative and IQR-outlier values for review; a flag is not proof the source is wrong.
- If stage/value fields exist, calculate stage counts, closed-only win rate and open/won values by currency. State the denominator and row-grain assumptions. No closed deals means an undefined rate, not 0%; never add CAD and USD or invent an exchange rate.
- Produce Overview, Data Quality, Key Patterns, Business Insights, Recommended Next Questions and Source / Query Evidence. Distinguish descriptive observations from causes or forecasts. If duplicate/grain concerns are unresolved, label totals provisional and return to Structure for review.
- Save a new analysis report/run with source hash or canonical dataset revision and calculation description. Read back that record. Verify the source hash is unchanged; only report artifacts and analysis records may be new. CRM changes require the separate Operate workflow.
Shared boundary
Use the course-support client for local or explicitly configured Prompthon storage. Remote organization/workspace, server-derived actor, scopes, revisions and canonical readback are mandatory. The Web App backend remains a tracked dependency; never give learners a Neon connection string. See source notes for licensing and the original implementation boundary.