---
title: PaperTube HubSpot Email Build
type: article
created: '2026-01-22'
updated: '2026-01-22'
source_docs:
- raw/2026-01-22-sprint-planning-meeting-116396706.md
tags:
- papertube
- hubspot
- email-build
- avoke
- sprint-planning
layer: 2
client_source: Paper Tube Co
industry_context: ecommerce
transferable: false
---

# PaperTube HubSpot Email Build

## Overview

During the [[wiki/meetings/2026-01-22-sprint-planning|2026-01-22 Sprint Planning Meeting]], the team defined ownership and approach for an upcoming batch of email builds for [[wiki/clients/current/papertube/_index|PaperTube]]. These are simple, text-only marketing emails to be built in HubSpot and assigned to [[wiki/team/avoke-onorimuo|Avoke]] 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 [[wiki/clients/current/cora-italia/salesforce-email-build|Cora Italia Salesforce email build]], 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:

1. **Platform simplicity** — HubSpot is more intuitive than Salesforce Account Engagement; no HTML authoring required for text-only emails
2. **Workload distribution** — Raphael was already being assigned the Cora Italia Salesforce build plus new page builds for Overhead and Advanced Health & Safety
3. **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

## Related

- [[wiki/clients/current/cora-italia/salesforce-email-build|Cora Italia Salesforce Email Build]] — parallel email build effort using a different platform and developer
- [[wiki/clients/current/bluepoint/hubspot-email-flow|Bluepoint HubSpot Email Flow]] — separate 3-email HubSpot flow assigned to Raphael (automation handled by Karly)
- [[wiki/meetings/2026-01-22-sprint-planning|Sprint Planning Meeting — 2026-01-22]]