Skip to content

PLATFORM CHOICE

The right platform is the one your team will actually use.

Eleven years, dozens of builds across Switzerland and the Nordics. For companies our size — 50 to 200 people, ready to leave the spreadsheet mess behind — HubSpot usually wins. Not always. Here's how we decide.

HOW WE CHOOSE

Tool-agnostic in method. HubSpot-deep in practice.

We've built on HubSpot, Salesforce, Dynamics, Pipedrive, Zoho. Which one you get isn't decided in advance — it's decided in the Audit, against four questions.

1
How complex is your sales motion?

One product and a short cycle is a different problem from multi-stage deals, territories, and a partner channel. The answer rules platforms in and out faster than anything else.

2
Where does your team already live — Microsoft, Google, mixed?

People don't adopt a tool that fights the one they're in all day. Deep Microsoft 365 commitment changes the calculation entirely.

3
How clean does your Bexio or Abacus sync need to be?If open invoices and payment status have to be visible next to the customer record, the quality of the Swiss accounting integration stops being a detail.
4
Who runs it once we've gone?

A dedicated admin, or two or three people alongside their day jobs? Different platforms assume different answers, and the wrong assumption costs more than the licences.

WHEN WE POINT ELSEWHERE

No platform loyalty

Those four questions don't always land on HubSpot. When they don't, this is usually where they land instead — and we'd rather tell you now than eleven months into a build.

Where our HubSpot work has gone

Two of those numbers are why HubSpot usually wins. 

11 yrs building on HubSpot, since 2014
50+ implementations across Switzerland and the Nordics
4-6 wks to an operational backbone, where Salesforce runs 3–6 months
2–3 ppl part-time, to run it after we hand over
THE PROOF

Eleven years. The work speaks louder than a badge.

Our credibility isn't a partner tier. It's the builds — across cleantech, industrial SMEs, B2B SaaS, professional services, and family businesses in Switzerland and the Nordics. We've seen what breaks, what scales, and which shortcuts cost more later than they save now.

"Vidalico Digital understood our needs from the beginning and there were absolutely no problems in communication. Our sales and marketing materials and messaging are aligned and our social presence is constant with our marketing goals. They are an integral part of our team."

Hubspot CRM - Cleantech
Ville HakalaCTO, Sofi Filtration

"We renewed both the design and platform of our website. The aim was to have a modern site that is easy to navigate and provides information effectively.  The workflow was very smooth between us and their team. We had constant discussions, and milestone meetings, and all the time communication was very easy. Vidalico responds to your requests fast. They really know what they are talking about. And it's not only talking, they also deliver what they promise."

MiningFinland - website design
Miia MikkonenCEO, Mining Finland

FREQUENTLY ASKED QUESTIONS

Do you make money if we choose HubSpot?

Not on the licences. Those go directly to HubSpot at HubSpot's price — we don't resell them, we don't take a margin, and we're not on a partner tier that rewards volume. We're paid for the Audit and the build, and we get paid the same whichever platform the Audit lands on. That's deliberate. A recommendation is only worth something if the person making it doesn't profit from the answer.

What if you decide HubSpot isn't the right fit?

Then we say so, and the Audit still gives you the roadmap. You'll have a written recommendation for whichever platform does fit, what the migration looks like, and what it costs. We'd rather lose the build than hand you a system your team abandons in eight months.

What does an implementation cost?

For a company of 50 to 200 people, a HubSpot build typically runs CHF 20,000–45,000 on top of licences, depending on how many hubs you're switching on, how messy the data migration is, and how much process redesign comes with it. The Audit prices your specific case before you commit to anything. Licences are separate and go directly to HubSpot.

Where does our data sit, and does this work under the revDSG? HubSpot offers EU data hosting, which covers the requirement for most Swiss companies under the revDSG and GDPR. If you're in a sector where data has to stay inside Switzerland — certain healthcare, financial services, defence work — that constraint can rule HubSpot out entirely, and it's one of the first things the Audit checks. Better to find out in week one than after the migration.
How long before the team is actually using it? Live in four to six weeks for a typical mid-size build. Adoption is the longer question. Expect a quarter before it's habit rather than something people remember to update, and plan for training to be a real line item rather than an afternoon. The builds that fail don't fail technically.
We already have HubSpot. Can you help?

Usually, yes — and it's a good share of what we do. Portals get built fast, then drift: workflows nobody remembers building, properties nobody uses, reporting that doesn't answer the question anymore. We audit what's there, tell you what's worth keeping, and fix what isn't. No migration, no rebuild, and often a smaller job than people expect.

What are the steps?

It starts with the Audit — where your data actually lives, which platform fits, what a migration involves, where the quick wins are. From there: align the funnel so marketing, sales and service run one customer journey rather than three. Connect your existing stack, accounting included, so data syncs instead of getting re-typed. Configure HubSpot around your process — fields, workflows, templates, pipelines. Build the reporting you'll actually look at. Then train the team, by role, until two or three people can run it without us.

Can we keep our existing CRM and run HubSpot alongside it? Sometimes. If your CRM is doing something specific and doing it well — a deep ERP integration, an industry system with no real alternative — HubSpot can sit alongside it and sync. But two systems means two sources of truth, and someone has to own which one wins when they disagree. We'll tell you honestly whether the integration is genuinely cheaper than a migration. Often it isn't; it just moves the cost somewhere less visible.
How much of our team's time does this take?

More than people expect, and it's the honest constraint. Plan on your project lead giving it a day a week during the build, plus a few hours each from whoever owns sales, marketing and service — they're the only ones who know how the work actually gets done. If nobody internally has that time, the build will technically finish and quietly fail. We'd rather delay a start date than pretend otherwise.

Does this work in German?

Yes. The platform runs in German, and so do we — Swiss German conventions, not translated-from-English copy. Training, documentation and day-to-day support all happen in German if that's what your team needs. French too, though at a working level rather than native.

We're smaller than 50 people. Is this still for you?

Sometimes. Below about 30 people with a single product and one salesperson, HubSpot is often more platform than you need, and something lighter will serve you better for less — we'll say so. What matters more than headcount is whether the mess has started: multiple tools that don't talk, data in someone's head, a question nobody can answer without a week of digging. If that's happening at 25 people, the conversation is worth having.