Forum Discussion
I agree. I think moving forward here, we're going to have basically Jobber that you pay for, plus a bunch of bolt-ons that are personally vibe coded so that those bolt-ons are personal to us.
We have a production board that we currently use that I vibe coded, fully connected to Jobber. I think, though, I might turn this over to Jobber projects. We'll see. I need to test it out.
We have a dashboard pulling metrics out of Jobber, showing them to us in a more custom way than what I typically would get from Jobber.
I have several Grokbots doing many different jobs, so this isn't something that I vibe coded. More of just an agent doing something for me that I would have never done myself. Or maybe there's not a product out there that already does it. Regardless, those are basically free.
I think that’s where this is heading too.
A strong core platform, then smaller custom tools built around the way your specific business actually operates.
That’s basically how I’ve been using Claude. KPI dashboards, reporting, admin automations, and little internal tools that would be hard to justify buying as separate software.
The production board connected to Jobber is a perfect example. I’d be curious whether Projects replaces enough of it to make the custom version unnecessary.