Backlog Board
Every sold job by stage from awaiting measure to installed, with stalled jobs highlighted against your thresholds.
We build a window replacement management app that shows a general manager every sold job between contract and install, which crew and measure tech hold it, what is still at the manufacturer and where remakes and service tickets are piling up.
For a window company, the riskiest number is the sold backlog: revenue signed but not yet installed. A general manager approving this project wants to see that backlog by stage at any moment, without asking the install coordinator to update a spreadsheet first.
The GM will also want evidence that the app catches problems early. A unit backordered at the manufacturer, a measure that has sat unassigned for a week, or a service ticket open for a month all cost money and reviews. If the app surfaces those before a customer calls, it has earned its place.
Finally, the numbers must match accounting. A backlog figure that disagrees with what finance sees will be ignored after the first meeting.
Start with the backlog board, the crew and measure tech schedule, and two or three reports the GM already asks for in meetings. That is enough to replace the weekly backlog spreadsheet and prove the data is reliable.
Sales performance by rep, commission calculations and custom report builders can follow in a later phase. They involve sensitive pay data and agreement on definitions, and they are easier to get right once the core pipeline is trusted.
We would also give the GM a simple alert setting for each stage, so a job sitting too long in ordered or delivered triggers a notice instead of waiting to be spotted on the board.
The general manager opens the backlog board and sees a cluster of jobs in the delivered column that have no install date. Tapping into them shows the install coordinator has been out, and nobody picked up the scheduling. The GM reassigns the task to the office manager with a note.
Next, the remake report shows three remakes this month for one measure tech, all on casements. The GM checks the photos attached to those measures and sees the tech is recording the rough opening rather than the existing frame. A short training session is scheduled for the next morning.
Finally, the service ticket list shows a fogged glass ticket open for five weeks, waiting on the manufacturer. The GM flags it so the office calls the homeowner with an update before they post a review.
Every sold job by stage from awaiting measure to installed, with stalled jobs highlighted against your thresholds.
Assign measure techs and install crews across the coming weeks, with deliveries and capacity side by side.
Remakes logged with cause, product line, responsible role and cost, so patterns are visible early.
Open service requests sorted by age, with manufacturer claim status and the assigned technician.
Window sales often climb in spring and again in early fall, and the backlog swells a few weeks later as orders come back from manufacturers. That lag means the GM needs to see incoming deliveries against crew capacity well ahead of time, not when the warehouse fills up.
The app should project install demand by week from expected delivery dates, so the GM can add a subcontracted crew or stagger start dates before customers are kept waiting. In winter, when some homeowners prefer to wait, the backlog board helps the GM decide whether to offer scheduling incentives or move crews to service work.
Peak months also strain the service side. New installs generate adjustment requests in their first weeks, such as a sash that needs a balance tweak, and those tickets compete with installs for the same technicians. A combined view keeps both visible.
The first error is tracking stages that nobody updates. If the office does not change a job from ordered to delivered when the truck arrives, the board goes stale within days. Each stage needs a clear owner and, where possible, an automatic trigger from the supplier or warehouse.
The second is copying every column from the old spreadsheet. Many of them exist because the spreadsheet had no other place for notes. Decide which fields drive decisions and leave the rest in the job record.
The third is leaving the install coordinator out of design. That person knows how jobs really move, and the app should make their day easier first.
Mobile apps with SIZ Group start at $4,500. A management app with a reporting layer and connections to your CRM, accounting and supplier data will sit above that starting point. The biggest cost driver is how many systems feed the backlog and how well each one shares data.
Timeline depends on the same factors plus how quickly your team can agree on stage definitions. We would phase the work: backlog board and schedules first, then remake and service reports, then sales and commission views. Each phase is confirmed in writing before it starts, which keeps scope from drifting.
Yes, where your CRM offers API access, such as Salesforce or MarketSharp. We would read signed jobs and stages from it and add the views it lacks. We confirm each connection during the free scoping call.
If your supplier provides order status data, we can update stages automatically. Otherwise warehouse or office staff mark deliveries in the app, which takes a few seconds per order.
Yes. Reporting screens are designed for larger screens and the quick checks for a phone, all from the same backend.
Yes. Subcontracted crews can be added with their own capacity and limited access, so the GM sees the full install picture.
Post-launch support is available for fixes, updates and new reports. Most GMs add reports after the first peak season once they know which numbers they check most.
Book a free scoping call and we will map your stages, crews and reports into a management app your office will actually keep current.