About

Somewhere between a spreadsheet and a sketchbook.

I'm cautiously obsessive about systems, I've tracked every one of the last 365 days of my life in a spreadsheet, and I genuinely cannot pick a restaurant to save my life. I also happen to run the operations practice behind some of the founders and coaches you follow.

Franchette, founder of CRMSN Founder / Operator

Franchette

CRMSN, Operations Practice
Why CRMSN exists

I'm Franchette, the operator behind CRMSN.

Most coaches and founders I work with aren't struggling because they lack vision. They're struggling because their backend hasn't caught up with their growth.

I started CRMSN because I kept seeing the same pattern: brilliant people with real momentum, held back not by effort, but by operations that never got rebuilt to match it. Missed handoffs. No onboarding. Content that lived in someone's head. Teams that couldn't run a single day without the founder in the room.

That's the gap CRMSN works in. I come in when there's friction under the momentum, when things are moving, but the structure underneath isn't holding. I'm not just executing tasks. I'm thinking alongside you, an operational partner, not a subcontractor.

Personal Index
Location
Hailing from the PhilippinesCurrently traveling across Asia, working globally
Background
STEM → Marketing → OpsTwo pivots before this one stuck
Currently obsessed with
Sweet potatoes & teaAny tea. Hardcore about it.
Known for
365 days, one spreadsheetA daily log of an entire year of her life
Off the clock
Manga, novels, sketchbooks, 3 dogsRomantasy and historical fiction on rotation
Fuelled by
Curiosity & local recsCan't plan a trip without a stranger's opinion
The long way here

Two pivots, one obsession that never left.

The pattern was there before the job title was.

STEM

Started here because order and logic already made sense to her. It was never really about the subject, it was the structure.

Marketing

Shifted into business, then marketing, learning how ideas actually reach people, and how much of that depends on what happens behind the scenes.

Operations

Landed here because it was always the real draw, building the systems that let good ideas survive contact with a growing business.

I've always been drawn to order, not the rigid kind, the kind that quietly makes everything else possible. Long before "operations" was a job title I'd claim, I was the person color-coding calendars for fun and building spreadsheets nobody asked for, just because I liked seeing a system click into place.

That instinct followed me through a STEM background, then a shift into business and marketing, before landing exactly where it was always headed. Marketing taught me how ideas reach people. Operations taught me what has to be true behind the scenes for that to actually work, and keep working, launch after launch, without the founder holding it all together by hand.

The honest version of this story is that someone else pointed it out before I did. I was already doing it — organizing, systematizing, making sense of the moving pieces around me — long before I thought of it as a skill, let alone something I could build a career around. It just felt like how things were supposed to work. I assumed everyone thought this way. Turns out, not so much.

The same brain that once built a 365-day log of her own life now builds the operational backbone for other people's businesses. That's not a coincidence, it's just where the obsession finally found a home.

I also draw and paint, occasionally these days, and I still think in frameworks even when I'm off the clock. If you've ever met someone who's constantly moving but fiercely protective of her own quiet time, that contradiction is basically the whole operating manual for how I work.

How I work

The principles behind every engagement.

01

Systems over hustle

I don't add more effort to a broken process, I fix the process so the effort isn't needed in the first place.

02

Thinking partner, not task-taker

I ask why before I ask what. You get someone who pushes back when something doesn't serve the goal.

03

Built to run without me

Everything is documented. If I stepped away tomorrow, your systems would still hold.

04

Discretion, always

I work inside real businesses with real stakes. What happens in the backend stays in the backend.

Say hi

Find CRMSN elsewhere.

Operational tips, behind-the-scenes builds, and the occasional dog cameo.

Home Offers Work About Contact Book a Call →