We already have the answers.

HubSpot (Diamond Partner), Salesforce (certified admins), Pipedrive, Attio. We also handle migrations between the four. For Zoho, Monday or a custom setup: we look case by case, and say no when the fit isn't there.

We're operators AND consultants. We code, configure and dedupe, we don't hand over a slide deck. And after the engagement we stay reachable on Slack Connect for 90 days, not a hotline that replies five days later.

No, we augment it. Most of our engagements run alongside an in-house RevOps person. We bring the bandwidth and the scaling expertise; you keep the business context.

First deliverables in week 1 (audit). First measurable commercial results from week 4 (live sequences, scoring activated). ROI calculable by week 8. We quantify it at the diagnostic, not after.

Yes, we've delivered across 5 countries at once (FR, BE, IT, ES, DE). The team writes and delivers in FR and EN. For multi-country setups, we map public sources per jurisdiction (ORIAS, FSMA, IVASS, DGSFP, BaFin, etc.) before enriching.

NDA signed before any access. View-only access during the diagnostic, role-based afterwards. GDPR-compliant, EU hosting. For sensitive clients: dedicated data room, auditable access.

Commercial B2B databases are built for scale across horizontal segments (tech companies, professional services, SaaS). Regulated verticals, insurance intermediaries, financial advisors, healthcare, require license-level data that commercial providers don't capture accurately. Registration status, license type, and specialty focus are only reliably available from the official regulatory body. Any commercial database pulling from secondary sources will have significant gaps and outdated records in these segments.

For five countries at this scope (~51,000 records + enrichment), the full cycle from extraction to Salesforce-ready delivery takes 4–8 weeks depending on data quality at the source and the number of validation rounds required. Single-country TAMs can be delivered significantly faster.

A prospecting list is a flat export of contacts that match a rough filter. A TAM is a structured, scored, and segmented database that maps your entire addressable market, not just the slice that's easy to find. The distinction matters operationally: a TAM tells you how much of the market you've covered, which segments remain untouched, and where to allocate sales resources across the full pipeline horizon.

We build deduplication logic before import, matching new records against existing CRM data using a combination of website URL, company name (normalized), and registration number where available. Ambiguous matches are flagged for manual review rather than automatically merged because incorrect merges are harder to fix than unresolved duplicates.

Yes. The core approach, identifying the authoritative regulatory registry per market, extracting structured data, standardizing across jurisdictions, and enriching with commercial context, applies to any regulated industry with national licensing bodies. The effort varies based on registry accessibility and data quality per country.

For a revenue team of this complexity, 200+ fields, multiple pipelines, a third-party CS platform integration, expect 6–10 weeks for a properly sequenced migration. Rushing the architecture phase to move data faster is the most common cause of post-migration rework.

Yes, but it requires upfront mapping of every object, field, and pipeline stage before any data moves. Legacy pipelines that no longer match your new process (like Maki's Renewal pipeline) need a deliberate migration strategy, not just a bulk export.

MEDDPICC works in Salesforce through a combination of custom fields on the Opportunity object and validation rules that make those fields required at specific stage progressions. Without validation rules, MEDDPICC stays optional in practice regardless of what the methodology says.

The key is rebuilding the integration logic natively — not relying on a generic connector. That means mapping every synced field explicitly, matching picklist values exactly, and defining the trigger logic (which Salesforce event creates or updates a Planhat record) before going live.

TAM stands for Total Addressable Market. A TAM Build means defining and populating the full universe of companies and contacts a business could sell to. Companies need one when their target market isn't covered by standard databases, typically niche verticals like municipalities, or when they need data points (like political delegations) that conventional tools don't capture.

You go to the source. In France, government APIs (data.gouv.fr, geo.api.gouv.fr, the Annuaire du Service Public) provide structured data on municipalities and identifiers. But no single source gives you a complete, sales-ready dataset. You need to combine them, cross-reference, and layer on contact enrichment using scraping, AI agents, and tools like Apollo and FullEnrich. It's a data engineering project, not a subscription.

For Vizzia, the initial sample was delivered within weeks. The full database, including scraping, cleaning, enrichment, and CRM import, was built over approximately three to four months alongside other concurrent workstreams. Timeline depends on the number of data sources, the complexity of the contact layer, and client validation cycles.

Municipal data changes at a predictable rhythm, mainly around election cycles (every six years in France) and annual restructurings. Between elections, turnover in deputy and cabinet roles is manageable with periodic refresh passes. That's what the TAM Refresh component addresses: a structured process to re-validate officeholders and update the CRM without rebuilding from scratch.

Yes, we proved it by extending the methodology from France to the UK within the same engagement. The framework (government data sources → scraping → enrichment → CRM import) is portable. What changes is the specific data sources and administrative structures. The methodology stays the same.

It depends on the volume and the mess. For Tellent, three merged CRMs, 90,000 contacts, 60,000 companies, roughly 300 properties, the cleaning phase took about four to six weeks, including coordination with an external agency handling initial deduplication. The key is to define clear archival criteria before you start deleting anything, and to keep a recovery window in case something important was removed by mistake.

Yes. HubSpot's custom objects, combined with an orchestration tool like Cargo and some custom development (in our case, a Python microservice for ATS detection), can deliver meaningful intent tracking at a fraction of the cost of dedicated intent data platforms. The trade-off is that you need someone who can build and maintain the integrations, this isn't a plug-and-play setup.

Account fit scoring is static: it tells you whether a company matches your ideal customer profile based on firmographic data like size, industry, and geography. Intent scoring is dynamic: it captures real-time buying signals like website visits, content downloads, or competitor monitoring activity. You need both, fit tells you who to target, intent tells you when to reach out.

We built a custom scraper that visits a company's career page, analyzes the HTML structure and embedded scripts, and matches patterns against a reference list of known ATS/HRIS platforms. This approach works well for tools that have a visible web footprint (like career page integrations). Some systems, especially internal performance management tools, are harder to detect because they don't leave public traces.

That was a core design constraint. Every automation and workflow was built to run on its own with error notifications, documented processes, and refresh cadences that don't require daily intervention. The ATS scraping service, for example, runs on a trigger from Cargo and only needs attention if the infrastructure changes. Tellent operates this system today with a lean team and occasional Cashmyrr support for optimization.

It depends on the size and complexity of the database. For a HubSpot instance the scale of Uptoo's, nearly 140K contacts and 75K companies, we delivered the full cleaning, enrichment, and button deployment in four months. Smaller CRMs can be cleaned in weeks; larger or more complex setups with multiple pipelines and custom objects may take longer.

Yes, that's where rule-based cleaning matters. We defines explicit exclusion rules before any deletion happens. In Uptoo's case, every customer, every contact linked to a deal, and every record with a scheduled next step was fully protected. The cleaning only targets records that meet clear "dead weight" criteria: bounced emails, missing identifiers, extended inactivity, or very low field completion.

They're custom action buttons embedded directly in HubSpot record views (on a contact page or company page) that trigger automated workflows behind the scenes. When a sales rep clicks the button, it queries external data providers, retrieves the missing information (like a phone number or decision-maker contacts), and writes it straight back into HubSpot, no copy-pasting, no switching between tools.

Generally, no. Enriching a database full of duplicates, orphaned records, and obsolete entries means you're paying to enrich contacts and companies that shouldn't be there in the first place. Cashmyrr recommends cleaning first to establish a reliable baseline, then enriching the records that actually matter, it's more cost-effective and the results are significantly better.

Without maintenance, yes and quickly. That's why Cashmyrr deployed a monthly automated cleaning workflow for Uptoo that continuously removes records falling into pre-defined cleanup criteria. Combined with the enrichment buttons that keep incoming data complete, this creates a sustainable hygiene cycle rather than a one-off fix.

Don't import legacy CSVs directly. Route every source file through a staging database first (we use SQL + MongoDB) to normalise opt-ins, exclude complaints and NPAI, and scrub bad formats. Only data that passes staging reaches the new CRM. In parallel, configure Brevo with a dedicated sending subdomain and full DKIM / SPF / DMARC authentication before the first send, so deliverability doesn't tank on legacy noise.

Yes, if the cutover is staged. We migrated TGV Lyria's stack across three markets and three languages without skipping a single send, including during a strategic commercial campaign already on the calendar. The principle: clean and validate data in a staging layer, set up the new sending infrastructure in parallel, and only flip campaigns once Brevo is fully authenticated and synced with HubSpot.

Because the two jobs are different. HubSpot is a CRM core: structured contact model, lifecycle stages, parent/child company relationships, segmentation, GDPR traceability. Brevo is a bulk-sending platform: deliverability tooling, IP warming, native authentication. All-in-one tools tend to be strong on one side and weak on the other. The combination, with native bi-directional sync, gives you both without compromise.

Yes, and many companies do. HubSpot is a strong first CRM for companies in the 10-100 rep range. When complexity demands it (usually around 200+ reps or when multi-entity reporting becomes critical), migrating to Salesforce makes sense. The migration isn't painless, but it's manageable with proper data cleaning beforehand.

Often, yes. We've audited Salesforce instances for 20-30 person teams where 60% of the features were unused and the data was messier than it needed to be, precisely because nobody had the time to admin it properly. The platform's power becomes liability without the resources to maintain it.

HubSpot Enterprise has improved significantly. Custom objects, advanced permissions, and conversation intelligence close many of the historical gaps. But if you need complex account hierarchies, channel partner management, or field service integration, Salesforce still has the edge.

Salesforce's mobile app is stronger for field sales, with offline functionality and more detailed record views. HubSpot's mobile app is cleaner and easier to navigate but less feature-rich. If your reps are in the field without reliable internet, Salesforce wins this category.

The most practical AI use cases in 2026 are email drafting, meeting prep (auto-summarizing a contact's history before a call), and lead scoring. Both platforms do these. The difference is access: HubSpot includes them, Salesforce charges extra. The more advanced capabilities (autonomous prospecting agents, conversation coaching) are promising but still early.

Not in any timeframe that matters for your planning. AI agents will reshape the SDR role, shifting it from manual research and high-volume outreach toward judgment-heavy work like qualification, objection handling, and relationship building. Companies that deploy AI agents effectively aren't firing SDRs; they're giving each SDR the research capacity of a small team. The Bureau of Labor Statistics still projects 4% growth in sales roles through 2032, even accounting for AI adoption.

Costs vary depending on the approach. Off-the-shelf platforms are priced by seats and volume; custom builds add setup costs on top of ongoing API and infrastructure fees. What actually drives the price you'll pay: the platform's level of autonomy (fully autonomous tools are priced differently than HITL-assisted ones), the number of users or accounts processed, whether you go off-the-shelf or custom, and the data providers and integrations required. The real question isn't the sticker price, it's cost per meeting booked: a workflow that lets the same SDR book meaningfully more meetings for the same headcount cost wins on that metric, even if the software itself costs more.

Sales automation (Outreach, Salesloft, HubSpot sequences) executes predefined workflows: send email A on day 1, email B on day 3, call on day 5. The logic is static. An AI sales agent adds a reasoning layer: it decides which accounts to prioritize, what to say based on real-time research, and how to adjust the sequence based on prospect behavior. Traditional automation is a conveyor belt. An AI agent is closer to a research assistant who also happens to draft your emails.

Between 12 and 20. Fewer than 10 and you won't have enough granularity to differentiate leads. More than 25 and the model becomes opaque. Start lean, add criteria when data justifies it, and remove criteria that don't correlate with conversion.

Quarterly at minimum. Monthly in the first 90 days after launch. Any time there's a significant change to your ICP, product, or go-to-market motion, revisit the model immediately. A scoring model from six months ago is already drifting.

Target 60% or higher. If sales is accepting fewer than half the MQLs marketing sends, either the threshold is too low or fit scoring needs work. Above 80% usually means the threshold is too high and you're leaving qualified leads un-worked.

Yes, but stick with manual scoring. Predictive models need volume (200+ closed deals minimum). Manual scoring works with any database size because you're applying rules you defined, not patterns the AI discovered. Even with 50 closed-won deals, you can identify your best-fit company profile and weight scores accordingly.

For a straightforward B2B TAM using commercial data sources (Apollo, ZoomInfo) with light enrichment, expect 2 to 3 weeks including ICP definition, data extraction, cleaning, and CRM import. For complex builds requiring custom scraping, multiple source reconciliation, or public-sector data, budget 4 to 6 weeks. The ICP definition step alone typically takes a week if you’re doing it properly with cross-functional input.

Quarterly is the minimum. If you’re in a fast-moving market with high job turnover (tech, startups), monthly enrichment refreshes on your Tier A accounts are worth the cost. At minimum, re-validate email deliverability every 90 days and re-run phone enrichment every 6 months. Set calendar reminders. Nobody remembers to do this without a system.

AI helps at specific stages but doesn’t replace the process. LLMs are excellent for fuzzy deduplication, classifying companies into ICP tiers, and standardizing messy company names. AI-powered enrichment tools like Clay and FullEnrich use multiple models to find contact data. But ICP definition, source selection, and validation still require human judgment. Companies that fully automate TAM building end up with large databases of low quality.

Intent data and ABM are natural partners. ABM gives you a target account list. Intent data tells you which accounts on that list are active right now. Without intent data, ABM is just advertising to a static list. With it, you can concentrate budget on the 15-20% of your TAM that is actually in-market this quarter.

Lead scoring assigns a numerical value to a lead based on fit (firmographic match) and engagement (behavioral actions). Intent data is one input into that score. You need both, but intent data without a scoring framework leaves you with raw data and no prioritization.

The data is clear: faster is better. Respond to first-party signals (website visits, demo requests) within 4 hours. Respond to high-value third-party signals (topic surge + funding event on the same account) within 24 hours. Respond to standalone third-party signals within 72 hours. After 7 days, most intent signals have decayed to the point where they are better used for marketing nurture than for direct sales outreach.

Run a full audit once a year. Do a lighter data quality check (Steps 2 and 3) quarterly. If you’re growing fast, adding new integrations, or changing your sales process, audit sooner. The cost of waiting is always higher than the cost of checking.

For a CRM with under 10,000 contacts and a straightforward tech stack, expect one to two days of focused work. For 50,000+ contacts with multiple integrations, plan for a full week. Larger databases with complex automation layers can take two to three weeks. Most of the time goes into Steps 2, 3, and 5.

You can absolutely run this checklist internally. The steps above are the same ones we use professionally. The advantage of an external team is objectivity and pattern recognition. After 50+ audits, we spot issues faster because we’ve seen them before. We also have benchmarks to tell you whether your 62% completeness score is normal for your industry or a five-alarm fire. If you want help, our audit service walks through this exact process with your team.

Your CRM itself (HubSpot, Salesforce, Pipedrive, etc.) plus a spreadsheet. That’s the minimum. For duplicate detection, your CRM’s built-in tools work for basic cases. For deeper analysis, tools like Insycle (HubSpot) or Demand Tools (Salesforce) help. For data enrichment gaps, Apollo, Clearbit, or Dropcontact can fill in missing fields after the audit identifies what’s missing.

It can. Before merging, audit which workflows reference the records being merged. HubSpot preserves associations and activity history on the surviving record, but workflow enrollment history for the deleted record is lost. Reports based on total contact count will obviously change. Build your reports on active, qualified contacts rather than total count, and this becomes a non-issue.

Clean first. Always. Enriching a dirty database means paying for credits on records you’ll later merge or delete. It also means your enrichment tool might not match the right record because the existing data it uses for matching (company name, email domain) is inconsistent. Clean, standardize, dedup, then enrich. The four phases exist in that order for a reason.

Quantify the waste. Pull a report on deals lost or stalled where the contact had outdated information. Calculate the hours reps spend per week verifying data outside HubSpot. Multiply by their hourly cost. At Tellent, the 6 hours per rep per week figure made the business case obvious. Even a conservative estimate of 2-3 hours per rep per week across a 20-person sales team is over 2,000 hours per year of productivity lost to bad data.