Why I am building SkillSaige

I’m Sayre. I’m the CEO and technical founder of SkillSaige, but I’m also a mother, an artist, an engineer, a game developer, and a storyteller. Those things are not separate from one another. SkillSaige exists because of the way they fit together–and because I have spent most of my life existing in the gaps between systems that expect people to be only one thing.

SkillSaige came from noticing something I could not stop seeing.

Professional growth is often designed for people who already have the things professional growth is supposed to create in the first place.

Confidence. Time. Money. Mentorship. Connections. Room to practice. Room to fail. Room to recover.

Miss one rung, and the next becomes twice as difficult to reach. Miss two, and the problem compounds.

We tell people to be more confident, but do not give them safe places to practice confidence. We tell them to communicate better, but rarely let them rehearse difficult conversations before the stakes are real. We tell people to advocate for themselves, then punish them when they do it imperfectly.

Even when professional training is available, it is often treated as an event: a seminar, a presentation, or a compliance requirement performed once or twice a year. That may satisfy a measurement. It does not necessarily help someone build a skill effectively.

Real learning requires practice. It requires repetition, feedback, experimentation, and the freedom to get something wrong without damaging your career, a relationship, or your ability to provide for your family.

That gap is SkillSaige.

If only it was that easy

Spoiler alert: it was not. My path to seeing that gap was not particularly direct.

I studied electrical engineering at CSU, with an emphasis on processor systems, then I trained as a concept artist at RMCAD and earned a BFA. I studied writing whenever I could because what I really wanted was to tell stories.

For a long time, those fields felt incompatible. Engineering could provide stability, but felt lifeless to me without art. Art could tell stories, but existed within industries where stability was difficult to find. I learned to program, design, write, build systems, and move between disciplines because at first it was what was afforded me, and over time was what I excelled at: the systems connecting it all.

At a startup incubator, I worked across art, marketing, product development, software, and business. Through work with SurveyGizmo, I saw marketing funnels, SaaS development, product cycles, sales cycles, customer personas, and the internal machinery that connects them.

Later, while developing Reliquary, I learned what happens when creative vision, technical reality, funding, leadership, and scope fail to align. I also learned how much can still be built when you understand your constraints clearly enough to design around them, and sensibly plan for the worst outcomes.

None of these experiences gave me a tidy career identity though, or at least, I used to think they didn’t.

What they gave me was tools

See, it turns out “career identity” can be a bit of a trap. It keeps your vision narrow, keeps you saying “I can’t learn that” before you even try. But skills are really just tools, not identity.

And concept art was a tool. Engineering was a tool. Writing was a tool. Software was a tool. Storytelling was a tool.

The real skill was learning how they fit together, and seeing the systems that leveraged them the threads connecting them all. Systems engineering learned by practice rather than study. I was learning the story of systems, and the tools that put them together.

That matters because building something people will genuinely use is, in many ways, a process of storytelling.

Good work involves a million stories coming together into one. The story of the person using the product. The person purchasing it. The person teaching with it. The people making and maintaining it. The systems surrounding it. The risks it creates. And understanding all that? It requires empathy.

I was not interested in building another tool exclusively for people who already had every advantage. I was also not interested in building another chatbot wrapper and pretending that an unpredictable conversation machine was automatically helpful because it could speak coherently.

Large language models are powerful technology, but power does not absolve us of the responsibility to decide where and how that technology should be used.

That meant SkillSaige would need to be structured enough to teach, flexible enough to feel natural, and carefully constrained enough to remain predictable. Saige needed moods, objectives, boundaries, and the ability to react to what a learner was doing without becoming an unbounded artificial companion, but also needed to be affordable.

That approach required more work than attaching a character portrait to a text box and a 10,000 word prompt: we did try that, to be sure. It didn’t cut it.

SkillSaige was built unusually lean in the beginning. I used every discipline I had because that was what the situation required. When my children were home, I was there to take care of them and help with homework. When they were at school, at an activity, or asleep, I worked. Without my team, my cofounder, it wouldn’t have been possible.

There is nothing magical about constraint. It will just as readily crush a person as strengthen them. But if you can live within it, it can force you to find unexpected answers to problems.

Constraints can reveal what a system assumes

If a system only works for people with money, time, childcare, health, confidence, and a strong professional network, then it is not neutral. It is selecting for people who already have support and calling the outcome merit.

That means it has blind spots. Gaping weaknesses you can walk through, if you’re willing to see them. And then it’s up to you if you reinforce them from the other side, to make it easier for the next person across… or wall it up and let no one through after you.

I want my children to see that you can care deeply and still build meaningful things. That you can refuse to disappear into a life that does not fit you and still succeed.

That belief shaped SkillSaige as much as any technical decision did, and now SkillSaige exists for people trying to grow without enough slack.

It exists because communication, confidence, leadership, and self-advocacy are skills, not personality traits granted to a fortunate few.

And it exists because technology should be built with empathy: for the people who use it, the people affected by it, and the people responsible for making it work.

That’s why I do what I do. Because doing good things well leads to breakthroughs, innovations, and genuine progress for the people whose lives it touches.