Key Takeaways:
- The most consequential decision in a CRM implementation in Vancouver is what an opportunity record represents — a customer, a financing, a project, or a renewal — because reporting, security, automation, and forecasting all build on top of it.
- Four assumptions baked into every default CRM break against Vancouver's economy: that the other party is a buyer, that both sides share a working week, that the account continues after the sale, and that deal value is known at qualification.
- From 1 October 2026, BC applies 7% PST to accounting, architectural, engineering, geoscience, security, and non-residential real estate services; engineering and geoscience fees are taxed on 30% of the purchase price, so $100,000 of work carries $2,100 in PST.
- BC has no HST, so a Vancouver CRM handles two taxes (7% PST and 5% GST) under separate rules — the tax configuration belongs in phase one, next to the pipeline.
- On the Power Platform, custom entities for financings, projects, or shareholder registers are built as configuration, not custom code — so there's no application to maintain underneath them.
- Head-term search volume for these queries is tiny; the value of getting this page right is being the clear, expert answer for the businesses that do search, and being citable when AI assistants summarize "how CRM implementation works in Vancouver."
Most CRM projects are won or lost on a single decision made in the first week: what an opportunity record actually represents. For a large share of Vancouver's economy, the answer isn't "a potential sale," and a CRM implementation in Vancouver that assumes otherwise ends up as an administrative chore the sales team quietly works around. An exploration company raises capital where the software expects purchases. A consultancy delivers discrete projects where the software expects ongoing accounts. An exporter runs cycles across a sixteen-hour offset where the software expects a shared working week.
There's also a date on the calendar forcing the question sooner than most firms planned. From 1 October 2026, British Columbia charges 7% PST on accounting, architectural, engineering, geoscience, security, and non-residential property services — where legal work was previously the only professional service the tax caught. Quote templates, price lists, opportunity values, and invoice layouts all have to carry that correctly from the first affected invoice. This guide covers both: how to shape a CRM around the way your business actually earns revenue, and what the PST change specifically asks of the system. If you already know you want to compare providers, our ranking of CRM consultants in Vancouver covers the firms serving British Columbia.
Tell Us How You Make Money
Gestisoft configures Dynamics 365 around the way your business earns revenue.
Free discovery call
What CRM implementation actually means for a Vancouver business
CRM implementation is the work of configuring customer relationship management software to match how a business sells, migrating its existing data, connecting it to the tools the team already uses, and training people to work in it. The licence is the smallest part. The implementation is the discovery, configuration, migration, and adoption work that turns a blank platform into something people open every day.
For a Vancouver business, one question sits above all the others in that process: what are you actually trying to win? A standard CRM answers "a sale." But if the thing you pursue is a financing round, a project award, or a grant, then the record the whole system is built around — the opportunity — has to be redefined before anything else is configured. Get that right and everything downstream fits. Get it wrong and you discover in month five that your "opportunity" should have been a "project," and you pay for the original build and its replacement.
Why the standard CRM data model struggles in Vancouver
Every CRM ships with a data model describing an assumed business. Accounts are companies you sell to. Contacts are people who work at those companies. Opportunities are potential purchases with a value and a close date. That model came out of enterprise software sales, and it fits businesses that resemble enterprise software sales. A large share of this city does something else — British Columbia's Mineral Development Office counts more than 800 exploration and mining companies headquartered in Vancouver alone, and for a junior explorer the function that resembles sales is investor relations and the function that resembles a pipeline is financing.
Four assumptions inside the default model break against the way this city earns money:
- The other party is a buyer. This fails the moment your pipeline holds investors, donors, or grantors rather than purchasers.
- Both sides share a working week. This fails across a sixteen-hour offset to Tokyo or Seoul, where follow-up has to be timed to the recipient's business hours, not yours.
- The account continues after the sale. This fails in project work, where the budget holder changes with each engagement and there is no ongoing account to nurture.
- Deal value is known at qualification. This fails in exploration financing and in competitive bidding, where the number isn't real until late.
Ignore the mismatch and the sales team maintains the CRM as busywork while keeping the information it actually relies on somewhere else. The cheapest hour in the whole project is spent comparing your real revenue model against what a CRM assumes — reviewing examples of CRM systems against your own operation before you shortlist anything.
What the October 2026 PST change asks of your CRM
British Columbia has no HST, so any CRM implementation in Vancouver already handles two taxes: a 7% provincial sales tax and a 5% federal GST, running under separate rules. What changed is the reach of the provincial one. As of 1 October 2026, a large slice of the professional services economy — accounting, architectural, engineering, geoscience, security, and non-residential property services — collects PST for the first time. Firms selling any of those services register and collect, and registration opened six months ahead of the date.
The detail that trips up a naïve configuration is the partial base. PST on engineering and geoscience services applies at 7% to an amount equal to 30% of the purchase price — so a firm selling $100,000 of taxable work charges $2,100, not $7,000. Disbursements form part of the purchase price. A tax field that holds a single flat percentage produces the wrong number every time, and a sales dashboard built on those values carries the error straight through to the board pack.
Five pieces of configuration carry the change into the system correctly, and they remain good practice long after the deadline passes:
- Separate product and service tax categories, so taxable work, exempt portions, and pass-through disbursements calculate independently on the same quote.
- Quote and invoice templates that show the partial base plainly — a client seeing an effective 2.1% on an engineering line will ask where it came from, and the template should answer before they call.
- Opportunity values that hold the fee and the tax as separate figures, so forecasting reports on revenue rather than gross billings.
- Transitional handling for work performed before 1 October but invoiced afterward, which follows when the service was performed.
- A fiscal position that remaps tax by the customer's location, since out-of-province and exempt clients follow different rules.
The firms that treated this seriously registered in the spring and tested the calculation on sample invoices months ago. Anyone starting now has less room, which is why the tax configuration belongs in phase one of the build, beside the pipeline itself rather than bolted on at the end.
Get the tax configuration right before the first invoice
If your firm becomes PST-taxable in October, the quote template and tax categories have to be right from day one. Gestisoft can settle that during discovery.
Book a free consultation
What to settle before a CRM implementation in Vancouver starts
An hour spent answering these internally decides whether the build fits the business paying for it. A partner who raises them unprompted has done this before:
- What are you trying to win — a customer, a financing, a project, or a renewal? Each needs a different opportunity record underneath it.
- Who sits on the other side — a buyer, an investor, a procurement officer, a repeat client? Each needs a different contact record.
- How long a typical cycle runs, measured against last year's closed deals rather than the target, since stage durations get set from that number.
- Where the people you deal with work, because a Pacific-facing operation needs follow-up timed to the recipient's hours.
- What a normal loss rate looks like in your business — a firm that bids at volume and loses most bids is performing exactly as intended, and the CRM should be built to expect that.
- Whether any of your services become PST-taxable on 1 October, because the quote template and tax categories have to be right before the first invoice.
- Who needs to see what, since access control costs far less to build at the start than to retrofit.
Put those answers in front of a specialist at the first meeting and a product demonstration turns into a scoping conversation. This is the work a CRM implementation consultant should be doing before a platform is ever named.
A realistic timeline for a CRM implementation in Vancouver
Eight to twelve weeks covers a configuration that stays close to the platform default — discovery, configuration, migration, integration, training, and go-live for a business with a single sales process and a manageable data set. Custom entities for project tracking or investor relations push the timeline toward fourteen to eighteen weeks, and discovery absorbs most of that extra time because the modelling work is where the thinking happens.
The video below walks through the pipeline view in Dynamics 365 Sales — a useful picture of how an opportunity actually moves through stages once the model is settled and the system is live.
The walkthrough shows how a team works the pipeline view in Dynamics 365 Sales — moving records through stages, reading the forecast, and prioritising the next action. It's the day-to-day payoff of getting the opportunity model right, which is why the modelling decision in discovery matters more than any single feature.
The first weeks after go-live generate more requests than the entire build did. That's normal, not evidence something went wrong — budgeting hours for the CRM implementation challenges that surface in the first quarter is what keeps the momentum a launch creates.
How Gestisoft approaches a CRM implementation in Vancouver
Gestisoft holds Microsoft Solutions Partner status and builds on Dynamics 365 with the Power Platform, delivering to British Columbia remotely from offices in Montreal, Toronto, Ottawa, and Quebec City. Everything downstream in a build inherits one decision — what the opportunity record represents — so Gestisoft treats that as the first written deliverable of discovery, signed off before the rest of the scope gets priced against it. An exploration company arrives at a financing; an engineering consultancy lands on a project carrying a phase and a budget holder; an exporter ends up with a sale running on a longer clock than its domestic equivalent.
The Power Platform is what keeps that affordable. A financing entity holding raise structure and allocation, a project entity holding scope, phase, budget holder, and assigned team, or a shareholder register — each gets built with business process flows over the top as configuration work, billed at configuration rates. Businesses that go to a development shop for the same outcome end up owning code, and owning code means funding a maintenance line for as long as the system runs. Defining what an opportunity should be is the same discipline behind good sales opportunity management on any platform.
“It was important for us to be in control of our system. Today, we're able to make every change ourselves.”
Delivery runs remotely, with the working overlap covering the start of the Pacific morning through early afternoon — discovery sessions, configuration reviews, training, and go-live support all happen inside it, and someone travels where an operation has to be seen before it can be mapped. A dedicated Customer Success Manager picks up the account at go-live. The test worth watching is the first financing closed on the new system, or the first quarterly repeat-client report that nobody has to assemble by hand.
“With a CRM like Dynamics 365, I can easily identify where each contact is in the process and prioritize the necessary actions.”
-
CRM implementation is the work of configuring customer relationship management software to fit how a business sells, migrating existing customer data, connecting the system to other tools, and training people to use it. Buying the licence is the small part; the implementation — discovery, configuration, migration, and adoption — is what turns an empty system into one the team actually relies on.
Liked what you just read? Sharing is caring.
August 24, 2026 by Shelley Sunjka by Shelley Sunjka Copywriter & Marketing Strategist
Armed with a psychology degree and an irrational obsession with okapis, I've spent the last decade helping bold brands tell better stories. I believe the best writing bends grammar rules on purpose and makes people feel something. When I'm not deep in words or nerding out on buyer behaviour, I'm probably convincing my kids that impromptu kitchen dance parties are totally normal.


