Rob Acker’s first assignment at Salesforce was a peculiar kind of sales job: sell a product that had not launched and a category the buyer could not yet name. It was 2000. The cloud was weather, software arrived in boxes, and trusting a business system to the internet required an explanation before it required a contract. Acker was Salesforce’s first sales leader. He spent his days talking to customers, listening for their worries, and carrying those worries back to the people building the thing.
That feedback loop became the motif of his career. First came access: persuade companies that important software could live somewhere other than their own server room. Then came impact: help nonprofits and universities use the same industrial-strength tools as commercial enterprises. Now comes the untidy consequence of victory. After decades of customization, many cloud systems have become less like pristine machines and more like old cities. Roads overlap. Extensions lean against extensions. Nobody remembers why one alley bends.
At Hubbl Technologies, where Acker is chief executive, the wager is that those cities can be mapped. The company reads Salesforce metadata and process activity to expose technical debt, security risk, redundant automation and wasted motion. Its promise is practical: before an executive asks an AI agent to sprint through the business, let it discover where the stairs end.
The salesman in the basement
Acker arrived in enterprise software through Oracle, where he held a series of sales roles during the second half of the 1990s. Salesforce offered the more improbable proposition. He has recalled joining before the product launch and helping shape how the company spoke to customers about technology that did not yet exist in the market. The setting was suitably unceremonious: Salesforce’s early team worked in the basement of a building beside a parking lot.
His Salesforce résumé grew with the company. He became a sales director, led a North American region, ran sales in Europe, the Middle East and Africa, and later took operating responsibility at Salesforce.org. It is tempting to read this as a sequence of promotions. The more revealing continuity is translation. Acker repeatedly worked at the boundary where a technical system meets a buyer, a user or an institution with a problem it cannot phrase in product language.
One small memory from a former colleague catches the texture. Jamie Grenney, hired onto Salesforce’s sales-development team in 2002, later recalled that Acker zeroed in on an odd line at the bottom of his résumé: Grenney had written a book called Pranks 101. The anecdote is minor, which is why it works. Leaders announce that they care about people. Curiosity usually arrives disguised as a follow-up question.
A business designed to give itself away
Acker became chief operating officer of Salesforce.org in 2013 and CEO in 2015. The organization occupied an unusual seam between charity and commerce. It made Salesforce technology available free or at a discount to nonprofits and educational institutions, then used paid business to fund further grants, products and support. Acker helped make that self-sustaining model work at scale.
His public language from the period is full of loops: technology enabling institutions, revenue returning to communities, one sector borrowing the useful machinery of another. He argued that organizations working on social problems deserved serious digital infrastructure, not a polite pile of hand-me-downs. He also insisted that digital access alone was insufficient. Institutions needed a unified view of constituents, students, donors and partners if they wanted technology to change outcomes rather than simply modernize screens.
In 2019, Salesforce paid $300 million to combine with Salesforce.org and created a nonprofit and education vertical under Acker. The move ended duplicated product work and gave the unit access to Salesforce’s broader engineering and product portfolio. It also required balancing commercial scale with commitments to open-source software and discounted access. That same year, the Schwab Foundation named him Corporate Social Intrapreneur of the Year. The title is corporate argot, but the idea beneath it is clear: build a public-purpose engine inside a large company without pretending economics are optional.
The problem success left behind
The origin of Hubbl reaches back further than the company’s name. Greg Malpass, founder of Salesforce consultancy Traction on Demand, met Acker in 2009 while Acker was helping integrate Jigsaw, later Data.com, into Salesforce. Their teams saw a recurring obstacle: a new piece of software might be reusable, but a customer’s Salesforce environment rarely was. Old code, overloaded workflows and layers of customization made apparently simple work expensive and unpredictable.
By 2011, Acker and Malpass were discussing what they called the last mile of cloud computing. The cloud had democratized access. It had not democratized success. Companies could buy the same platform; they did not inherit the same ability to configure it well, clean it up or know whether it was delivering value.
Traction’s team began developing technology to assess technical debt and estimate the effort required to repair it. When Salesforce acquired Traction on Demand in 2022, that intellectual property and its most committed builders moved into Malpass’s incubator. The project became Hubbl. Acker, who left Salesforce after 24 years, joined founders Malpass, Chris Bruzzi and Michael Bogan in 2024. The long conversation had turned into an operating company.
Metadata as corporate archaeology
Metadata sounds like clerical residue: fields, permissions, flows, objects, bits of description about other bits of software. Hubbl treats it as a corporate genome. It records choices about how a company sells, serves, approves, escalates and measures. Where the official process chart shows intention, metadata shows what builders actually encoded. Process mining adds the behavior: the paths work takes, the variations it develops and the places it stalls.
This distinction matters because enterprise AI is being invited into environments that few humans fully understand. An agent can execute quickly and still choose badly. Acker’s argument is that the missing ingredient is not more fluency but more context: which automation is brittle, which field is trusted, which deviation is useful, which apparent shortcut is actually a control.
Hubbl compares patterns across thousands of Salesforce organizations, then recommends priorities. The ambition is to replace expensive episodes of manual discovery with continuous observation. In Acker’s preferred future, platforms become “self-healing”: they notice complexity, risk and waste, then recommend or carry out the next action. The phrase is medically flavored, but the work is closer to urban maintenance. Nothing stays fixed. The value lies in noticing what changed before a small crack becomes a closed bridge.
A second category, with scar tissue
In February 2026, Hubbl announced a $6 million Series A led by Salesforce Ventures, with Industry Ventures participating. The company said it had more than 4,000 customers and had scanned tens of thousands of Salesforce organizations. The money is intended to accelerate its intelligence platform as businesses prepare their systems for AI-driven operations.
Acker’s timing is informed by memory. The current agentic-AI rush resembles the early cloud transition in one important way: enthusiasm is running ahead of institutional readiness. Yet the starting point is different. Early Salesforce asked customers to trust a new, mostly clean system. Today’s AI agents are arriving inside systems with decades of inherited decisions. The cloud’s first act moved software out of the server room. Its second may require somebody to label all the boxes.
This is where Acker’s mixture of sales and social-enterprise experience becomes relevant. Sales taught him to listen for the objection behind the objection. Salesforce.org taught him that adoption is hollow when organizations cannot turn access into outcomes. Hubbl binds the two lessons together: understand the environment, then make the next useful action easier.
The habit beneath the thesis
Acker’s public biography calls him a self-taught musician. That is a charming fact in danger of being crushed beneath a metaphor, so let it remain mostly itself. Still, listening has been the most consistent verb in his account of work. He listened to customers when the cloud was unfamiliar. He listened to nonprofits describing the gap between donated technology and usable capacity. At Hubbl, the product itself is a kind of mechanical listening: examine what the system has been saying through years of configuration and behavior.
His professional connections follow the same long arc. Malpass and the Traction team moved from implementation partners to co-builders. Salesforce shifted from employer to investor. The ecosystem Acker helped expand became both the market and the dataset for his next company. There is no clean break here, and that is the point. Hubbl is a startup built from institutional memory rather than rebellion.
The aspiration Acker repeats is to “democratize success.” It is a grand phrase attached to painstaking work. Success, in this version, begins with an audit, a benchmark and an honest picture of the mess. The technology industry prefers greenfield stories because nothing has gone wrong in them yet. Acker has chosen the brownfield: the living systems, old compromises and crowded streets where the next wave of computing will actually have to work.