Anon and Personal AI — Engagement Notes

Anon and Personal AI — Engagement Notes

Follow-up notes (8/17/23)


  • This document outlines a potential product scope and pricing for an engagement between and Anon.
  • My aim for the call is as follows:
    • Get feedback on product scope and pricing.
    • Align on integration timing (testing, production launch) and estimated user counts.
    • If in agreement, we would move to drafting up a contract.

Product Scope Outline

  • For now, we are just focused on a singular use case:
    • 1A (Send and receive messages as a user)

Pricing considerations

  • Simplicity. Eventually, we will have volume-dependent pricing that will scale with users, connections, usage, and more, but we want to keep this simple and measurable, for now.
  • Minimum commitment. At this stage, we’re choosing which use cases to support so need to have some guaranteed minimum commitment outside of volume-based pricing.
  • Early partner discount. We want to acknowledge that would be one of our earliest partners so we want to create a structure that reflects that.

Suggested pricing structure

  • Per-user pricing: $1/user/month
    • Discounted from $2/user/month as a Design Partner.
    • Unlimited authentications, refreshes, usage, data throughput, etc.
    • Volume discounts above thresholds (e..g $0.85/user/month above 10k users).
  • Testing period pricing: Free
    • All integration and testing work prior to launch is free.
  • Contract length: 6 months.
    • Can include a 30 or 60-day “out” clause in the agreement.
    • Can also include an MFN/pricing protection for the future.
  • Minimum monthly pricing (post-launch):
    • Ramp-up period (months 1,2): $2,500/month
      • Due to limited service availability, we want to offer a lower minimum. We still need some minimum because we’re allocating significant resources.
    • At-scale (months 3,4,5,6): $5,000/month
      • We should have most integrations desired by ready during this time.

Integration availability

  • Our aim would be to have the first few “First Phase” services available for launch, and release any that aren’t available for launch shortly post-launch.
  • The “Second Phase” integrations should be available by month 3, but pending some scoping for WhatsApp, specifically.

Integration-specific notes

Tech Difficulty
Scheduled Avail
Second Phase
Some device limitations; still exploring
Very Difficult
Likely only possible with MacOS app (not Chrome/iOS)
First Phase
Lots of demand; priority
First Phase
Lots of demand; priority
First Phase
Lots of demand; priority
First Phase
Lots of demand; priority
Second Phase
Moderate demand; moderate priority
Second Phase
Available via API, so lower priority
Third Phase
Moderate demand; moderate priority
Third Phase
Less demand; low priority

END OF SECTION — notes from older meetings to follow.

Notes from prep session and call (8/8/23)

  • Daniel prepared the following materials ahead of a call with Sharon on 8/8.

Initial scope

  • The Design Partnership Agreement is meant more as an LOI to engage with our services in the future. There are no agreed-upon integration requirements or commercial agreements.
  • We do want to start aligning on details (timeframe, use case, etc.) for a future integration, though.

Potential products

  • Per our discussion, there are a number of potential ways could use Anon. The following is synthesized from our first conversation notes:

Type 1: Outbound “actions”

  • 1A: Send and receive messages as a user
    • ⚙️ Integrations:
      • Instagram, Facebook, Twitter, LinkedIn, etc. (maybe iMessage, WhatsApp, etc.) or even Tinder, Hinge, Bumble, etc.
    • 🚀 Actions:
      • Write draft messages or actually send and receive messages as a user via his/her social channels.
  • 1B: Post on social networks as a user
    • ⚙️ Integrations:
      • Instagram, Facebook, Twitter, LinkedIn, etc.
    • 🚀 Actions:
      • could post messages as a user on various social platforms.
  • 1C: Take other “actions” as a user
    • ⚙️ Integrations:
      • Many possibilities.
    • 🚀 Actions:
      • Booking travel, restaurants, hotels;

Type 2: Inbound training data

  • 2A: Train personalization models with external social data
    • ⚙️ Integrations:
      • Instagram, Facebook, Twitter, LinkedIn, Evernote, Notes, Spotify, etc.
    • 🚀 Actions:
      • Easier access to training data to more quickly build a users personalized model.

Questions to address

  • Which of the prior use cases fits into’s roadmap?
  • What is the urgency and timetable for building any of these use cases?
  • Are there other use cases we aren’t considering that would fit here?