Where skincare becomes
a timeless promise
For Ani · for your eyes
Paudelmar × Yaksok
Engagement record · June 2026
paudelmar ×
Engagement record · April 20 – June 20, 2026

The first two months,
and everything built in them.

A complete record of the work delivered on Yaksok so far — the strategy foundation, the team rebuilt from the ground up, the financial model, and every artifact, in one place. What was done, what broke, what was fixed.

10
Strategy & brand
deliverables
5
Team roles sourced
& negotiated
3
Full plans — each
rebuilt repeatedly
~450h
Over 9 weeks
full-time

Month one built the brand foundation. Month two turned to execution — diagnosing a team that couldn't deliver, then sourcing and building one that can.

A complete record of the first two months: the strategy that was set, the team that was built, the plan that was modeled, and every document behind them. The timeline, the work track by track, the problems solved along the way, and a full index follow.

01 — The arc

How the two months actually ran.

The real chronology, week by week — exact dates, the pivot, and the rounds of revision that each conversation triggered.

Apr 20Month 1 · Strategy

Strategy & brand foundation

A full strategy sprint, on its own. Brand audit, competitive reframe, positioning, core messaging, the psychometric customer profile, the go-to-market plan, and the strategic proposal — the thinking everything else runs on.

May 20Month 2 begins
The pivot

Execution intended — then the team diagnosis

Began building the processes to run the strategy through the team already in place — an initial team structure was created and presented, with a responsible owner assigned to each marketing area. Within days it was clear the team couldn't execute it. The reports requested since the start weren't coming; the processes had nothing reliable to run on. Decision: stop patching, rebuild the execution layer.

May 24–25holiday weekend
Urgent

Last-minute brand acquisition strategy

An urgent request from Ani landed over the holiday. Two near all-nighters to produce a complete brand acquisition strategy and presentation on the deadline.

Wk of May 26build + recruit

Built the engine structure and framework, and started hiring

Wrote job descriptions for every role; began recruiting and interviewing while still running the existing team. Built the repeatable, scalable engine structure and framework — the processes for performance marketing, social, conversion, and content production — plus every role brief and scope and the additional vendors needed. Issued RFPs. Deep-dived Google & Meta Ads and pushed new ads live, and chased the CAC/ROAS report owed since the beginning.

June 1presented the team
Decision point

New team presented — spend in question

Presented the people found and the priority functions needed to start seeing results. Ani was unsure on spend for both the team and content production. Activated the Scenario B already prepared for exactly this: renegotiated rates with the team, re-briefed the production companies, ran a fresh RFP. In parallel — with no performance hire imminent and no results — ran the full performance deep-dive: analyzed every Google Ads campaign, built the performance summary report and its conclusions, built a new Google Ads tracking dashboard, and wrote a corrective action plan. The decision to bring on Luke (CRM) was made this week — though he wouldn't start until the initiation payment was made, 11 days later. Also prepped Luke's onboarding, negotiated the Paudelmar contract and payment terms, and began the 6-month marketing plan on the newly negotiated rates.

Wk of June 8revised proposal
Revision

Lower-cost proposal — still not a yes

Ran a presentation-level deep-dive on Google Analytics — into the CAC, LTV, and ROAS outlook. Re-presented the proposal at lowered rates, this time with the exact output numbers the production and content cycles would generate. Ani still wasn't sure — so built a full marketing financial plan: forecasting demand, projections, budget, ROI, break-even points, and win-back estimates under the current setup, over the next two years.

June 15scenarios
Revision

Multi-scenario plan — the store goes in

Began presenting the scenarios — but a key input had been missing from the earlier demand planning: the store's own sales numbers needed to be built into the projections and counted as part of the marketing results, not just ecommerce. Ani also made clear the store launch had to be included, without question, and that we should think big first and reduce scope if necessary, rather than the other way around. Through the week, after more conversations, understood what going big really meant in terms of execution and involvement. Anabel now folded into the production picture. The scenarios were re-modeled on every new input, until landing on the single plan with everything Ani wants, and what it would cost.

June 20where it stands

Foundation set, plan costed, one open question

New team sourced and negotiated, and the launch-inclusive plan modeled and costed. Luke (CRM) started June 15 — delayed by the lag in his initiation payment — after the prior week spent getting him ramped up on the brand. He's set to deliver the project by June 30, with a full week of Q&A beginning after review. The open question is scope — this has become a larger engagement than typical fractional-CMO work, and sizing it correctly is the next conversation.

A note on revisions

Every plan above was rebuilt after each conversation with Ani. The team proposal, the production approach, and the 6-month model were each revised repeatedly as spend appetite and scope shifted — most of the work between June 1 and June 20 was re-modeling the same plan against new constraints, then presenting it again.

02 — The work

What was built, line by line.

A checklist of every deliverable, grouped by track. delivered · built & ready · in motion. Each linked item opens the document.

II

Team, operations & production

Month 2
Diagnosed the inherited teamTwo weeks of execution surfaced that the existing team couldn't deliver to standard — the call that triggered the rebuild. Done
Sourced & interviewed a new teamRecruiting, candidate sourcing, and interviews across CRM, performance, social, and editing — agency-of-record work beyond a standard CMO retainer. Done
Built the marketing engine structure & framework + role scopesRepeatable, scalable structure and framework for performance, social, conversion, and content production — plus job descriptions, briefs, and scopes for every role and the additional vendors needed. Built
Performance lead — in negotiationPaid/media lead (Block5) — rate and scope being finalized. In motion
Performance marketing deep-diveWith no hire imminent and no results coming, analyzed every Google & Meta Ads campaign, built a performance summary report and a new Google Ads tracking dashboard, and wrote a corrective action plan. (Dashboard still to be finalized.) Built
III

Planning, finance & the case to Ani

Month 2
Marketing budget & P&L modelMulti-tab workbook restructuring spend that had crept up before the engagement began into a real, governable budget. (File: yaksok_marketing_budget.xlsx) Built
KPI tracking dashboardDaily / weekly / monthly tracking structure — the measurement layer for once the engine is live. (File: yaksok_kpi_dashboard.xlsx) Built
Team & execution boardTeam structure and content-execution flow for the marketing engine, June–November. Built
6-month plan + multi-scenario modelsA full 6-month marketing plan on negotiated rates, plus multiple growth scenarios modeled against the marketing P&L and budget — different spend levels, different speeds, different actions — re-modeled on every new input until it included the store launch Ani required. Built
Presented & re-presented to AniThree rounds — the team (Jun 1), the lower-cost proposal (Jun 8), and the multi-scenario plan (Jun 15) — each rebuilt after the conversation before it. Presented
03 — Honest account

What didn't go to plan — and what I did about it.

The point of a record is that it includes the hard parts. Each of these is a problem that was diagnosed and acted on, not absorbed.

The inherited team couldn't deliver.
→ resolved by
Diagnosed it within two weeks of execution and made the call to rebuild rather than keep patching.
Reports & analysis weren't produced.
→ resolved by
Requested them on a cadence; when they didn't come, produced them directly so decisions weren't blocked.
Processes had nothing reliable to run on.
→ resolved by
Rebuilt the operating model — the playbook, ownership, and handoffs — around a team that can actually execute it.
Spend had crept up before the engagement.
→ resolved by
Diagnosed where it was going and restructured it into a governable budget and P&L.
04 — Engagement scope

Engagement scope.

The role, going forward

What this engagement is showing is a business with many moving pieces and a larger structure that still needs to be built underneath it. The role sits at two levels at once — a creative-direction layer, with a CMO layer on top of it.

In practice that spans more than a typical fractional brief. It includes ongoing recruiting — likely continuous, given the hire-fast, let-go-fast nature of an early-stage company. It includes a wide body of brand work that's essential to execution: non-AI, human-written copy across ecommerce and the brand's online presence; vendor selection and management, including cleanup of redundancy and overlap between production companies and freelance roles. And it includes actually leading and managing the team, reporting on results, data analysis, monitoring performance, and always planning ahead to stay in front of it.

On top of that is the creative strategy itself — ongoing and evolving — and the brand vision and story, reiterated with every new campaign. And a large part of Paudelmar's value is me as a representative and a network: opening doors for the brand and building community, so Yaksok is inserted organically on a value-based perception rather than paid impressions.

Put together, the role is a combination of strategy, execution, creative direction, and data-driven marketing — heavy on data analysis and financial modeling — plus community building backed by a strong PR network. This is what Yaksok needs right now: someone who can see the whole picture and understand the business inside and out, and at the same time execute the marketing strategy, manage the team, and represent Yaksok's vision everywhere it shows up.

Given that focus and scope, delivering the results I was brought on to create means proposing the next step — and the projections of what it will produce. Part of that is raising the retainer, so I can execute at full capacity, with the focus this needs to be on Yaksok.

05 — The archive

Everything, in one place.

Every document produced in the first two months, linked below. To publish this page, keep the files in the same folder as this file (or repoint each link to its Google Drive location). Spreadsheets live in the Paudelmar Drive; Miro boards link out directly.

Planning, finance & presentation

KPI DashboardXLSX · Drive
Where this leaves us
The foundation is set.
The team is real. Now it runs.

Two months in: the strategy is done, the spend is governable, and — for the first time — there's a team that can actually execute it. From here the work shifts from building the engine to running it.

Paudelmar × Yaksok · Engagement Record · April–June 2026 Prepared by Paula Andrade · Paudelmar