Review of Skeddly
Keeping routine AWS work on a schedule is helping our operations team control avoidable cloud spending, because instances can be turned off when they are not needed and recurring tasks no longer depend on someone remembering each step; for a coordinator accountable for predictable procedures, that outcome is more useful than a dashboard, and it makes cost easier to justify.
I still watch the budget closely, since any automation tool adds a cost that has to earn its place alongside the AWS resources it is meant to manage. The setup also needs to match our actual routines, rather than create extra checks for staff.
So far, the practical value is in reducing repetitive operational work and supporting cost control without asking the team to become cloud specialists; I would want dependable help when a scheduled action is unclear, but this is fitting our needs well and I am comfortable continuing with it.
Review of Fieldwire
I value having current drawings and task information available in the field, since our coordinators need a dependable, shared view of work without adding another handoff. For an education operation, the shared hub and on-site markups make collaboration feel practical, and the ability to track schedules and punch-list work can reduce avoidable confusion; still, I am weighing whether that workflow fit is broad enough to justify the pricing pressure for a team that needs clear, consistent value from every tool it adopts.
I also want confidence that people can keep using the information easily across the devices they bring to a site, because small communication gaps become costly to coordinate; the core approach looks useful, though I would keep checking that day-to-day fit before treating it as a settled choice.