css templates

The “No-Code / Low-Code” way of work with CDPs. The need of a coding-free hands-on experimenting with customer data.

November 25th, 2020

The no-code approach is becoming trendy in several software categories related to B2C interactions/communication. We are progressively watching the market shift towards reducing the technical skills to use and even customize digital products. There are very popular no-code website builders such as Wix, mobile app builders like AppMachine, conversational creation tools such as Landbot (chatbots) or Voiceflow (voice assistants/apps). Visual design, forms and flow composers are making it feasible to create mobile, web or voice experiences without coding a line.

The low-code approach has been actively embraced by other B2B software categories as in CRM, Marketing Hubs, ERPs. Until now, the deployment of a CRM, ERP etc. in a big or medium corporation was a large project involving not only expensive licenses of the CRM or ERP chosen but a large amount of customization of professional services, usually implemented “with a lot of coding” by the IT integrator, requiring long setup times and large teams. Agile did not yet arrived to our lives :-) The cloud and SaaS paradigms are forcing us to increase the flexibility of corporate software categories to be fully customizable with low-code, reducing the time to go live to the production environment of a given solution. This low-code approach is creating a win-win-win scenario. 

     ● The corporations reduce the initial investment (non-perpetual licenses as an up-front fee and         less initial integration/customization costs).

    ● The solution vendor reduces the “versioning” nightmare, creates a simpler way to trigger the         “try” that could be converted to “buy” and facilitate conquering lower tier companies in every         level where its solutions could apply and deliver value.

    ● The IT integrator or integration partner of the solution vendor initially reduces the amount of             services for a given integration, but on the other hand increases the number of opportunities         to serve more customers in tiers where the budgets are not as big as the big corporates         budgets. The customer base can be extended.

In the emerging space of CDPs (customer data platforms) with analytical, actionable or automatic new data generation the point is to decide where No-Code applies and where Low-Code applies.

At Whenwhyhow we are eager to offer a very interactive product which can also be heavily used by the new key roles coming from Liberal Arts backgrounds. Cognitive, AI, Analytics, Prediction, design experiments are progressively led by humanistic profiles that could be the best “understanding & modeling data”, thinking of new ways of testing behaviors, but not tech savvy. We want to offer a hands-on non-techie approach to extend the range of potential users of the CDP in the areas of customer marketing, business analysts, service designers, interaction planners, etc. without needing the “technical translator”.

Our approach is:

    ● No-Code for the data model design. The segments and its values, the digital channels and         its potential metrics, the customer actions attributes that could be recorded and the external         events that could be impacting the end-customers may be designed visually using forms.         The flexibility of the NoSQL “key:value” paradigm allows to create very different data-model         for different companies even in a multitenant/SaaS platform.

Example. Channel metrics definition GUI

Example: External context definition GUI.

    ● Low-Code to produce the data connectors. Agnostic API make it feasible to connect with         chatbot platforms such as Dialogflow, or app or web or contact center session managers,         CRMs, or external information data sources. For tight budgets it is mandatory to shorten         times and integration costs, and hours are better than days, and integration in days are better         than integration in weeks. Entry level coders may be able to create the connectors with the         data “live” feeding the CDP and the ETL scripts to reuse past data to add extra value to the         the CDP.

Example: .js library connector for Dialogflow

Example: Reporting chatbot interactions from Dialogflow to Whenwhyhow

    ● Low-Code for the own feature-product roadmap development. We invested great initial         effort building the product in creating a flexible framework to define data-models, manipulate         data, secure the data ingestion and offering the first set of metrics combining different types         of data (channels, segments, external events, customer actions) when defined and sourced: a         moldable clay easy to adapt to any corporation that operates intensively in customer         interactions. Whenwhyhow is designed to facilitate the fast creation of new features as         microservices using Agile/Scrum planning. This translates into a great potential to         continuously grow the functionality with new metrics, automatic suggestions for         segmentation, abnormal pattern discovery and more client suggested ideas to add value to         the product and their data.

Facilitating the use of new generation tools like CDP and Marketing Hubs by a myriad of different roles have a double benefit: as more internal-users could extract valuable information the value that the product delivers is increased and it will be easier to have more internal sponsors/ambassadors to convince about the need of integrating internal data not yet integrated.

You can follow Whenwhyhow in linkedin, twitter & instagram

C/Acanto 22, office 13-1
28045 Madrid (Spain)


Email: hello@whenwhyhow.tech                  
Phone: +34 91 4219805