Vision | USP | CSF| Varal 6.0


Habot is a go to place for Vendors & buyers of services in the UAE.
It is simple, profitable, & cash generating.

Unique Selling Proposition (USP)

  1. Single post multiple replies, multiple vendors
  2. Very simple to use (Ultra Simplicity)

Critical Success Factor (CSF)

1. Vendor & Buyer signups.
11,200 signups as buyers and 3,400 vendors

Customer obsessed

  • Use only customer feedback to guide the process and product improvements and add new products
  • Use only customer goodwill to build Word of Mouth demand
  • All product tracks must be triggered by customer orders or inquiries only
  • User experience becomes the stickiness factor to have clients return
  • Thrive on taking user feedback to launch improved versions of products and processes


  • Everything will fail
  • Respect compliances and rules and regulations as very important
  • Backups are important as errors occur in the system
  • Manage backup passively
  • Triangular check at every step to ensure accuracy
  • Respond immediately, act quickly
  • Make revisions as required in the byts quickly
  • The energy to find ways to resolve the issues quickly
  • We don’t have to be right – only to solve the user’s problem

Take full advantage of the power of compounding

  • Do today what we can do every day.
  • Not wait for big projects or ideas or actions.
  • No single solution will solve all problems
  • Zero Investment Improvements [ZIIs] and
  • Continuous improvement
  • Continuous learning

Build and automate assembly line tracks for every service required by customers and internal processes in Varal

  •  Deconstruct every task into reusable byts starting from end documents
  •  Make tracks based on deconstructed byts for every process and product and automate completely ang cheaply
  •  Relentlessly starting every track only from end document
  •  UI must have a station to find the end document of what the client is asking for
  •  if there is no available end document, make end documents for us to have
  •  Jobs to be broken up into very small ones that low trained people can do
  •  Jobs must be done only through the tracks
  •  All solutions must be a system based without human intervention required

Be continuously profitable by driving costs down relentlessly

  • Pay for work, not for making work
  • Use Micro Task Outsourcees [MTOs] as much as possible
  • Budgets should not be crossed
  • Use standardized software, stations, database, and field functionalities, so they are reusable to cut costs
  • We should be able to get the work completed accurately, quickly, and debugged rather than by exotic coding solutions

Documentation for everything including internal communications

  • Every track must move on documents
  • Cuts out feelings and politics
  • Makes everything clear, concise, simple, and reliable
  • Nothing is implicit it must be written down into the track
  • Collating all information from the formal sources
  • All information either given to the client or asked from the client must be generated from the deconstruction of a track.
  • This information must be obtained by asking the question 1. What should I tell the client so that he can give me the correct answer for that field?

Manage risk rather than avoid it

  • Use Compliances, Permissions, Clocks, and Triangular Checks to manage it
  • Clocks are used to check the performance of people and stations and full job
  • Permissions built into every step it deconstructs the risk
  • Respect compliances and build them into every track
  • Build system design to minimize the loss due to hacking rather than to prevent it
  • Government rules will keep changing, so the system must be able to convert them into compliances and build into our process tracks

Acquire skills, not people

  • Base skills required in Varal on Strategy
  • Encourage existing Varalians to keep upgrading their own skills
  • Acquire the best skills at affordable cost points wherever they are
  • Use Micro Task Outsourcing [MTO] to break up complicated tasks into those requiring low training
  • Keep thinking jobs inhouse and doing jobs with MTOs
  • The values come in deciding and designing and breaking up so-called expert jobs into low trained ones
  • Give small jobs to 3 people to ensure accuracy. Whichever 2 match is the right answer
  • Keep total fixed headcount and wage cost low

Preserving Wealth

  • Varal data
  • Intellectual property, know-how
  • Customer data
  • Assembly lines
  • Savings
  • Profits
  • Net worth


Varal Consultancy DMCC, 1502 One Lake Plaza, Cluster T, Al Sarayat Street, Jumeirah Lake Towers PO Box 11726 Dubai, United Arab Emirates


+971 4 447 2064

Office Hrs:

Monday to Friday 0830 to 1830 Hrs GMT +4

13 Key ​Ideas ​[TKIs] ​For ​Radical ​Transformation ​of ​Varal

TKI 1: Everything will fail

1. All technology, people, and processes will fail
2. We will not have a sufficient number of trained people to scale up the volumes
3. Customers will not be able to relate to what we are going to offer nor give us complete information
4. Staff might make a mistake
5. The process may fail to be executed as designed
6. Machines can fail
7. The customer uses software or website for a purpose it is not designed for
8. Compliance required may change

TKI 1 Summary idea:

Given enough time ‘Everything will fail’ [NO Matter What] due to human, machine, time, money, technological failure.

For example, given a cloth [dress] may …

1. Tear
2. Stain
3. Need ironing
4. The button may fall off
5. Shrink

TKI 2: Manage failure passively rather than through human intervention

1. Backups must be active
2. Be on load and not be powered down
3. Backup and passive restoration without any human intervention
4. Embed controls in the process itself to bring manageability to the business
5. Focus on prevention and managing the accident
6. Containment, isolation of the failure
7. Prevention by improving the system as derived from the failure
8. Detection and response

TKI 2 Summary idea:

1. Two parallel backup sources must be on at all times
2. Given any issue or failure detected in the 1st backup, the 2nd backup must come on [as a solution for the given time] 3. Make a new backup with the solution in it

For example, given a chair breaks,
replace it with a new chair and analyze the broken chair.
Improve the shortcomings in the next chair.

TKI 3: Break up the process into the smallest reusable components [Byts]

1. Keep deconstructing till existing processes or components could be reused
2. Design process steps for low skill making them repeatable and scalable
3. Build new components by creating new elements, nesting existing elements, and adding in series [daisy chaining] 4. Use sequential and partitioned processes [can be isolated] 5. Cuts costs of the process so we can offer to everyone
6. Focus on consistent customer experience
7. For any gaps in the process, design a new reusable component and keep for future use as well
8. Flexible to changing customer needs
9. Low training time
10. Deployment easily

TKI 3 Summary idea:
1. Reusable designs help enforce standards
2. The consistent design makes systems easier to use and components easier to assemble
3. To break down projects into tasks:
3.1. Identify the tasks: the smallest/last task functionality
Readmore 3.2. Look at task dependencies: find for reusable and scalable tasks 3.3. Set milestones: build new elements and include it in tasks (nesting) 4. The reusable units should be: 4.1. Effective 4.2. Cost-cutting (reusable) 4.3. Flexible to customer needs 4.4. Easy and quick to train and deploy 5. Small reusable units help locate and resolve issues quicker For example, the smallest bit in the cloud database project: (field should be reusable) 3 types of fields: 1. Available on database 2. Available in form 3. Exists in station Each field should have the functionality of all 3 types. Compliance should be checked for the fields in the form. solutions on various projects. Read less…

TKI 4: Take away the constraints

1. Skill set
2. People
3. Product set
4. Cost
5. Processes
6. Attitudes

TKI 4 Summary idea:
Constraints only inhibit one’s ability to do things better, may it be a person’s skill set or may it be a process’s efficiency due to cost constraints. Having an open mind and unprejudiced thinking opens your thinking to new possibilities, examining what could be possible in the future and how that impacts product concepts the team envisions. Read more…

1. Ways to deal with the constraint:[Given the Example of COVID19]

1.1. Accepting the constraints: [Sit at home]

1.2. Reduce the constraints:[Use platform to replace barriers]

1.3. Around i.e. Get around the constraints:[Use sanitizer, gloves, masks]

1.4. Cure the constraint:[Find vaccines for COVID19] 1.5. Take away the constraint: (Mindset) Not a constraint anymore:[Remote Working]

Take away the constraint: (Change Mindset to) Not a constraint anymore.

Read less…

TKI 5: Process must be scalable

1. Repeatable
2. Unit fixed cost of doing the process must go down with volume
3. Variable cost should go down by volume
4. Not limited by constraints

TKI 5 Summary idea:

1. The variable cost must go down
2. If the variable cost doesn’t reduce with volume, scalability isn’t done right

For example, given a printing business, the cost of paper and ink for printing reduces with volume.

Hence, the unit cost of printing in bulk reduces the cost of printing, i.e paper, and ink consumption cost.

TKI 6: Offer work rather than make work

1. Pay for work vs pay to come to work
2. Generated by the task center until the system goes live
3. Pay variable gain share rather than a fixed salary

TKI 6 Summary idea:

Pay variable gain share than a fixed salary.

All work, All get paid (Paying for the work done)

Read more…

Scenario 1:

1. When you offer work, it gives the person the opportunity to make up his mind

2. You pay for the work done

3. The work is defined


Scenario 2:

1. Make work. For example: Monthly Salary: Showing oneself as busy when there is no work

2. (Paid to come to work)

3. Work is not defined

Read less…

TKI 7: Completely different organization structure

1. Task center
2. To offer work, manage outsourcing, stations, tracks
3. Decide requirements
4. System architecture
5. New products
6. Deconstruct forms, terms & conditions for accurate information and process automation
7. Processes
8. Compliances, risks, government requirements
9. Managing failure
10. Finance & Accounts
11. Automation, web, generate leads, user experience

TKI 7 Summary idea:

TKI 8: Clocks & triangular check engine: A-B=0

1. Google API will change, Operating system will change, hardware, network, etc will all change
a. Use triangle nodes to introduce changes [not clear how] b. Use the A – B engine to control parity between a node with existing API and New API etc.

2. Use everywhere
3. Use to get accurate information
4. Use to measure the performance of employees
5. To measure the performance of vendors, services
6. To solve problems
7. To rate clients responses and link to discounts
8. Use imagination

TKI 8 Summary idea:

1. Using one specific data (field) we do a triangular check

2. Data and a form is given to two people

3. Data entered is compared

4. IF: Entered data matches, it is entered into the database

5. Else: Data and form is given to a third person

Read more…

6. The data is then compared again

7. With whose data the entry matches is the final data

8. A specific field is chosen for comparison to avoid permutation combination of options making the decision difficult

For example, for tasting only one ingredient must be chosen to make judgments for improvement. Given salt is considered as the key element given comparison helps get to the conclusion. Given salt and spice for a given taste testing, the given comparison will have 4 outputs increasing the options for judgment. Hence, making the decision more difficult.

Read less…

TKI 9: Use only standard software & sub-processes

1. Same small tasks to be repeated
2. Use the same stations in different processes
3. Google APIs and Google cloud only in automation efforts
4. Break the sequential process in two parts: sending <===> receiving
5. Use them to control the quality of the work and to help keep modularity in the design
6. Existing technology only
7. No custom software or task design
8. If we feel it’s required, rethink the application, requirement, or solution

TKI 9 Summary idea:

1. Modularity refers to the concept of making multiple modules first and then linking and combining them to form a complete system

2. Modularity is the degree to which a system’s components are made up of relatively independent components or parts that can be combined

Read more…

3. Helps increase efficiency and helps locate issues with the system more easily. We can look into that issue without affecting other units of the system

4. By using standard processes we use a level of quality of software that is used generally, making it easy for every other person to operate and understand

5. Having a custom software made can’t scale up to the standards achieved by standard software, as they are made on a larger scale of infrastructure, security, efficiency

6. Scaling our efficiency to standard software wouldn’t be that cost-effect

7. Breaking down a process into – sending and receiving makes the process more effective and reduces the risk of any mix-up

8. Avoiding the chance of any other complication

Read less…

TKI 10: Monitor and track risk

1. Build into our process
2. Technology
3. Government offerings, tie-ups, vision
4. Rules impacting our products
5. Compliance
6. Update and incorporate process continuously

TKI 10 Summary idea:

1. Building a monitoring system into the system makes it more efficient than looking over a system, as we could miss out on certain transactions (processes)

Read more…

2. Compliance refers to the company obeying all of the legal laws and regulations in regards to how they manage the business, their staff, and their treatment towards their consumers. The concept of compliance is to make sure that corporations act responsibly

3. Monitor/ lookout for laws, pricing, etc that impacts the business processes and products keeping it up-to-date

Read less…

TKI 11: With all products start with deconstructing final product fields, working backward on tracks, stations & all forms adding costs and price

I. Use deconstruction to:

1. Acquire information on more products

2. Digest it faster

3. Use it for marketing, web pages, templates

4. Use it for sales, communication

5. Track jobs

Read more…

6. Use it for training

7. Eliminate 90% rework

8. Add pricing and costs

9. Remove skill constraint

10. Keep proprietary knowledge

11. Outsource cheaper

12. Build-in compliance

II. Leverage deconstructed fields of final products to find out

1. What information is required &

2. To ensure accuracy and

3. To get reliable information on multiple products quickly

4. Offer them succinctly

5. Use source documents

6. Authority’s terms & conditions

7. Know your client documents

8. Known written compliance to get reliable information on multiple products quickly & offer them succinctly

Read less…
TKI 11 Summary idea:

1. Start a process backward, i.e. from the finished product to the first document [source documents] (field) required
2. Use it to your advantage [by knowing what all documents are required from the client, and their alternatives]

For example, given a license (driving) look for all the fields present in the license. The license is your end document. Every field from the license must be extracted [even the logo is a field, every element on the license is a field] and traced back to its source document. Using this backward method helps us go through every element of the process.

TKI 12: Impossible to define an accurate decision making sales process so don’t bother

1. Therefore, information must be available to the lead

2. Where he or she wants it

3. How they want it

Read more…

4. In whichever media they want it

5. As accurately as they need it with no cross-checking required

6. Accurately, reliably, in simple terms, easy to understand

7. No person to person selling should be required

To have the lead find the information they Want, as & When they want, How they want, Via whichever media they want we should be able to

1. Web pages, Social media

2. Info-graphics

3. Video

4. FAQs

5. Chat

6. Phone script, calls

7. Email

8. Templates

9. Training material

10. Comparison tables

11. Collect information accurately and quickly

12. Update information accurately and quickly

13. Make this information visible to the lead quickly and accurately in a way he or she understands

1. Acquire information on more products

2. Digest it faster

3. Use it for marketing, web pages, templates

4. Use it for sales, communication

5. Track jobs

Read less…

TKI 12 Summary idea:

1. Every customer is unique and we can’t have a common sales pitch for every customer
2. Every customer will have a different preference for communication and we should be available with
2.1. All the information they want
2.2. As & when they want
2.3. How they want
2.4. via whichever media they want

TKI 13: Finished products ordered by the customer are not words but documents and all works in progress are forms that travel through stations

1. Deconstruction of fields of final documents
2. What information is coming from where
3. Develop the track
4. Total up the prices, steps, time, documents
5. Assumes that all forms are already deconstructed
6. Help lead to decide from alternatives
7. Compare pricing
8. Deciding track from WIP forms
9. Documents required
10. All jobs to be offered, sequence, to whom

TKI 13 Summary idea:

1. Final products are the end document or the products they have asked for, rather than words or in a process step
2. Every field should have a price, step, time, documents information associated with it. This will help us compare pricing and find the documents required
3. Decide tracks from WIP [Work in Progress] forms i.e action at every field/station
4. If you miss some data, request for documents that will give us the required information


No tags for this post.