Base acquires Rubiq to give post-sale AI a shared customer history
Rubiq’s technology already powers Orbit’s Customer Graph. Base says customers can now use it to connect account data, conversations and past decisions.
Loading page…
Rubiq’s technology already powers Orbit’s Customer Graph. Base says customers can now use it to connect account data, conversations and past decisions.
Listen to this story
Base is folding Rubiq’s customer knowledge graph into Orbit, aiming to give post-sale agents a persistent record of customer requests, company promises, and decisions across teams and channels. The practical bet is that this history can help agents choose account-specific actions—such as expansion offers or reference requests—instead of relying mainly on segments or snapshot health scores. Base says its Customer Graph and context models are available now; the acquisition price and other financial terms were not disclosed.
Rubiq was founded in 2025 by Eyal Efroni and Shaul Amran.
The graph combines structured CRM and product-usage records with conversations, support tickets, community posts, surveys, and email.
Base says sales, customer success, executives, and Orbit agents can draw on the same customer context, with each interaction adding to it.
Base has acquired Rubiq, adding technology designed to give its post-sale AI agents a shared history of customer needs, promises and decisions. Announced November 20, 2026, the deal brings Rubiq’s customer knowledge graph into Base’s Orbit platform, where the company says it already powers the Customer Graph used in customer-growth programs.
Rubiq was founded in 2025 by Eyal Efroni and Shaul Amran. Its technology is now part of a platform Base uses for work after a sale, including onboarding, adoption, renewals and expansion. The acquisition announcement did not disclose a purchase price or other financial terms.
Rubiq connects structured information—records organized into fields, such as customer relationship management records and product usage—with less orderly material from conversations, support tickets, communities, surveys and emails. Base describes the resulting knowledge graph as a way to preserve the relationships and meaning across those sources, rather than leave each record standing alone. The intended context includes both what customers have said and what the company has done in response.
The distinction is the history behind an individual signal. In Base’s example, a request carries different meaning when a customer has already raised it three times, or has just expressed satisfaction on a call. Rubiq’s system is designed to reason over that history, including customer needs, team decisions and the reasons behind them. Base says it uses very long context windows to consider that information together.
When AI agents act on your behalf with customers, a wrong guess puts the relationship at risk.
Eyal Efroni, Rubiq co-founder and CEO
Base contrasts Orbit’s approach with post-sale programs built around customer segments and moment-in-time health scores. Its pitch is that choosing an action requires more than placing an account in a category: the system should also account for what was requested, what was promised and what was decided. The company offers two examples of how that fuller record is meant to shape customer outreach:
The integration is also intended to keep different users working from the same customer context. Base describes a sales request made through customer relationship management software, a customer success manager’s question in Slack, an executive’s query through Model Context Protocol, and an Orbit AI agent all drawing on the same facts, insights and decisions. These are different routes into one shared record, rather than separate histories for each team.
Base says each interaction adds to what the next user or agent knows. That makes the proposed workflow cumulative: an answer or decision becomes part of the context for later work, rather than remaining only within the interaction that produced it. The company positions that shared history as the basis for choosing the next action for an individual contact or account.
For Base customers, access is not presented as a future integration milestone. The company says the Customer Graph and context models are available now.
Loading discussion...
Join the conversation
Share when remembering would help, or when forgetting would be better.
Be the first to share a perspective or an experience.
Reader comments
Newest comments first. Replies stay oldest first.