Nu Terra Labs

Nu Terra Labs If you don't know how to develop custom business solutions to win with digital innovation, don't worry!

At Nu Terra Labs, we speak your language and have the ability to support you whether its a simple or complex.

Most of the AI in your organisation wasn't built by your team. It arrived pre-built, inside SaaS products you were alrea...
08/28/2026

Most of the AI in your organisation wasn't built by your team. It arrived pre-built, inside SaaS products you were already using, or inside AI vendors you brought in specifically.

Your team still owns what that AI does to your customers.

This is the point most leadership teams underestimate. AI governance is often framed as a discipline for organisations building AI. Model choices, training data, evaluation frameworks. If you're not building, the framing suggests, the governance is somebody else's problem.

The framing is wrong. Governance follows use, not construction. If your team is deploying AI, integrating AI, exposing customers to AI outputs, or making decisions based on AI recommendations, the accountability sits with your team. The fact that the underlying technology was built elsewhere is a supply chain concern, not an accountability defence.

The teams that get this right are running governance programs that treat purchased AI, licensed AI, and integrated AI with the same discipline as built AI. They're documenting the use cases. They're assessing the risks. They're maintaining incident records. They're producing the artifacts a customer or regulator would ask for, regardless of who built the underlying model.

Nu Terra Labs' TrustFRAME work is designed to cover the AI you use, not just the AI you build. Which for most organisations is where the actual exposure lives.

→ Send us a message to book an intro call.

"Founder mode" became a leadership category in the last two years. Founders who stay deep in the details, who make decis...
08/28/2026

"Founder mode" became a leadership category in the last two years. Founders who stay deep in the details, who make decisions across all functions, who don't respect the org chart. In the right context, it produces exceptional companies.

In the wrong context, it produces micromanagement dressed up in the language of founder leadership.

The difference is usually about mandate. A founder has legitimacy that comes with having built the thing. Their team accepts founder-mode behaviour because the founder has earned the right to reach into the details. The behaviour is a feature.

A mid-market CEO who inherited or joined the company later doesn't have the same mandate. When they operate in founder mode, the team reads it differently. Not as decisive leadership. As lack of trust. As a leader who doesn't believe the team can execute without their constant input.

The behaviour looks the same on the surface. The organisational response is completely different.

The CEOs I've seen navigate this well are careful about the distinction. They're deep in the details where they have earned or been given specific authority. They're deliberately hands-off where the team is stronger without them. They talk about the trade-off openly, so the team knows which mode they're in and why.

That kind of self-awareness is not what "founder mode" writing usually emphasises. It's what actually works for CEOs without a founder's mandate.

→ Send us a message to book an intro call.

The consent form your customer signed mentioned AI. They clicked through it in eleven seconds. You know they didn't read...
08/27/2026

The consent form your customer signed mentioned AI. They clicked through it in eleven seconds. You know they didn't read it.

That's not consent. That's plausible deniability.

Consent as a governance concept assumes that the person consenting understood what they were agreeing to. When the language is dense, the disclosure is buried in a longer document, and the user experience makes reading impractical, consent becomes legally defensible and ethically thin. It might hold up in a court. It won't hold up in a customer conversation, a regulator inquiry, or a public incident.

The organisations that are ahead on this are treating consent as a design problem, not a legal one. They're writing AI disclosures in plain language. They're separating AI consent from broader terms of service. They're using progressive disclosure, so customers can drill in when they want to. They're accepting that some users will opt out, and building for that possibility.

This is more expensive than a checkbox. It's also more defensible when the question comes back later, which it will.

If your team's current AI consent flow is a paragraph in the standard TOS that users click through in seconds, the risk isn't legal. It's reputational and regulatory. Both are getting harder to insure against.

Nu Terra Labs' TrustFRAME work includes designing consent flows that produce actual understanding, not just clicks.

→ Send us a message to book an intro call.

"Modern" is the most abused adjective in enterprise technology sales, and it's worth pausing on what it usually means.Mo...
08/27/2026

"Modern" is the most abused adjective in enterprise technology sales, and it's worth pausing on what it usually means.

Modern data platform. Modern workplace. Modern CRM. Modern security stack. The word appears in almost every vendor's marketing. It rarely means anything specific.

When you press on it, "modern" tends to mean one of three things. Sometimes it means cloud-native, replacing an older on-premise architecture. Sometimes it means AI-integrated, replacing a rule-based predecessor. Sometimes it means "not the vendor you're currently using," which is a positioning claim rather than a technology claim.

The three meanings have very different implications for buying decisions. Cloud-native has real trade-offs. AI-integrated has real trade-offs. "Not your current vendor" has almost none of the trade-offs the marketing suggests, because the underlying technology is often similar to the vendor being replaced.

The question worth asking when a vendor uses the word "modern" is specific. What is modern about this, technically. Compared to what. What are the trade-offs of that modernity. Which of my current problems does that specifically solve, and which does it not.

Vendors who can answer these questions cleanly are describing real technology. Vendors who can't are using the word as decoration.

Strategy and Advisory work at Nu Terra Labs often includes pressure-testing vendor language before the RFP goes out.

→ Send us a message to book an intro call.

Your AI vendor uses AI vendors of their own. Their governance choices become your exposure.This is one of the least-disc...
08/26/2026

Your AI vendor uses AI vendors of their own. Their governance choices become your exposure.

This is one of the least-discussed dimensions of enterprise AI risk. The AI product you bought from a vendor is often built on top of foundation models from another vendor, which are built on top of infrastructure from a third vendor, which use data pipelines from a fourth. Each layer makes its own governance decisions. The decisions compound.

If any layer in that chain has weak data handling, poor incident response, or opaque training practices, your organisation inherits that exposure. Not through direct choice. Through the vendor's supply chain, which you signed up for implicitly when you signed the contract.

The teams handling this well have started asking their AI vendors specific questions. Who are your upstream AI providers. What governance commitments do they make to you. What happens to your governance posture if one of them changes their terms. Can you name the sub-processors that touch your customers' data.

Most vendors are not used to answering these questions yet. That's exactly why asking them matters. The vendors who take the questions seriously are the ones building the operational discipline your governance program will eventually need to rely on.

Nu Terra Labs' TrustFRAME work includes supply chain questions in vendor evaluation frameworks.

→ Send us a message to book an intro call.

The all-hands was engaging. The slides were good. The Q&A was thoughtful. The next day, nobody on the team could name a ...
08/26/2026

The all-hands was engaging. The slides were good. The Q&A was thoughtful. The next day, nobody on the team could name a single decision that had been made.

This is a failure mode that leadership teams often miss because everyone left the room feeling good. The presentation was well-received. The energy was positive. The messaging landed. But information transmitted is not the same as commitment made, and most all-hands meetings are optimised for the first, not the second.

The problem is that people at the meeting mistook a briefing for a decision-making forum. The CEO shared the strategy. The team nodded. Nothing was actually decided, because the all-hands wasn't the venue where that would happen. But the appearance of consensus creates the impression that alignment exists, when in fact the harder conversations are still queued.

The teams that use all-hands well have clarity about what the meeting is for. Sharing decisions that have already been made. Building shared understanding of the direction. Answering real questions. What they don't do is treat it as a strategy session. Strategy happens in smaller rooms, with the people who actually own the decisions, before the all-hands ever happens.

If your team's next all-hands has "align on strategy" on the agenda, that's usually the tell. Alignment on strategy is not an all-hands artifact.

→ Send us a message to book an intro call.

Most board members don't know what to ask about AI. Not because they're not smart. Because nobody has given them the que...
08/25/2026

Most board members don't know what to ask about AI. Not because they're not smart. Because nobody has given them the questions.

This isn't a knock on directors. Board members are expected to be broadly competent across a lot of topics, and AI has moved faster than any of the standard governance frameworks were designed to handle. The questions a board would ask about cybersecurity, financial controls, or regulatory compliance have decades of muscle memory behind them. AI doesn't yet.

The result is board conversations where the executive team presents a slide, the directors nod, and the discussion moves on. The oversight is nominal. If something goes wrong later, the board's exposure is real, but the mechanism for catching problems earlier wasn't in place.

The fix is straightforward. Give the board a short list of questions to ask about AI. Not technical questions. Governance questions. What use cases are running. Who owns them. What's been retired and why. What incidents have happened and what changed as a result. What the team's exposure looks like in the next quarter's customer questionnaires. What the plan is if a regulator publishes new guidance.

Ten questions. Written down. Reviewed at every board meeting. That's the difference between nominal oversight and real oversight.

Nu Terra Labs' TrustFRAME work includes drafting board question packs for organisations that don't have them.

→ Send us a message to book an intro call.

"Best practices" is one of the most quietly misleading phrases in enterprise software conversations. It sounds like univ...
08/25/2026

"Best practices" is one of the most quietly misleading phrases in enterprise software conversations. It sounds like universal wisdom. It usually isn't.

A "best practice" is the answer that emerged from someone else's context. That context includes the specific market they were in, the specific customer they were serving, the specific team they had, the specific technology stack they inherited, and the specific set of trade-offs they were willing to make. The practice worked in that context, at that time.

Whether it will work in yours is a different question. Sometimes the answer is yes. Often the answer is "close, but adjusted for these differences." Sometimes the answer is that the practice is actively wrong for your situation, and following it would produce worse outcomes than a first-principles approach.

The problem is that "best practice" language obscures the context that produced it. The team adopts it as canon, and stops asking whether the context matches. Two years later, the practice is entrenched, the results are worse than expected, and nobody remembers why the practice was adopted in the first place.

The teams that handle this well treat "best practice" as a starting hypothesis. What context did this produce it. Does our context match. If not, what would we adjust.

That kind of context-first thinking is what Nu Terra Labs' Strategy and Advisory engagements produce. Not more best practices. The right ones for the situation you're in.

→ Send us a message to book an intro call.

Every human on your team has a job description. The AI system that reviews half of their work probably doesn't.This is a...
08/24/2026

Every human on your team has a job description. The AI system that reviews half of their work probably doesn't.

This is a governance gap in one line. If a human employee were making the decisions the AI is making, that human would have a defined scope of authority, a documented set of responsibilities, a manager, and a performance review. The AI has none of these, and nobody thinks it's strange.

The reason is historical. Software systems didn't need job descriptions because they didn't make judgment calls. They executed rules. The rules were the job description. AI systems make judgment calls that look more like human decisions than like rule ex*****on, and the governance scaffolding hasn't caught up.

The teams that are ahead on this are writing AI system charters that look like job descriptions. What decisions this system is authorised to make. What decisions it escalates. What "good performance" looks like. Who reviews its outputs. Who is accountable when it gets a decision wrong. How it will be evaluated in ninety days, six months, and a year.

The charter is not heavy. Two pages, maybe three. It's also the artifact that makes it possible to answer any question a regulator, customer, or auditor might ask about the system's role in the organisation.

Nu Terra Labs' TrustFRAME work includes drafting these charters.

→ Send us a message to book an intro call.

The senior hire you brought in never actually became senior.The pattern is common enough to be worth naming. A leadershi...
08/24/2026

The senior hire you brought in never actually became senior.

The pattern is common enough to be worth naming. A leadership team hires someone with a big title, from a bigger company, at a compensation number that reflects the scope they used to operate at. Twelve months in, the new hire is executing work that a person one level below could have done, is spending most of their week on tactical items, and is starting to look for the next role because "this wasn't what I was hired to do."

The failure isn't the hire. It's that the role stayed the same size as the person who left it, or the same size the team knew how to define.

Senior talent needs senior scope. If the organisation doesn't have work sized to that scope, the hire will produce mid-level output, get bored, and leave. The compensation was for the person's ceiling. The work was for their floor.

The teams that get senior hires right define the scope before the hire, not after. What decisions this person will own. What the first ninety days looks like. What "success" produces at twelve months that the organisation couldn't have produced without them.

If those questions can't be answered before the offer letter goes out, the hire is a leadership signal, not a leadership decision. Both are legitimate. They aren't the same thing.

That kind of role sizing is often the first work of a Strategy and Advisory engagement.

→ Send us a message to book an intro call.

Address

Edmonton, AB

Opening Hours

Monday 9am - 5pm
Tuesday 9am - 5pm
Wednesday 9am - 5pm
Thursday 9am - 5pm
Friday 9am - 5pm

Telephone

+15877150179

Website

Alerts

Be the first to know and let us send you an email when Nu Terra Labs posts news and promotions. Your email address will not be used for any other purpose, and you can unsubscribe at any time.

Contact The Business

Send a message to Nu Terra Labs:

Shortcuts

Share

Category