Due Diligence Checklist

Due Diligence Checklist Professionals already know how to conduct a general due diligence evaluation of a company, without needing any coaching from us.

From a technical standpoint, however, what we are presenting here is somewhat different from a conventional business opportunity, based on a narrowly bounded product or service. Here the scope of things is much broader than this. To coin a phrase, what we are presenting is a "protocol-based, industry-building leadership play."

In purely technical terms, the execution of this requires a number of critical assets, all of which must work together in coordination. To understand how this protocol play works, reviewers must understand what these technical components are, and how they fit together. To assist reviewers in reaching this understanding, the following is a checklist of all the assets and components that we consider to be key to our engineering and business success.

This list is our suggested starting-point for the technical dimension of due diligence. As a bare minimum, any potential investor should satisfy himself that each of these assets is real, and fit for its intended purpose. An investor may well do more than is presented here, but no investor should do less.

For investors conducting their own investigation the checklist is a suggestion; for investors wishing to interrogate us it is a requirement. For any investor who wishes to subject us to questioning, familiarity with everything in the checklist is our precondition to talk to you. We understand that any serious investor will have lots of tough questions. But we insist that you do your homework first. We will then be happy to give you clear answers to all your questions.

Basic Concepts

Read Operation WhiteBerry.
Read the Business Plan Executive Summary.

Protocols

Read The LEAP Manifesto.
ESRO. Verify that this protocol exists, that it has been RFC published, and that it has the technical characteristics we are claiming.
EMSD. Verify that this protocol exists, that it has been RFC published, and that it has the technical characteristics we are claiming.
Maintenance organizations. Visit the ESRO and EMSD maintenance organizations, and verify that they provide adequate resources for the support of their respective protocols. Join one or more of the mailing lists at these sites.
The LEAP Forum. Visit the LEAP Forum website, and verify that it has adequate resources for the support and development of the LEAP protocols.
Review the Free Protocols Foundation website. Verify that patent-free declarations have been made for ESRO and EMSD.

Subscriber Services

Read A Vision for Libre Services.
ByName services. Thoroughly review the www.ByName.com and My.ByName.com websites.
Create your own ByName account, and verify that the service provides all the functionality we claim.
Visit all other Libre Services websites: ByNumber, ByAlias, BySMB, ByWhere, ByTopic. Verify that basic starting-point services are available at all these sites.
Read about the Neda Data Center.

Open-Source Software

Review all our open-source software distribution centers: MailMeAnywhere, BySource, ByBinary, VoRDE. Verify that the claimed software is available at all these sites.
Retrieve and evaluate the WhiteBerry source code.

Business

Read the entire Business Plan.
People. Read the professional biographies of all Neda principals.
Verify our list of consulting clients.
Verify our list of Internet services clients.
Verify our list of software licensees.

Investment

Read our Investment Philosophy.
Review available prior due diligence reports.

Miscellaneous

Google us using a few relevant words and phrases. Try the following:

	"Operation WhiteBerry"
	"Libre Services"
	"RIM Patent Fiasco"
	"The WAP Trap"
	"Neda Business Plan"
	"MailMeAnywhere"

Independent Thinking

What is the significance of Internet RFC publication? Why is this an important requirement for us?
Why is the Free Protocols Foundation important to us? What is the significance of patent-freedom of our protocols? What effect do we expect this to have?
What do we mean by "protocol-based, industry-building play"?
All our software is licensed under the General Public License (GPL). What is the significance of this? What effect do we expect this form of licensing to have?
Why have we published an Open Business Plan?

Sections