Originally, Decisions was designed as a rule and workflow engine that could be embedded into other applications and solutions. As demand for the product grew, Decisions began selling directly to customers who wanted to manage their own business processes without code.
At the same time, resellers and other software providers began using the software in industry-specific situations. These businesses wanted to present their own branding and maintain a corporate image while leveraging Decisions’ solutions for their clients. In an effort to empower business users to own and maintain processes while still providing them the opportunity to brand their platform, Decisions now allows users to apply a skin to the Decisions portal.
In our recent webinar, “Branding the Portal,” we lay out the value of branding the Decisions portal and discuss the no-code functionality that makes this possible.
Why Brand Your Portal?
Before you brand your portal, it’s important to understand the business benefits of this process. In some cases, clients may opt to not brand the portal because the benefits of branding don’t apply to their intended use.
For example, if you plan on only using Decisions as a back-end machine, spending time to brand the portal for other customers might not make sense. Likewise, if you have no external or customer-facing processes, you probably won’t benefit from having your own branded portal. If you have your own customer-facing UI, you don’t need branding on the portal itself because your UI will overlay on the customers’ end.
For many businesses, though, branding offers clear benefits. It can reinforce a strong customer loyalty for businesses while supporting marketing and advertising efforts by keeping the brand top of mind.
