
growth.newsletter·versija 1.0.0·melnraksts1 jāpārbauda
Ikmēneša jaunumu vēstule tiek plānota, uzrakstīta, pārlasīta, apstiprināta un nosūtīta, un tās rezultāti tiek fiksēti.
The monthly send date is coming up and the newsletter has not been sent. Not for a one-off campaign mail to a segment — that is growth.run-experiment territory if it is a test, or a one-time send the owner approves separately. Not for social posts — use growth.social-post-weekly. If the list itself is suspect (bought, scraped, stale), fix that first; do not send over it.
news@company, never a person's mailbox).Jebkurš solis var gaidīt līdz datumam un atveras pats; katrs noslēgts solis atstāj pierādījumu (piezīmi, saiti, skaitli).
Pull from the growth log, the tasks and goals, and the owner's notes: what shipped, what is coming, any offer or event with a date.
Izdarīts, kad a short list of 3–5 candidate items exists with dates and facts.
Apstiprinājums · S2 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu
Present the candidates with a proposed subject line and one-sentence angle for each. The owner names one lead item and approves the subject line direction.
Izdarīts, kad the owner has picked the lead and the send date is confirmed.
Write the issue: subject line, lead item first, one clear call to action, plain language, under ~300 words of body. Every link gets its final destination now, not later.
Izdarīts, kad a full draft exists with all links pointing at real pages.
Open every link and confirm each lands on the right page; check the mail renders with images off; spell-check the subject line; confirm the sender address and reply-to; confirm the unsubscribe link works.
Izdarīts, kad every link, address and the unsubscribe link have been verified by opening them.
⛔ A dead link found here costs a minute; found after sending it costs an apology.
Read the whole text aloud once — catches broken sentences and missing words. If the company has a second person, they read it too.
Izdarīts, kad the text has been read end to end and corrections applied.
Apstiprinājums · S6 · īpašnieks — izpilde apstājas, līdz nosaukts cilvēks ieraksta lēmumu
Show the final draft, the recipient list size and the source of the list. The owner approves sending to this list on this date.
Izdarīts, kad the owner has said yes, in writing (a message or a task comment).
Send from the approved sender identity to the approved list, at the agreed time of day.
Izdarīts, kad the send is complete and the sent copy is archived in the mail module.
After 3–5 days, read back the numbers: delivered, opens, clicks, unsubscribes, replies. Write them into the growth log next to the issue, compare with the previous month, and note one thing to try next issue.
Izdarīts, kad the numbers and the note are in the log and the owner has a two-line summary.
| Pazīme | Rīcība |
|---|---|
| A wrong or dead link was sent | Send a short correction mail the same day with the right link; note it in the log. |
| Spam complaints or a spam-folder landing | Check the sender identity, SPF/DKIM/DMARC of the sending domain (see tech.dmarc-review); pause further sends until fixed. |
| The list contains addresses with no consent record | Do not send to them; remove or re-permission them; tell the owner before the next send. |
| Open rate collapses versus last month | Check deliverability first (bounces, complaints), then subject line and send time; do not change two things at once. |
| The send date slips | Send late rather than skipping — an unbroken streak matters more than the exact day; note the reason in the log. |
The approved draft and the owner's approval (who, when) · the sent copy · the recipient count and list source · open/click/unsubscribe numbers with the read-back date · the growth log entry.
After every 6 sends ask: are opens and clicks flat, rising or falling, and did the one change noted in S8 move them? Did any send go out with a broken link or to a wrong list? Was any issue late, and why? A new version changes the step that caused the slip or the miss, and says so in its change note.
Nosaukums un kopsavilkums ir latviski. Detalizētā izpildes kārtība pagaidām ir kanoniskajā angļu valodas versijā; juridiskos un finanšu soļus publicēsim latviski tikai pēc cilvēka pārbaudes.
Obligātās sīkdatnes tur sarunu kopā. Analītika ir izslēgta, līdz tu atļauj — tā neliek nevienu sīkdatni un neglabā ierīces identifikatoru.Necessary storage keeps your conversation together. Analytics is off until you allow it — it sets no cookie and stores no device identifier. Ko mēs glabājamWhat we store