Skip to content
This repository was archived by the owner on Dec 12, 2024. It is now read-only.

Demo Call Outline

Chris Pondoc edited this page Jun 8, 2024 · 1 revision

Demo Call Outline

Here was our planned outline for Demo Calls.

  • Outline:

    • Recap Previous Call
    • Start Story and Product Orientation
    • Pain and Benefits (Try to Highlight 3 Things)
  • Intro:

    • Making sure this is still a good time?
    • Thanks again! Been working with the team and would love to show you a demo of what we’ve built
    • How we’re gonna structure the call
      • Recap the motivation
      • Orient around the needs the product solves for
      • Showcase pains and benefits
      • Open-ended feedback
    • Sounds good?
  • Recap Previous Call:

    • We talked last time about the concept of AI search
      • Search is an important part of e-commerce – first thing people see/go to on websites and is a critical part of conversion
      • However, traditional search is old-school – you’re not capturing user intent, you’re only able to surface quite general search results, etc.
    • We want to build a solution that is personalized and truly captures what a user’s intent is
  • Start Story and Product Orientation:

    • Let’s say I’m an e-commerce business, and I have my internal list of SKUs (use the fashion dataset)
    • I’m using existing keyword search, but I’m not getting a high conversion rate, even after optimizing other metrics
    • I also want to build this new form of semantic search inspired by new AI platforms, but building in-house is tricky
      • Maybe I don’t want to drain my engineering talent, maybe there are more relevant features on my product roadmap, so on and so forth
  • Is there a way to easily build from the ground up?

  • Pain Points and Benefits:

    • For demo: explain the concept of SUPost
    • First: it might be difficult to understand how to get started with your complex e-commerce data
      • We offer a full platform that allows you to upload your arbitrary data, pick which features are relevant, and let us handle the complexities of implementing AI search
      • You can also look back on all the collections you’ve made, and then even do a preview of the search
    • Next: search might be difficult because search queries change all the time, and users are giving more natural language queries that your search engine can’t understand
      • Our search engine can handle them :) take a look at some sample queries
      • Sample searches
        • Cool art to put in my room
        • Modern kitchen items
        • Cheap computer equipment
        • A new laptop for school
    • Finally: you might be wondering why a specific search query gave you the results that it did
      • Our algorithm handles that, as well! We provide the explanations necessary so that users don’t feel like it’s a black box
  • Feedback:

    • Would love to leave it open for feedback!

Table of Contents

For other information, check out our team's Google Drive. For a daily stream of thoughts, check this document.

Important Documents

Meetings

General Meetings

SGM Notes

Unusual Ventures Meetings

Kenja: A New Experience for Shopping

Initial Brainstorming

Needfinding

Customer Discovery Calls

Prototypes

Wine Marketplace Platform

Initial Brainstorming

Wine Needfinding

Prototypes

Miscellany

Clone this wiki locally