Implementation / 2026
Rebuilt the company’s software onboarding around Asana, ServiceTrade, and a custom Python operating layer so teams could stop managing work through manual admin, spreadsheets, and disconnected handoffs.
Client
Fire & Life Safety Company
Technologies
Asana
ServiceTrade
Python
Google Sheets
Workflow Automation
Data Migration
Google Sign-In
Documentation & Training
Operating Layer
Workflow Model
Primary Goal
Project Type
01 – Challenge
The company had outgrown its ad hoc onboarding and job-management process. Key work still lived in Google Sheets, email, side notes, and manual follow-up, while ServiceTrade and the rest of the team were not staying in sync. The result was extra admin work, delayed handoffs, and meetings spent talking about work rather than solving problems.
02 – Approach
Started by mapping the real operating flow from lead and job intake through execution handoff. Used that to define what Asana should own, what ServiceTrade should remain authoritative for, where Google Sheets still mattered during transition, and which manual steps needed to disappear instead of being renamed.
03 – Solution
Implemented an end-to-end onboarding and job-management model anchored in Asana and ServiceTrade, then added the custom Python layer needed to support imports, workflow management, system handoff, and future direct sync work. The rollout included data migration and cleanup, custom views, operating rules, documentation, security-conscious access patterns, and a structure the owner could continue improving without being locked into outside vendors or Zapier.
04 – Outcomes
Eliminated major manual admin work that had been living between spreadsheets, status chasing, and disconnected tools
Turned recurring meetings into problem-solving and decision-making instead of ‘work about work’
Created real-time visibility and cleaner interdepartmental coordination around live jobs and handoffs
Set the business up to reduce Zapier dependence and own the workflow long term
05 – The Story
This was not a simple software installation. The company needed a way to move from a fragile mix of spreadsheets, follow-up habits, and tool-by-tool workarounds into one operating model the team could actually trust.
Asana became the place where work was captured, clarified, planned, and updated. That mattered because the real gain was not just task visibility. It was reducing the ‘work about work’ that had started to dominate meetings, follow-up, and ownership.
ServiceTrade remained an important source of operational truth, but the workflow needed more than a vendor default. The build required real handoff design between departments, better communication loops back to ServiceTrade, and a structure that could keep improving as the company matured.
To make that sustainable, I built the surrounding Python layer and implementation discipline around the rollout. That created room for data migration, workflow cleanup, security-minded access, dashboards, and future direct automation so the company was no longer trapped by manual pulls, Zapier dependency, or consultant lock-in.
What mattered
The point was not to install software and walk away. The point was to create an operating layer the business could trust, improve, and own after handoff.
That meant documenting the system, making the workflow legible, and removing the extra work that shows up when teams are forced to manage operations across disconnected tools.
Next project
Continue through the work to see another example of strategy, systems, and execution translated into a better operating result.
Think of me as your Director of Infrastructure and Operations à la carte. With extensive experience and a hands-on approach, I provide customized solutions to help your business grow and thrive.
Navigate
Contact
Availability
Currently accepting new engagements
© 2026 OCDATA – Michael Bennett
Currently accepting new engagements