Try : Insurtech, Application Development










Dev Ops(2)

Enterprise Solution(22)




Augmented Reality(17)

Customer Journey(12)


User Experience(34)

AI in Insurance(31)


Product Innovation(37)





Telehealth Care(1)


Artificial Intelligence(109)



Cognitive Computing(7)

Computer Vision(8)

Data Science(14)


Intelligent Automation(26)

Machine Learning(46)

Natural Language Processing(13)

How to Win Customers through Smarter Form Filling?

3 minutes read
How to Win Customers through Smarter Form Filling?

During the pandemic, an online form was a necessity for businesses to continue their operation. Digital forms, however, are today much more than just a tool for data collection. Organizations now want to get information from the customers quickly without making them write too much. They are trying to shorten the tedious form-filling process and win customers through smarter form-filling.

Why is it necessary to shorten the overlong customer journeys?

Gen Z and older millennials are the biggest motivators pushing insurers to create smarter forms for these consumers. Why? Because of their shorter attention span. Yes. Gen Z typically has an attention span of merely 8 seconds. They are ready to pay more for a great experience and convenience. They want faster services and appealing visuals and designs.

Organizations are already using Auto-filling (to fill out forms automatically with saved info, like addresses or payment info) and OCR scanners where customers can fill in the information asked in the forms by just scanning their id cards/ business cards. Data on the card gets auto-populated in the appropriate fields.

How AI can fix boring forms?

Artificial intelligence (AI) has been helping organizations assess risk, detect fraud and reduce human error in the application process. It can do so by: 

  1. Verifying the document in real-time
  2. Giving Instant feedback
  3. Improving Operational efficiency
AI can fix boring forms.

For example, if a customer uploads the Aadhar Card instead of a Driving License while uploading the document, the manual process would take a lot of time. In the case of AI-driven tools, customers can get notified instantly that the uploaded document is incorrect and users will be able to upload the correct document immediately avoiding the delay in the process. This will save time and effort for the customer and the company, both. 

How can you design a smart form to win customers?

AI is transforming customer experience (CX) across all businesses. However, industry stalwarts need to keep in mind the User Interface (UI) perspective as well in order to make the form filling smarter and faster. A smart form should be designed so that it requires the least effort from the user. Here are a few rules that companies need to keep in mind when designing the form for their customers. 

  1. Vertical Design: A vertically designed form is more convenient to read and easily scanned if needed.
Vertical Design

Vertical Design

  1. ‘F’ Pattern Layout: People like to read in an F reading pattern meaning the reading pattern is left to right, top to bottom. They pay most attention to the screen’s top, upper left corner, and left side, only occasionally looking towards the right side of the display. Content should be placed at the center. 
F-design Layout

F-design Layout

  1. Shorter Questions: Too long questions can make the form-filling process more tedious. Questions asked in the form should be short and crisp.
  2. Question Sequence: Make sure the questions are in a logical order and relevant as it will give better content clarity to the reader.
  3. Avoid complex words: Easy words should be used in the form so that it is convenient for the reader to understand and also can be easily scanned.
  4. Readable Font Size: Big font size will lead to more no. of pages making the filling process boring for the user. There should be a perfect balance between the length of the form and the number of questions with readable font size. 
  5. Categorizing Questions: Divide similar questions into groups for better understanding.
  6. More Objective and less subjective questions: Focus should be on keeping your user engaged during the process. Form should have more objective questions so that users are able to answer questions without writing too much. 
  7. Users should sense achievement, especially on pages that require a little more patience.
How can you design a smart form to win customers?


The new normal is all about CX. Businesses are in a race to win customers who are more detail-oriented than ever. They observe their experience at every step of the journey to evaluate and decide whether or not to stay with the brand. 

Organizations can shorten the mundane form-filling process: a) by leveraging technology like AI in the workflow and in the minutest of processes to achieve efficiency and excellence and b) by keeping UI perspective in mind while designing to make the process more user-friendly. Great CX will ultimately lead to higher conversion. After all, it’s all about winning customer loyalty. 


Knowledge thats worth delivered in your inbox

Implementing a Clean Architecture with Nest.JS

4 minutes read

This article is for enthusiasts who strive to write clean, scalable, and more importantly refactorable code. It will give an idea about how Nest.JS can help us write clean code and what underlying architecture it uses.

Implementing a clean architecture with Nest.JS will require us to first comprehend what this framework is and how it works.

What is Nest.JS?

Nest or Nest.JS is a framework for building efficient, scalable Node.js applications (server-side) built with TypeScript. It uses Express or Fastify and allows a level of abstraction to enable developers to use an ample amount of modules (third-party) within their code.

Let’s dig deeper into what is this clean architecture all about. 

Well, you all might have used or at least heard of MVC architecture. MVC stands for Model, View, Controller. The idea behind this is to separate our project structure into 3 different sections.

1. Model: It will contain the Object file which maps with Relation/Documents in the DB.

2. Controller: It is the request handler and is responsible for the business logic implementation and all the data manipulation.

3. View: This part will contain files that are concerned with the displaying of the data, either HTML files or some templating engine files.

To create a model, we need some kind of ORM/ODM tool/module/library to build it with. For instance, if you directly use the module, let’s say ‘sequelize’, and then use the same to implement login in your controller and make your core business logic dependent upon the ‘sequelize’. Now, down the line, let’s say after 10 years, there is a better tool in the market that you want to use, but as soon as you replace sequelize with it, you will have to change lots of lines of code to prevent it from breaking. Also, you’ll have to test all the features once again to check if it’s deployed successfully or not which may waste valuable time and resource as well. To overcome this challenge, we can use the last principle of SOLID which is the Dependency Inversion Principle, and a technique called dependency injection to avoid such a mess.

Still confused? Let me explain in detail.

So, what Dependency Inversion Principle says in simple words is, you create your core business logic and then build dependency around it. In other words, free your core logic and business rules from any kind of dependency and modify the outer layers in such a way that they are dependent on your core logic instead of your logic dependent on this. That’s what clean architecture is. It takes out the dependency from your core business logic and builds the system around it in such a way that they seem to be dependent on it rather than it being dependent on them.

Let’s try to understand this with the below diagram.

Source: Clean Architecture Cone 

You can see that we have divided our architecture into 4 layers:

1. Entities: At its core, entities are the models(Enterprise rules) that define your enterprise rules and tell what the application is about. This layer will hardly change over time and is usually abstract and not accessible directly. For eg., every application has a ‘user’. What all fields the user should store, their types, and relations with other entities will comprise an Entity.

2. Use cases: It tells us how can we implement the enterprise rules. Let’s take the example of the user again. Now we know what data to be operated upon, the use case tells us how to operate upon this data, like the user will have a password that needs to be encrypted, the user needs to be created, and the password can be changed at any given point of time, etc.

3. Controllers/Gateways: These are channels that help us to implement the use cases using external tools and libraries using dependency injection.

4. External Tools: All the tools and libraries we use to build our logic will come under this layer eg. ORM, Emailer, Encryption, etc.

The tools we use will be depending upon how we channel them to use cases and in turn, use cases will depend upon the entities which is the core of our business. This way we have inverted the dependency from outwards to inwards. That’s what the Dependency Inversion Principal of SOLID implies.

Okay, by now, you got the gist of Nest.JS and understood how clean architecture works. Now the question arises, how these two are related?  

Let’s try to understand what are the 3 building blocks of Nest.JS and what each of them does.

  1. Modules: Nest.JS is structured in such a way that we can treat each feature as a module. For eg., anything which is linked with the User such as models, controllers, DTOs, interfaces, etc., can be separated as a module. A module has a controller and a bunch of providers which are injectible functionalities like services, orm, emailer, etc.
  1. Controllers: Controllers in Nest.JS are interfaces between the network and your logic. They are used to handle requests and return responses to the client side of the application (for example, call to the API).
  1. Providers (Services): Providers are injectable services/functionalities which we can inject into controllers and other providers to provide flexibility and extra functionality. They abstract any form of complexity and logic.

To summarize,

  • We have controllers that act as interfaces (3rd layer of clean architecture)
  • We have providers which can be injected to provide functionality (4th layer of clean architecture: DB, Devices, etc.)
  • We can also create services and repositories to define our use case (2nd Layer)
  • We can define our entities using DB providers (1st Layer)


Nest.JS is a powerful Node.JS framework and the most well-known typescript available today. Now that you’ve got the lowdown on this framework, you must be wondering if we can use it to build a project structure with a clean architecture. Well, the answer is -Yes! Absolutely. How? I’ll explain in the next series of this article. 

Till then, Stay tuned!

About the Author:

Junaid Bhat is currently working as a Tech Lead in Mantra Labs. He is a tech enthusiast striving to become a better engineer every day by following industry standards and aligned towards a more structured approach to problem-solving. 

Read our latest blog: Golang-Beego Framework and its Applications


Knowledge thats worth delivered in your inbox

Loading More Posts ...
Go Top