Skip to content
English
  • There are no suggestions because the search field is empty.

What Is Analytics?

Learn about what Analytics shows you and the key terms used across your reports.

On This Page


Understanding Analytics

Analytics is JobNimbus's reporting tool pulling directly from your JobNimbus data. Your reporting lives in the Hub, which shows the Reports Library of pre-built reports organized by category, like Sales or Work Orders, along with any custom reports and folders you create. Each report has a Dashboard, the read-only view your team sees day-to-day. On Analytics Enterprise, reports also have a Workbook page which allows you to build or edit charts and dashboards.

Reports draw from data such as:

  • Estimates
  • Invoices
  • Payments
  • Material Orders
  • Work Orders
  • Profit Tracker
  • Job and Contact workflow statuses

Data refreshes about once an hour. You can export a report, schedule it for delivery, or ask a question in the Analytics AI chat bubble on your dashboard.

Depending on your plan, you may also have Analytics AI, which adds the AI chat agent, or Analytics Enterprise, which lets you build and customize your own reports and dashboards from scratch. Check out this article for example prompts to use with Analytics AI.

Glossary

These are the terms and calculations used across Analytics reports. You can also see them anytime inside Analytics by selecting Definitions in the top right.


Sales and Revenue

  • Sold: A job is sold once it reaches the Sold stage in your workflow. JobNimbus stamps a Sold Date at that moment. It's based on where the job sits in your workflow, not on Estimate paperwork. See Total Sales.
  • Total Sales: The dollar value of approved and invoiced work on jobs you've marked sold. An Estimate counts when it reaches Approved or Invoiced status and its job has a Sold Date. JobNimbus uses the Estimate total, and if a job has several qualifying Estimates, they all count. A sold job with no approved or invoiced Estimate adds $0.
  • Close Rate: Of the jobs that came in as leads, the share you sold. Jobs with a Sold Date divided by jobs with a Lead Date. Each job counts once, no matter how many Estimates it has. Jobs that ended up Lost still count as leads, because reaching Lost doesn't remove a job's Lead Date.
  • Estimating Conversion Rate: Of the jobs you estimated, the share you sold. Jobs with a Sold Date divided by jobs with an Estimating Date, which is set when a job reaches the Estimating stage.
  • Sign Rate: The share of Estimates you sent that got signed. Estimates signed divided by Estimates created. This is measured per Estimate, not per job, so a job with three Estimates counts three times. Signing is its own event, separate from status.
  • Accounts Receivable: What customers still owe you: billed minus paid. Aging counts days past an Invoice's due date, not its Invoice date. Partial payments count too, so a partly paid Invoice ages only its remaining balance. Aging buckets: Not Overdue, 1–30, 31–60, 61–90, and 91+ days past due.

Records and Stages

  • Jobs and Contacts: Two separate kinds of records. A Contact is a person or company. A Job is a piece of work. Most questions are about one or the other. Combining them inflates counts, since one Contact can have several Jobs. Dashboards state which they're counting.
  • Record Type and Job Type: Record Type is whether a record is a Job or a Contact. Job Type is your own category for the work, taken from the name of the workflow the Job is on, such as Retail, Insurance, or Commercial.
  • Pipeline Stages: The standardized stage sequence across JobNimbus: Lead, Estimating, Sold, In Production, Accounts Receivable, and Completed. Lost is an end state a job can reach from any stage. Your workflow can have as many statuses as you need; every status maps to one of these stages.