TIE-UP WITH SUN

27 Dec 2003

Raju

TIE-UP WITH SUN

“What is in it for me?”

For Sun

·     To be able to show/demonstrate to Sun’s client/potential clients worldwide, that, it is possible to develop high-end “business applications” on J2EE’S multilayered architecture (as exemplified by RecuirtGuru).

·     To prevent arch competitor Microsoft from being able to make such a claim (by ensuring that RequirtGuru switches over from Net to J2EE)

For Recruitguru

·     To be able to ramp-up development of Recruitguru as a full fledged

RECRUITMENT PROCESS PLATFORM

(especially as a pay-per-use Webservice)

before competitors (Monster-Naukri-Jobs-Ahead/Jobstreet/times jobs etc) cheep-up from behind, develop their own extraction software and “overtake” us.

Hopefully, with sufficient technical/financial/marketing support from SUN, we should be able to gain “First Mover” advantage and to able to establish Industry-standards (for online e-recruitment industry) and decide “Rules of the Game” (eg. Pay-per-use/webservice/self-service etc.)

These 9 things are essential to become Industry-leader

If, with support from SUN, we succeed in developing a world –class “Expert system” for helping corporate Recruiters, it is quite likely that SUN would like to “Show-case” RecruitGuru in all of their marketing / advertising campaigns, worldwide. This could catapult-us into the “big league”. 

Having answered

“What is in it for me?”

-    Both, for Sun & Recruitguru, next question is,

-    What kind of support/help do we need from Sun?

-    In return for such support, what do we promise/commit to SUN?

-    How long do we need such support from Sun? i.e. time frame.

What Support/Help do we need from SUN?

We would need,

-    Hardware (Servers/desktops/leased lines etc.)

-    Software (Proprietary software packages either developed by sun or third parties/licenses).

-    Technical Guidance/QA/Load Test Simulations.

-    Marketing Support

-    Promoting Recruitguru amongst Sun’s Clients/Potential clients/general business community thru

·     Printed brochures/sales literature

·     Online advertising (Sun’s website)

·     Offline advertising (print media)

·     Seminars/conventions/conferences etc etc.

And the most important/urgent support, we need will be,

-    Financial/Funding

This would primarily consist of salaries of S/w developers/HR experts/Business Analysts/QA personnel/DBA /Marketing professional’s etc.etc.

We would need to figure out,

-    How many (of each type) we need & when

-    What would they cost (Annual Salaries)

Depending upon the no. of persons proposed to be employed, we would also need to fund

·     Related Administrative Expenses

·     Related “Office-space” Expenses

We would need to project these as well.

In return for above support/help, what do we promise/commit to SUN?

Assuming that Jan-Feb-March 2004, go un mobilizing our “collaboration” with sun & mobilizing the required “Resources” 

(HW/SW/Space/Manpower), we should promise/commit to deliver/deploy following modules on Recruitguru, during 2004/2005 (i.e. by 30 March 2005):

·     GuruAd Description Module

·     Job description Module

·     Organization charting Module

·     Interview Management Module

·     Executive Profiles Module

-    Function Profiles 9aLready implemented)

-    Industry Background Profiles

-    Skills Profiles (for IT industry)

-    Compensation Profiles (Age/Ind./Func./Exp/Edu. Wise)

-    Job market Analysis Profiles (“ + Region)

-    Job Advts. (Function-wise) profiles etc. etc.

Of course, what we can deliver will largely depend upon the support/help offered by Sun.

Hr. Manish kapoor said that, he could manage to get the necessary “In –principle clearance from his bosses, within one week from receipt of our (a) vision statement (b) Technical write up.

If we send these on Monday, MK could hopefully get such “In principle” clearance, say by Jan 7^th.

I suggest, we prepare & keep ready our “DRAFT PROJECT PLAN” by Jan 7^th , so that as soon as we get an email from MK, we could shoot-off this plan to him. Our plan should spell-out

-    What we need from Sun (showing detailed /breakup calculations)

-    What we will deliver to sun & when (Bench-marks for development/for testing & for deployment as webservice)

The plan should clearly bring-out each & every: ASSUMPTION” including “assumed” dates for

-    Signing partnership Agreement

-    Getting/ receiving HW/SW/Funds from SUN.

Any delay in these (events) could lead to corresponding delay in “Deliverables”

Hemen Parekh