FS Sandbox
Driver | Approver | Contributors | Informed Stakeholders | Status |
---|---|---|---|---|
@Vineet Singh | @rikin (Unlicensed) | @Razak K M @Shreya Agarwal (Unlicensed) @Andrew Hicks (Unlicensed) | @Stuti Verma (Unlicensed) @Mayank (Unlicensed) | NOT STARTED |
Release FS Sandbox on the revamped FS website
Objective
Release FarmStack sandbox that lets visitors to:
see how FS works with a dummy data
integrate data in the google sheets
configure a usage policy
leave comments for further questions
What do we want to build?
On FarmStack website there is a prominent CTA “See how it works” or “FS Sandbox” or “See it in action” with email id. See the example of segment for positioning on website. This lets the user in a model with the following steps.
S. No. | Steps | Feature | Outcome |
---|---|---|---|
1 | Demo overview | Video explaining the mock use case and steps involved
| Spends 45-60 seconds and move to next |
2 | Preparation material | One google sheet created with dummy data in view mode that has PII data (farmer identifiers, produce details like crop, yield, grade etc) Application - a node.js code snippet that joins two tables and outputs more than two tables with de-anonymised data | Sees the data, understand the different fields |
3 | Configure connector | Connector 1 for farmer/ activity is preconfigured Connector 2 for file 2 is asked to be configured:
| Connector is configured by the user Notes:
|
4 | Usage policy | Configure usage policy:
| Usage policy is configured |
5 | Output | Two options:
| User gets the output file as email or browser |
Reference example flows
Elastic.io |
|
---|---|
Market Research
Closest to FS (open source):
pipelinewise - side project of transferwise
Meltano - side project in gitlab
Similar (not open source) and diff model - big ones:
Competitive Analysis
FarmStack can be categorised as a iPaaS and application integration blocks above
The closest to FS is Airbyte in terms of vision as an open source
What differentiates FS?
Focus on open source brings transparency
Trusted connector used for secured inter organisation data transfer
Connector architecture lets custom application integration
Usage policies lets users restrict data to be used by a verified application
Success metrics
Goal | Metrics |
---|---|
Acquire new enterprise customers | Increased signups Increased demo requests |
Gain insights | Requests for customisation Requests for usage policies |
Target Personas
Type of persona | Profile |
---|---|
Government/ research/ grant officers | senior officer looking at increasing impact using data |
senior officer researching tools for increased value of grants | |
For profit companies | product and program manager looking at tools for integrating data |
engineering person looking at how FS works | |
Technology/ business consultants | consultants looking to advise government programs on data centric solution |
engineering person exploring a specific tool that shows the promise |
Messaging & positioning
Product description
Short positioning statement
Detailed positioning statement
Top-Line message | |||
Product promise |
|
| |
Customer pain points |
|
| |
Product proof points |
|
|
Pricing
Free!!
Open source
Communication activities
Activity | Owner | Due date | Status | Notes |
---|---|---|---|---|
Internal comms | ||||
|
| NOT STARTED |
| |
|
|
|
|
|
PR | ||||
|
|
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Blog | ||||
|
|
|
|
|
|
|
|
|
|
Social | ||||
|
|
|
|
|
|
|
|
|
|
Engineering Decisions
Product will be developed in three stages:
A Frontend will be developed using React framework.
A demo video will be created using the frontend and uploaded to the website.
Backend APIs and plugins will be developed and connected to the Frontend.
More plugins (for example, Kobotoolbox plugin) could be later integrated to the product.