Data Ecosystem MVP: Product Requirements Document

Very active data ecosystem

# of connections between end clients and data provider

Options for data buyers

# of data providers and data assets

Largest single location of value creation for data asset owners

# of opportunities.

streamlined process for data providers

time to full on-boarding.

Revenue From enterprise clients access the provider network.

$15,000 for end data consumers

$75,000 for intermediary

Small

1. 1-10 employees

2. <3mm ARR

3. Single data asset 

4. Limited in-house capabilities

5. Revenue strapped, so value revenue above all else (will exchange short term cash for long term strategy)

[Why would the small ones use Knoema?]

1. Data assets typically are limited in business use cases

2. Small providers cannot pay anything. They are revenue strapped. DO NOT BUILD BUSINESS AROUND THEM

Medium

1. 5-50 employees

2. 3mm -30mm ARR

3. Have business model figured out

4. Single valuable data asset or multiple data assets

5. Understand productization and selling data

6. Have in-house capabilities, but lack resources to grow often

7. Looking for revenue, but also have a strategy

1. Reduce friction and offer scale

2. Multi data asset providers will look for scaling product information & 

3. Find data value creation success stories in Medium data providers (evangelists)

   1. Offer the scale they do not have with their internal teams.

1. Single data asset providers will require access control & monitoring

Large

1. 50+ employees

2. 50mm+ ARR (Typically multi-billion dollar businesses)

3. Maintain full control of their revenue/ sales initiatives

4. Looking for opportunities that “move the needle”

5. Worried about cannibalization of sales

6. Control / access control is very important.

7. Will not engage with something that looks like another platform.

1. Use direct data buying and large intermediary opportunities to drive adoption.

2. Provide open source protocol in V2 for to meet large data provider requirements for control of branding.

3. Have monitoring and access control early in product life cycle.

HIGH

Must have email notification

 Data provider receives email notification for new public opportunity, new private opportunity shared, new public data request

HIGH

Must have monitoring of opportunities

Data provider can monitor basic metrics provided back on from opportunity (Dataset for every opportunity). Example: number of views data provider has received through the Knoema.Com Ecosystem Introduction opportunity.

• Build datasets per data provider and dashboard for every on-boarded opportunity. Have set visualization template to showcase specific metrics.

• Snowflake metrics example: https://docs.google.com/spreadsheets/d/1BRWmbwEaGJcYYyBqGNNZ-FeXxGScwET-DwVYz5m3YEQ/edit?usp=sharing

  • Specifically get the request snowflake metrics.

HIGH

Must have minimum viable opportunities and data requests

Data providers must login and see 5 standing data opportunties and see 4 data requests.

HIGH

No Development required

Must have neutral branding and provider logo

Data provider can put their logo at the top of the Portal Nav Bar. “Powered By Knoema”. Data provider feels this is their tool for value creation.

MEDIUM

Must collect meaningful information

Provider can provide information to central repository of Company/Product/Asset Info for use in opportunities (Free, open-source protocol) 

https://docs.google.com/spreadsheets/d/10fdPy9A-IDyC43ZsR2zjzWIS1rNP1FD5TZ8PPnz9QWA/edit?usp=sharing

1. Traditional Metadata Collection (Free, open-source protocol)

MEDIUM

Opportunities

Sales will bring in new enterprise clients which will increase total number of opportunities that are possible

CSMs will push enterprise clients to create standing opportunities for how they would like to engage with data provider network.

Graham will coordinate and advise on creation of opportunities. Standard layout does exist in google doc shared with enterprise client

At end of stealth phase, marketing will starting pushing Knoema data provider network and engagement through opportunities.

@Emily Somma (Unlicensed)

@Graham Tolson (Deactivated)

@RichardYonkers

@Marketing

Data Request

CSMs will provide Data Request form to enterprise client on either portal homepage (all portal users can submit) or portal admin dashboard shared privately with admins.

Graham will triage data request and initiate a data request dashboard in provider.knoema.com portal. All providers are notified.

@Emily Somma (Unlicensed)

@Graham Tolson (Deactivated)

On-boarding data providers

Graham will convert current data provider network to formal network by approaching and email/ personal outreach.

New data providers will be invited to join with marketing material provided by marketing.

@Graham Tolson (Deactivated)

@Marketing

Assignment of Opportunities & data requests

Graham will coordinate and organize assignment of opportunities to on-boarded data providers.

@Graham Tolson (Deactivated)

Monitoring datasets

Knoema content team will push monitoring metrics to an individualized data provider data set. (Data_provider_opportunity_metrics.csv). Dataset will then populate opportunity monitoring dashboards, which are assigned by Graham per data provider

@Ivan Lapitsky (Unlicensed) @Graham Tolson (Deactivated)