It started with the program itself.

Before you can sell an education program, you need to know exactly what you're selling.

I worked on defining the competency standard for the program and translating that into an actual curriculum.

That meant thinking through what students should be able to do by the end of the program, what they needed to learn along the way, and how the learning experience should progress from one stage to the next.

The curriculum wasn't built simply as a list of software features to learn.

The focus was on building practical capability around video editing, professional workflows, portfolio development, and preparing students to actually enter the field.

From there, I worked through the details that turn a curriculum into something that can be delivered: modules, class structure, schedules, learning materials, assessments, and the supporting processes around them.

Then came the part nobody sees.

A course can look great on paper and still fall apart when you actually have to run it.

I worked on the operational side of making the program function in practice.

That included building class schedules, distributing hours across the program, organizing sessions, preparing student-facing materials, creating learning overviews, working through computer requirements, and figuring out how students would receive information throughout the program.

Even small things needed systems.

How students submit documents.

How information is communicated.

How class schedules are shared.

How students get support.

How the community is organized.

How progress is tracked.

The screenshots from the work show just how broad that operational layer became, from class routines and hour distribution to student documentation, module handouts, Discord structure, and learning overviews.

Building the student experience around the course

I didn't want the student's experience to stop at the classroom.

I worked on the systems around the program as well, including the student community and communication structure.

That included setting up the Discord environment for enrolled students, thinking through roles and onboarding, organizing information, and creating a place where students could continue interacting with the institute outside of class.

I also worked on the supporting materials students would actually need throughout the program, from course documents and module handouts to computer specifications and other onboarding information.

The idea was to make the experience feel like an actual professional program rather than simply a collection of classes.

And then we had to fill the seats.

Once the program was structured, the next challenge was getting the right people into it.

I worked across the acquisition and sales process, including Meta advertising, lead generation, lead management, sales messaging, and direct conversations with prospective students.

The process went well beyond generating leads.

I worked on how those leads were contacted, what they were told, how questions were handled, and how the conversation moved toward an actual admission decision.

That included developing sales scripts and messaging specifically for prospective students, while also handling direct, face-to-face sales conversations myself.

So the work moved from:

Campaign → Lead → Conversation → Consultation → Admission

That gave me visibility into the entire acquisition process rather than only the marketing side of it.

Marketing the program

For the acquisition side, I worked on the campaigns and creative used to promote the program.

That included Meta Ads research and strategy, campaign development, messaging, promotional content, and the visual communication around the institute.

The challenge was different from marketing a normal consumer product.

We weren't simply selling a service.

We were asking someone to invest several months of their time, money, and effort into developing a new professional skill.

That meant the marketing had to communicate much more than what the course contained.

It needed to answer the questions a prospective student naturally has:

What will I actually learn?

What will I be able to do afterwards?

Is this suitable for me?

What does the learning experience look like?

Will this help me build a career?

That shaped a lot of the messaging and sales process around the program.

Sales became part of the job too.

I also got directly involved in converting the interest that the campaigns generated.

I developed sales scripts, worked through lead follow-up, handled questions from prospective students, and took face-to-face meetings with people considering the program.

This was useful because it created a direct feedback loop between marketing and sales.

You quickly find out what people don't understand when you're the person sitting across from them.

You hear the objections.

You hear the questions.

You find out which parts of the offer are clear and which aren't.

And that information can go straight back into the marketing, the messaging, and even the structure of the program itself.

There was a team behind it too.

Building the institute wasn't something I could do entirely alone.

I was also involved in managing the people responsible for delivering different parts of the program and coordinating the work around them.

That meant making sure everyone understood what needed to happen, keeping different pieces of the operation moving, and stepping in wherever something needed to be figured out.

The role became very cross-functional.

One moment I could be working on curriculum structure.

The next could be a Meta campaign.

Then a student issue.

Then a class schedule.

Then a design.

Then a sales conversation.

Then figuring out how the next phase of the program should operate.

That variety was probably the defining characteristic of the project.

Building the things around the program

A lot of the work ended up being things that don't necessarily belong to one obvious category.

I worked on the institute's communication and brand materials, admission forms, admission tests, professional designation formatting, Facebook page messaging, brochures, student documentation, privacy policies, and other operational materials.

I also worked on the physical and digital experience around the institute, including materials for students and the systems used to keep information organized.

These details might seem small individually.

Together, they are what made the program feel like an actual institution rather than just a course being offered by a marketing agency.

From idea to operating system.

What makes Narratives Institute different from most of my other projects is how many layers I touched.

I wasn't brought in to solve one specific problem.

I was involved in turning the whole thing into something operational.

Program design.

Curriculum.

Marketing.

Lead generation.

Sales.

Team management.

Student operations.

Community.

Creative.

Documentation.

Processes.

And because all of those areas were connected, decisions in one area often affected another.

Changing the curriculum affected the marketing message.

Talking to prospective students exposed gaps in the offer.

Running the program revealed operational problems.

Those operational problems led to new systems.

It became a continuous loop of building, testing, learning, and improving.

The part I found most interesting

The project taught me something I think about a lot now.

When you're building something from scratch, there isn't really a job description.

There is just a problem that needs solving.

Sometimes that problem is strategic.

Sometimes it's operational.

Sometimes it's marketing.

Sometimes it's a spreadsheet, a schedule, a sales conversation, a student asking a question, or a process that nobody has thought about yet.

You solve whatever is in front of you, then build something so the same problem becomes easier to handle next time.

That's essentially what I was doing with Narratives Institute.

Taking an idea and turning it into something that could actually run.