DataRPM announced a $5.1 million Series A on March 11, 2014, led by InterWest Partners, with existing investor CIT GAP Funds participating. The startup aimed to make enterprise analytics easier by connecting scattered business data, automating parts of data modeling, and letting users ask questions in ordinary language. Progress Software acquired DataRPM in 2017, so the raise is a historical funding event—not evidence of a current independent DataRPM product.
What DataRPM raised and who invested
The financing was a Series A of $5.1 million, announced on March 11, 2014. InterWest Partners led the round, and CIT GAP Funds, an earlier investor, also participated, according to TechCrunch’s contemporaneous report and the company announcement reproduced by VentureBeat. It was equity financing, not a grant, loan, acquisition, or verified total of all the company’s funding.
DataRPM said it would use the capital to accelerate its go-to-market work, expand internationally, hire, and continue product development. Contemporary coverage described the software as available in both cloud and on-premises deployments; that describes the offering in 2014, not its availability today.
The enterprise analytics problem DataRPM targeted
DataRPM’s pitch addressed two related obstacles. First, businesses often had information spread across different systems, and preparing it for analysis could require substantial manual integration and modeling. Second, many business intelligence tools depended on technical users who knew SQL or could ask analysts to build reports.
Quick wins for a faster PC:
Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →Scan for outdated or missing drivers - takes under a minuteDriver Scan →#1 Best Overall
The company argued that data modeling could take as much as 80% of the time involved in analytics. That was DataRPM’s estimate, not an independently established industry benchmark. Its broader proposition was that reducing setup work and making questions easier to ask could bring analytics to more employees.
How the product was meant to work
DataRPM described a business-intelligence platform, not simply a chatbot. Its approach combined data connections and indexing with semantic modeling, query interpretation, and visual presentation. Contemporary descriptions said it used a distributed computational search index rather than relying exclusively on a conventional data warehouse. The product’s intended workflow was:
- Connect data. Bring information together from disparate business sources.
- Index and model it. Apply semantic and statistical techniques, with machine-learning methods, to organize data for analysis and adapt the model as data changed.
- Ask a business question. Let a user enter a question in natural language instead of writing SQL.
- Interpret and analyze. Translate the question into an analytics query against the connected information.
- Present an answer. Return results with visualizations and, according to the company, relevant or suggested views.
This is the company’s historical product description, not a current technical specification or independently verified performance profile. The company also described analysis as near-real-time and the platform as highly scalable, but the available contemporary coverage does not establish refresh intervals, latency, dataset sizes, concurrency, or test conditions. Claims of unlimited scale therefore should be read as marketing, not as a measured guarantee.
The platform’s aim to automate data preparation did not mean that it could remove the need for sound source data, clear metric definitions, or analytical review. A natural-language question can be ambiguous; a system still has to map terms such as “customer” or “revenue” to the right fields and business rules. Data quality, governance, permissions, lineage, and the freshness of indexed data remain important whether users type SQL or ask questions conversationally.
Recommended Free Tools
What was known about DataRPM’s early traction
At the time of the financing, TechCrunch reported that DataRPM had 17 customers and 25 employees, with customers in financial services, telecommunications, media, and software. These are point-in-time figures reported in March 2014, not audited operating results. TechCrunch also reported an alpha release in March 2013 and beta testing in August 2013. The same report described the company as based in Fairfax, Virginia; a later Dealroom company record lists Redwood City, California. The sources do not establish why the location differs.
A customer quoted in the company announcement said DataRPM had delivered an end-to-end BI deployment in under 30 days and reduced ownership costs. That is an attributed customer testimonial, not a typical deployment promise or independent benchmark. The announcement named co-founders Sundeep Sanghavi, CEO, Shyamantak Gautam, and Ruban Phukan, and described the team’s experience as spanning BI, big data, and search. TechCrunch noted Sanghavi had previously founded Razorsight and SearchRidge.
Why the round mattered in 2014
DataRPM was competing for attention in a market moving toward self-service analytics: making data exploration accessible beyond data scientists, engineers, and dedicated analysts. Contemporary coverage placed it alongside emerging data-discovery and BI companies such as ClearStory Data and Looker, as well as a broader shift among established vendors toward more accessible analytics. TechCrunch cited a roughly $36 billion BI software market figure from DataRPM CEO Sanghavi; that was his characterization at the time, not a current market-size estimate.
The product’s ambition was broader than adding a conversational search box to a dashboard. To make a plain-language question useful, the platform had to connect sources, organize fields and relationships, interpret the user’s wording, execute analysis, and present a comprehensible result. Automating more of that chain could reduce friction, but each layer also created ways to fail: a connector might not support a needed source, field matching could be wrong, a term could have conflicting business meanings, or an attractive chart could conceal stale or incomplete data.
PC Slower Than It Used to Be?
A free scan shows the junk files, broken settings and background clutter dragging Windows down - then fixes them in one click.Free scan · Windows 10 & 11Outdated Drivers Are Slowing You Down
One free scan finds every outdated or missing driver and matches the right update for your exact hardware.Free scan · exact hardware matchBest Value
Offering cloud and on-premises deployments potentially widened the set of organizations that could consider the product, but those modes carry different operational demands. Buyers would still need to examine security, data residency, connectivity, upgrades, infrastructure ownership, identity integration, and how the system handles governance. Natural-language access does not by itself make analytics reliable or eliminate the need for data engineering and review.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What happened after the Series A
Progress Software acquired DataRPM in 2017. Progress reported approximately $30 million in aggregate consideration—$28.3 million in cash plus $1.7 million in restricted stock units or other consideration—in its acquisition accounting and transaction materials. A Progress SEC filing characterized DataRPM as having minimal revenue at the time of acquisition.
Progress presented the deal as supporting its cognitive-applications and predictive-maintenance strategy. In retrospect, that makes the acquisition a sign of strategic value to Progress, but not proof that DataRPM became a leading standalone BI vendor, achieved profitability, or delivered a financial return to its investors. The available evidence does not establish those outcomes. It does show that DataRPM’s independent company identity did not continue as an independent BI business after the acquisition.
What the DataRPM story says to today’s analytics buyers
The 2014 pitch remains useful as a way to judge analytics products, but it should not be mistaken for a current DataRPM buying option. The evidence here supports treating DataRPM as an acquired historical company; it does not confirm a current standalone product, signup path, or DataRPM-specific pricing.
Free tools Windows power users keep installed
One-click scans. No signup required.
Quick Recap
- Test answers, not just the interface. Use representative business questions and verify how the system interprets terminology, handles ambiguous requests, and exposes the resulting query or logic.
- Inspect the semantic layer. Confirm how sources, fields, transformations, and business metrics are mapped, reviewed, and changed.
- Check freshness and governance. Establish refresh schedules, permissions, lineage, and auditability rather than assuming conversational access guarantees trustworthy results.
- Validate deployment claims. Ask for evidence using your sources, data volumes, workloads, and operational constraints; a customer’s reported sub-30-day implementation is not a general benchmark.
- Separate strategic acquisition value from standalone success. A larger vendor may value technology for a different product direction—in this case, Progress’s cognitive-application and predictive-maintenance plans—without demonstrating that the original startup proposition prevailed on its own.
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
