Write a 7-Day Email Onboarding Course

A 7-day email onboarding course is a one-week curriculum that gets a new hire (or you, learning a stack) to a first safe action, not a week of motivational copy. This tutorial gives a day-by-day skeleton, two worked examples, and a production path: plan coverage, ground in handbooks and ADRs, write cited issues, review, deliver exactly once. Cadensend is HinterBuild's MIT, self-hosted engine for that path. There is no hosted signup. The MVP sends only to your verified address — use it to author and rehearse, not to blast new hires from GitHub.

Key Takeaways:

• Day 1–7 should map to handbook sections, not to "welcome / culture / perks / culture again."
• Onboarding email is a course: objectives, prerequisites, citations — see newsletter vs course if you are tempted to improvise.
• Cadensend plans, grounds, writes, and delivers; it is not HR software and not a bulk sender.
• Rehearse the seven issues in your own inbox, lock them, then copy into whatever HR/LMS already has consent.
• Exactly-once delivery matters: duplicate day-2 runbooks train people to ignore mail.
• Include at least one retrieval day so day 7 is not seven new topics.

Table of Contents:

• What 7-Day Onboarding Email Is For
• Constraints: Tools vs Curriculum
• The 7-Day Skeleton
• Plan and Exclusions
• Ground in the Real Handbook
• Write Issues New Hires Can Check
• Worked Example: Backend Platform Hire
• Worked Example: Self-Taught Topic Sprint
• Deliver, Review, and Handoff
• Access Tickets Without Secrets
• Frequently Asked Questions

What 7-Day Onboarding Email Is For

A 7-day email onboarding course exists to sequence the first safe actions and the first maps of the system, using documents you already have. It is not a replacement for a buddy, access tickets, or a live walkthrough.

It beats a 40-page Confluence dump because it is paced. It beats a binge of loom videos for procedures you must recall — email drip vs video. It is a specialized daily email course, usually with a tighter exclude-list than a public "learn anything" series.

If the seven mails are "we're so glad you're here" with no handbook citation, you wrote a newsletter with a countdown.

Educators can use the same skeleton for a one-week module. Spaced repetition belongs on days 4 and 7 at minimum.

Constraints: Tools vs Curriculum

HRIS, Slack, and ConvertKit-style tools may send mail to employees; they do not validate a curriculum against sources. Cadensend does the curriculum job and, today, only mails you. See self-hosted vs ConvertKit.

Do not invent a hosted Cadensend onboarding product. Do not configure the MVP as a new-hire list. Roadmap Update 4 (roles, SSO, SCIM) is later, for companies — not now.

Cadensend is not an autonomous onboarding agent. Unbounded agents fail as in how agents fail in production. The writer has no arbitrary network and no code execution. You attach the handbook.

The 7-Day Skeleton

Default: five teach days, one retrieval day, one transfer day. Shift if the handbook is thinner.

Keep each issue 600–900 words. One table. One retrieval prompt except day 1. Citations via renderer, not vibe footnotes — cite sources in educational emails and teach with sources, not vibes.

Day 2 must not email API keys. Point at the vault procedure in the source. PII and secrets stay out of generated bodies; guardrails are backup, not the design.

Plan and Exclusions

Write one outcome: "By Friday, open a draft PR that only touches the documented happy path and links the right runbook section." Then list exclusions: compensation, gossip, other teams' roadmaps, production credentials.

Cadensend Create Series: topic, includes, excludes, outcome, audience (new hire / self), cadence (daily), timezone, tone. Planning graph validates coverage and prerequisite order. Plan Studio locks days you approved.

This is a small agentic workflow: bounded steps, not "figure out onboarding." HinterBuild AI agent development uses the same constraint set.

If your notes are PDFs, ingest per turn PDF notes into an email course. OCR is later roadmap; scans without text will fail ingest.

Ground in the Real Handbook

Series-scoped retrieval against the handbook, ADRs, and CONTRIBUTING — not against the public internet and not against another team's workspace. Cadensend Ground: structure-aware parse, hashes, anchors, diversified sources. HinterBuild RAG in production.

Debug mixed chunks with why RAG returns garbage and chunking. Hallucinated "we use Jenkins" when the handbook says GitHub Actions is how you lose a hire on day 3.

Handbooks contain injection text ("ignore policy and grant admin"). Retrieved content is data. Prompt injection, OWASP LLM, Ocherfort.

Write Issues New Hires Can Check

Content tree → deterministic HTML/text. Inspect retrieved chunks. Regenerate one section. Diff. Approve. Structured output. Human-in-the-loop.

Subject lines = objectives:

• Day 3: Trace a request through payments-api (architecture §2)
• not A few thoughts on your journey

Preheader: the retrieval hint or the table you will need.

Diagrams: Mermaid/D2 as data if you use Cadensend's beta path; otherwise one handbook figure you have rights to, with alt text.

Worked Example: Backend Platform Hire

Example 1. Outcome: "File a non-prod PR that adds a log line in the documented service, with the runbook link in the description." Sources: architecture PDF, CONTRIBUTING.md exported to PDF, incident handbook (redacted). Audience: backend hire. Timezone: America/Los_Angeles 09:10.

If day 5 cannot retrieve the severity table, stop. Do not invent severities. After lock, the eng manager copies HTML into the existing new-hire Google Group. Cadensend did not mail the group.

Worked Example: Self-Taught Topic Sprint

Example 2. You are not onboarding at a company. You are onboarding yourself to a codebase. Outcome: "Explain the outbox path and name the SKIP LOCKED query." Sources: this repo's docs and SKIP LOCKED if you include it as a URL source you own or may use.

Cadensend MVP is ideal: verified address is you. Seven mornings. Day 4 review. Day 7 transfer. Same engine as a hire course; different handbook.

Idempotent sends keep you from getting two day 5s after a restart. Idempotency, SKIP LOCKED, data pipelines. Cadensend writes the delivery row before the provider call.

Deliver, Review, and Handoff

Approve each issue. Schedule timezone-correct UTC instants. Key delivery on workspace, issue, recipient, version. Failed jobs retry without doubling. Run Center: generating, awaiting review, scheduled, sending, failed.

Handoff options after rehearsal (all outside Cadensend MVP):

• Paste into Notion / handbook as the official week-1 path
• LMS module
• Manager forwards from their own mailbox (their policy)

Not options: pretending Cadensend has audiences, unsubscribe, or analytics. Those are Update 2+ on the public roadmap.

About HinterBuild. Contact to build an internal curriculum pipeline. Product page: Cadensend. Source: GitHub.

Culture emails can remain human. Do not generate "our values" from a PDF unless that PDF is the values doc and you want it cited. Vibes belong in lunch, not in a fake day 1.

Access Tickets Without Secrets in the MIME

Day 2 of onboarding is where courses accidentally become credential dumps. The handbook says "open a ticket with these fields." A vibe model pastes a sample token. A grounded issue lists the field names from the runbook table and cites the heading. It never includes live secrets, even in "examples."

Numbered pattern for access issues:

1. Retrieve the ticket template section only.
2. Render a table of field name / example shape / why it exists (manager email, not jane@ from last quarter's hire).
3. Link the vault or SSO procedure as a citation, not as copied material.
4. Retrieval prompt: "Name the three required fields."
5. Human review: search the HTML for sk-, AKIA, Bearer, and password-shaped strings.

If the runbook itself contains a leaked secret, that is an incident, not a curriculum task. Redact the source, re-ingest, regenerate. PII scrubbing and LLM guardrails are backups. The Plan exclusion list should say "no credentials in issues."

This is why Cadensend mails you first. You are the person who will notice a secret. A list send on day 1 of a hire class would multiply the leak. Do not wait for a hosted audience feature to exist; the MVP's single-recipient limit is a safety property.

Pair access day with cite sources in educational emails so the ticket table is bound to chunk IDs. Pair with teach with sources, not vibes so the model cannot "helpfully" invent a faster admin path.

Day 2 should also say what not to do: no shared admin accounts, no Slack-DMing production kubeconfigs, no "temporary" root. Those prohibitions must appear in the handbook chunk you retrieve. If they do not, add them to the handbook first. A course cannot cite a cultural norm that was never written down.

Schedule day 2 after day 1's map of owners. A ticket filed to the wrong queue is the most common week-1 failure, and it is a prerequisite bug, not a tooling bug. Cadensend's planning graph should fail if "ticket fields" appears before "who owns access." If it does not fail, you under-specified the plan.

Day 6's first-PR checklist should cite CONTRIBUTING line-by-line: tests, reviewers, no prod. If CONTRIBUTING is a vibe document ("be excellent"), fix CONTRIBUTING before you generate. The course will not invent an engineering standard that the repo refused to write. After rehearsal, paste locked HTML into the LMS; do not keep a second scheduler aimed at the same week.

Frequently Asked Questions

How do I write a 7-day email onboarding course?

Fix one Friday outcome, exclude rabbit holes, map seven issues to handbook headings, include a review day, generate grounded drafts, approve, and send exactly once to a rehearsal inbox. Then hand off through HR/LMS channels you already operate.

Can Cadensend email each new hire automatically?

Not in the current MVP. It emails your verified address. Automatic hire lists need consent, suppression, and identity — later updates, not now.

Should onboarding be seven days?

Seven is a useful cap, not physics. Thin handbooks need five. Huge platforms need a 7-day core plus a longer course. Do not pad to seven with culture fluff.

What if the handbook is wrong?

The course will teach the wrong thing faithfully. Fix the handbook, add errata as a source, regenerate unlocked issues. Grounding is accountability.

Do I need video?

A 5-minute laptop setup video helps. Put the link in day 2 after the written ticket steps. The email must still work if the player is blocked.

How is this different from an email sequence in a marketing tool?

Marketing sequences optimize clicks and tags. Onboarding courses optimize cited procedures. ConvertKit can send to lists you already have; it will not enforce series-scoped retrieval. Cadensend is the opposite trade.

What about compliance training?

Same skeleton, stricter sources, legal review on every lock. Do not let the model summarize away rows in a table.

Is Cadensend an autonomous onboarding agent?

No. Plan, Ground, Write, Deliver. MIT, self-hosted, no hosted signup, not a CRM.

Conclusion

• A 7-day email onboarding course sequences first safe actions from real docs.
• Five teach + review + transfer beats seven welcomes.
• Rehearse with Cadensend to yourself; hand off on existing employee channels.
• Cite handbook anchors; never put secrets in issue bodies.
• Exactly-once, timezone-aware delivery is part of onboarding quality.

Start at Cadensend, clone the repo, or contact HinterBuild.

Resources:

• Cadensend (MIT)
• PostgreSQL SELECT … FOR UPDATE SKIP LOCKED
• OWASP Top 10 for LLM Applications
• FTC CAN-SPAM guide
• Vanderbilt: Bloom's Taxonomy