You and your team understand the business. You just don't have the time to step back and fix what's slowing it down. I do that with you - not instead of you.
I'm not an IT consultant. I'm an operations person who learned systems to make businesses run better. Most IT people understand the system but not the business. Most operators understand the business but avoid the system. I bridge that gap.
I don't send long questionnaires or ask you to fill out forms. If you had time for that, you wouldn't need me. I get what I need by being in the business, talking to your team, and seeing how the work actually happens.
I spend time with the people doing the work, understand where things are frustrating, and fix those issues first. No blame. No disruption. Just making their jobs easier while improving how the business runs.
I look for bottlenecks, roadblocks, unnecessary steps, and manual work that shouldn't exist. Then I remove them using a mix of process changes and system improvements - especially NetSuite.
I don't separate learning from execution. I get up to speed by working directly in the operation and focusing on the highest-impact issues right away, so there's visible progress early on.
I'm an operator, not a consultant. Before Clearpath I trained in logistics at IKEA and spent more than a decade running distribution, e-commerce, and a NetSuite rollout at Unicon Concrete Specialties in Edmonton. I fix how a business actually runs, with the customer at the center of it.
"He consistently sought out opportunities to refine processes, streamline workflows, and position the business for future growth."
Brett Desroches, Owner & CEO, Unicon Concrete Specialties
The problem isn't that your systems don't technically work. It's that they don't work together.
On NetSuite specifically, I'm comfortable across workflows, saved searches and reporting, custom fields, records and forms, process design and system alignment, and SuiteScript - knowing where it adds value vs. where it adds unnecessary complexity.
The goal is simple: make your systems support how your business actually runs, not the other way around.
Answer four quick questions. No email required, no homework. You'll get a straight recommendation on where to start - and you can send the result to yourself if you want it for later.
Every engagement starts by finding the highest-impact issue, then fixing it fast. We build from there.
Some clients want full independence. Others want me in their corner as things evolve. This isn't just system support - it includes both operational and system-level improvements.
Every engagement includes a custom-trained AI assistant built from your actual workflows, scripts, and system logic. When I leave, your team has a tool they can ask questions to in plain language and get answers specific to how your business actually runs.
New hire training. Day-to-day troubleshooting. Process questions. Handled without calling me back. This isn't a bonus - it's baked into every engagement from day one.
A bad NetSuite implementation costs more to fix than it did to build. The people selling it don't get paid to tell you that.
Your implementer builds the system. I'm the operator on your side of the table making sure they build the right one, and that your team can actually use it when it's done. I'm not here to replace them. I'm the one who knows how your business really runs, which is exactly what they don't.
NetSuite's implementation team knows the system. They don't know how your warehouse actually runs, how your team processes orders, or where your real bottlenecks are. Nobody on that call has ever done your job.
By the time you're in implementation, the contract is signed. There's no incentive to slow down and make sure the configuration actually fits your business. Speed to launch is the goal. Fit comes later - if at all.
Unless someone pushes back, you get a standard setup with standard workflows. Your business isn't standard. The gap between what they build and what you actually need is where the problems live for the next two years.
NetSuite is complex enough that most teams don't know what they should have asked for until they've been running it for six months and something breaks - or they realize a report they assumed existed doesn't.
NetSuite makes money on what you license. Without someone who knows your operation in the room, it's easy to get talked into modules and add-ons you won't use. I help you buy only what fits how you actually run - which can save thousands over the initial contract term alone.
I spend time in your business understanding how work actually moves - orders, fulfillment, purchasing, finance - before a single field gets configured. The system gets built around your operation, not the other way around.
I'm not trying to close a deal. If a default NetSuite approach doesn't match how you run, I say so and we find a configuration that does. You get the version of NetSuite that works for your business.
Roles, permissions, layouts, saved searches, and workflows are set up for the people doing the work - not for a generic user in a demo environment. Your team walks in on day one knowing where things are.
Every configuration decision gets documented. Why a field exists, how a workflow triggers, what a saved search is for. Combined with the AI knowledge base, your team isn't dependent on me or on NetSuite support to answer basic questions.
The worst NetSuite problems are the ones that get normalized. A broken workflow that everyone works around becomes invisible after six months. I catch those during implementation - when they're cheap to fix - instead of after go-live when they're not.
Before I quote, I spend a couple of days in your operation doing my own legwork. Nothing for you to fill out, no charge to find out. Then a fixed price, paid by milestone, no surprises.
Talk About Your MigrationI'm an operations person who fixes the daily friction slowing a business down, especially around NetSuite, workflows, and repetitive admin that shouldn't exist. I'm not an IT consultant. Most IT people know the system but not the business, and most operators know the business but avoid the system. I work in the gap between the two.
Yes, because it's a different job. Your implementer builds the system. I'm the operator on your side making sure they build it around how your business actually runs, and that your team can use it on day one. I'm not there to replace your implementer. I'm the person in the room who knows your operation, which is the thing they don't.
It depends on the work. A one-time fix, like cleaning up roles and permissions, is scoped small and priced to match. Bigger engagements are quoted around where your business is today, where you want to get to, and the return you would expect from getting there, using your own numbers. Everything is fixed price, milestone-based, and you pay as each piece is done. No hourly billing and no invoices for time.
No. No questionnaires, no homework, and no paid discovery step before you get a quote. I learn how your business works by being in it and talking to your team, then I give you a fixed price.
Both. On a live system, the common fixes are roles and permissions, reports and saved searches your team can't build, broken or missing workflows, and getting people to actually use the system instead of working around it. On a migration, I make sure it gets built right the first time.
Edmonton, and I work with businesses across Alberta. For this kind of work, being on site matters, so I stay local for the core engagement. Ongoing support after that can be remote.
15-minute call. No prep required. We find the biggest friction point and talk through how fast we can fix it.
Fix It This Week →