From a live cohort course to a 6-month evergreen program

I built a remote work education program designed to help experienced professionals transition their careers to international, remote roles.

Evolution: From a 1-month live cohort → 5 iterative editions → a structured 6-month evergreen program.

My target audience was experienced professionals in LATAM aiming to work remotely in international companies.

And the outcome I got was:

Hundreds of students across multiple cohorts
Score of 9.10 / 10 stars with +350 answers
Strong demand validation before full build
The program became the core, scalable product of the business

Context: why I built this course

I was building this course while sunsetting another product. At that time, the membership and the course coexisted. The membership had proven emotionally valuable, but it lacked a clear, single job to be done.

I was actively looking for a product that was:

Highly specific
Outcome-oriented
Easier to explain and sell
Directly tied to a concrete pain

Remote work fit that criteria perfectly.

There was clear demand from my audience, and I had deep, hands-on experience navigating international careers, hiring processes, and remote work standards. This allowed me to design a product where the pain was explicit, the outcome was tangible, and my expertise was immediately credible

This course was a deliberate move toward focus and sharpness, informed by the limits I had already seen in broader community-based products.

Validating before building

I deliberately chose to validate demand before creating the full product.

What I did:

Designed and published a landing page
Defined the course index and themes
Clarified who it was for and what problem it solved
Opened sales before building the classes

I only did this because I had high confidence that I could deliver the value if people bought.

This approach allowed me to test willingness to pay, message resonance, and audience readiness.

The first edition sold well, and that was the signal to proceed.

First edition: live, scrappy, and fast

The first cohort lasted one month and included four live classes. I delivered the theory and had live debates with work experts.

Each week, I prepared the class, taught it live, collected feedback, and improved the content immediately. The course was built while being delivered.

Iteration through cohorts (editions 2–5)

Instead of locking the product early, I treated each cohort as a learning and pricing experiment.

Key changes across cohorts:

From edition 2 onward, the course focused exclusively on people seeking full-time remote roles in companies, so we excluded freelancers.
Each cohort added more assets: guides, templates, exercises, and frameworks.
Pricing increased progressively as the product matured.

Between:

In the third and fourth editions, the price increased roughly 3x
Between the fourth and fifth editions, it increased by another 2x

In parallel, I introduced paid upgrades:

1:1 conversations with me
Profile, CV, and LinkedIn reviews
Personalized feedback
Support from a recruiter

This allowed me to segment willingness to pay, keep the core program accessible, and offer deeper support to people who needed it. By the fifth cohort, the offer was clearly structured, differentiated, and economically validated.

Strategic shift: from cohort to evergreen

After five live editions, I made a strategic decision: to convert the course into a structured evergreen program.

When we asked, we people did not buy the course, the first reason was money, but the second one was that the timing was wrong. So instead of having a fixed start date, we would give them the chance of a flexible start date.

This required a different type of work.

What we did:

Edited all live theoretical classes into 30+ professional videos
Wrote 200 pages of structured exercises, guides, and resources for each week
Designed a six-month progression that could be followed asynchronously
Organized all content into a clear learning path

The goal was to maintain depth and quality while increasing scalability.

The evergreen program combined async structure with live reinforcement.

Key components:

Six months of access
Curated weekly learning path
Private Discord community
Weekly newsletter
Access to 200+ curated remote job opportunities every week
Live coworking sessions with no fixed agenda
Practical workshops to connect theory with action

This hybrid model preserved accountability, human connection, and flexibility for different schedules

User podcast testimonials

Designing the full user lifecycle: onboarding, offboarding, and extension experiments

As the course matured and moved toward an evergreen model, I started treating it as a full lifecycle product, not just content delivery.

That meant intentionally designing:

onboarding
in-program checkpoints
offboarding
and post-program experiments

Onboarding: reducing activation friction

Every participant went through a structured onboarding sequence. The goal was activation.

Onboarding included:

A multi-email welcome sequence over the first 30 days
Clear explanation of what the program included and what it didn’t
Step-by-step guidance on:
- accessing the platform
- joining Discord
- completing their profile
- understanding how events, reviews, and support worked
A live onboarding session each month to align expectations and answer questions

This helped reduce early overwhelm and made progress paths explicit from day one.

In-program checkpoints: maintaining momentum

Throughout the months, we ran periodic check-ins:

Short surveys asking where participants were stuck
Emails contextualizing “where you should be at this point”
Invitations to ask for help when progress slowed

This allowed us to detect drop-off early, surface emotional or confidence-related blockers, and adjust support without over-engineering the product.

Offboarding: intentional closure and feedback

The last month of the program included:

Clear communication about what access would end and what would remain
Exit interviews or short 1:1 conversations when possible
Structured feedback collection
Reflection prompts to consolidate learnings and next steps

The intent was to close the experience responsibly, avoid silent churn, and respect the work participants had done.

Experiment: extending access after program completion

I also tested a post-program extension experiment.

Hypothesis: If participants could extend access to the community and live support after the program ended, retention and long-term outcomes would improve.

What I shipped: A paid option to extend access for six additional months, which led to continued access to the community, events, and live support. The experiment did not work as expected.

While participants valued the program during the structured phase, most did not convert into extended access once the formal journey ended.

Selling at higher prices: building the sales engine from scratch

As the price increased, selling the program became significantly harder. Early cohorts sold mostly through direct communication with my existing audience, but once the price went up, that stopped being enough.

This forced me to design a sales system. To support the higher price point, I introduced live sales webinars.

The initial format:

One free class per month
Open to anyone
Delivered live by me
No pre-recorded content
No production team

I ran this format once per month for eight consecutive months, starting in February 2025, iterating every single time.

Iteration loop on the webinar itself

The first version of the class had a clear problem: it didn’t connect well enough with what came next in the program, so I redesigned it.

From the second month onward, the free class became:

A real, valuable class on remote careers
A direct introduction to the logic, level, and depth of the paid program
A way to calibrate expectations before selling

The structure stabilized into:

First part: real educational content
Second part: live explanation of the program and invitation to enroll with Time-bound incentives: aggressive discounts valid for 24 hours
Third part, answering all the questions people had in the chat, as long as it took to go through all of them.

Each month, I iterated on Narrative, Examples, Structure, Objection handling, and Flow between content and offer

All of this was executed solo.

I designed the class, delivered it live, managed the chat, answered questions in real time, and sold the program myself.

I had no production team, no sales team, and no paid acquisition. I was streaming from the living room of my house, using my laptop.

While I hired a community builder to support enrolled students operationally, selling the program remained my responsibility.

Distribution and demand generation

Filling the webinars was one of the hardest parts.

Everything was organic, so to bring people in, I experimented month over month with:

LinkedIn content
Instagram content
Lead magnets
Newsletter promotion
Calls to action across channels

This was a continuous monthly effort, not a one-time launch.

Across those eight months:

~4,000 people attended the free classes
Conversion happened primarily live, during the webinar window

This reinforced a key constraint: Evergreen content still requires active demand generation.

This phase taught me that:

Pricing changes the entire system around a product
Selling is part of product design
Founder-led sales are unavoidable early on
Distribution is a product in itself
Iteration does not stop after validation

This experience deeply shaped how I now think about product-market fit, pricing strategy, sales enablement, and founder responsibility in early-stage products

Webinar engine

Execution plan (operational rigor)

Each webinar followed a detailed, checklist-based execution plan that covered the full lifecycle:

Pre-launch

Updated landing page and post-registration redirects
Automated confirmation and reminder email sequences
Calendar integration to increase show-up rate
WhatsApp group creation for pre-event engagement
Backup YouTube live links to prevent technical failure
ManyChat automations for Instagram and LinkedIn traffic
Centralized registration across web, link-in-bio, and profiles

Pre-event

Multi-touch reminder system: 24h, 3h, 1h, and “starting now” emails
Content updates based on previous webinar feedback
Time-bound discount configuration and checkout setup
Pre-written WhatsApp messages to guide participation

Live delivery

Founder-led, fully live session without production team
Real-time chat monitoring and Q&A
Seamless transition from education to offer
No script reading, adaptive pacing based on audience behavior

Post-event

Time-limited access to replay
Structured post-webinar email sequences
Coupon expiration logic
Follow-up content for non-buyers
Automation cleanup and landing reset for the next edition

This system was reused and improved month over month.

Iteration insights and learning loop

Over multiple webinar editions, I tracked performance and ran deliberate experiments:

What the data revealed

Show-up rates were consistently high, but conversion varied widely
The main objection was price (reported by ~80% of non-buyers)
Many attendees miscategorized the program as “CV rewriting” or “recruiter mentoring”
Shorter program duration (3 months vs 6) improved perceived feasibility
Methodology-first framing converted better than CV-focused messaging

Key experiments run

Changed program length and scope
Removed ineffective discounts
Tested bonuses and time-bound offers
Improved post-webinar email sequences
Added WhatsApp pre-event surveys to qualify intent
Adjusted positioning to avoid comparison with recruiters

What did not work

Traffic-only ads without intent
Linktree as a primary conversion surface
Over-indexing on CV improvements in the pitch
Long replay availability windows

What worked better

Landing pages embedded in the main website
Emphasizing career methodology and systems
Real salary examples to anchor value
Aggressive but short-lived urgency
Live interaction and extended Q&A

These learnings were documented and directly informed subsequent iterations.

Building the team to sustain the program

As the program grew in scope and complexity, it became clear that I couldn’t run it alone anymore, especially if I wanted to maintain quality and consistency. This forced me to design a small, focused team around the product.

Community Builder: ownership of progress and signal

The first role I hired for was a Community Builder. Their responsibility was not moderation, it was product signal.

They were in charge of:

Making sure participants were actually advancing through the program
Encouraging people to share what they were working on
Detecting who was stuck, disengaged, or struggling
Acting as a real-time “thermometer” of the cohort

This role became essential to maintain momentum, surface issues early, and reduce blind spots in async progress

I had someone in a different role on the team. We redefined that role, and during that transition, she supported me in designing and structuring the program itself. When she later left the team, I had to restart the hiring process from scratch.

That meant:

Defining the role clearly
Running interviews
Designing practical challenges
Selecting someone who could combine empathy, structure, and execution

Recruiter support: depth where it mattered

This role focused on:

1:1 meetings with participants
CV and LinkedIn reviews
Profile rewrites in some cases
Giving market-level feedback on positioning and expectations

Some of that work was done by her, and some directly by me.

This required:

Clear internal coordination
Shared criteria and standards
Alignment with feedback and tone

Beyond the core team, the program also included:

Guest speakers
External contributors
Live sessions that required coordination and scheduling

Designing these workflows was part of the product work because even with a small team, this introduced operational complexity, calendar dependencies, and quality control across different voices.

What this taught me about building teams:

Programs don’t scale without clear role ownership
Community requires active stewardship
Hiring for judgment matters more than hiring for tools
Product quality depends on internal coordination as much as content
Even small teams need clear processes

This experience strengthened my ability to design roles around product needs, hire under real constraints, and lead cross-functional execution in a lean setup.

Challenges

1. How the industry changed underneath the product

One of the biggest learnings from running this program over time was understanding how much the job market itself changed.

When the course launched, the remote work market was expanding rapidly. Hiring was more flexible, and opportunities were abundant.

By the time, the program evolved into its evergreen version in 2025:

The job market had tightened significantly
AI reshaped hiring expectations
Processes became longer and more competitive
Rejection rates increased across the board

This forced the product to evolve from “how to access opportunity” to “how to survive and stand out in a constrained market”

2. The real difficulty was psychological

Another critical insight was understanding why this problem is so painful for people. Updating a CV or LinkedIn profile is not hard because of time or tools.

It is hard because it forces people to answer uncomfortable questions:

What am I actually good at?
Why should someone hire me?
What have I achieved so far?
How do I explain my value clearly?

This is emotionally taxing work. It requires reflection, confidence, and self-recognition.

As a result, people procrastinate heavily, they avoid the task even when they know it matters, and they underestimate how much support they need

This insight shaped the structure of the program, the emphasis on guided reflection, and the importance of feedback and external validation

3. Privacy over visibility

At the beginning, we issued completion certificates. Over time, we realized this created an unintended risk.

Many participants were employed full-time, exploring a career change quietly or not ready or able to signal dissatisfaction publicly

For them, having a visible certificate could create tension with their employer or expose intentions prematurely.

We decided to remove certificates entirely and prioritize participant privacy.

This meant less public proof of completion and fewer artifacts to share externally

Because privacy mattered, it became harder to collect public testimonials, share detailed success stories, and showcase internal progress publicly.

4. Outcomes take time, especially in a harder market

Another challenge was the time lag between effort and results.

Even when participants:

Completed the content
Improved their CV and LinkedIn
Clarified their positioning

They still needed to:

Apply
Interview
Navigate rejections
Wait for the right opportunity

As the job market tightened and processes became longer, outcomes often took months, not weeks.

This created a mismatch between the effort delivered by the program and the visibility of results in the short term

This reinforced an important lesson: Career products operate on delayed gratification.

You can provide structure, tools, and support, but activation depends on:

Emotional readiness
Market timing
Persistence over time

Designing for this reality requires:

Managing expectations clearly
Valuing privacy over marketing assets
Measuring progress beyond immediate job offers

This constraint strongly shaped how we framed results, communication, and success going forward.

5. Charging candidates in a company-paid industry

Another structural challenge was pricing in an industry where candidates are not used to paying.

In traditional recruiting models, companies pay to access talent; candidates rarely pay for employability services, and paying for career support is seen as the exception, not the norm.

Some potential buyers compared the program to:

A freelance recruiter reviewing a CV
A one-off mentoring session
A tactical resume rewrite service

That comparison missed the point.

The program was:

A multi-month system
Focused on positioning, clarity, and execution
Designed to support a full career transition, not just optimize a document

But because it lived close to the “recruiting” mental category, the perceived value was often anchored too low.

This forced me to:

Educate the market on what they were actually buying
Reframe the product away from “employability services”
Emphasize outcomes, process, and depth instead of artifacts (CVs, templates)
Be very intentional about not competing on price or scope with recruiters or coaches

It also reinforced why:

Live selling mattered
Narrative and framing were part of the product
Positioning was as important as content quality

This challenge made something very clear: When you price against the wrong category, even a strong product looks expensive.

Designing and selling this program required not just building value, but changing the reference frame people used to evaluate it.

That insight has shaped how I now approach pricing, positioning, and category creation in every product I build.

Product extension: turning a sales webinar into a standalone e-book

After running the last sales webinar for the program, I realized I had created something valuable beyond conversion.

The educational part of the webinar, without the sales section, was:

Structured
Narrative-driven
Focused on career decision-making
Useful even without joining the program

Instead of letting that content disappear, I decided to turn it into a new product.

What I did:

Transcribed the full webinar
Removed the sales section entirely
Re-edited the content as a coherent career narrative
Reorganized ideas into structured chapters
Added clarity, transitions, and examples
Designed custom illustrations using NanoBanana
Turned it into a 45-page career e-book

The result was a standalone product focused on:

Career clarity
Decision-making
Reframing professional identity
Understanding how to position oneself in a changing job market

This extension served multiple purposes:

Content leverage
One live webinar became a sales asset, a learning asset, and a standalone product
Different price point, different commitment level
The e-book allowed people to access value without joining a 6-month program, engage privately, and start reflecting before taking bigger steps
Clear product ladder
The e-book sat naturally between free content, the paid newsletter, and the full program.

It expanded the ecosystem without adding operational complexity.

Key performance indicators

KPI 1: Program iterations launched

KPI value: 6 editions
KPI description: Five live cohorts iterated in production plus one fully evergreen version

KPI 2: Learners served

KPI value: +200 participants
KPI description: Professionals with prior experience transitioning to international remote roles

KPI 3: Pricing growth

KPI value: ~6× increase
KPI description: Program price increased progressively as scope, depth, and support expanded

KPI 4: Content production

KPI value: 30+ recorded lessons
KPI description: Edited, professional videos created from live cohort classes for evergreen delivery

KPI 5: Reviews

KPI value: 9.10 out of 10

Product learnings

This case reinforced several product principles for me:

Validate demand before building at scale
Cohorts are powerful learning engines
Iteration beats perfection
Narrowing the audience increases clarity and outcomes
Evergreen products still need human touchpoints
Content scales better when the structure is explicit

Conclusion

These courses and program represents one of my proudest product builds.

It started with a hypothesis and a landing page, and grew through five live editions where I taught, listened, and improved every single week.

Only after deeply understanding the user, the content, and the outcomes did I turn it into an evergreen system.

This project taught me how to build responsibly, scale without losing substance, and design learning products that respect people’s time, ambition, and context.