Absolute Cleaning Services
Project context
Founder-Led Operations · Workflow Implementation Using Off-the-Shelf CRM
The Problem
As job volume increased, relying on informal tracking made it difficult to maintain clear visibility of work in progress. While Jobber provided a standard job lifecycle, inconsistent use of statuses reduced its effectiveness.
This resulted in:
- Jobs not being progressed promptly
- Uncertainty about whether action was required
- Difficulty distinguishing between scheduled, completed, and invoiced work
- Increased risk of delayed invoicing
The challenge was not a lack of tooling, but ensuring the lifecycle was used consistently and meaningfully.
The Objective
Implement and enforce a clear job lifecycle within Jobber that:
- Reflected real operational stages
- Was used consistently across all jobs
- Made next actions obvious
- Supported invoicing and reporting
- Reduced reliance on manual reminders
The Approach
Using Jobber’s built-in job status functionality, I:
- Defined which statuses would be actively used in day-to-day operations
- Established clear meaning for each stage (e.g. scheduled vs completed)
- Ensured jobs were only marked complete when service delivery had finished
- Used Jobber’s prompts (such as invoicing reminders on job closure) to enforce discipline
- Regularly reviewed open jobs to identify stalled or incorrectly staged records
Rather than customising the platform unnecessarily, I focused on process clarity and user behaviour.
The Outcome
By consistently applying Jobber’s lifecycle:
- Job visibility improved across active work
- Invoicing delays were reduced
- Fewer jobs were left in ambiguous states
- Daily operational oversight became simpler and more reliable
The system worked effectively because it was used correctly and consistently.
Key Learning
This project highlighted an important operational principle:
Good systems only work if people use them consistently.
Process enforcement and clear definitions matter more than customisation.
Salesforce Relevance
This experience closely aligns with Salesforce administration, where:
- Standard platform functionality is often sufficient
- The administrator’s role is to configure, govern, and drive adoption
- Consistent status usage enables reporting, automation, and visibility
- Over-customisation can reduce usability
It reinforced my preference for using standard platform features well, before introducing complexity.
Let’s talk
If you’re a Salesforce Admin, Architect, or Recruiter and would like to discuss this approach, trade ideas, or explore how I think through problems like this, feel free to connect with me on LinkedIn.