And finally, SAP Business ByDesign is relevant to SME

SUMMARY:

SMEs are getting more of SAP’s attention these days. At a recent event aimed at that segment, I dug into the product line up but with emphasis on Business ByDesign.

SAP Business ByDesign
SAP Business SME Summit – via TechVentive Inc

A few weeks ago, SAP re-sync’d its go-to-market strategies with its various small-to-mid market product lines. This is important as 85% of net-new SAP customers are small-to-medium sized firms.  SAP defines small businesses as having less than 100 employees and small-to-medium sized firms as having less than 1,000 employees.

This event brought a number of SAP SME customers, partners and SAP executives together with a number of IT industry analysts and press. It was an interesting event especially since SAP itself seems to have reached new levels of clarity around its offerings especially in light of Oracle’s takeover of SME stalwart NetSuite.

NetSuite wasn’t just any ordinary tuck-in acquisition for Oracle. NetSuite’s products are on a single platform (NS-BOS), are quite extensive in breadth and depth of functionality and are all-cloud. It’s multi-tenant, too.

In fact, that new SAP clarity was quite evident in the resurgent role of SAP’s Business ByDesign product line. But, I’m getting ahead of things.

How are SAP’s product lines organized?

SAP salesforce is organized into two teams: large enterprise and General Business Segment. The latter team roughly focuses on businesses with 1,500 or fewer employees and/or less than $1 billion in revenue. The General Business group accounts for 30% of SAP’s revenues. More importantly, SAP expects this part of the firm to grow threefold by 2020.

The General Business group will sell three product lines: SAP Business ByDesign, S/4 HANA and SAP Business One.  SAP Anywhere will be sold by the SMB Team Anywhere salesforce.

The S/4 HANA products will be sold to companies with 1500 or more employees.

SAP Anywhere is a cloud-based product and an architecture. It competes with Shopify, Magneto and other commerce products although some customers use it as a cloud access mechanism to older on-premises accounting solutions. Both SAP and select partners are creating these integrations to pre-existing accounting solutions. Aspects of SAP Anywhere can be used to provide cloud services to on-premises software products. Customer sizes for SAP Anywhere start at the 10 employee and up.

The Business One product line is sold by 700 or so partners in over 150 countries and used by one million users. The product has been localized for 43 countries and in 27 languages (some partners may support additional locations). It is an on-premises and private cloud solution. SAP partners can leverage the Business One Cloud Control Center (CCC) technology to run multi-tenant clouds for their customers. Sales of on-premises solutions still are popular especially in geographies with slow, intermittent or non-existent internet access. The target buyer for Business One is a firm with 350 or fewer employees. SAP is providing hosting services for its Australian Business One partners.  Over time, SAP may use some of the SAP Anywhere cloud services to extend the useful life of the Business One product line.  The Business One product line has a HANA underpinning (3000+ customers are currently using this version).

Business One release 9.2 was launched in June 2016 (Version 9.1 was launched 18 months prior). Approximately ½ of the Business One install base is on version 9.1 or 9.2. Most of the remainder customers are on version 8.

Business One has over 500 micro-verticals for 18 industries many of which were created by partners. Microsoft Dynamics (and their numerous partner product extensions) is a major competitor to Business One.  Going forward, SAP expects even more competition for the Business One product line to come from NetSuite (now part of Oracle).

SAP Business ByDesign is a multi-tenant cloud product that can be a divisional solution for a large firm (a la two-tier ERP). This product line is targeted for firms with 250-1,500 employees and like Business One, it has a HANA underpinning. The ByDesign suite includes an MRP and MES set of functionality. As such, it is a very complete ERP product line.

SAP Business ByDesign – a recap

While my colleague Den Howlett has talked about this ad nauseum, it is worth revisiting Business ByDesign’s history.

SAP Business ByDesign’s tortured history within SAP is hopefully at an end. Launched with great fanfare in 2007, the product originally offered ‘mega-tenancy’ – a kind of multi-tenancy where each customer’s data was physically separated on different server blades.  The product was reworked to possess a more traditional multi-tenant architecture and to permit the solution to scale more effectively and cheaply.

The product’s breadth and depth were expanded significantly over the years. It went from a solution that could support service firms and high growth startups to possessing a full manufacturing capability. But the product underwent other changes, too. The software was enhanced to make it viable in more countries. It also needed its underlying architecture to be upgraded to utilize the HANA in-memory database technology.

Each re-working of this product line made it stronger and better but it also put a cloud around it, too (no pun intended). SAP’s internal support for this product line seemed to fluctuate over the years. These attitude changes were noticed by many analysts and, apparently, some partners, too.

What troubled the product line in the past was that it was in competition with other solutions. It was a product without a clearly defined market niche. BusinessOne, the Enterprise Suite (ECC, R/3) and other products had their niches but SAP Business ByDesign’s was AWOL  or always in flux.

Oracle acquiring NetSuite – a wake up call

While Oracle’s acquisition of NetSuite was no surprise to industry watchers, the consummate of that particular marriage changed everything for SAP Business ByDesign. NetSuite has a full multi-tenant ERP cloud suite and had made a number of sales as a divisional solution for large enterprises. Coincidentally, these were the same markets that SAP Business ByDesign had excelled in as well. Customers could run the SAP ECC solutions at corporate and ByDesign at the divisional level.  Today, ByDesign is needed in the portfolio if only to keep Oracle out of the divisions of its enterprise suite customers.

There is a flip side to this element of the discussion. It is far from clear whether the team running Oracle Fusion has the appetite to absorb NetSuite into the Oracle portfolio or whether it will – at least in the short term – suffer the same fate that befell ByDesign for some years. We shall have to wait and see.

Will SAP Business ByDesign perform well? It should. It’s got the functional breadth, country-specific versions, the SAP support infrastructure, etc. to succeed. It will need all of that and more to match Oracle’s market firepower. More partners will help too. In speaking with SAP Business ByDesign partners, one finds executives that really like the product. For my two cents, this product line has finally found its place within SAP and it’s about time.

There are still some kinks to work out though. There are considerable education and communication rollout items that must be addressed. Speaking with some of the partners and SAP executives at this event showed that not all persons have the same level of understanding regarding the positioning of all product lines.

Can we get some naming convention clarity?

SAP’s website and other content/collateral needs updating. For all the importance that the SME solutions have within SAP, it’s really hard to find SME product focused information on the SAP website.

How SAP names products is unclear. In the SME case, it appears that SAP has defaulted to the (in)famous SAPenese nomenclature.

Product names such as “SAP® S/4HANA for SAP Business All-in-One” are just too long and too confusing. Then there’s “SAP Business All-in-One” that may or may not be the same thing as the previous product line.  Just look at the subset of SAP solutions that can be hosted on Amazon’s AWS cloud service:

You need a scorecard and a decoder ring to understand which product family is appropriate for your firm and the deployment method you desire. Next, you need to cross-reference the potential solution with all of the alternate names/brands it may be known by.  Throw in some other naming words like NetWeaver, Cloud or Simple and it gets even more confusing.

This is a big problem as today’s prospective customers do a lot of pre-selection ‘research’ on the web before ever contacting a vendor or software channel partner.  If they can’t easily figure out which product line they need, they’ll abandon SAP as a potential solution provider. Even if they persist, they’ll get frustrated working their way through that website. Too many confusing/changing product names, too much irrelevant material to wade through, etc. make shopping for SME solutions a chore.  Something as simple as the deployment/employee matrix I provided at the beginning of this article would be a great addition to their website.

A sensible upgrade path

One other area that SAP should address is the potential migration of SAP Anywhere or Business One customers to a more upmarket solution like SAP Business ByDesign or S/4HANA.  This isn’t so much a cannibalization play as it is recognition that high growth firms will want a seamless migration path to other products as their business needs change.

For example, one should expect some percentage of Business One customers will want to move to a multi-tenant cloud solution that can scale up more. The logical choice is to move them to ByDesign. But, while both product lines have HANA underpinnings, the SAP Business ByDesign product has a different way of integrating bolt-on or integrated applications. Also, the data models of each product line are slightly different.

My recommendations

While partners can do these migrations on a one-off (and expensive) basis, SAP should develop these migration tools for two powerful reasons:

  • If a customer has to investigate new upgrade options, it could open up the SAP install base to predation by competitors. If there is a pre-defined, pre-built mechanism for enabling Business One customers to move to SAP Business ByDesign, then existing customers are less likely to consider other, quite different, solutions.
  • A pre-built conversion mechanism makes the cost to upgrade much lower for customers. This gives customers an economic incentive to stay with SAP instead of looking for true love elsewhere.

I’d also recommend that SAP create migration tools for non-SAP ERP suites to SAP Business ByDesign. There are tons of older client server installations of competitor products out there. Those users might very much want to move to a more modern multi-tenant cloud solution but the conversion costs and implementation may be more than they want to (or can afford to) stomach. Taking this conversion cost issue away could be just the deal motivator they need and want.

In closing I should add that Howlett and I were among the very first people to take an in depth look at SAP Business ByDesign way back when. At the time we liked what we saw but were cognizant of many missing functional piece parts. That’s all history. Today, SAP Business ByDesign is a highly credible player in an otherwise much underserved market.

Endnote: Check out the links below this story for more color and research around SAP Business ByDesign

Image credit - TechVentie where noted and SAP

Disclosure - SAP, Oracle and NetSuite are premier partners at time of writing. SAP covered most of the author's T&E for attending the event.

    Comments are closed.

    1. Brian,

      A good analysis of the current state of play for SAP with their SME stack.

      Interestingly, more and more companies are realizing that SAP is a player in the SME space at all levels…except for the smaller SME customer…many of whom struggle with SAP Business One and the footprint of SAP Anywhere just doesn’t cover the full functional requirements.

      Take a look at Enterpryze from an Irish company Milner Browne…its an interesting concept that allows for small companies (and other SAP Business One customers) to consume the functionality at very low cost through a series of small apps (can I call them applets?) https://enterpryze.com/ is the URL .

      It sits across SAP Business One and enables subsets of functionality for more users across the business as well as delivering a web based UI for that functionality if you choose to use it

    2. Great article! One item of clarification – offering a “migration path” (moving the customer’s data) from one system to another (in your example SAP Business One to SSP Business ByDesign) addresses only one third of the three implementation aspects of moving from an old system to a new system. SAP Business ByDesign has the built in ability to easily import data from any system, but data migration isn’t the only aspect to migrating to a new system.

      All three implementation aspects can be summed up as follows:

      1.) Getting the data ready;
      2.) Getting the new software ready;
      3.) Getting the business ready;

      Agreed, a data migration path “map” for moving SAP Business One data into SAP Business ByDesign is something that could help speed up a B1 to ByD conversion by a few hours, however, they are two different systems and as such steps 2.) and 3.) will always require additional time from the customer and implementation partner before the customer can go live.

      The “migration path” can really only resolve the “Where do I put the data” aspect of moving to a new system (or step 1.).

      Since every customer doesn’t use their old system and new system the exact same way another customer uses their old/new systems, Step 2.) “Getting the system ready” or configuring the system for how a customer will want to use it, can’t be automated and requires involvement and decisions from the customer so the implementation partner can set up the system according to the customer’s specific requirements. In other words, functionality and configuration is not a one to one relationship from one system to another. If it were, then why move to a new system? So, a “migration path” can’t help with this aspect.

      Step 3.) “Getting the business ready”, is basic Change Management for the customer’s business. It includes user training on the new system and processes, as well as making sure their customers and vendors are educated on any newly automated processes that would impact them. This step is the “people” part of the equation and since every customer does not do everything the exact same way (and every customer will tell you this too), it requires human effort to learn the new system, so a “migration path” wouldn’t help with this step either.

      While creating a “migration path” from SAP B1 to SAP Business ByDesign is available from SAP partners, the fact is a “migration path” will only help with the data migration aspect of transitioning to a new system.

      A little info on me, I have been directly involved in the implementation of a variety of 89 ERP system implementations, and indirectly involved in hundreds.

      Thank you for helping educate the audience. I really appreciate the thoroughness of your and Dennis’ articles. Keep up the great work!

    3. Bruce Richardson says:

      I remember meeting with Dr. Peter Zencke back in 2003 when he started working on Business ByDesign. This is a very long gestation period.

      I’m curious as to how many customers are using it — especially those that are live. Brian, I assumed you asked …

      1. Hi Bruce, realistically for a ground up soup-to-nuts business system, even one for SMEs, I think the first 10 years is “gestalt and gestation”. Then adoption gets going. 2013 to 2016 perhaps a fair review period?

    4. Richard Nagel says:

      @Bruce:
      Over 3600 entities in more than 100 countries are using SAP Business ByDesign productively. The solution serves companies/organizations in about 30 industries.

      1. @Richard:
        “About 30 industries”, that is a huge claim. Concerns me this type of claim has gotten standard ERP into trouble with complexity over scalability. Opening the doors up to demand driven platforms skimming all the profits away from ERP leaving just the gnarly complexity. Translates to creaming profits off the top by Amazon/Alibaba away from many manufactures.

        1. Richard Nagel says:

          Thanks Clive for your reaction. Still I am just using facts – and don’t use a claim here. As SAP Business ByDesign contains a good set of standards/best practice end-to-end scenarios, these scenarios (and processes) it has proven to be a good fit in many industries.

          Yes, ByDesign is more used in certain sweetspot industries like professional services – but in completely other industries and segments companies trust to run on ByDesign’s bestpractices as well.

    5. Matthew King says:

      That ByD can accommodate a wide range of industries without drowning in complexity is the SDK. In other words ByD is as much PaaS as it is SaaS.

      Rainer Zinow himself acknowledges this point in this video (from the 3 minute mark).

      https://m.youtube.com/watch?v=TMSpCIsqOZc&feature=youtu.be

      In addition to being robust accounting and inventory controlling systems, ECC has been successful for much the same reason (i.e. packaged software plus application platform SDK).

      S/4HANA will continue that concept but on a simplified code base thanks to de-normalisation of table structures and predominately in-memory columnar storage.

      We have all have heard about mass customisation in ECC and other components of the Business Suite. There are good and ways to implement custom code from a techinical viewpoint, but the notion of a standard system that can cover dozens of industries without customisation – results in systems that confound the IT department and business users alike, and in the end sink under their own weight.

      1. @Matthew:
        Thanks for adding how to bifurcation of packaged software plus application platform SDK work well together with each other to cover dozens of industries. Clearly SAP ByD have mastery of domain understanding to design the SaaS with PaaS for as Richard says about 30 industries. My thoughts are the customization services are not inexpensive.

        Lastly I wonder how easily the customized SyD can up upgraded on a rolling basis. I’ve only seen Microsoft Project Green (Dynamics replacement that failed c/o convolution with the original Windows Vista). Plus a system I designed properly handle rolling updates of customization in a standard SME ERP system (of course it is still working under Dutch ownership).

        1. Richard Nagel says:

          one of the ByD USP’s is that SAP can upgrade the solution every quarter – as it has beend doing since years. In fact for its users these upgrades are considered to be “non events”.

          Customers can create add-ins in ByD using the SDK and still remain “in standards”, enabling them a smooth quarterly upgrade.

          The SDK in ByD does not make it a PaaS – it is a SaaS associated with SLA.

          1. Quarterly about right for business application functional updates. As business model changes to demand driven (DDMRP), critical the full stack from web to database is on a rolling release of continuous deployment for good security.

            Salute SAP ByD is leading the other ERP vendors from pre-internet practises. Whether cloud-saas or on-premises a secured execution environment needs to be trusted current.

    6. Good article Brian – wanted to add something about SAP’s drive into SMB. All the products above have been moved into SAP Business Networks and Application Division together with Concur, Ariba and Fieldglass. The division under Steve Singhs leadership have a desire to break open the SMB market in a serious way. Concur is already on their way to mass adoption, and Fieldglass have just launched Fieldglass Flex aimed at the SMB market. With an understanding of Business Networks and Microservices exciting things are on the Horizon

    7. Rodrigo Sandoval Vivanco says:

      Excelent SAP ByD review, it is very well wrote and have a strong investigation of the SME market

    8. Jonathan Phillips says:

      I think ByD is a significantly under-rated product & I am pleased to see it getting some further traction.

    9. says:

      SAP BYD is good product indeed. It looks modern and has lots of similarities with ECC. I think the business processes are more polished in BYD and all the small things that were bothering in ECC are now fixed in BYD. Heres basic pricing information about BYD http://allbyd.com/sap-business-bydesign-cost/