Earlier quoted context omitted.
"But we want it to run on our chosen database product." "But we want it to integrate with our single-sign on product." "Our security team scanned it with our chosen tools and you have to fix these things before we will deploy it." "We aren't willing to make those network changes to allow it to run." "We won't allow it to connect to our server but it is a requirement to connect to our server if it is going to be hoste…
> Oh and they want you to hold their hand through it but they aren't willing to pay for consulting. These sound like tire kickers and un-serious customers, why focus on their expectations? Serious customers, almost by definition, are willing to pay for custom work they want done.
I want to convince you to have an on-premise offering
91–93 of 93 posts
Re: I want to convince you to have an on-premise offering
#92Earlier quoted context omitted.
It irritates me, too. But honestly, how harmful is it to your business unless your addressable market is mostly English majors? And even then, it probably prompts interaction from the English majors, who can finally show off a little with a correction.
I posted for people who like to use words correctly and might appreciate the note. The rest can get their prostrate's examined for all I care.
Re: I want to convince you to have an on-premise offering
#93Building an on-premise deployment requires a maturity of company that is quite rare for a startup to have: * It’s much easier to do on-prem if you do a monolith, or at least a small number of services. * You have to build and test your application against a range of OS and hardware combinations. You’ll almost certainly need to support RHEL, and probably Windows Server 20XX. Many companies won’t let you use Docker. *…