Enterprise Software Customization

But that is just you sadly.I am working on SaaS solution in different area. We would LOVE to sell our approach to the problem but then you start getting big customers...Guess what, each one of them wants this changed that different color, "tasks" should be named "todos" or whatever. Then everything has to have customization options because next customer contact changes mind and the other one is leaving company.For now our sales reps do loads of configuration for thos

I'm a manager in an in-house corporate IT dept. Far from running scared from this kind of thing I'm constantly trying to get the rest of the business to except off the self software for all the little tools that they ask for so that we can focus on the key business differentiators.Problem is, they're a big company and they want slick corporate branded stuff that integrates with our ActiveDirectory and where the drop downs have sucked values in from other apps so it all just works. Which is fi

>What I’m saying is you can choose to not buy into one of those uber-programmable enterprise platforms and instead (let someone) build fast and user friendly specific software just for your needs.the problem is not everyone can afford a IT dept with software programmers that can build out custom software.If IT is not their core most companies seek out software that is already out there with somewhat decent reputation.edit: at one of my previous job, they have a in-house software that

There are two different scenarios.Scenario 1: You're doing something that every other business is doing. E.g. ERP/accounting, sales, contact center, etc.Scenario 2: You're doing something few other businesses are doing. E.g. your actual customer business, creative, etc.(1) is amenable to making your process fit software, to good results. (2) is usually a train wreck.Unfortunately, figuring out if your thing is scenario 1 or 2 is non-trivial.Canonical example: EMR&#x

Sounds like the software systems you are talking about are so mainstream and well understood that it might be simpler to buy something off the shelf. Now that more and more pieces are available as SaaS solution my intuition is that organizations should only focus on those pieces that are unique to the problem they are trying to solve. Rest everything should be acquired as a SaaS solution.

I don't think you'll see it done with a web startup anytime soon . . .I've worked at a startup (not really a startup anymore) for 6 years that does software for the P & C insurance industry, and that sort of software is just an entirely different ballgame to develop, implement, and sell. Yes, their existing systems are terrible, but they work(-ish), they've been building them for 20 years so they do a ton of things, and they have anywhere from 5 to 30 different systems that all need to b

>> you are nothing else but the custom dev shop for one or two bucket of money customers and you dont have a real product.This is my experience building for and selling to enterprise. There are a limited number of 800lb gorillas and but every company thinks they are a special snowflake. This quickly has you building software tightly coupled to workflow which is death for commercial software. It's usually one of the reasons the market exists in the first place; incumbents can't

I agree with this, I am currently working in an Enterprise focused company and I generally look at our job as being custom integration. Not because that is the best way to develop software, but the best way to engage with these large clients. It's how they want to be engaged. In turn you charge them appropriately, help guide them away from the obvious traps, and have a fundamental knowledge about what your domain expertise is. The last one is important to know what to say yes/no too. It can

It is just my opinion that market opportunity for a tool like this is actually quite small. There are two constant struggles that I can of that you might be facing. People find the product great but don't know what do build with it. It is hard to be in front of the customers when the painpoint is there, and when the painpoint is there they might be solved it is some form. Secondly, developers will trivialize the product. Developers might say things like if I have to run scripts I would rath

"Vanilla is the best flavor."One of the smartest healthcare IT managers I have dealt with said that regarding enterprise hospital software. The major hospital products have the same issues as ERP products: they are very expensive and implementation projects tend to involve a lot of painful customization. After getting burned a few times that manager swore off customization altogether. Now if they decide to buy a commercial product they implement it as-is, even if that means changing the busin