Who to hire for RelateIQ on Salesforce

RelateIQ is probably the oddest entry among the acquisitions people search for, because the search itself usually comes from one of three situations. Someone has found an old export from the product and wants to know what to do with it. Someone has read that Salesforce once owned a clever, low-maintenance CRM and wants the same thing now. Or a small team has outgrown spreadsheets and wants a simple tool that does not demand constant data entry. All three lead to the same practical hire, and none of them leads to a RelateIQ implementation.

#What happened to the product

The history is short and checkable. Wikipedia records two facts. "Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020." And: "As part of the 2015 Dreamforce conference, RelateIQ was rebranded as SalesforceIQ." The same article says the company was founded in 2011 and acquired by Salesforce in 2014. For a hiring decision the numbers matter less than the dates. The product has not been sold under its original name for more than ten years and has not existed at all since 2020. A partner who offers to implement it is selling a story. The sum paid for the acquisition is the old deal's price and tells you nothing about what a partner should cost now, so ignore it in any conversation about fees.

The background reading on the purchase is what happened to RelateIQ, and the question of whether anything should move is at should I migrate from RelateIQ.

#What you are really hiring for

The idea that made RelateIQ interesting was relationship tracking from email and calendar activity with little manual entry. In Salesforce today, the nearest equivalent is Sales Cloud with email and calendar capture switched on. The product's own rules matter, and a candidate should explain them without prompting. Capture tools can store activity data outside the standard Salesforce objects, which affects reporting and automation, and different capture options behave differently. Ask the candidate to explain what a seller will see, what a manager can report on, and what cannot be used in a flow.

The work divides into four parts:

• a small, deliberate data model for accounts, contacts, opportunities and activities
• email and calendar capture configured with sensible privacy rules
• import of whatever you kept from the old tool, cleaned and de-duplicated
• reports and a short training session that sellers will actually attend

None of this is exotic. That is the point. A partner whose proposal is heavy has misunderstood what a lightweight CRM is for.

#Skills and certifications

For a small team, one person with Salesforce Certified Administrator credentials is the foundation of the hire. For a team that wants advice on process, add a Salesforce Certified Sales Cloud Consultant, whose credential covers designing and implementing Sales Cloud solutions. If you need custom screens or automation beyond clicks, a Platform App Builder credential signals declarative skill, and Platform Developer I signals code. You can check holders on Trailhead's credential pages. The credential list changes between releases, so verify names there rather than trusting a profile.

Beyond certificates, ask about experience with small teams. Many consultants have only worked on large programmes and bring weight a five-person sales team cannot carry.

#A realistic first engagement

A good first engagement is short, and it is built around one question: can your sellers get value in the first fortnight? Ask for a pilot configured for a handful of users, with capture on, a minimal opportunity process, and two reports your sales lead has said they want. Add an import of your legacy contacts into a sandbox so you can judge quality before touching production.

Agree what finished means before work begins. For example: sellers can see their last interactions with a contact without typing, the pipeline report matches what the sales lead reads aloud on a Monday, and any duplicate records from your import have been resolved or flagged. If those things hold, widen the rollout. If they do not, you have lost a small amount of money and learned why.

#The three situations, and the hire for each

If you hold an old export, the work is data first. Ask what the export contains: contacts, companies, notes, the pipeline stages used, and perhaps lists. Decide which of these deserve a place in Sales Cloud. Notes and activity history are often the most valuable and the hardest to keep in a useful form, because they arrive as text. A partner should propose a staged import, starting with a clean subset, and show you a sample before the bulk load. The right person here is a data-minded administrator, and the work can be measured in days for a small file.

If you want the old idea of a CRM that fills itself in, the work is configuration and expectation setting. Decide which mailboxes and calendars are captured, who sees what, and how a seller can exclude a private message. Then agree what a manager can rely on. Captured activity is a strong prompt for follow-up. It is a weaker foundation for forecasting, so the pipeline still depends on sellers keeping opportunity stage and close date current. A partner who is honest about that line is worth hearing.

If you are a small team leaving spreadsheets, the work is restraint. The temptation is to model the whole business. The better approach is to begin with accounts, contacts and a single pipeline, add fields only when a report needs them, and review after a month. The partner you want will keep saying no to additions that nobody can name a use for.

#Adoption is the real deliverable

Many failed CRM projects deliver a working system that sellers ignore. A lightweight CRM stands or falls on whether people open it voluntarily. Ask the candidate how they measure that: logins by user, activities captured per week, the share of open opportunities with a next step and a date. Ask what they do when the numbers are poor in the third week. A strong consultant will describe sitting beside a seller and removing a field or a click. A weak one will schedule another training session.

Ask, too, who owns the system after the partner leaves. A small business needs one named administrator, even part time, with the credential and the authority to say no. If you do not have that person, the first deliverable may be a role description and some coaching, and that is a perfectly reasonable thing to pay for.

#Red flags

A proposal that includes a lengthy discovery phase for a team of a few sellers is the classic one. A proposal with dozens of custom fields before anyone has logged an activity is another. A partner who promises that capture means you will never type data again has overstated the technology. A partner who ignores the legacy export and starts with a blank database is wasting your history. And a partner who dodges questions about privacy, such as which mailboxes are captured and who can see them, should not be trusted with a tool that reads people's email.

#Comparing what you can ask for

None of these is the right answer in general. The right one is the cheapest that still protects data quality.

#Ten interview questions

1. How would you explain email and calendar capture to a seller who worries about privacy?
2. What does capture store, where, and what can I not report on?
3. Which fields would you refuse to add to the opportunity record?
4. How would you clean and de-duplicate a legacy contact export?
5. What is your approach to opportunity stages for a team of five?
6. Which two reports would you build first, and why?
7. How do you handle a seller who refuses to log anything?
8. What do you do when two capture tools disagree about a meeting?
9. When would you recommend a different tool entirely?
10. What can my admin do alone after the handover?

Question 9 is the honesty test. A partner who has never recommended against Salesforce for a small client has not been honest about fit.

#Privacy and trust questions

A tool that reads email and calendars needs a privacy conversation before it needs a configuration. Ask the candidate to walk through what is captured by default, what a seller can exclude, what happens to messages that are clearly personal, and who in the organisation can see another person's captured activity. Decide your answers with human resources or legal rather than leaving them to a consultant's defaults. In some workplaces, employees must be told what is monitored, and a rollout that surprises people will lose their goodwill on the first day.

Also settle where captured data lives and for how long. Reports on activity may be less capable than reports on standard records, so ask for a worked example of the two or three reports you care most about, built against real data in the pilot. If a report cannot be built the way you imagined, you want to learn that in the second week, not after the licences are bought.

#Growing past the first version

A lightweight set-up should have a path to something larger without a rebuild. Ask the candidate how the first configuration would cope if you doubled the team, added a service function or began using marketing automation. A sound answer keeps the original objects standard, avoids clever custom structures and records the reasons for each decision, so that a later consultant can extend rather than replace. The test of a small design is that it can grow quietly. If every sensible next step needs the foundations redone, the design was too clever.

#Checking references

Ask for a reference from a small team, not a household name. Ask the reference whether sellers still use the system six months later and what the manager's reports are based on. Ask for a sample handover document. Ask who actually configured the pilot. A reference who says the partner talked them out of something is worth three who say the work was fine.

#Commercial models and statement of work

For a pilot, a fixed fee over a short period works. For a wider rollout, phases with acceptance criteria work better than an open-ended time arrangement. The statement of work should list users in scope, the capture options chosen and why, the objects and fields to be created, import and cleaning rules, the two reports, training sessions, documentation and a clause that you own all configuration. For the cost side of the old product, see RelateIQ implementation cost and the RelateIQ licence page, and integrating RelateIQ with Salesforce if you still have a connection to untangle.

#When you do not need a partner

A team of a few sellers with one capable administrator can do all of this unaided. The cost of getting it slightly wrong is low because you can change a small model quickly. Bring in help when data volume is large, when several sources must be merged, when privacy rules are strict or when sellers refuse to adopt. This page ranks no agency and recommends none.