HYBRID MODEL OF WEB SERVICE

Kartavya

cc : Abhi

                          

In my note dt. 21/04, I had described 2 models and suggested that we adopt model (B) the "Hub & Spoke" type LICENSEE MODEL

However, on p. D/3 of that note, I did say that, if a Corporate wants to subscribe to our web service, directly, without going thru a Licensee, he should have that option. I am afraid; there will be many corporate who may want to deal us directly.

And this may also be true of many placement Agencies / Portals etc.

In new economy, we cannot be right, we have to be flexible

In fact, one of the advantages (being touted) of Internet - and especially of Web services is

MASS CUSTOMIZATION

 as opposed to MASS - PRODUCTION / MASS - RETAILING.

 "MASS - CUSTOMIZATION" means, we should be able to serve each customer UNIQUELY, depending upon his needs. Just as DELL. Com is able to Configure unique (PC) (within practical limits of course), we should be able to configure our service.

Some corporate wants a "bouquet" of services and therefore prefers to deal with a jobsite, whereas some other corporate likes to deal with another jobsite (for another set of services) and yet a third, wants to deal with 3P directly.

That brings us to HYBRID MODEL, showing in Annex.

Now let us consider the issue of RESUME DATABASES.

Which will emerge in Hybrid Model.

 Corporate who are subscribers of jobsites would want to create their own "Private" resume databases, using ResuMine.

eg. Corporate   A - 20,000

              B - 50,000

              C - 10,000

              D - 7000

              E - 11,000

Presumably, these "Private" resume database get generated & get stored, on the web servers of respective jobsites. And, it is this web server where corporate will also "Search" this database/ prepare shortlist/ send - out interview - all emails etc. etc. (of course, each transaction will be recorded/ aggregated by our own MAIN SERVER - for billing  & ADMIN purposes).

But,

The servers of Jobsites (our licensees), have over the years, also accumulated their own/ fairly large resume databases.

 eg. 

Naukri     Claims     -      8 Lakh

 Monster Claims     -      5 Lakh

Jobs Ahead Claims   -      4 Lakh

Jobstreet Claims     -      3 Lakh

Obviously, the jobsites would not want to "Give - up" these resume databases, collected at a huge cost !

And, what is more,

the jobsites would like that their corporate subscribers ALSO search these databases, even as each creates its own/ private database.

In fact, Annual subscriptions for "Resume Database Search" are the MAJOR Source of Revenue for most Jobsites. Monster India for example, charges Rs. 1.8 Lakh/ Year for this. So Obviously, none of these jobsites would want to give - up this source of revenue, even when they opt to become our licensee. So, they will continue to offer this (Resume search of their own database) as an independent / stand - along "Service" which is not linked with our web service.

 And riding on top of everything, on our own web server, there may be a resume database of 1 million/ 5 million resumes that we have managed to build - up, over next 6/12 months, as a result of our projects Mahattan / Ego/ Cyber

This should be searchable by

    . Our own "direct" Subscribers

    . Our "indirect" subscribers (thru Licensees)

    (We will not allow "licensee" Jobsites themselves an access to this database). And, whether, a subscriber is direct or indirect, he pays per transaction. If he is direct, he pays us. If he is indirect, he pays our licensee - who, in turn will pay us, depending upon our understanding with him.

h.c.parekh