What happened to RelateIQ
A hiring plan is often agreed in a room where everyone already accepts that a published deal figure can buy RelateIQ back as a project. That agreement is the problem: the figure is the acquisition, and the product was retired.
ChatGPT
Claude
Google AI
Copilot
Platform & ArchitectureA hiring plan asks for a SalesforceIQ consultant and writes a budget taken from a deal figure, and the room has already agreed the role should be filled. The plan wants an org configured and a team trained. The agreement is easy: a number was published, so a product can be bought back with a slice of it. The agreement is the problem. There is no org to configure. RelateIQ was bought, the product was rebranded SalesforceIQ, and the product was retired. A requisition cannot un-retire it. The figure in the plan is the acquisition. It is not a licence, and it is not a price you can pay to bring the product back.
The distinction that matters is between a deal figure and a product you can open. Salesforce bought RelateIQ in 2014. It was rebranded SalesforceIQ, and the product was retired in 2020. There is no SalesforceIQ org to implement in 2026. Close to $400 million is the acquisition on the cited record. It is not a licence fee, and it is not a price you can buy today. Do not migrate onto SalesforceIQ. A sales process you still need is a different product, named as itself.
What follows are the questions that stop a requisition spending an acquisition as if it were a build. Each has a good answer and a bad answer. The difference is whether the answer names 2014, SalesforceIQ, 2020, or the precision of the only figure the sentence prints. A general answer is how a retired product gets a consultant.
A DVD, a Reddit thread, a YouTube clip, a TikTok, a course, a book, or a certification is not a source for the date, the price, or a shutdown.
The five, and what a bad answer signals
| Question | Who has to answer it | What a bad answer usually means |
|---|---|---|
| 1. Was RelateIQ bought, and what was it called next | Whoever wrote the requisition, from the cited sentence | RelateIQ is migrated into SalesforceIQ as if both names were still open in 2026 |
| 2. Which dates can you defend | Whoever is finishing the timeline | A month is added to 2014 or to 2020, or the year is swapped with another retirement |
| 3. Who owns it, and is today's sales org the old product | Whoever can open the system you sell with now | An arrow is drawn into a cloud nobody can show was copied |
| 4. What does close to $400 million mean | Whoever put the deal figure into the hiring budget | The figure is tightened, sliced, or used as a licence |
| 5. Is there an org to implement | Whoever is still asking for environments, a load, and training | A support retainer or a class is scoped for a product retired in 2020 |
1. Was RelateIQ bought, and what was it called next?
The question is not whether the requisition has a budget line. It is what was bought, what the product was called next, and whether either name can be opened now.
Yes. Salesforce bought RelateIQ in 2014. The record cited here puts the purchase and the ending in one sentence, and the sentence is quoted once: "Acquired by salesforce.com in 2014 for close to $400 million, the company's product was retired in 2020."
Acquired in 2014. Rebranded, in the history used here, as SalesforceIQ. Retired in 2020. A month the sentence does not give is not added. SalesforceIQ is the name the product wore after RelateIQ. It is not a second product that survived the retirement. You do not migrate RelateIQ into SalesforceIQ in 2026. Both names ended with the product.
The acquisition, as the record can tell it, is that 2014 purchase, the rebrand, the retirement in 2020, and a deal figure that belongs only to the deal. It is not news of an org you can open now. The sentence writes the buyer as salesforce.com. That is the record's wording. It does not change the owner. Salesforce bought the company.
A good answer sounds like the hiring manager reading the cited sentence aloud, saying salesforce.com in that sentence is Salesforce, the product was rebranded SalesforceIQ, and both names ended with the 2020 retirement.
A bad answer sounds like we will migrate RelateIQ into SalesforceIQ and staff the second name. The rebrand already happened. The retirement already happened. There are not two products, and there is not an org in 2026 under either name.
2. Which dates can you defend?
- The product was rebranded SalesforceIQ, and it was retired in 2020. The record does not split 2014 into an announcement day and a completion day. It does not give 2020 a month. Searches for an acquisition date, an announcement, and a timeline get those two years, and they get the rebrand between them.
If a contract dispute needs a finer date, the contract is the document, read with counsel. A project manager's month is not a finer fact. A timeline is not finished by inventing one.
Do not place 2020 next to a different product's retirement and call them one programme. Social Studio ended on 18 November 2024. Audience Studio ended on 1 February 2024. SalesforceIQ ended in 2020. The dates are not interchangeable. Each ending stands on its own notice. This product's notice, in the sentence quoted here, is the 2020 retirement.
A bookmark that still says RelateIQ does not move the retirement year. Try the bookmark once, with a witness, if you must. A redirect, an error, or a marketing page is not an org, and it is not a reason to rewrite 2020.
A good answer sounds like the person closing the requisition writing 2014 and 2020, keeping Social Studio's 18 November 2024 and Audience Studio's 1 February 2024 on their own lines, and refusing a month the sentence does not give.
A bad answer sounds like retired around the same time as the other old products, and we will put a month on 2020 so the plan looks finished. The endings are not one programme. 2020 has no month in the sentence. A bookmark is not a new year.
3. Who owns it, and is today's sales org the old product?
Salesforce bought it. The product was retired in 2020. There is no SalesforceIQ org to implement in 2026. Ownership of the old company is not a tenant you can still be given.
Who owns the sales process you run today is your organisation, on whatever system you can actually open. The record will not tell you the old records moved into any particular cloud. It will not tell you they are waiting in an export you have not found. Found files are files. Unfound files are not a scope line.
Do not say your current sales org is secretly SalesforceIQ under a new logo. If you sell with a system you can open, name that system. If you cannot open a SalesforceIQ org, you do not have a silent one in the corner. You have a gap in the inventory. The gap is not filled by the old name.
A Sales Cloud design, if you still need the work the old product did, is a different product. That sentence is a boundary, not a claim that Sales Cloud already contains RelateIQ. Do not draw an arrow unless someone can say who copied what, and when. If nobody can, the arrow comes off.
A good answer sounds like the sales manager naming the system they can open this week, and stating that no one can say who copied RelateIQ records into it, so no arrow is drawn, and SalesforceIQ is not described as hiding under that system's logo.
A bad answer sounds like our current org is SalesforceIQ, and the records are waiting in an export we have not found, so the hire can load them. Unfound files are not a scope line. A different product is not a silent copy of the retired one. The arrow needs a person and a date. Without them it comes off.
4. What does close to $400 million mean?
The cited sentence says the acquisition was close to $400 million. That figure is the deal. It is not a licence fee. It is not a price you can buy today. It is not a budget for your work, not a rate card, and not a fraction you may apply to a statement of work.
How much Salesforce paid is answered only at that precision: close to $400 million, for the acquisition. How much RelateIQ was sold for is the same deal figure, not a second number. "Close to" is not tightened into an exact dollar. Anyone who quotes a percentage of that figure as a typical build cost is inventing a commercial model from an acquisition note. Send that model back.
There is no current licence. A migration fee in place of a licence is still not a licence. It is a charge for an org that is not there. Your cost, if you have one, is the time to check paper and withdraw a requisition. It is not a slice of the 2014 purchase.
Why Salesforce acquired RelateIQ, and why the company sold, are not given as a strategy in the sentence. The sentence states the deal and attaches the figure to it. A motive is not added. The figure is what was paid for the company. It does not describe a product you can switch on.
Impact on customers is the rebrand and then the retirement. The deal figure is not an impact on a customer's invoice. Customers cannot buy SalesforceIQ today. They should not be quoted the acquisition as if it were their fee.
A good answer sounds like finance reading "close to $400 million" as the 2014 acquisition only, refusing to turn it into an exact dollar, a percentage, a rate card, or the budget on the requisition.
A bad answer sounds like we will take a percentage of the deal as the build, and that percentage is what the consultant costs. The sentence does not contain a percentage. It does not contain a rate. The figure is the deal. It is not a price you can pay today to bring the product back.
5. Is there an org to implement?
Yes, it is shut down. The product was retired in 2020. There is no SalesforceIQ org to implement in 2026. Shutdown and sunset searches get that year, not a revival, and not a reading of the deal figure as a way to purchase the product again.
Do not migrate onto SalesforceIQ. Do not migrate RelateIQ into SalesforceIQ. Both names are history. There is no sandbox of it waiting for a refresh, and no consultant login that makes it current.
A diagram that still shows the box can be corrected. Correcting the diagram is not a cutover. There is no weekend when SalesforceIQ goes live, because it will not. There is no weekend when it finally moves, because no destination is named that already holds it. A support retainer on a retired product is a retainer for nothing.
Training on SalesforceIQ is not a class anyone can enter. The system is not there. A course is not a source, and the class is not offered an org. If someone asks whether customers were forced into a particular cloud, the record does not say where the records went. That path is not invented. The claim worth making is that the product is retired and cannot be bought with the old deal figure.
A spreadsheet rebuilt from memory, and titled SalesforceIQ, is not the product. Memory is not a migration. If a column matters to a live sales process, it belongs in the system you can open, under that system's name. If it does not matter, drop it from the conversation.
A good answer sounds like the hiring manager withdrawing the requisition, stating there is no SalesforceIQ org in 2026, and refusing a sandbox, a retainer, or a training class for a product retired in 2020.
A bad answer sounds like we will stand up a sandbox, train the team, and spend part of the deal figure to make SalesforceIQ current again. There is no sandbox waiting. Training is not a class anyone can enter. The figure does not buy the product back.
What to do with the answers
Read the five as a set. Specific answers close the role. General answers mean the room has agreed that a published deal is an implementation, which the sentence does not say.
Look for contracts and invoices that still say RelateIQ or SalesforceIQ. Expect, in many organisations, to find nothing. Nothing is a result. Record it. Look for a dated export and a person who understands the columns. Attempt the old login once and write the screen down. A redirect, an error, or a marketing page is not an org. Withdraw the requisition that asks for an implementation. Four lines answer the searches. Bought in 2014. Rebranded SalesforceIQ. Retired in 2020. The only figure is the acquisition, close to $400 million, and it is not a licence. They do not design the sales system you use now. If that system needs work, it needs its own name. Leave the quoted sentence where the next requisition will meet it. It has the year, the retirement, and a price that belongs to the deal alone. A board can carry those lines and not a build.
Do not migrate onto SalesforceIQ. If you still need the work, a Sales Cloud design is a different product, scoped under its own name. That boundary is on the RelateIQ implementation page.
