Categorization Methodology

To manage the process of categorizing the software products and the related reviews in the G2 community, the following methodology is followed:

1. Basic Product Guidelines:
In order to be reviewed and available in the G2 community a software product must be:
  • Associated to a specific software vendor or an open source project
  • Available for access and use, either from a customer accessible distribution medium and install process on some premises, or as a cloud or hosted service. The actual license of the software to the user organization can be a traditional perpetual, open source, some form of a term, metered or other limited use license.
  • Categorized into at least one category or subcategory heading based on the function(s) of the software (features), and not based on what the software is used for or who uses it. Many products could be used for purposes other than those that they were specifically designed for, but that subsequent use does not change the categorization of the product. For example, project management software’s functional design is to provide the features necessary to manage the work and resources associated with planning and executing a project. Projects take many forms though, and you could use the software equally well to manage the construction of a bridge or track the maintenance of a factory. The software is still project management software in each case, and not bridge construction software nor factory maintenance software. It might integrate to other systems to help accomplish those activities more effectively, but the software remains categorized as “project management”.
2. Pre-Integrated Product Suites:
Some products are available bundled as a suite of pre-integrated products. Suite products will be categorized in the following ways:
  • If the bundled products are only available in the bundle (are not priced or sold individually by the vendor), then the entire bundle will be placed in a single category that is appropriate for that bundled set of functionality only.
  • If the bundled products can be purchased as a bundle and as an individual module, then each product (module that is sold / licensed individually by the vendor) will be placed in an appropriate category by module function. In addition G2 Crowd may choose to provide a higher-level category that represents the complete bundle / suite at its discretion, based on generally accepted market understanding and use.
3. Compound Products:
Products that have the capability to be used in several different categories based on product configuration or a broad set of features (referred to as a compound product), can either be treated as a platform on which custom solutions are developed (and placed in an appropriate category for that type of platform), categorized by its most commonly recognized set of features into a single category, or included in more than one category at G2 Crowd’s discretion. (Note: These products are different from a product that is used for a function other than what it was originally designed or can be used for other functions outside of its generally intended purpose without unique configuration.) For compound products, reviews will be added to the category that most closely matches the function(s) specifically identified by the reviewer.

 

4. All-In-One Products
Products that are sold as an individual product, but have the capabilities that cover features of several different categories. These products differ from compound products in that they have generally have less robust features for each category than products dedicated to that category. These products usually target the SMB market with a single tool that provides a breadth of features. All-in-one products will be categorized only in the appropriate All-in-one categories, as these products are packaged and sold as an all-in-one product and used by users in such a way.

 

5. Company Size Product Segmentation:
In addition to categorization by function, products will also be evaluated for, labeled by and have the capability to be segmented by the appropriateness for use by company size and broken into 3 groups. The evaluation will include looking at vendor intent, market perception, market share by company size if available, reviews and other information that may be available. The subsequent decision though, is at the description of G2 Crowd. This segmentation does not change the categorization, but does provide the capability to display “like” products in a category based on target company size. The three categories are:
  • Generally appropriate and most often used by small and medium businesses (below $1B in total annual revenue)
  • Generally appropriate and most often used by large businesses ($1B and higher total annual revenue)
  • Generally appropriate and used across all businesses regardless of company size
6. Acquired Products:
Acquired products would remain categorized as originally assessed and the company name would be adjusted to the acquirer (or other naming / branding as established by the acquiring vendor), unless the acquired product is incorporated into another product as a feature / function and not available as a separate SKU under the new ownership. All reviews will follow the product. All changes to acquired products and companies occur after the acquisition officially closes.

 

7. Discontinued Products
Discontinued products would be removed from the site upon confirmation from the vendor that a product sunset date has been set and there are no new or upsell sales being made. All reviews would be removed from the site along with the product. Impacts to reports would be covered under our report amendment policy.

 

8. Vertical Product Categories:
Vertical products are products that are developed for use in a specific industry vertical to execute a unique process or set of processes, and cannot be used by companies that are not in that industry without significant customization. These products are, in other words, unique to the respective industry. Other software that could be used in the vertical but is based on horizontal software like financial accounting or procurement, even if the software has some tailoring to make it more industry relevant, would not be included in the vertical product categories, but instead with its respective functional category.

 

9. Composite Categories:
From time to time it is necessary to create a new category that is effectively the combination of some of the products and /or features from an identifiable set of other categories. These new composite categories will be clearly defined and will not impact the underlying category structure. Instead they will operate in conjunction to the original product categories.

 

10. Categorization Inquiries:
Questions and / or challenges to the categorization of a product can be submitted to G2 Crowd and will be evaluated on an individual basis, with a decision communicated in a reasonable amount of time. The above categorization methodology will be applied to all inquiries and the reviewer will include a thorough review of any evidence or information provided by the individual / company filing the question.

Notes:

Company size categorization is based on this chart:

Company Size Number of Employees
Small Total number of employees 50 or fewer
Medium Total number of employees between 51 and 1000
Enterprise Total number of employees greater than 1000

From a software buying and use behavior perspective many departments of enterprise companies can and do perform in many of the same ways as small and medium businesses. Many departments or divisions have the authority to purchase, deploy and operate their own software based on specific needs, and simply roll up data to the corporate systems as needed. Cloud software is making this behavior more prevalent as it removes the need for the division / department to provide and operate its own infrastructure.

5/13/16 – Added definition for all-in-one products.

Future changes and updates to this policy will be made in the body text and a change note will be included in the notes footer.

G2 CROWD Standard Definitions

G2 Crowd’s list of standard definitions are as follows:

1. Cloud Applications
Cloud applications are software applications that are accessible over the Internet and must have the following characteristics:
  • A standard and shared service that is available as either public or private cloud
  • Provide a user interface that is built using standard technologies
  • Turn-key solution that is packaged to include all required system resources
  • Self provisioning although may use some vendor onboarding assistance
  • Dynamic, fine grained elastic scaling for performance optimization
  • Self-service application administration
  • Published integration APIs based on web services or other Internet standards based technology
  • Use based pricing capabilities (service metering), although private cloud deployments may or may not actually utilize internal pricing (chargebacks)
2. Platform as a Service (PaaS)
A set of services in the same integrated development environment, which provide the capability to develop, test, deploy, manage and operate cloud applications. PaaS shares the same basic characteristics as cloud applications, including:
  • A standard and shared service that is available as either public or private cloud
  • Provide an administrative interface that is built using standard technologies to provide user control over software deployment and configuration
  • Turn-key solution that is packaged to include all required system resources
  • Self provisioning although may use some vendor onboarding assistance
  • Dynamic, fine grained elastic scaling for performance optimization
  • Published integration APIs based on web services or other Internet standards based technology
  • Use based pricing capabilities (service metering), although private cloud deployments may or may not actually utilize internal pricing (chargebacks)
3. Infrastructure as a Service (IaaS)
A set of cloud services that provide access to compute resources across the Internet with the following characteristics:
  • A standard and shared service that is available on a public cloud
  • Automated administrative tasks
  • Desktop virtualization capabilities
  • Self provisioning
  • Dynamic, fine grained elastic scaling that is user adjustable
  • Policy based services
  • Use based pricing capabilities (service metering)
4. Perpetual Software License
A perpetual software license provides the licensee the right to use a software product indefinitely as well as the right to access any updates and upgrades during the 1st year of the license. Access to updates and upgrades after the first year is generally offered by the vendor for an addition fee (usually a percentage of the license fee), often bundled as a part of a product support agreement and referred to as maintenance.
5. Term Software License
A term software license provides the licensee the right to use a software product for a specific period of time. In addition the license generally includes all updates and upgrades, and some type of product support during the term of the license.
6. Public Cloud
A method for accessing compute resources as a service for applications, platforms and infrastructure that meet the criteria listed above for SaaS, PaaS and IaaS, and are managed by a single software vendor but made available to external customers using Internet technologies.
7. Private Cloud
A method for accessing compute resources as a service for applications and platforms that 1. Meets the criteria in SaaS/PaaS listed above and 2. Is isolated to a single company, many times managed by the company or a hosting and managed services provider.
8. Hosted Application
A hosted application is a software application that is purchased on a perpetual license but then is given to a hosting provider to manage for a monthly fee that covers the infrastructure and management of the application to make it available using Internet technologies.
9. On Demand
On demand software is an application software deployment model that emulates the cloud delivery of SaaS applications with an application that was not architected to run in a cloud environment, and does not meet all of the accepted criteria for a SaaS application, in particular the shared resources component.
10. Software Suite
A software suite is a set of software modules or applications that are pre-integrated, share a common user interface and are designed to smoothly interoperable to execute an end-to-end business process or set of processes. The suite is sold as a single product, but may also be sold by individual module.
11. Compound Product
A compound product is a software product that has the capability to be used in several different categories based on product configuration or a broad set of features, usually the result of combining functions from several existing applications.

12. All-In-One Products
An all-in-one product is a software product that is sold individually with the capability to cover features in several different categories.