Nerds On Site - Edmonton/Red Deer

06/12/2026

You know what's wild? We've gotten so obsessed with automating everything that we forgot the actual bottleneck in most businesses isn't the tools, it's the people using them.

I was chatting with a shop owner recently who spent three grand on this fancy AI page generator for his Shopify store. Beautiful tool, honestly. Generates product pages in minutes, pulls winning products from ad libraries, spits out Facebook copy. All the bells and whistles.

But here's what actually happened. He generated like five pages, imported them, and then... nothing. They just sat there. Why? Because he didn't have a testing framework in place. No idea what metrics actually mattered. No system for iterating based on results.

The tool wasn't the problem. His workflow was.

This keeps happening in businesses across the board. We throw automation at a process and expect magic to happen. But if the underlying process is messy or unclear, you're just automating mess faster.

Before you invest in the next shiny AI thing, ask yourself this. Do I actually understand my current workflow well enough to improve it? Can I clearly define what success looks like? Do I have the team structure to act on what the tool generates?

Automation amplifies what you're already doing. If that's chaos, you're just getting chaos at scale.

What process are you thinking about automating right now? Have you mapped out what you're actually trying to solve?

06/11/2026

Chrome just quietly made vertical tabs a thing and I'm honestly surprised more people aren't talking about it. 🤔

Look, I know tabs seem like a small UI thing. But if you're someone who works with 15+ tabs open (and let's be real, who isn't these days?), the difference between horizontal and vertical is actually pretty significant.

Vertical tabs give you way more real estate to see what you're actually looking at. Instead of squinting at "Untitled, 1" across 20 compressed tabs, you get readable tab names stacked on the side. It's a small change that genuinely impacts how fast you can navigate.

The setup takes about 30 seconds if you know where to look. For anyone drowning in browser tabs, this might be one of those "why didn't I do this sooner" moments.

If you're curious how to flip it on, Google's got the walkthrough. But honestly, the bigger question is why this isn't the default already.

Are you a tab hoarder? Have you switched to vertical yet or does the horizontal setup still work for you?

Want to enable vertical tabs in Google Chrome? In this quick and ea...

06/10/2026

Most small business owners pick a phone system and just... stick with it. Even when it's clearly not working anymore.

I get it. Switching feels like a hassle. You've got your number set up, your voicemail configured, and changing feels like friction you don't need right now. But here's what I've noticed: a lot of founders are still using systems that were designed five years ago, with interfaces that feel clunky, support that's slow, and features that don't actually help them grow.

Callture does the basics. Call forwarding, voicemail, online logs. But "basic" works until it doesn't. You take more calls. You bring on a team member. You want call recording or better integrations. Suddenly you're frustrated because the system can't keep up.

The thing is, there are solid alternatives out there right now that cost about the same (or less) but actually feel modern and don't make you want to throw your phone across the room. Clean setup, real support when you need it, and features that actually scale with you instead of against you.

If your current phone system is making you feel like you're working around it instead of with it, that's worth fixing sooner rather than later. Your business probably deserves better.

What's your biggest frustration with your current phone system? Is it the interface, the support, or just that it's missing features you actually need?

Looking for the best Callture alternative in 2026? Here are 10 better options for startups and small business owners we tried and tested.

06/09/2026

Most small business owners are still overpaying for their phone system. They're stuck with these enterprise platforms that have way too many features they'll never use, confusing pricing that keeps adding up, and support that feels like you're talking to a robot.

The thing is, you don't need all that complexity. You need a phone system that takes 15 minutes to set up, costs what it says it costs, and actually works when you need it to work.

I've watched so many founders waste time and money trying to force themselves into platforms built for companies 100x their size. It's like buying a semi truck when you just need a sedan.

The better play? Pick something built for where you actually are right now. Something that scales with you as you grow, not something that forces you to rebuild everything when you hire your first employee.

What's your current phone system like? Is it doing the job, or are you paying for stuff you don't even touch? 🤔

06/08/2026

Agentic AI is coming to IT service management, and honestly, it's not what most teams think it is.

I've been reading up on how ITSM is shifting in 2026, and the difference between a "copilot" that suggests actions and actual agentic AI that executes them is massive. We're talking about AI that handles password resets, access provisioning, and incident triage on its own, within guardrails you set.

Here's what gets me: most organizations are still treating AI in ITSM like it's a nice, to, have feature. But the teams that are actually deploying agentic AI properly are cutting manual effort on repetitive, structured tasks and freeing their people up for work that actually requires judgment.

The catch? Governance. You can't just flip a switch and let AI loose. Organizations that align AI initiatives with actual governance and operating models scale effectively. The ones that don't? They end up with chaos.

If you're an IT manager or running a service desk, ask yourself: Are your repetitive tasks structured enough for automation, and do you have the governance framework ready to deploy it safely?

What's your team's experience been with AI in service management so far?

Exploring how AI-driven automation, hyper-personalized service experiences, and resilient digital operations are reshaping IT service management for a faster, smarter, and more human-centered enterprise in 2026.

06/07/2026

Most companies I talk to are stuck in analysis paralysis when it comes to software solutions. They're trying to decide between buying something off the shelf or building custom, and they're treating it like there's a magic answer.

There isn't.

I've watched teams waste months comparing spreadsheets and vendor demos when they should've been asking completely different questions. Like, what's your actual timeline? Can your team maintain this long term? Do you have the budget for the unexpected headaches that come with either path?

Buying something ready made feels safe until you realize it doesn't quite fit your workflow. Building custom feels empowering until you realize you've got a 18 month project and you're still debugging. Both have real tradeoffs that people gloss over.

Here's what actually matters. Start with your constraints, not the tools. If you've got tight deadlines and limited engineering resources, buying probably wins. If you've got specific workflows that nothing off the shelf handles, building might be your only real option. If you're somewhere in the middle, honestly, that's where it gets interesting because you can actually evaluate both without pretending one is obviously better.

The companies doing this well aren't choosing buy or build. They're choosing based on what they can actually execute well. That's the real conversation to have with your team.

What's blocking your team right now? Are you trying to decide between these options, or are you stuck with something that's not working?

06/06/2026

Most teams write requirements and then act surprised when the solution doesn't actually work for people.

They'll specify that something needs to be "fast" or "easy to use" without ever defining what that actually means. Fast to who? Easy compared to what? Then six months in, they're frustrated because the solution technically meets the requirements but nobody wants to use it.

This is where non, functional requirements come in. Not the features themselves, but all the stuff that makes those features actually functional in the real world. Performance targets. Security standards. How many users it needs to handle at once. Whether it plays nice with other systems already in place. How quickly it needs to recover if something breaks.

The boring stuff, basically. Except it's not boring at all because this is where projects actually succeed or fail.

I've seen teams skip this step because it feels tedious. They want to jump straight to building. But when you nail down these requirements upfront, you save yourself months of rework and frustrated conversations later. Your architects know what they're building toward. Your team knows what success actually looks like. Your stakeholders get a system that doesn't just work technically but works for the people using it every day.

The real question isn't whether you need non, functional requirements. It's whether you want to figure them out now or deal with them as expensive problems later.

What's one thing you wish had been defined more clearly on a project you've worked on? Drop it below.

06/05/2026

I've been talking with IT teams lately who are getting blindsided by AI infrastructure costs. They budgeted for cloud, scaled up for AI workloads, and now they're staring at 30% cost overruns they didn't see coming.

There's a reason for this. IDC's FutureScape report flagged something that's actually happening right now: by 2027, G1000 organizations will face up to a 30% rise in underestimated AI infrastructure costs. That's not a projection. That's a warning.

The problem isn't the AI itself. It's the unpredictable consumption patterns. GPUs, storage, networking, data pipelines, they all consume differently when you're running real AI workloads versus testing. Most teams don't have visibility into where the money's actually going until the bill lands.

Here's what separates teams that survive this from teams that panic: They treat cost management as a continuous operational discipline, not a quarterly review. Real, time resource optimization. Tracking actual usage patterns instead of peak outliers. Understanding which workloads actually deliver business value versus which ones are just running up the meter.

The infrastructure you're building today for AI? It needs governance built in from day one. Not bolted on later when the CFO is asking questions.

Are you seeing this cost creep in your environment? What's your biggest blind spot with AI infrastructure spend right now?

https://www.techrepublic.com/article/enterprise, it, infrastructure, trends, 2026/

Enterprise I&O in 2026: Seven trends reshaping hybrid strategy, AI costs, observability, resilience, and zero-trust security.

06/04/2026

Most businesses are still treating SIP trunking like it's some complicated telecom mystery that only specialists can handle. Spoiler alert: it's not.

I've been looking at what's actually happening with Cisco CUBE deployments right now, and the friction point isn't the technology anymore. It's finding a provider that doesn't nickel and dime you while actually delivering reliable service.

Here's what matters when you're evaluating SIP providers for CUBE:

1. Actual reliability matters. Nearly 100% uptime isn't a flex, it's table stakes. Your calls need to work consistently.

2. Transparent pricing beats everything else. No setup fees, no porting fees, no cancellation fees. Month to month means you're not locked in if things change.

3. Seamless integration saves you hours of headaches. If your provider has solid provisioning guides and actually responds when you need help, that's worth real money.

4. Support that's actually in your timezone and speaks your language. U.S. based support matters more than people realize when something breaks at 2 PM on a Tuesday.

5. Scalability that doesn't require renegotiating contracts. You should be able to add lines or adjust without friction.

The gap between expensive legacy providers and the newer breed that actually understands modern business communications is getting wider. If you're still working with someone charging you for every little add on, you're probably overpaying.

Who's actually running CUBE in production right now? What's your experience been with SIP providers? Drop your real talk below.

Looking for a cheap but reliable SIP trunk provider for Cisco CUBE? See why Unitel Voice SIP is the best choice based on price & service.

06/03/2026

The panic around AI replacing workers is overblown, and honestly, we've seen this movie before.

Every major technology shift triggers the same doomsday narrative. When ATMs rolled out in the 80s, everyone said bank tellers were done for. Spoiler alert, they weren't. The jobs shifted, the skills required changed, but the workforce adapted. Same thing happened with the web. Same thing will happen with AI.

Here's what's actually happening right now, and it's way more interesting than the job apocalypse storyline. We're in a massive skills realignment. ML scientists, data product folks, and business leaders who actually know how to apply AI are commanding premium compensation. That's real. But that's also temporary market inefficiency.

The real opportunity isn't in panic or hype. It's in recognizing that soft skills are about to matter more than ever. Adaptability, problem solving, emotional intelligence, curiosity, the stuff machines still can't replicate at scale. The professionals who double down on those while staying current with AI fundamentals? They're going to thrive regardless of what industry they're in.

Lifelong learning isn't some corporate buzzword anymore. It's table stakes. The question isn't whether your job survives automation. It's whether you're willing to evolve faster than the technology.

What skills are you actually investing in right now? Not just tech skills, but the human stuff that keeps you relevant when tools change every 18 months?