Sumo Stomp
We acquired SumoQuote! Learn more here
🏔️ Peak Performance 2024 is here. Get the report
Sumo Stomp
We acquired SumoQuote! Learn more here
🏔️ Peak Performance 2024 is here. Get the report

Why You Should Use Jobs in JobNimbus

When setting up your JobNimbus roofing management app, one of the important questions to ask yourself is whether or not to use Jobs. You can use Jobs to track your customers and projects in JobNimbus. The Job approach automatically creates jobs under the contact for each project you are working on for them. All information including notes, tasks, attachments, financials, and work orders are tracked by the specific job they relate to. Using the Job approach is a little more complicated than the contact approach, however, it can offer better benefits depending on your company’s situation. So why should you consider using Jobs? Here are a couple of points for you to consider before deciding whether using Jobs is right for you.

Your Existing QuickBooks

One of the easiest ways to decide if you should use Jobs in your roofing management app is to look at your existing QuickBooks. If you’re already tracking Jobs by sub-customers in QuickBooks, or if you plan to sync your QuickBooks with JobNimbus, you would definitely want to use Jobs in JobNimbus. If you’re not using Jobs in QuickBooks or tracking by sub-customers, then you would do not want to use Jobs in JobNimbus. This is because you would then have to change your QuickBooks around rather than keeping it the same.

Multiple Jobs Per Customer

Another factor to consider is whether you have multiple jobs with a single customer. Jobs is a good approach for companies with multiple projects per contact. If you do a lot of repeat business with customers and your projects are large and span multiple days, using Jobs in JobNimbus is a good choice. The Job approach would help greatly in keeping track of multiple projects per client in your roofing management app.

If multiple jobs per customer are rare, you may consider not using Jobs. It may complicate the workflow for your users, especially when multiple jobs per customers is not common. Instead, just track by contact and create a duplicate contact in those rare cases when you need more than one project.

Hybrid Approach

Some users also like the Hybrid approach where you can combine Contacts and Jobs together in your roofing management app. This approach tracks the sales side of your process by contact, then tracks the production side of your process by the job. Jobs are created only when the project moves to production. The downside to this approach is that it can be confusing. Since users have the option of adding attachments, financials, etc., in either the contact or the job, it could be difficult to find these documents. The best option would be to try to standardize your process to either Contacts or Jobs alone.

Many users prefer working with Jobs in their roofing management app due to its flexibility. JobNimbus lets you manage Jobs with a “digital file folder” for each of your projects. This lets you easily access all your information and keep it nice and organized. Again, Jobs would be a better option for your company if you already track Jobs in Quickbooks or have multiple projects per contact. If you’re interested in an overview of how to set up your workflows when using jobs, check out our video on it here. What has your experience with Jobs been like? Let us know in the comments below!

Leave a Reply

Your email address will not be published. Required fields are marked *