Cora Italia Salesforce Email Build
Overview
Raphael is building a set of complex, HTML-based marketing emails for Cora Italia inside Salesforce Account Engagement (formerly Pardot). This is Raphael's first significant project in Account Engagement, and the work had been stalled for approximately one month due to a missing content document. The blocker was resolved during the [1], with Karly committing to provide the content doc and a one-week due date extension.
Context
This task was surfaced during sprint planning as part of a broader review of developer workloads. The email build had been sitting in the backlog unstarted — not because of developer capacity issues, but because the content document was never attached to the task. Raphael had not flagged the missing content, which was noted as an accountability gap: developers are expected to raise blockers proactively rather than let tasks sit idle.
Technical Notes
- Platform: Salesforce Account Engagement (formerly Pardot)
- Build type: True marketing emails — templated designs with images and branded layout
- Build method: HTML required; Account Engagement does not offer a drag-and-drop builder comparable to HubSpot
- Complexity: Higher than typical email builds due to the HTML requirement and platform unfamiliarity
Karly noted that Account Engagement is less intuitive than HubSpot and that HTML-based builds are more time-consuming. Raphael was told to reach out to Karly or Mark if he needs a walkthrough or has platform questions.
Assignment Rationale
The broader email build strategy established in this sprint divides work by platform expertise:
| Developer | Platform | Client | Email Type |
|---|---|---|---|
| Raphael | Salesforce Account Engagement | Cora Italia | Complex HTML marketing emails |
| Avoke | HubSpot / plain text | PaperTube | Simple text-only emails |
| Raphael | HubSpot | Bluepoint | Simple 3-email flow |
Raphael was kept on the Cora Italia Salesforce build specifically because these emails require HTML and a higher design fidelity — a better fit for his skill set than the simpler PaperTube emails, which were redirected to Avoke.
Status
| Field | Detail |
|---|---|
| Assigned Developer | Raphael Mangadap |
| AM Owner | Karly Oykhman |
| Platform | Salesforce Account Engagement |
| Blocker | Missing content doc (resolved 2026-01-22) |
| Due Date | Extended by one week from original date |
| Task Start | Backdated to week of 2026-01-20 |
Key Decisions
- Raphael stays on this build — despite limited prior Account Engagement experience, he is the right fit for HTML-heavy email work
- Due date extended one week — Karly will provide the content doc and adjust the deadline accordingly; Karly will cover the delay with the client in her next weekly call
- Accountability note — Raphael should have flagged the missing content doc sooner; the expectation going forward is that developers surface blockers before tasks go stale
Action Items
- [x] Karly — Attach content doc to the Salesforce email build task
- [x] Karly — Extend due date by one week
- [ ] Raphael — Begin email builds in Salesforce Account Engagement once content doc is received
- [ ] Raphael — Reach out to Karly or Mark with any Account Engagement questions (offer of a 15-min walkthrough is open)
Related
- [2]
- [3]
- [4]
- [5]
- [6]
Sources
- 2026 01 22 Sprint Planning|2026 01 22 Sprint Planning Meeting
- Index|Cora Italia Client Overview
- 2026 01 22 Sprint Planning|Sprint Planning Meeting — 2026 01 22
- Email Build Platform Strategy|Email Build Platform Strategy
- 2026 01 22 Hubspot Email Build|Papertube Hubspot Email Build
- 2026 01 22 Bluepoint Email Flow|Bluepoint 3 Email Flow — Hubspot