Every AI company right now is selling you cookie-cutter products. Sign up for our platform. Watch our tutorials. Figure out how to connect it to your business. Good luck.
That model works great for the AI company. Not so great for you.
Here is the thing. A plumber in Hamilton does not run the same operation as an HVAC company in Calgary. A tree service in Niagara has completely different workflows than a field services company in Ottawa. The calls are different. The quoting is different. The scheduling is different. The customers expect different things.
So why would the AI system be the same?
It shouldn't be. And that's exactly why we built the Blueprint process.
What the Blueprint actually is
The Blueprint is a paid scoping engagement. It's the first thing we recommend for every client who comes to us wanting a custom AI system.
Before we write a single line of code or configure a single workflow, we sit down and figure out exactly how your business runs, where the gaps are, what's costing you money, and what AI can realistically fix. Then we put it all in a document that you own.
That's the Blueprint.
It's not a sales pitch dressed up as a consultation. It's real work. And it costs real money because it delivers real value.
Why it's paid
We used to do free consultations. Here's what happened: we'd spend hours mapping out someone's operation, identifying the opportunities, putting together a plan. Then they'd take it and ghost. Or they'd hand it to their nephew who "knows computers" and try to build it themselves. Or they'd just never follow through.
Paying means both sides are serious. You're serious about fixing your operation. We're serious about doing the work to scope it properly. And the fee goes toward your build anyway, so if you move forward with GlassRiver, you're not paying twice.
What you actually get
No jargon here. The Blueprint includes:
Executive summary. A plain-language overview of what we found, what we recommend, and why. You should be able to hand this to your business partner or spouse and they should understand it in five minutes.
Phased delivery roadmap. We don't dump everything on you at once. The roadmap shows what gets built first, what comes next, and why we sequenced it that way. Usually the first phase is the thing that stops the bleeding fastest.
Detailed requirements. Every workflow, every integration, every trigger, every edge case we can identify. This is the technical spec that the build team uses.
Acceptance criteria. How do you know it's working? We define that upfront. Not "it feels like it's working." Specific, measurable criteria that you can check yourself.
Full legal agreement. The SOW, the scope, the deliverables, the timeline expectations. Everything buttoned up before a single dollar moves.
How the four weeks work
Week one: Discovery. We get on a call and I ask you a lot of questions. How do you get leads? Who answers the phone? What happens when you miss a call? How do quotes work? What does your morning look like? What's the thing that drives you crazy every single day? We also look at your existing tools, your call volume, your team structure.
Week two: Mapping. We take everything from discovery and start mapping it out. Call flows, data flows, decision trees, integration points. This is where we figure out what AI can handle, what needs a human, and where the handoffs happen.
Week three: Draft review. You get the first draft of the Blueprint. We walk through it together. You tell us what we got right, what we got wrong, and what we missed. There's always something. No matter how good the discovery call is, there's always a workflow or an edge case that only comes up when you see it on paper.
Week four: Final delivery. We incorporate your feedback, finalize the document, and deliver the completed Blueprint. At this point you've got a complete picture of what your AI system looks like, what it costs to build, and how long it takes to get there.
Every Blueprint is different
Here's what I mean by that.
One HVAC company came to us needing a multi-phase system. Their after-hours alarm monitoring was a mess. Receipts were getting lost between the truck and the office. Their CRM data was unreliable because nobody was entering it consistently. The Blueprint scoped out an alarm automation system, a receipt capture engine, and an intelligence layer that would clean up their CRM data over time.
A tree service needed something completely different. They were missing calls left and right during the busy season. Their quoting process was slow because the owner had to go back to the office, sit down at a computer, and type everything up. The Blueprint focused on an AI receptionist that could answer calls, qualify leads, and transfer to the owner when available, plus a voice-to-quote system and an operations dashboard.
A field services company needed the full stack. Operations management, crew scheduling, client communications, the whole thing. Their Blueprint was the most detailed one we've ever done.
The big thing is each Blueprint was completely different because each business is completely different. Same industry, completely different operations, completely different solutions.
The Blueprint is yours
This is important. If you go through the Blueprint process and decide not to build with GlassRiver, the Blueprint is still yours. You own it. You can take it to another developer, you can use it as a spec for an internal hire, you can put it in a drawer and come back to it in six months.
We're not holding your plan hostage. We did the work, you paid for it, it's yours.
Most people do build with us because they've seen the quality of the scoping work and they trust us to execute it. But there's no lock-in. That's not how we operate.
"What if AI doesn't work for my business?"
That's actually the best reason to do the Blueprint.
Because here is the thing. Maybe AI isn't the right answer for your specific situation right now. Maybe your call volume is too low to justify an AI receptionist. Maybe your workflows are too chaotic to automate without fixing the underlying process first. Maybe the technology isn't there yet for what you need.
The Blueprint answers those questions before you spend real money on a build. If we go through the scoping process and determine that AI isn't the right play, we'll tell you that. We'd rather be honest about it than take your money and deliver something that doesn't work.
That's what the Blueprint is for. It protects you from building the wrong thing.
Voice-first, zero-login
One thing that comes up in almost every Blueprint is the question of how the owner actually interacts with the system. And our answer is always the same: you shouldn't need a laptop to run your business.
Everything we build is voice-first. Phone calls and text messages. Your morning brief shows up as a text. Your AI receptionist handles calls and texts you summaries. You dictate quotes from the truck. You get end-of-day recaps without opening an app.
If you have to log into a dashboard to get value out of the system, we've failed. That philosophy gets baked into every Blueprint from day one.
Not everyone needs the full Blueprint
I want to be straight about this. Some owners just want to start with an AI receptionist to stop missing calls. That's a real problem and it has a straightforward solution. We can do that without the full scoping process.
The Blueprint is what we recommend when you're looking at a bigger system. Multiple workflows, multiple integrations, a real operational overhaul. If you just want someone answering your phone 24/7, qualifying leads, transferring calls to you when you're available, and texting you summaries when you're not, we can get that going without a multi-week scoping engagement.
But if you're the kind of owner who looks at their operation and thinks "there has to be a better way to run all of this," the Blueprint is where we start.
Based in Windsor, built for Canadian trades
GlassRiver is based in Windsor, Ontario. We work with trades businesses and SMBs across Canada. Everything we build is compliant with PIPEDA and Canadian privacy requirements. Your data stays where it should.
We're not a Silicon Valley startup trying to figure out how contractors work. We've been in the trenches with HVAC companies, tree services, plumbers, electricians, and general contractors. We know the workflows because we've mapped dozens of them.
What's next
If you're curious about what a Blueprint would look like for your business, book a demo call. No pressure, no pitch deck. Just a conversation about your operation and whether the Blueprint makes sense for you.
And if you want to see what happens after the Blueprint, check out Beyond the Phone: What an AI Operations System Actually Looks Like. That post walks through what a complete build looks like once the scoping is done.