LinkedIn Twitter Facebook

Ben Kepes is a technology evangelist, an investor, a commentator and a business adviser. His business interests include a diverse range of industries from manufacturing to property to technology. As a technology commentator he has a broad presence both in the traditional media and extensively online. Ben covers the convergence of technology, mobile, ubiquity and agility, all enabled by the Cloud. His areas of interest extend to enterprise software, software integration, financial/accounting software, platforms and infrastructure as well as articulating technology simply for everyday users.

More about Ben here.

4 responses to “Business ByDesign meet NetSuite, NetSuite meet Business ByDesign”

  1. dahowlett

    @ben: the pricing you’re looking at for NetSuite is the starting price. Even then I suggest you check the math: $499 + ($99×10) = $1489 which is within $10 of SAP BYD pricing at 10 users. That difference widens in NS favor at 25 users = $750/mth.

    NS work on a per module basis. I think you’ll find that once you make a ‘sort of’ apples to apples’ comparison then NS starts to look more expensive or at least comparable. But even then that’s not really the right sort of comparison.

    When NS was shooting at SAP it was going after the R/3 4.6 EOL base. That’s a very different animal to BYD so NS had a good target. That’s changed a little with BYD.

    To argue BYD is ‘fresh’ from now when it is at version 2.5 is a bit daft. 2.5 was largely a technical upgrade. More to come in 2.6 on functions – due end of year.

    You can exclude at least 90% of the current developer community from the discussion. It’s a different sales beast.

    Did you miss the VisualStudio.net reference in my posts? That’s the dev platform.

  2. dahowlett

    All that stuff about multi-tenancy is a sideshow. The original design (which goes back about 5 years) was fundamentally wrong at many levels but should not be a surprise. The bigger surprise is that the penny dropped re: the issues about a year ago. They threw engineering resource to solve the technical problem. Job done but with a nice twist for those that want blade separation.

    Reality check: only geeks care about that stuff. End users don’t care until there is a cost implication. Which they’ve addressed, hence the ability to take down to 10 users plus resolve provisioning issues etc. Story now dead. Moving on.

  3. Ben Kepes

    Hi Dennis – thanks for your comments.

    Re pricing – agreed it’s not completely apples with apples – I guess until we have real product out in the wild it’s hard to know how this will shake down. Point taken though

    Re visualstudio.net development. I think there is a bit of a difference between a PaaS offering built right on top of the core offering and a true PaaS. As an analogy, there is a significant difference between force.com, a rich PaaS, and, for example, the ability to build something in .NET on Azure. Again it’s apples with apples and a true PaaS makes things a lot easier for development

    Multi-tenency – Agreed that giving customers choice is the best approach. In fact if geeks DO care it’s because they want to be able to give their CIOs physical data separation ByD’s options do this so agree it’s a nice twist

  4. dahowlett

    @ben: duh? As far as ‘true’ this or that is concerned – nobody cares…all that matters is whether customers easily derive value. All that matters here is access to sufficient devs to makes BYD a runner. With 700K MSFT VS.net devs (as at end last year) to choose from, SAP has made a reasonable commercial choice.