One app for Marketing & Sales to work the leads
Another for finance to manage accounts
a third system for employees to enter their leaves
Recruitment without system and problems abound
Another team to chase these teams and get the scores
and feed it to a yet another system to generate reports
One App to integrate these teams, one app to unite them
One app that connects their work and in the functionality bind them
One System with CRM, HRIS, ERP, eCommerce -  Sysblitz.com

My Precious!

When you go to a bank, you may meet a pleasant person on the counter who goes out of his/her way to get things done for you; or you may meet somebody who simply brushes you off, redirects you to numerous other counters and then begrudgingly completes your work.

Where is the difference? It’s in the interaction. The same task is done, the same service is achieved yet one interaction leaves you happy and smiling and the other leaves you dismayed to say the least.

That is the difference between a good CRM and a bad CRM.

CRM by architecture is not a very difficult system. Most systems available these days offer more or less the same functionality. The rocket science however is how do they offer that functionality; how easily does your CRM gets your work done. Even the extra features that a CRM may offer is simply that – an added level of ease and comfort in getting something done.

So next time when you are out deciding which CRM is good, you can’t find that out from the number of ticks in the features list, or the beautiful screenshots or what the CRM Experts are saying. Those may tell you which CRM is bad, but if you really want to know what a good CRM is all about – just take the free trial demo and simply dive in.

“You’re not perfect, sport, and let me save you the suspense: this girl you’ve met, she’s not perfect either. But the question is whether or not you’re perfect for each other.” Robin Williams in Good Will Hunting

If you must know, before we started off the company, the product that we had in mind was “IDrona”. There weren’t any plans of making a SaaS based suite of Business applications, let alone any research or market sizing about the need of such a suite. The only reason jusbill.com was born was because we really really wanted to make IDrona.

I belong to a business family running a small manufacturing unit. A small factory with limited resources – legal, people, marketing or financial. This small business runs like most other small businesses, which is, in a fire-fighting mode. Hence while there was always finance & sales & operations to take care of, the focus of my daily actions was that activity which was on fire. There were systems in place, accounting & production & regulatory but those systems were not helping.

Jusbill was born out of the top floor of this factory, built by a team of people who understood programming & software and business and the usual problems of a small business. It was built with an intuitive user-interface because the office-staff wasn’t computer savvy; it was built online because the business is 24X7 and operational from everywhere – home, office, car, client’s office, restaurant, port; it was built to handle most aspects so that activities can be managed quickly, efficiently, automatically and in an error free fashion; it was built to be secure and with roles and workflows built into it.

Jusbill benefits from the knowledge of these nuances, those intricacies and that insider information. It benefits from being tested in that actual environment and being able to deliver in that actual environment.

IDrona, by the way is still in development and should see the light soon!