“What does the data say?” is usually too vague to be useful.
A company may have a CRM, accounting software, spreadsheets, call records, web analytics, inventory exports, and years of customer history. That does not mean it has an answer. Data becomes useful when a specific person needs to make a recurring decision and the information arrives in time to help.
Southern Utah companies operate across fast-growing service markets, construction, healthcare, tourism, professional services, retail, manufacturing, technology, and ecommerce. The right analysis varies, but the discipline is the same: define the decision before polishing the dashboard.
“Which estimate sources produced the most gross profit last quarter after cancellations?” is useful. “Can AI find insights in our CRM?” is a demo request.
Build a metric dictionary before building a prediction.
Small-business data often looks obvious until two employees define “customer,” “lead,” “booked,” “revenue,” or “complete” differently. AI cannot resolve a business definition the company has never agreed on.
Name the field
Use a plain business name and the exact source column. Record whether the field is entered by a person, calculated, or imported.
Example: “Qualified lead” is not the same as “form submission.”Define the formula
Write the numerator, denominator, filters, date used, exclusions, and rounding rules.
Example: close rate may use created date, decision date, or completed-job date.Record the grain
Determine whether each row represents a person, lead, call, invoice, line item, appointment, job, or day.
Mixing grains creates totals that look reasonable and are wrong.Mark missing data
Distinguish zero, unknown, not applicable, not yet recorded, and intentionally withheld.
A blank is not always zero.Track changes
Note when software, pricing, categories, staffing, campaigns, or data-entry habits changed.
A trend break may be a process change, not customer behavior.Use AI where explanation and repetition meet.
Which sources create qualified, profitable work?
Separate volume, qualification, close rate, average value, gross profit, and time to conversion.Where do good opportunities stall?
Compare stage age, follow-up activity, objections, owner, and outcome without treating correlation as cause.Which work creates rework or delay?
Group reasons, handoffs, job types, teams, and time periods. Review category quality before blaming a department.What questions and problems repeat?
Cluster calls, tickets, reviews, and emails after removing or protecting personal information.What changed from plan to actual?
Explain the variance by volume, price, mix, timing, cost, and one-time events. Keep accounting review in place.Where is staff time being absorbed?
Estimate frequency, handling time, wait time, correction time, and the portion that is actually recoverable.AI is particularly useful for writing queries, explaining formulas, summarizing patterns, testing alternate groupings, and turning a reviewed analysis into a readable brief. It is less trustworthy when definitions are hidden, samples are tiny, the data has changed, or the system is asked to guess why something happened.
Separate facts, explanations, and decisions.
A decision brief should make it difficult to confuse an observed number with a theory. Use four sections every time:
What changed, by how much, during which period, and according to which defined metric.
What may have contributed. Label this as a hypothesis until additional evidence supports it.
Missing fields, small samples, quality concerns, outside events, and questions the dataset cannot answer.
What will we do, who owns it, when will we know whether it worked, and what result would cause us to change course?
Prove one review before connecting every system.
Write the exact question, current method, owner, timing, and cost of uncertainty.
Export only the needed fields. Remove duplicates, identify blanks, normalize dates, and protect sensitive data.
Reconcile row counts, revenue or job totals, date ranges, and key calculations with the source system.
Run the analysis, test alternative explanations, inspect outliers, and verify calculations independently.
Show observations, hypotheses, unknowns, source notes, and proposed actions.
Record the decision, owner, due date, and questions that should improve the next dataset.
Measure decision quality and preparation time.
Do not let a fluent explanation outrank a verified total.
Protect customer and employee information, limit datasets to the task, and use an AI environment approved for the data involved. Important calculations should be reproducible outside the model. Important conclusions should show the source period, filters, definitions, and uncertainty.
Recalculate key totals and formulas with deterministic tools. Language models can produce incorrect arithmetic and code.
Remove personal information when names are not needed. Apply role-based access and retention rules.
Ask what evidence would disprove the explanation and whether a process or measurement change created the pattern.
Useful questions before you build.
Can AI analyze an Excel or CSV file?
Yes, many tools can summarize fields, write formulas, create charts, and test questions against a file. The result is only as reliable as the definitions, completeness, calculations, and permissions. Verify important totals and conclusions independently.
What data should a small business analyze first?
Choose data connected to a repeated decision, such as lead response, estimate conversion, job profitability, service backlog, inventory movement, customer retention, or cash collection. Start with one dataset and one owner rather than combining every system.
Can AI predict future sales?
It can assist with scenarios and forecasting, but a forecast is not a promise. Small datasets, seasonality, pricing changes, one-time events, and changing market conditions can make confident projections misleading. Show assumptions and ranges.
Do we need a data warehouse or business-intelligence platform?
Not for every first project. A controlled spreadsheet or export may be enough to prove value. Invest in larger infrastructure when repeated manual preparation, access control, data volume, or freshness becomes the measured bottleneck.
Sources and further reading
- NIST AI Risk Management Framework
- U.S. Census Bureau QuickFacts for Washington County, Utah
- U.S. Bureau of Labor Statistics, St. George area economy
- Utah Office of Data Privacy
- Washington County Economic Development
Local community discussions are treated as qualitative signals, not statistical evidence. Examples and calculations in this guide are illustrative unless a source is cited.