From ef4ec39a761ce67a2ad27c1a0ea0bb7c8f9fbdf4 Mon Sep 17 00:00:00 2001
From: Daniel Avila <messagedaniel@protonmail.com>
Date: Sat, 11 Feb 2023 11:54:17 -0500
Subject: [PATCH] update press release notes

---
 _PRESS-RELEASE.md | 20 +++++++++++++++++---
 1 file changed, 17 insertions(+), 3 deletions(-)

diff --git a/_PRESS-RELEASE.md b/_PRESS-RELEASE.md
index 21aed8e950..061d80e091 100644
--- a/_PRESS-RELEASE.md
+++ b/_PRESS-RELEASE.md
@@ -1,6 +1,7 @@
 # Project Name #
+ChatGPT Clone
 
-<!-- 
+<!--
 > This material was originally posted [here](http://www.quora.com/What-is-Amazons-approach-to-product-development-and-product-management). It is reproduced here for posterities sake.
 
 There is an approach called "working backwards" that is widely used at Amazon. They work backwards from the customer, rather than starting with an idea for a product and trying to bolt customers onto it. While working backwards can be applied to any specific product decision, using this approach is especially important when developing new products or features.
@@ -9,36 +10,49 @@ For new initiatives a product manager typically starts by writing an internal pr
 
 If the benefits listed don't sound very interesting or exciting to customers, then perhaps they're not (and shouldn't be built). Instead, the product manager should keep iterating on the press release until they've come up with benefits that actually sound like benefits. Iterating on a press release is a lot less expensive than iterating on the product itself (and quicker!).
 
-If the press release is more than a page and a half, it is probably too long. Keep it simple. 3-4 sentences for most paragraphs. Cut out the fat. Don't make it into a spec. You can accompany the press release with a FAQ that answers all of the other business or execution questions so the press release can stay focused on what the customer gets. My rule of thumb is that if the press release is hard to write, then the product is probably going to suck. Keep working at it until the outline for each paragraph flows. 
+If the press release is more than a page and a half, it is probably too long. Keep it simple. 3-4 sentences for most paragraphs. Cut out the fat. Don't make it into a spec. You can accompany the press release with a FAQ that answers all of the other business or execution questions so the press release can stay focused on what the customer gets. My rule of thumb is that if the press release is hard to write, then the product is probably going to suck. Keep working at it until the outline for each paragraph flows.
 
 Oh, and I also like to write press-releases in what I call "Oprah-speak" for mainstream consumer products. Imagine you're sitting on Oprah's couch and have just explained the product to her, and then you listen as she explains it to her audience. That's "Oprah-speak", not "Geek-speak".
 
 Once the project moves into development, the press release can be used as a touchstone; a guiding light. The product team can ask themselves, "Are we building what is in the press release?" If they find they're spending time building things that aren't in the press release (overbuilding), they need to ask themselves why. This keeps product development focused on achieving the customer benefits and not building extraneous stuff that takes longer to build, takes resources to maintain, and doesn't provide real customer benefit (at least not enough to warrant inclusion in the press release).
  -->
- 
+
 ## Heading ##
   > Name the product in a way the reader (i.e. your target customers) will understand.
+  ChatGPT Clone
 
 ## Sub-Heading ##
   > Describe who the market for the product is and what benefit they get. One sentence only underneath the title.
+  Wrap all conversational AIs under one roof.
 
 ## Summary ##
   > Give a summary of the product and the benefit. Assume the reader will not read anything else so make this paragraph good.
+  Conversational/Utility AIs are the future and OpenAI revolutionized this movement with ChatGPT. This app commemorates the original
+  styling of ChatGPT, with the ability to integrate any current/future conversational AI models through user-provided APIs.
 
 ## Problem ##
   > Describe the problem your product solves.
+  ChatGPT is down ( and don't want to pay for ChatGPT Plus). ChatGPT/Google Bard/Bing AI conversations are lost in space or
+  cannot be searched past a certain timeframe.
 
 ## Solution ##
   > Describe how your product elegantly solves the problem.
+  Serves and searches all conversations reliably. All AI convos under one house.
+  Pay per call and not per month (cents compared to dollars).
 
 ## Quote from You ##
   > A quote from a spokesperson in your company.
+  Keep AI open
 
 ## How to Get Started ##
   > Describe how easy it is to get started.
+  Input your API key(s) and you're ready to go.
 
 ## Customer Quote ##
   > Provide a quote from a hypothetical customer that describes how they experienced the benefit.
+  I can semantically search my conversations and customize templates for any AI model!
 
 ## Closing and Call to Action ##
   > Wrap it up and give pointers where the reader should go next.
+  Keep an eye out for new conversational AI models and respective API access! Own your
+  conversations! Pay per call and not subscription!