The site, the CRM, and search should be one system
Written by AERVIO, a Montreal studio. Human-reviewed before publish. Contact: hello@aervio.io · +1 438-498-3913.
Most briefs we see in Montreal are not a “website problem.” They are a split brain. Marketing bought a theme. Sales lives in a spreadsheet or a bloated SaaS nobody updates. Search is a PDF audit from 2023. Each vendor is locally correct and globally wrong: the form dumps to email, the pipeline has stages the site never mentioned, and Google has nothing quotable to lift into a Map pack or an AI answer.
AERVIO’s job is narrower than an “agency of record.” We ship the site, the pipeline, and SEO/GEO so they describe the same company. When you also need the desk — Hands-off IT, an IT bench, a 365 / Azure workplace — it sits next to that product, not in a separate stack with a different story.
The failure mode we keep walking into
A typical week-one call looks like this. The homepage says “solutions for enterprises.” The CRM stages are Lead / Qualified / Proposal / Won — copied from a template. The Google Business Profile categories were guessed by whoever had the login. The contact form emails three people and dies in Promotions.
None of that is a talent problem. It is a system boundary problem. Three tools, three owners, no shared objects:
- The offer (what you actually sell, in the words a buyer uses)
- The object that moves (a lead, a job, a patient, a shipment — not a generic “contact”)
- The place that object is allowed to live (CRM field, not a Slack screenshot)
If those three are not named the same way on the site, in the CRM, and on the pages we want cited, you will keep paying for “more content” and “more ads” that feed a hole.
What “one system” means in practice
It does not mean one vendor logo on a slide. It means one sequence we can point at:
- A person in Montreal, Laval, or elsewhere in Canada finds a page that states a complete offer — service, geography, language.
- They send a form that creates a record with fields a human can work, not a 40-column import.
- Someone answers in Montreal hours (weekdays, 9–17 ET), not a chatbot that promises a recap.
- Search — Google, Maps, and AI answers — can quote a sentence that is still true after the call.
We write that sequence down before we pick Next.js or WordPress. The CMS is a consequence.
Why three vendors almost never converge
Agencies optimise for the artefact they invoice. A web shop ships pages. A CRM partner ships workflows. An SEO retainer ships tickets in a portal. Each artefact can look finished and still refuse to talk.
The tells we use in discovery:
- The site CTA is “Get a quote” and the CRM has no Quote object.
- Blog posts target keywords the sales team has never heard on a call.
- French exists as a plugin language pack, not as fields an editor can ship under Bill 96.
- “Lead source” is a UTM soup, so nobody can say whether Maps, a partner, or a PDF drove the last ten deals.
Fixing one artefact in isolation feels productive. It rarely moves revenue.
The objects we actually model
We do not start with personas on a whiteboard. We start with the noun the business already uses.
| Business | Object that must survive the hand-off | What usually gets modelled instead |
|---|---|---|
| A professional services firm in Montreal | An engagement with a named buyer and a language | A “marketing qualified lead” |
| A service-area trade | A job with a city, a window, and a crew | A contact in Mailchimp |
| A B2B product | An account plus a champion, not a lone email | A demo request with no company |
| A clinic or regulated shop | A request that Law 25 can actually govern | A Typeform dump in a shared inbox |
If we cannot name the object in one sentence, we do not build the form yet. That sounds slow. It is cheaper than rebuilding the CRM in month four.
Search is not a layer you paint on later
SEO and GEO in Montreal are not a blog calendar. They are whether the offer is a complete sentence on a URL that Google and AI systems can cite.
Google’s own guidance on creating helpful content is blunt: who wrote it, how, and why. A theme with lorem and a stock skyline fails that test. So does a “web development Montreal” page that never says who answers the phone.
GEO — generative engine optimization — is the same pages, written so a model can lift a self-contained claim: hours, language, what we will not do (rented lists, fake map pins), how a project starts. We do not write a second site “for ChatGPT.” We write pages a human would quote on a call.
What we refuse to fake
Montreal local SEO still weights Google Business Profile, reviews, and proximity. We do not invent a street pin we do not occupy. AERVIO is a service-area studio: Montreal is the hub, Canada is the area served. NAP stays consistent — AERVIO, Montreal, QC, hello@aervio.io, +1 438-498-3913. If you have a storefront, we treat GBP as an operational surface, not a ranking trick. That stance is in our Montreal page on purpose.
We also do not blast rented lists. First touches are written by a person. That is a CASL and a trust issue, not a vibe.
How a project is actually sequenced
Discovery is a call, not a 40-page RFP. We want the last ten real enquiries, the current CRM (even if it is Excel), and who is allowed to publish French.
Then a written proposal: scope, timeline, what stays yours. Typical first slice is not “rebrand + app + SEO empire.” It is:
- One offer page that sales will recognise
- A form that creates the right object
- Technical hygiene so the page can be indexed (and, where it applies, French-first)
Retainers exist for the second slice: measure which queries convert, ship the next page, keep backups you can restore. The stack stays yours. We are not a hostage CMS.
Where IT belongs in this picture
A beautiful Next.js site on a tenant nobody can recover is not a system. If there is no internal hire, Hands-off IT is the desk: tickets, devices, backups. If you already have admins, the IT bench takes overflow and nights — they keep the keys. 365 / Azure is the office the site and CRM already live in. We do not sell those as a four-logo hub. They are how the product keeps running after launch.
What “done” looks like
You can answer four questions without opening three tools:
- What do we sell, in the buyer’s words, on a URL?
- Where does a new enquiry live, and who owns the next step?
- What would Google or an AI answer quote tomorrow morning?
- Who do we call at 10:00 ET if the form stops posting?
If you cannot answer those, you do not have a digital presence. You have files. Services is the catalogue; this article is the reason the catalogue is one list.
A week-one workshop we actually run
Ninety minutes, not a two-day offsite. In the room (or on a call in ET): whoever answers the phone, whoever owns the CRM login, and whoever can publish a sentence on the site. We bring the last ten form submissions, exported, with names redacted if you want.
The agenda is rude on purpose:
- Read three submissions out loud. If nobody can say what the person wanted, the form is wrong.
- Open the CRM on the same three. If they are not there, the hand-off is wrong.
- Search the company name + city in an incognito window. If the snippet is a ThemeForest sentence, search is wrong.
- Ask who publishes French. If the answer is “a freelancer sometimes,” Bill 96 is not a CMS ticket later. It is a people ticket now.
We leave with a one-page sequence, not a mural of sticky notes. The proposal quotes that page.
How we know the system is lying
Dashboards lie politely. These tells do not:
- Ten “MQLs” this week and zero calendar events
- A blog that ranks for a tool name you do not sell
- Salesforce full of companies with no phone and a website field that 404s
- Google Business Profile hours that do not match the footer
- A French URL whose English twin has a different offer (not a different emphasis — a different product)
When we see two of those, we stop adding content. Content on a lying system is how you teach Google the wrong company.
Language is an object too
English vs French is not a toggle on a hero. It is a field on the offer, the CRM record, and the support path. A bilingual homepage with a monolingual pipeline produces English follow-ups to `bonjour` forms. That is both rude and, for some Quebec public surfaces, reckless.
We store language on the lead. We publish equivalent URLs, not a widget. We put hours and +1 438-498-3913 on both doors. Details: French-first CMS and the French article.
What we need attached to the first email
Not a brand book. Attach:
- The current homepage URL and the CMS login situation (who has it)
- A CSV or screenshot of the pipeline stages you actually use
- Search Console access or a screenshot of the last 28 days of queries
- Whether anyone has restored a backup this year (yes/no is enough)
That package lets us write a proposal that does not invent a discovery phase you already paid someone else for. hello@aervio.io.
Questions
Do we have to rebuild everything at once?
No. We usually fix the hand-off first: form to pipeline, then the pages Google and AI answers can actually cite. The stack stays yours between those steps.
Can you work with Salesforce or HubSpot we already pay for?
Yes. We do not rip a CRM that the team already lives in. We connect the site and the search pages to it, and only build a custom desk when the SaaS is the bottleneck.
Is this only for Montreal?
We work from Montreal, including French-first public pages where Bill 96 applies, and we ship for companies across Canada. Hours are weekdays 9–17 ET.
Let's write the next step.
