Update email marketing schedule

rfortherestofus · May 14, 2024 · 3a01930 · 3a01930
1 parent 7dc3c71
commit 3a01930
Show file tree

Hide file tree

Showing 2 changed files with 10 additions and 3 deletions.
diff --git a/email-marketing.qmd b/email-marketing.qmd
@@ -22,9 +22,9 @@ We have four main types of emails that go out to people:
 
 - **What's New in R** emails are emails with three interesting packages/tutorials/etc. They go out Monday mornings at 5am, except when Monday is a holiday in the United States, in which case they should go out Tuesday at 8am. These are sent manually as broadcasts. 
 
-- **Master Sequence** emails are prewritten emails that educate people on a variety of R topics. They often include links to blog posts and other resources we have created. They go out Tuesday mornings at 5am. The [Master Automation](https://app.convertkit.com/automations/1271379/edit) automation looks for people who get the Flag - Newsletter Signup, Interested - R in 3 Months, Purchased - Course, or What's New in R tags added and then adds them to the [Master Sequence sequence](https://app.convertkit.com/sequences/1690383). 
+- **Master Sequence** emails are prewritten emails that educate people on a variety of R topics. They often include links to blog posts and other resources we have created. They go out Wednesday mornings at 5am. The [Master Automation](https://app.convertkit.com/automations/1271379/edit) automation looks for people who get the Flag - Newsletter Signup, Interested - R in 3 Months, Purchased - Course, or What's New in R tags added and then adds them to the [Master Sequence sequence](https://app.convertkit.com/sequences/1690383). 
 
-- **Live Broadcast** emails are for new content that R for the Rest of Us produces (new blog posts, podcast episodes, etc). They generally go out Wednesdays at 5am and are sent manually as broadcasts.
+- **Live Broadcast** emails are for new content that R for the Rest of Us produces (new blog posts, podcast episodes, etc). They generally go out Thursday at 5am and are sent manually as broadcasts.
 
 # Course Signup Emails
 

diff --git a/proposals.qmd b/proposals.qmd
@@ -2,4 +2,11 @@
 title: "Proposals"
 ---
 
-We use PandaDoc to create proposals for clients.
+We use PandaDoc to create proposals for clients.
+
+Proposals should always lay out information on:
+
+1. Scope
+1. Timeline
+1. Meeting schedule
+1. How we will communicate requests and feedback