From P2PVenture.org's Wiki

Contents 1 Introduction 2 Requirement Specifications 2.1 For entrepreneurs 2.1.1 Visibility 2.1.2 Screening 2.1.3 Investors relationship management 2.1.4 Coaching 2.1.5 Q&A on entrepreneurs 2.2 For investors 2.2.1 Screening 2.2.2 Due Diligence 2.2.3 Negociation 2.2.3.1 Q&A on negociation 2.2.4 Q&A on investors 2.3 For mentors 2.3.1 Screening 2.3.2 Coaching 2.4 For organizers 2.4.1 Creating a FundCamp 3 Functional Specifications 3.1 Public / private space 4 Functional Architecture 4.1 Q&A on functional architecture 5 Technical Specifications 5.1 Using Drupal 5.2 List of Drupal modules 5.3 List of custom developments 6 Prototype

[edit] Introduction

This page should be used to describe the specifications we want to give to a platform supporting FundCamps, which are organized to select a couple of startups receiving investment at the end of a physical "camp".

[edit] Requirement Specifications

We should list here what are the requirements of the users (e.g. user want to be able to find, then contact another user).

[edit] For entrepreneurs

[edit] Visibility

• Ability to expose their project to give them visibility

[edit] Screening

• Ability to get a list of investors to contact

[edit] Investors relationship management

• Private place where to store sensitive information and control access to it

[edit] Coaching

• Ability to consult anonymized information and results for the different projects
• Ability to ask questions to particular mentors
• List of reference links for startup knowledge

[edit] Q&A on entrepreneurs

Question: How do we qualify entrepreneurs(if at all)? Is it open registration for all? Or, just for those involved in FundCamp?--SamRose 13:07, 17 September 2007 (EDT)

Answers: I think this is open registration for anyone. That does not mean that the entrepreneur applies to a FundCamp, just that he/she is ready to communicate and receive mentor ship. I don't know yet if application to a FundCamp should be make public or let at the discretion of the entrepreneur to let this information being published. -- FredericBaud 16:04, 17 September 2007 (EDT)

[edit] For investors

[edit] Screening

• Ability to file projects per domains

[edit] Due Diligence

• Ability to share information and discuss projects

[edit] Negociation

• Syndication between investors

[edit] Q&A on negociation

Question: Can you explain this more? What do you mean by "syndication"?

Answers: This is probably something not necessary for FundCamps. This is the ability for different investors to pool their investment capabilities to fund a specific project. For FundCamps, pooling is done prior to the due diligence process. This feature would be for some kind of continuous FundCamp (like projects that have not been funded during the last camp, but developed enough so that investors start to be interested in funding them "over the counter". -- FredericBaud 16:04, 17 September 2007 (EDT)

[edit] Q&A on investors

Question: How do we qualify Investors? Is it open registration for all? Or, just for those involved in FundCamp?--SamRose 13:07, 17 September 2007 (EDT)

Answers: In a first stage, I would suspect that this is only for investors involved in a FundCamp that agree have their information made public (something we should strongly recommend, but probably not require as mendatory). -- FredericBaud 16:04, 17 September 2007 (EDT)

[edit] For mentors

[edit] Screening

• Ability to identify projects looking competencies corresponding to the mentor's

[edit] Coaching

• Ability to provide coaching to specific projects
• Ability to help in the building of business documents (exec summary, investor pitch, business plan,..)

[edit] For organizers

[edit] Creating a FundCamp

Organizers should be able to create a FundCamp (name, language,..) then track who is submitting an application, managing selection process,..

[edit] Functional Specifications

We should list here the list of functions that will be available (e.g. search function based on criterias,..)

[edit] Public / private space

Everyone should be able to set a private or public status to different resources belonging to them. When private, they should be able to provide access to these on a per user basis.

=== Temporary discussion on public/private technical note: for technical implementation we could maybe use "ACL with OG User Roles" (http://groups.drupal.org/node/5392)

[edit] Functional Architecture

We should list here the big components that will constitute the system (e.g. a component will manage everything concerning projects, another component will manage everything concerning FundCamps,...)

[edit] Q&A on functional architecture

Question: It seems like "entrepreneurs", "investors", "mentors" should be roles that people can register under. Does this seem right? --SamRose 13:07, 17 September 2007 (EDT)

Answers: I think this can be roles. Maybe some people could have multiple roles (investor and mentor). I think we should have for every individual content (read content_type) associated to his declared role (a mentor should have a field expertise, a field bio,..; an investor should have a field industry profile, level of investment, investment bio,...) -- FredericBaud 16:04, 17 September 2007 (EDT)

[edit] Technical Specifications

We should list here the technical solution that we will use to deliver all the above.

[edit] Using Drupal

Version 5.2.

[edit] List of Drupal modules

• CCK for custom content types (used to create "Project" entity)

[edit] List of custom developments

If any, php pages, sql scripts,...

[edit] Prototype

We are starting prototyping and you can access this prototype at http://platform.fundcamp.org