Hello to Canada’s SaaS and AI Community,
Product teams today can build faster than ever. Tools like Claude Code and AI copilots have compressed development cycles and lowered the cost of execution.
What hasn’t changed is the harder part of product work. Teams still need to decide what deserves to exist, how to avoid unnecessary complexity and how to protect the people doing the work as expectations rise.
At SAAS NORTH 2025, Kris Nicolaou, Founder and CEO of Brain Box Labs, explored that tension through a simple idea: great products emerge when strong systems support great people.
Key takeaways:
- Strong product teams rely on clear systems that help teams focus on the right problems.
- Minimum viable thinking protects speed by validating value before complexity.
- Coaching and autonomy allow leaders to scale decision making across teams.
Speed Has Changed; Judgment Has Not
Since our most recent SAAS NORTH, the capabilities available to product teams have expanded quickly. AI-assisted coding environments, autonomous agents and tools like Claude Code allow small teams to move with a level of velocity that would have seemed unrealistic only a year ago.
That acceleration hasn’t removed the core challenge of product leadership. If anything, it has sharpened it. When the cost of building drops, the risk of building the wrong thing rises.
Kris framed the balance clearly early in the session.
“Great product equals strong systems and great people.”
Execution may be faster today, but the operating system around that execution still determines whether progress compounds or simply creates more noise.
The Cost Of Weak Systems
Kris shared findings from a national survey of 500 product decision makers. Fifty-six percent reported burnout driven by unrealistic timelines and unclear priorities. Only twenty-nine percent use any form of scoring or prioritization model, and nearly half skip retrospectives entirely.
None of these statistics suggest a shortage of capable teams. Instead, they reveal how easily strong teams struggle when the systems around them lack clarity.
When prioritization depends on urgency or the loudest stakeholder rather than a shared framework, roadmaps begin to drift. When retrospectives disappear, opportunities for learning fade with them. Over time the pressure accumulates quietly across the team.
As AI tools make building easier, those weaknesses become even more visible. Speed without structure tends to magnify the same problems rather than solving them.
Building The Right Things First
To reduce reactive product decisions, Kris introduced the MASON framework, which stands for Must have, Should have and Nice to have.
The structure encourages teams to ask three stackable questions before declaring something essential.
- Is it required?
- Is it needed on day one?
- Will the product fail without it?
Only when the answer to all three questions is yes does the feature qualify as a must-have.
This discipline helps teams separate critical functionality from ideas that may be valuable later but can delay progress in the early stages.
In an environment where building has become easier, that filter becomes even more valuable.
Minimum Viable Thinking As A Habit
Kris encouraged the audience to extend minimum viable thinking beyond product launches.
“Build the smallest thing to validate that it solves the customer’s pain point.”
The goal is not to release something incomplete for the sake of speed. It is to prove the product actually solves a meaningful problem before investing heavily in polish and expansion.
Kris illustrated the point with a story about an SEO platform that spent four weeks building a sophisticated sharing modal that fewer than one percent of customers actually used.
A simple email link could likely have delivered nearly the same value in a few hours.
The example reflects a pattern many teams recognize. Complexity tends to appear long before it proves necessary, while the simplest version of a solution often produces the clearest signal from customers.
Clarity Before Execution
Even strong prioritization frameworks cannot prevent friction if scope is unclear.
Kris emphasized writing specifications with enough clarity that two different people could interpret them and arrive at the same outcome. His teams reinforce that clarity through mid-sprint check-ins designed to surface risks early and through a shared definition of done that establishes when work is truly complete.
One practical habit involves recording short walkthrough videos of completed features before they reach QA. These demonstrations allow teams to confirm alignment visually and resolve misunderstandings before testing begins.
Even release timing reflects the same philosophy. Shipping early in the week allows teams to respond collaboratively if issues appear, while retrospectives scheduled at the start of the next sprint ensure insights remain fresh.
Systems Alone Are Not Enough
Systems only succeed when people adopt them.
“If they’re surprised, they resist. If they’re informed, they engage.”
Product teams tend to combine analytical thinking with creativity, which means abrupt changes can feel disruptive even when the goal is improvement.
Kris recommends introducing new processes gradually through early notice, reinforcement during meetings and clear written follow-up. Even small shifts in language can influence adoption, encouraging teams to view new practices as enhancements rather than disruptions.
Leadership As Leverage
Survey data also highlighted the influence leadership has on retention. Forty-four percent of employees leave because of lack of growth and poor leadership, compared with twenty-nine percent who leave primarily because of compensation.
Kris described coaching as one of the most powerful tools available to leaders.
“Coaching is asking good questions.”
He supports this mindset with the 1-3-1 framework, which asks team members to bring a problem alongside three possible solutions and their recommended path forward. When mistakes occur, Kris uses a framework built around Facts, Fix and Future to guide recovery and learning.
The conversation begins with what happened, moves to how it will be resolved, and ends with how similar issues can be prevented in the future.
Why This Conversation Matters
Kris closed with a reminder that resonated with many product leaders in the room.
“Yes, product is hard, but with great systems expertly deployed, great teams with your leadership, and the tools, frameworks, and tactics to bring it all together, I can confidently say you got this.”
AI tools are changing what product teams can build and how quickly they can build it.
The deeper challenge remains deciding what deserves to be built in the first place and ensuring the people doing that work can sustain the pace.
SAAS NORTH continues to create space for these conversations, where founders and operators share the systems and habits behind great products rather than just the outcomes.
SAAS NORTH is Canada’s hub for scaling SaaS and AI companies. Founders, teams, and investors come to learn, connect, and grow with the country’s largest in-person tech community.