Using consultants for business software versus in-house development

Previous Topic Next Topic
 
classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

Using consultants for business software versus in-house development

Jack46
Our company is at a crossroads regarding business software solutions. We're considering either developing some custom tools in-house with our existing IT team or bringing in external consultants to help us implement and optimize off-the-shelf software. I'm keen to hear about others' experiences with both approaches. What are the pros and cons you've observed? Did one route prove significantly more cost-effective or efficient in the long run for your specific needs?
Reply | Threaded
Open this post in threaded view
|

Re: Using consultants for business software versus in-house development

HarryPotter
For what it's worth, we've dabbled in both in-house development and external consulting, and our conclusion leans heavily towards the latter for specialized software. While our internal team is fantastic, their expertise covers a broad range of IT needs, not the niche intricacies of specific CRM or ERP systems. Bringing in a zoho consultant for our CRM implementation was a game-changer. They deeply understood the platform and our business processes, allowing for faster implementation and more effective customization than we could have achieved internally. The consultant's specific expertise meant they could foresee potential issues and build efficiencies that our generalist in-house team wouldn't have known about.
Reply | Threaded
Open this post in threaded view
|

Re: Using consultants for business software versus in-house development

Rozalinda
In reply to this post by Jack46
It really does seem like a constant balancing act for businesses to decide between internal resources and external specialists. While in-house teams offer dedicated knowledge of a company's specific culture and operations, consultants often bring a broader perspective and specialized expertise in particular software ecosystems. The decision likely depends heavily on the complexity of the software, the specific skills required, and the long-term vision for maintenance and scalability.