Live route board
Each crew's route, status and next stop appear on one screen, so slippage shows up before it reaches the customer.
A window cleaning manager app puts open jobs, crew assignments and each route's progress on one screen. SIZ Group would build it so the general manager can move a route or hold exterior work for rain without phoning every crew lead.
A storefront property manager emails at ten at night asking for the windows on a three-story retail row to be cleaned before a Saturday opening. The office enters the request into the work queue, and the app records the building's window count, the lift needed and the gate code for the back alley. Nothing gets lost in a forwarded inbox thread.
At 6:45 the general manager opens the app and sees the new job at the top of the queue, flagged as needing a lift. She drags it onto the crew working the closest downtown route, which the app confirms has a lift assigned that day. The crew lead receives the job card on his phone with the access notes and the before photos already attached.
By mid-afternoon the board shows which routes are finished, which windows still need a second pass and where a crew is waiting on a customer. The manager can see the whole day without phoning anyone, and the end-of-day report is ready for the invoice.
Window cleaners see most of their work shift with the weather. Spring pollen and summer dust tend to bring a rush of exterior requests, while cold months slow outside work when glass is icy and ladders and lifts cannot be set up safely.
The manager oversight app should handle this by letting the general manager set weather holds per route, so exterior jobs move to a dry day without anyone rebuilding the whole week. Storefront clients often want glass clean before a holiday weekend or a grand opening, so a rush job should be able to jump the queue with its reason logged.
The most common mistake is building the dashboard around the office rather than the route. A screen that lists customers alphabetically looks tidy, but a manager needs to see which crew is nearest to an open job and whether that crew has the right equipment.
Teams also try to make the first version do everything, from payroll to a customer portal. That usually delays the parts that matter most to the manager, such as the live board and the job queue. We would keep those first and connect payroll later through an export if the business still needs it.
Leaving out offline use is a third trap. Crews often work on rooftops and in basements where signal drops, so the crew view must keep the job card and photos on the phone and sync when coverage returns.
Each crew's route, status and next stop appear on one screen, so slippage shows up before it reaches the customer.
New requests land in a queue sorted by building type, access needs and whether a lift or extension pole is required.
Jobs that need a lift go to crews trained on that equipment, and the app blocks any assignment that does not match.
Exterior jobs pause when the forecast crosses limits you set, and affected customers receive a drafted notice for approval.
Completed windows, photos and notes roll into one report the billing team can export without retyping.
Owners, managers and crew leads each see only the screens their work needs, which keeps pricing and payroll out of the field view.
Pricing starts at $4,500 for a mobile build, and the number that finally lands depends on the manager roles, how deep the reporting goes and how many outside systems the app reads from. A live board with map views needs more engineering than a plain job list does.
We would fix the first release to the manager board, the job queue and the end-of-day report. Each extra role, report or integration raised later is quoted and approved in writing before work on it begins.
Decide early which records must be exported and which photo rules apply. Those choices shape most of the form design, and they cost far less to change on paper than inside a finished build.
A manager app only works when the office and crew leads use it every day. Start with the staff who take calls, because they create the jobs. Load two weeks of real addresses into a test board so the team can check their own accounts before go-live.
Crew leads adopt the app faster when it removes a task they already dislike, such as texting photos to the office or redrawing the day's route on a whiteboard. Show them the job card first and keep the first screen short enough to read with wet gloves.
Give the general manager a simple daily routine: open the board at the start of the shift, resolve anything flagged red and close the day from the report screen. Review the first month of data together and fix the two or three screens people avoid.
Measure the app against numbers the general manager already tracks. Compare the time from a request arriving to a crew being assigned, the share of jobs moved because of weather and the number of calls the office takes about route changes. Set the baseline from the three months before launch so any change is visible.
Revenue per crew day, completed jobs per route and the number of re-cleans caused by missed panes are useful too. Pick five numbers, put them on the manager board and review them monthly rather than tracking everything at once.
The schedule depends on the features in the first release and the systems the app must connect to. SIZ Group confirms the timeline and scope in writing after a free scoping call, so you know the plan before committing.
Jobber and Housecall Pro are common choices for service businesses like yours, and we can connect to them where the vendor offers API access. If your jobs live in a spreadsheet or a shared inbox, we can start with a simple import and add a live link later.
They will if it replaces something they already do, such as texting photos to the office. We build the crew view around the job card and the photo upload, and keep it readable on a phone held in one hand.
Mobile apps start at $4,500 for iOS and Android. The final price follows the number of roles, reports and integrations, and we settle it in writing before any build work begins.
Yes. Ownership, hosting accounts and data export are written into the agreement, so you can move to another developer later. Post-launch support is agreed in writing too, so fixes after go-live follow a clear process.
Book a free scoping call, and we will put the scope and price in writing before you commit to anything.