wiki/clients/current/papertube/2026-01-22-hubspot-email-build.md · 366 words · 2026-01-22
PaperTube HubSpot Email Build
Overview
During the [1], the team defined ownership and approach for an upcoming batch of email builds for [2]. These are simple, text-only marketing emails to be built in HubSpot and assigned to [3] based on platform fit and workload balancing.
Assignment
| Field |
Detail |
| Assigned To |
Avoke Onorimuo |
| Platform |
HubSpot |
| AM |
Karly Oykhman |
Scope & Approach
- Approximately 30 emails in the pipeline; copy not yet finalized as of 2026-01-22
- Emails are text-only — no graphics, no HTML template required
- Simpler build complexity compared to the [4], which requires custom HTML in Salesforce Account Engagement
- The division of labor was deliberate: Avoke handles PaperTube's straightforward HubSpot builds; Raphael handles the more complex Salesforce/Account Engagement work for Cora Italia
"It's not a true marketing email, there's no graphics or anything, so we don't have to do HTML for that one." — Karly Oykhman
Context & Rationale
The email build assignments were made during a broader developer workload rebalancing discussion. The team was managing a high volume of upcoming email builds across multiple clients and platforms. The decision to assign PaperTube to Avoke (rather than Raphael) was driven by:
- Platform simplicity — HubSpot is more intuitive than Salesforce Account Engagement; no HTML authoring required for text-only emails
- Workload distribution — Raphael was already being assigned the Cora Italia Salesforce build plus new page builds for Overhead and Advanced Health & Safety
- Avoke's availability and willingness — Avoke confirmed she was comfortable taking this on
Status
- Copy: Not yet complete as of 2026-01-22; Karly is working on it
- Task creation: Pending copy completion before tasks are formally created in the project management system
- Timeline: Karly expected copy to be ready within approximately one week of the meeting
- [5] — parallel email build effort using a different platform and developer
- [6] — separate 3-email HubSpot flow assigned to Raphael (automation handled by Karly)
- [7]