Reporting Analyst -- BuildOps / Sigma (Ongoing | Part-Time | Remote)

Reporting Analyst -- BuildOps / Sigma (Ongoing | Part-Time | Remote) About the Company We're a Florida-based multi-entity services company operating across landscape maintenance, builder services, and commercial construction. We run BuildOps as our field service management platform and use its embedded Sigma reporting environment for operational analytics. We're in growth mode and need to build out a reporting library that gives our operations leaders clear visibility into visits, labor hours, and financial performance at the job and service agreement level. What We're Looking For We need a part-time reporting analyst who is comfortable working inside Sigma and can translate operational data into clean, usable reports for a field service business. This is not a financial accounting role -- it's an operational reporting role. You'll be working directly with operations and department leaders who need to understand what's happening on the ground: which visits were skipped, where hours are running over, and where margin is being left on the table. You'll work day-to-day with our leadership team and directly with department managers in the field. Good communication and the ability to ask the right questions before building the wrong thing are just as important as technical skill. The Work We have a defined initial report backlog organized into three categories, each requiring reporting across multiple dimensions (by account manager, by location, by service type, by date range, by customer, by property, and others): Visit Reports -- Skipped Visits, Overdue Visits, Extra Visits, Go-Backs, Early Visits Used Hours Reports -- Hours vs Budgeted, Scheduled Hours, Planned Hours, Unscheduled Hours, Unplanned Hours Financial/Performance Reports -- Budget vs Actual, SA Revenue, Pull Through Revenue, Unplanned Expenses, Expenses Remaining, Profitability, Pull Through Profitability, Pull Through GP vs Estimated, Pull Through Proposed $s, PT Awarded $s, PT Win/Loss Ratio by count and dollars, PT Average GP across Proposed/Awarded/Completed Beyond the initial backlog, there will be ongoing work to refine, improve, and expand reporting as the business evolves. This is designed to be a long-term engagement. Occasionally there will be light Excel work -- exporting, structuring, or formatting data for specific audiences. That's secondary to the Sigma work. How We Work Simple requests should be turned around within 2 business days. For anything more complex, give us a time estimate upfront and wait for approval before proceeding. Specifically: Under 3 hours -- just do it and bill accordingly Over 3 hours -- send an estimate, wait for a green light We don't want to micromanage. We do expect proactive communication and no surprises on the invoice. What You Need to Bring Hands-on experience in Sigma (required -- this is the primary tool) Familiarity with field service, landscape, or maintenance operations data is a strong plus -- understanding what "skipped visits" or "pull-through revenue" means in context will save everyone time Ability to learn the BuildOps data model quickly -- we can orient you on the business logic, but you need to be comfortable exploring a new data environment Strong communication; you'll be interacting with operations managers who aren't data people, so translating what you're seeing and asking the right clarifying questions matters Light Excel competency for the occasional export or formatted summary Engagement Details Type: Ongoing contract Hours: Variable, estimated 10-40 hours/month Location: Remote Availability: Must be responsive within 1 business day and able to turn around simple requests within 2 business days How to Apply Please include in your proposal: Your Sigma experience -- how long, in what context, and what kinds of reports or workbooks you've built Any experience with field service, maintenance, or service agreement-based businesses -- even brief context helps A specific example of a reporting backlog or reporting project you worked through end-to-end, and how you managed scope and communication with the stakeholders you were supporting Generic proposals will not be considered. We're building a reporting practice from the ground up and want someone who wants to grow with it.