Amelia S. Gagne — CEO, Kief Studio.

I'm CEO and co-founder of Kief Studio, a technology studio headquartered in Shrewsbury, Massachusetts. I run operations and strategy, and I build across the full stack alongside my co-founder and spouse, Brian Gagne (CTO). The studio was formally founded in 2022, but the partnership predates the entity by a decade — I've been in tech since 2012, and Brian and I have been working together the entire time.

But the work started long before that.

I've had a job since I was twelve — babysitting business, helping manage my aunt's in-home daycare. By high school I'd taught myself the Adobe and Microsoft suites and was using them daily. My first real technology project was helping an orthodontics office transition from paper filing to a fully computerized system. I didn't call it a digitization project at the time, but that's what it was.

Before 2012 I'd held four supervisory roles in retail — budgets, hiring, training, inventory, marketing production, vendor coordination — alongside a long-running role at a fine dining restaurant and event venue where I worked my way into five positions over nearly a decade, two of which were created because I kept filling gaps no one else would. I also produced branded marketing collateral for national restaurant, telecom, and grocery chains. By the time I started working with Brian, I'd already managed teams, hit sales targets, built operational workflows from scratch, and created marketing materials for audiences I'd never personally belong to. I just hadn't written any code yet.

Brian changed that. He showed me how the web actually works — not as an application you use, but as infrastructure you build. I started with HTML, CSS, and WordPress sites. The more I learned, the more projects he brought me into. Meanwhile, it was my job to find the work: email campaigns, lead generation, outbound prospecting, building the pipeline that kept us busy enough to keep building. Marketing wasn't a department — it was survival.

In 2014 I learned Python. That was the turning point. Suddenly the repetitive parts of our work — data cleaning, report generation, content formatting, lead research — became automatable. I wanted more: data science, additional languages, deeper systems thinking. By 2015 we had a growing roster of clients across industries that had nothing in common except that they all needed technology they couldn't staff internally. That cross-industry exposure became our advantage. When you serve as the technology arm for businesses in healthcare, cannabis, finance, retail, legal, hospitality, and e-commerce simultaneously, you see patterns that specialists miss. You also learn to wear a lot of hats — and when you're responsible for other people's content and brand voice, you learn to think like their customers, not yours.

As the client base grew, so did our own operational pressure. Thirty articles to write across five industries. Three websites to build. A go-to-market strategy to execute. Two people, less than a week, and the same standard of quality on every deliverable. The answer was never "work more hours" — it was "automate every repeatable piece, communicate constantly, and leverage each other's strengths." That pressure is where our methodology was born. Not from theory, but from necessity.

Brian introduced me to AI after he'd been experimenting with IBM Watson. He saw where the field was heading before most people were paying attention. We started integrating AI into our own operations first — wherever it made the most sense, wherever it could compress a timeline or improve accuracy without sacrificing quality. It worked. We were able to expand what we offered clients and deliver faster than teams three times our size. In a market where everyone was still talking about AI, we were already shipping with it. That became a genuine differentiator. The methodology we'd already built — observe, decide from data, automate what holds, replicate what works — mapped directly onto AI adoption. We weren't learning a new discipline. We were getting better tools for one we'd been practicing for years. That experience became the foundation for The Crossroads of AI Integration, the 800-page book Brian and I co-authored, and eventually for the Perplexity AI Business Fellowship. The credibility came from the work, not the other way around.

Cybersecurity followed a similar arc, but that one was Brian's from the beginning. He's been teaching me cyber safety since 2012 — not as a course, but as a constant discipline woven into how we work. As his expertise deepened, our infrastructure got better: stronger architecture, better monitoring, tighter access controls. He opened my eyes to how exposed most small businesses actually are — not through fear, but through demonstration. Once you see what's out there, you can't unsee it. That understanding became one of the driving forces behind Kief Studio: helping good people do good things. When you're handling other people's data, their customer information, their infrastructure — security isn't something you add later. It's a constraint you design around from the start. Security at Kief Studio isn't a service we sell — it's a byproduct of how we build. Every system ships with it baked in because we wouldn't ship it any other way.

Visibility has been the common thread in every engagement we've run. I've been on my own since eighteen — no safety net, no family funding. So when someone has a strong idea and not enough resources to execute it, I understand that problem personally. We got exceptionally good at search engine optimization — years of testing methods, mastering ranking on different platforms, proving that a disciplined strategy beats a large budget. What those engagements gave back was deep, operational knowledge about how different industries work, what breaks first, and what technology actually solves versus what it just complicates.

Along the way, we donated full builds to ten businesses — seven of them women-owned. Not as charity. As investment in the kind of work we believe in, and in the knowledge that comes from building real systems for real operators who can't afford to waste a dollar on something that doesn't work.

One thing that defines how Brian and I work together: we challenge and motivate each other constantly. We learn at least one new thing every day — not as a slogan, as a practice. Different rabbit holes, different skill sets, but the expectation is the same on both sides. When one of us levels up, the other one notices and pushes harder. That dynamic is what keeps a two-person studio operating at the level it does.

The behavioral science side of my work came from a personal place, not a professional one. I studied psychology because I wanted to understand how people communicate — starting with my own relationships, my own patterns, the gaps between what I intended to say and what people actually heard. I pursued certifications in marketing psychology, consumer behavior, positive psychology, and neuro-linguistic programming not to hang them on a wall, but because the frameworks genuinely changed how I operated. They changed how I listened in client conversations, how I structured onboarding flows, how I wrote messaging that resonated instead of just informing. When you understand cognitive load, default bias, and how people actually make decisions under uncertainty, it stops being soft science and starts being an engineering constraint — as real as memory limits or network latency. The code and the people questions aren't separate tracks for me. They're the same discipline, and the psychology training is what made that visible.