
Obviously AI.
The company that made predictive machine learning accessible to business users—and the story of its evolution into Zams, an enterprise AI-agent platform, before an announced 2026 wind-down.
Obviously AI publicly rebranded to Zams on 11 February 2025. Co-founder Nirman Dave announced in August 2026 that Zams (previously Obviously AI) was winding down. Older pages at obviously.ai still load, but their signup offers, price information, features and compliance claims must not be mistaken for current service availability. [1][2][3]
Obviously AI at a glance
Obviously AI was a San Francisco-based, privately held B2B software venture. Its original product let non-programmers train predictive models on structured business data. Its successor, Zams, focused on orchestrating AI agents across sales and revenue workflows. The original company’s exact legal name remained Obviously AI, Inc., trading as Zams in 2026. [4][5]
| Legal entity | Obviously AI, Inc. — Delaware corporation; Doing Business As: Zams (as documented April 2026) |
|---|---|
| Brand evolution | Obviously AI → Zams (11 February 2025) → wind-down announced August 2026 |
| Founders | Nirman Dave; Tapojit (Tapu) Debnath |
| Headquarters / business address | San Francisco, California, United States; 55 Francisco Street in April 2026 Zams terms |
| Founded | 2018 project/company work; February 2020 public beta. Some company listings report 2020 as founding year. |
| Corporate form | Privately held, venture-backed; no publicly verified acquirer or parent for Obviously AI, Inc. |
| Original focus | No-code predictive analytics, automated machine learning, assisted data science |
| Later focus | Agentic AI, natural-language workflow automation, sales/revenue operations |
| Original website | obviously.ai (legacy pages) |
| Successor brand website | zams.com (may remain reachable after wind-down) |
| Former support / contact | info@obviously.ai (legacy privacy policy); info@zams.com (April 2026 privacy policy); current responsiveness unverified |
| Public shares / market capitalization | Not applicable: a privately held company; valuation not publicly confirmed |
| Employees / active paying customers | Reliable current counts not publicly disclosed |
Evidence: Zams terms, founders' college announcement, original company page and 2025 rebrand statement. [4][6][7]
About Obviously AI
Short company description (55 words): Obviously AI was a no-code predictive analytics company that helped business users create machine-learning models from historical data without programming. Teams could upload or connect structured datasets, choose an outcome such as churn or sales, examine results, and generate predictions. The company later shifted toward automated AI agents under the Zams brand before announcing its wind-down in 2026.
The old problem
Business analysts knew their customers, sales and operational datasets, but needed data scientists and engineers to convert that information into production-ready predictive models.
The company's answer
Automate model selection and tuning, give business users an understandable interface, then let teams use predictions through reports, shareable apps, integrations and APIs. [8]
Traditional BI primarily describes past performance through dashboards and metrics. Obviously AI sought to answer what is likely to happen next using supervised learning. That does not make its historical no-code models interchangeable with modern LLM-based agents.
Who founded Obviously AI?
Nirman Dave and Tapojit Debnath met at Hampshire College. Dave had worked on customer-behavior prediction at Streamlabs; Debnath had machine-learning experience at retail startup b8ta. Their combined experience shaped the original user-friendly AutoML product. Hampshire College says they started the venture in 2018. [6][9]

| Founder | Historical leadership | Background | 2026 status |
|---|---|---|---|
| Nirman Dave | Co-founder and CEO | Hampshire College; behavioral economics and ML studies; Streamlabs internship; early educational-electronics venture CircuiTricks | Named founder/CEO on Zams pages before the 2026 wind-down; ongoing role following wind-down not established |
| Tapojit (Tapu) Debnath | Co-founder and CTO | Hampshire College; technical/product development; b8ta ML internship | Historically verified CTO; precise position at the wind-down could not be independently verified |
Leadership beyond the founders
The public sources checked do not support a complete current 2026 leadership roster. Historic CEO and CTO titles should not be presented as active appointments after the announced wind-down. A 2023 SEC filing identifies the two founders among company officers and Kiran Mysore Ravi as a director; a 2021 financing announcement says TMV took a board role. Later full board composition is not publicly confirmed. [10][11]
Founding story and company history
The founders saw a mismatch: business users were asking predictive questions, but existing tools were built for programmers. They developed the idea together at Hampshire, then worked in an Airbnb basement in the Bay Area as the company took shape. The startup passed through UC Berkeley SkyDeck before moving from beta toward a commercial product. [6][9]
Hampshire College documents Dave and Debnath beginning work on Obviously AI, rooted in their student projects and data-science internships.
The company's 2021 announcement explicitly dates its public beta to February 2020.
TMV led; B Capital Group, Golden Gate Ventures and Arka Venture Labs participated. The company said the service was exiting beta.
UTEC led a reported extension, with existing investors participating. The $4.7M figure includes the previously announced $3.6M rather than representing an entirely separate additional $4.7M.
A November SEC Form D records a private securities offering; O'Shaughnessy Ventures announced an investment in December. Specific investor allocation was not disclosed.
The business publicly repositioned from predictive modeling toward AI agents for sales and revenue workflow automation.
Zams published an article by Nirman Dave about AI workers, its latest dated product-focused article identified in this review.
Nirman Dave publicly stated that the team was winding down Zams, previously Obviously AI. No formal dissolution date is asserted here.
Products and features: past versus later
Obviously AI predictive AutoML
Browser-based no-code ML: ingest structured data, choose a target field, build and compare supervised models, inspect feature importance, share reports, run batch or live predictions, and expose REST endpoints. Human data-science support was offered alongside software.
Output: classification scores, numerical predictions, time-series forecasts, model reports, apps and APIs. [7][14]
Zams AI agents
Natural-language orchestration of business tasks and workflows across workplace systems, with a focus on sales/revenue teams, CRM hygiene, account research and operational automation. Rather than only predicting an outcome, an agent could take configured steps in business software.
Output: executed workflows, updated records, summaries, task automations and operational reporting. [1][4]
Self-service, managed service, or enterprise platform?
Answer: a hybrid model over time. Obviously AI combined no-code SaaS with optional hands-on data science; 2024–2025-era pricing pages offered software plus dedicated data-scientist and strategist support. Zams subsequently emphasized enterprise agent orchestration and sales-led deployment. It was not exclusively a simple spreadsheet-to-model app, nor solely a consulting firm. [14]
How Obviously AI built a predictive model
Historical company documentation describes a supervised machine-learning workflow, where historical records include the outcome to be learned. A user did not need to write Python, but still needed a meaningful target variable and correctly structured business data. [15][8]
CSV, tables, database or connected source
Churn, loan outcome, sales or another labeled value
Shortlist, tune and evaluate candidate approaches
Report, what-if view, shareable app, API or integration
Data requirements and input methods
The 2021 data-requisites page recommended one structured table or file, at least 1,000 rows and five columns, and an identifiable target/outcome column. Its CSV guide specifies a 25 MB file limit for that particular historical workflow; this is not a universal data cap across all later plans. Personally identifying information was not required. [15]
| Input method | Documented evidence | Interpretation |
|---|---|---|
| CSV file | Legacy pricing + data requirements | Confirmed historical upload path |
| Spreadsheet | 2021 company product explanation | Confirmed general import category; exact Excel/XLSX entitlements unverified |
| Database | 2021 data requirements and company announcement | Confirmed historical connection pathway; specific vendor list not comprehensively verified |
| CRM | 2021 company announcement | General CRM connectivity reported; individual native connectors need verification |
| Cloud warehouse and SaaS app | Historical marketing mentions integrations | Do not infer Snowflake, BigQuery or HubSpot native connectors without per-product evidence |
AutoML technology and algorithms
Obviously AI described its proprietary Edge Sharp AutoML pipeline as extracting dataset characteristics (including data types, dimensions, sparsity and variance), shortlisting five suitable algorithm families, testing hyperparameter configurations and choosing a model on reported accuracy/performance. Its publicly described model-search counts and speed are company-reported marketing claims, not independent benchmark results. [16]
Dataset profiling
Detects numeric, categorical and date/time feature characteristics and potential missing values.
Model search
Prioritizes candidate algorithms and tunes settings rather than requiring manual experimentation.
Evaluation & delivery
Presents a selected model, metrics and explanatory business-oriented reporting.
Which algorithms were actually documented?
The official algorithms page confirms multiple machine-learning algorithms and tuning but presents the specific list within an image that could not be reliably transcribed for this review. It would be misleading to state that XGBoost, LightGBM, CatBoost, random forests, logistic regression or neural networks were each available without separately verifiable documentation. [16]
| Algorithm or capability | Evidence status | Notes |
|---|---|---|
| Edge Sharp AutoML and automated hyperparameter search | Company-confirmed | High-level method disclosed in official documentation |
| Classification / regression / time series | Company-confirmed | Problem families, not specific algorithms |
| Five shortlisted candidates | Company-reported | Described in 2023 algorithms document |
| Random forest / gradient boosting / XGBoost / LightGBM / CatBoost | Could not be independently verified | Do not assume use from the word “AutoML” |
| Neural networks and generative foundation models inside predictive stack | Not publicly established | No verified architecture or serving-provider inventory |
Explainability and performance
Official material described influence of underlying factors, shareable model reports and what-if simulations. These are useful explanations of correlation and model behavior, not proof of causal effect. Accuracy was discussed for classification; a complete historical checklist of F1, precision, recall, AUC, RMSE, MAE, R², confidence intervals and drift dashboards could not be verified across every plan. Always evaluate validation design and holdout performance before relying on a result. [10][17]
Prediction types and real-world uses
| Prediction family | Required historical input | Typical output | Business example | Verified? |
|---|---|---|---|---|
| Binary classification | Past records labeled yes/no | Probability or predicted class | Customer churn, loan default, lead conversion | Yes, original homepage |
| Multi-class classification | Historical categorical target | Class label or class probabilities | Classify a customer into one of several outcomes | General classification confirmed; multi-class plan details unverified |
| Regression | Past numeric targets | Numerical value | Deal size, yield, cost, dynamic pricing | Yes, original homepage |
| Time-series forecasting | Ordered timestamps and measurements | Future values over time | Sales in future months | Yes, original homepage; plan-dependent |
| Clustering | Feature data without target | Group assignment | Customer segmentation | Appears in later pricing comparison; legacy general-availability not confirmed |
Classification, regression and time series are explicitly advertised on the original homepage. Individual applications are examples, not guaranteed product performance. [7][14]
Marketing and retention
Team: Growth. Problem: churn. Data: historical activity and subscription history. Prediction: attrition risk. Action: prioritize retention outreach.
Sales and lead scoring
Team: Sales. Problem: too many leads. Data: CRM stages and past conversions. Prediction: lead-to-customer probability. Action: prioritize follow-up.
Finance and lending
Team: Credit operations. Problem: repayment risk. Data: historical repayment features. Prediction: risk score. Action: inform human-reviewed lending decisions, with fairness and regulatory controls.
Operations and pricing
Team: Operations. Problem: uncertain cost/yield. Data: transaction and process history. Prediction: numeric revenue or yield. Action: adjust planning and inventory decisions.
Predictive machine learning versus generative AI agents
Predictive AI (Obviously AI)
Question: “Which customers are likely to cancel?”
Method: Models are trained on labeled historical rows to estimate outcomes. The output is a score, category, number or forecast.
Evaluation: Holdout predictive quality, calibration, drift and business impact.
Agentic AI (Zams)
Instruction: “Update these CRM records and prepare a pipeline briefing.”
Method: A language-driven system uses tools and integrations to plan and carry out operational actions.
Evaluation: Task correctness, permission safety, auditability, cost and completion.
Zams officially positioned itself as an enterprise AI-agent orchestrator, not merely a refreshed version of a regression tool. Its 2026 legal terms document autonomous agents, task automation and knowledge assistants. Exact underlying OpenAI, Anthropic, Google or other foundation models were not established from the official public materials reviewed. Do not assign a specific LLM or model family without disclosure. [1][4]
API, integrations and deployment
The original site explicitly supported hosted shareable model web apps, real-time REST APIs and Zapier automation. The 2021 funding announcement referred to Adalo and Zapier integrations. The official homepage mentioned external presentation of predictions in BI tools such as Power BI and Looker; this does not establish native Power BI or Looker connectors. Developers should not rely on historical endpoints after the wind-down. [7][10]
| Capability / service | Type | Evidence | 2026 status |
|---|---|---|---|
| Shareable prediction web app | Hosted deployment | Official product page | Historical; operational status unknown |
| Real-time REST prediction API | API | Official product page | Historical; developer docs inaccessible |
| Zapier | Automation integration | Official product page, financing release | Historical; no current live test |
| Adalo | App integration | 2021 company release | Historical |
| CSV | Direct data upload | Official requirements | Historical |
| Database / CRM | General connection category | 2021 company release | Exact connector vendors undetermined |
| Power BI / Looker | Analytics visualization destination, cited by website | Legacy marketing | Native connector not independently verified |
| Salesforce / HubSpot / Slack / Gong | Later Zams workflow ecosystem | Zams/third-party agent descriptions | Do not treat as legacy Obviously AI native integration |
| Snowflake / BigQuery / Redshift / Airtable / Shopify | Specific native connector | Insufficient current original-product evidence | Not independently verified |
Developer details: Public API authentication, limits, pricing, SDKs and batch endpoint specifications could not be checked because the historical developer portal was not accessible during this research. REST support is confirmed; a current usable API is not. [7]
Obviously AI pricing — historical, not a live quote
The original pricing page remains reachable and shows a blend of software subscriptions, human-led services and enterprise packages. It does not supply reliably current checkout prices, and it cannot be treated as a live purchasing offer after the 2026 wind-down. [14]
| Legacy advertised tier | Price | Displayed limits / features | Interpretation |
|---|---|---|---|
| Free | Advertised as free | Page mentions 1,200 predictions, one seat, CSV, models; some model families indicated as excluded | Historical advertisement; no live availability verified |
| Startup | No verified public amount | Up to 1 use case, 100 MB files, 1M rows; software + data scientist | Historical / sales-led |
| SMB | No verified public amount | Up to 3 use cases, 1 GB files, 100M rows; dedicated support | Historical / sales-led |
| Enterprise | Custom / contact sales as advertised | Up to 5 use cases, 10 GB files, 250M rows; security/governance features displayed | Historical / sales-led |
Pricing checked: 30 October 2026. These are legacy web-page displays, not confirmed product availability. An earlier 2021 TechCrunch article quoted plans starting at $75/month; that amount must not be represented as a 2026 price. [9]
How did the business make money?
Confirmed historical monetization included paid no-code software tiers, enterprise sales and managed data-scientist/AI-strategist services. Specific 2026 subscription revenue, agent usage fees, gross margin, net revenue retention or annual recurring revenue were not publicly disclosed. The company was therefore best characterized as software plus human data science, later transitioning to an enterprise AI-agent platform.
Funding, investors and ownership
Financing is one area where the date matters. The company announced $3.6 million in May 2021, and TechCrunch reported an expanded $4.7 million cumulative seed in July 2021. A November 2023 SEC Form D supports another financing event, and O'Shaughnessy Ventures announced its investment in December 2023. The later Zams website stated $10 million raised; this is company-reported, not independently audited. [10][9][11][12][5]
| Date | Round / event | Amount | Selected investors | Evidence quality |
|---|---|---|---|---|
| May 2021 | Seed announcement | $3.6M cumulative then | TMV (lead); B Capital, Golden Gate Ventures, Arka Venture Labs | Company press release |
| July 2021 | Seed extension | $4.7M cumulative seed ($1.1M above May figure) | UTEC (extension lead); TMV and B Capital participation reported | Independent TechCrunch reporting |
| November 2023 | Private offering (SEC Form D) | $5.1M amount sold according to filing-derived registry [27]; review original filing for instrument details | Investor allocation not itemized publicly | SEC filing + filing-derived analysis |
| December 2023 | OSV investment announced | Individual check undisclosed | O'Shaughnessy Ventures | Investor press release |
| By 2026 | Aggregate funding claim | ~$10M | Multiple funds and angels | Company-reported; not audited |
Notable backers: TMV, UTEC, B Capital Group, Golden Gate Ventures, Arka Venture Labs, O'Shaughnessy Ventures; older company material also lists Sequoia Scouts and other investment groups. Accelerator: UC Berkeley SkyDeck, documented by TechCrunch. Company ownership percentages, preferred share rights, comprehensive cap table, post-money valuation and founder control are not publicly disclosed. The 2023 private filing is not itself proof of a current valuation. [9][7]
Valuation, revenue and workforce
Current valuation: not publicly disclosed. Annual revenue, ARR, profitability, margin and audited income: not publicly disclosed. Current employee count after the wind-down: not independently verifiable. Company-directory employee or revenue numbers should be marked as third-party estimates, not official financial disclosures.
Customers and historical market traction
Obviously AI's 2021 press release claimed 3,000+ users and 82,000+ models hosted as of May 2021. These are dated, Obviously AI-reported; not independently verified. They should not be described as active paying customers in 2026. The legacy homepage features named endorsements; those are evidence of attributed testimonials, not independently audited ROI. [10][7]
| Organization | Publicly attributed use | Reported outcome | Evidence category |
|---|---|---|---|
| Dai Nippon Printing (DNP), Japan | Marketing and sales analytics; onboarded analysts | Representative said onboarding took hours | Named executive quoted by TechCrunch; customer-reported |
| Learning Leaders | Building AI models | Attributed testimonial about time/cost savings | Legacy website testimonial; not audited |
| Sound AG | Yield prediction | Attributed testimonial about sales process | Legacy website testimonial |
| Max Van Trading | Real-time price prediction | Attributed profitability assertion | Legacy website testimonial; unverified metric |
| Creditt India | Predictive analytics for credit use cases | Ease of integration endorsed | Legacy website testimonial |
| Unnamed Indian microlender | Repayment/default risk modeling | Company published default-reduction and accuracy claims | Official anonymized case study; no independent audit |
A company logo shown under “backed by,” “built by,” “integrations,” or “in the news” is not proof of a customer contract. This table intentionally limits examples to named customer testimonies and explicitly described cases. [7][9][18]
Case-study evidence: lending model
The company's anonymized credit-risk case study reports 100,000 data rows, five days to value, 79.2% prediction accuracy and a 7% decline in defaults. A narrative passage on the same page describes identification of 83% of new likely defaulters, which is a different, insufficiently defined metric. These results are Obviously AI-reported; not independently verified and should not be generalized to other datasets. [18]
Industries and target users
Documented or explicitly marketed sectors include marketing, software/SaaS, direct-to-consumer commerce, fintech, insurance, printing, agriculture/yield and consumer gaming. Its original buyer was often a business analyst, marketer or operating manager with usable structured data but without a machine-learning engineering team. Data expertise still mattered for labeling outcomes, assessing leakage, judging fairness and interpreting model results. [9]
Privacy, customer data and model ownership
The April 26, 2026 Zams privacy policy states that Zams did not use customer data to train its own or third-party AI models without explicit written authorization. It also says customer data was processed to deliver customer-defined tasks, with stated deletion-request procedures. This is a statement of documented policy, not an independent audit of actual processing, and predates the wind-down. [19]
What is documented
- Customer data processing under customer-defined operations (Zams policy).
- No customer-data training of proprietary or third-party models without written authorization (Zams policy).
- Data may be shared with subprocessors under confidentiality conditions.
- Deletion rights and legal retention exceptions are described in the policy.
What remains unclear
- Current support channels and handling of stored data after wind-down.
- Full list of training/inference model vendors.
- Ownership and portability terms for every historical trained model.
- Present-day deletion completion, processor status and service availability.
The older Obviously AI privacy policy was dated February 4, 2025 and was primarily a general website/service privacy notice. It does not by itself establish a comprehensive contractual right to ML-model export or permanent ownership of every trained artifact. Specific contract and DPA terms would be necessary. [20]
Security and responsible AI
Legacy Obviously AI security pages state SOC 2 Type II coverage, encrypted connections (TLS), encryption at rest (AES-256), Google Cloud hosting, GDPR practices and HIPAA/BAA support. The company-reported compliance assertions were posted before the wind-down; independent current certificate validity and applicability to any successor service were not reverified. Data centers holding third-party certifications are not equivalent to the product itself holding the same certification. [21]
General limitations of AutoML
- Biased, missing or unrepresentative data produce biased predictions.
- Label leakage can inflate test accuracy.
- Correlations are not causal explanations.
- Small sample sizes can make scores unstable.
- Shifting user behavior causes model drift.
- Incorrect targets produce misleading optimization.
- High aggregate accuracy can hide poor subgroup performance.
- Business context and ongoing human oversight remain essential.
These are general ML cautions, not evidence of a documented defect uniquely affecting Obviously AI.
Reviews and user sentiment
The G2 product page showed a small historical review sample (four reviews in the results inspected), insufficient for robust market-wide conclusions. Reviewers praised accessible model creation and helpful hands-on data-scientist support; some said configuration knowledge and limited customization could be challenging. These are user-reported experiences, not product-wide measurements. [22]
| Reported positives | Reported drawbacks / qualifications |
|---|---|
| Fast no-code prototyping and intuitive model reports | Users still need to understand the meaning and quality of the dataset |
| Human data-scientist assistance and collaboration | Some additional back-and-forth required for data interpretation |
| Useful starting point for business ML use cases | Less algorithm-level customization than writing custom code |
| Directly actionable predictive workflows | Historical pricing, production availability and support are no longer reliable buying signals |
Competitors and alternatives
Competitors depend on the period: the original Obviously AI competed primarily in no-code predictive modeling, while Zams competed more broadly with workflow and agentic automation. Following its announced wind-down, use this comparison to identify current alternatives, not as a claim that Obviously AI is actively taking new customers.
| Platform | Primary focus | No-code | Predictive ML | AutoML | Forecasting | API | Enterprise | Best suited to |
|---|---|---|---|---|---|---|---|---|
| Obviously AI (legacy) | Self-service predictive ML | Yes | Yes | Yes | Yes | Yes | Sold to teams | Historical; no longer a safe new-buy recommendation |
| Akkio | AI workflows for agencies, data and campaigns | Yes | Yes | Yes | Yes | Yes | Yes | Marketing/agency predictive workflows |
| Pecan AI | Business predictive agent | Yes | Yes | Yes | Yes | Yes | Yes | Churn, LTV, demand, growth forecasting |
| DataRobot | Enterprise predictive AI platform | Visual options | Yes | Yes | Yes | Yes | Yes | Larger ML/MLOps programs |
| Dataiku | Governed analytics, AutoML and agents | Visual options | Yes | Yes | Yes | Yes | Yes | Cross-functional enterprise AI |
| H2O.ai | Enterprise AI/ML | Varies by product | Yes | Yes | Varies | Yes | Yes | Technical/enterprise predictive AI |
| Power BI / Tableau | BI and reporting | Yes for reporting | Limited / adjacent | Not core equivalent | Built-in forecasting options | Yes | Yes | Dashboards and descriptive analytics |
The comparison is high-level, based on official platform positioning; specific plan access varies. See vendor sources for Akkio, Pecan, DataRobot and Dataiku. [23][24][25][26]
Obviously AI vs Akkio
Both historically served non-coders with predictive modeling. Akkio now also emphasizes AI-native marketing workflows, connected data, natural-language analysis and forecast/predict functions. For a business purchasing software in 2026, Akkio is a live-market alternative to investigate rather than a simple feature-for-feature successor. [23]
Obviously AI vs Pecan AI
Pecan similarly emphasizes churn, conversions, lifetime value, demand and revenue predictions without a dedicated data-science team, and describes automated data preparation, modeling, validation and deployment. Compared with the historic Obviously AI self-service UI, Pecan's 2026 positioning is closer to an outcome-focused predictive agent. [24]
Obviously AI vs DataRobot
DataRobot positions its offering around enterprise-scale model development, tuning, explainability, operational monitoring, deployment and governance. Its broader MLOps depth may suit mature data teams, while Obviously AI originally prioritized rapid self-service access for comparatively nontechnical buyers. [25]
Obviously AI vs Dataiku
Dataiku combines visual/no-code and full-code ML with collaborative preparation, AI agents and enterprise governance. This is a wider platform category, with greater implementation scope than the original Obviously AI model-building experience. [26]
Obviously AI vs Power BI / Tableau
BI dashboards answer “What happened?” using metrics and visualization. Predictive ML answers “What is likely to happen?” based on a trained model. BI products do support forecasting and extensions, so the boundary is not absolute; they are not exact one-to-one replacements for supervised AutoML in every scenario.
Strengths, limitations and who it suited
Evidence-supported strengths
- Accessible no-code supervised learning for structured data.
- Classification, regression and time-series problem support.
- Shareable reports and web-app-style inference.
- Real-time REST API capabilities advertised.
- Human data-scientist support alongside software.
- Documented founder and investor history.
Material limitations
- Business status changed: Zams wind-down announced 2026.
- Old prices and signup links are not verified active offers.
- Model architecture and named LLM providers not fully disclosed.
- Human input still needed for labeling and validation.
- Specific integrations and plan limits changed over time.
- High-stakes predictions still require governance and expert review.
Historically best for: business analysts, marketing and sales teams, operations staff, founders and SMBs with clean-enough tabular data and well-defined labels. Historically less suitable for: teams requiring custom deep-learning architectures, absolute control over every ML pipeline stage, or heavily regulated production without additional safeguards. For new buyers in late 2026: assess currently operating alternatives instead of treating archived Obviously AI pages as an active vendor offer.
Frequently asked questions
Short answers are based on dated evidence; a remaining legacy webpage is not a guarantee of commercial availability.
What is Obviously AI?
A former no-code predictive analytics and AutoML platform for turning structured historical data into predictions; it later rebranded as Zams.
Who founded Obviously AI?
Nirman Dave and Tapojit (Tapu) Debnath, documented by their college and company announcements.
When was Obviously AI founded?
The founders began work in 2018; public beta launched in February 2020. “Founded 2020” in some profiles reflects the launch period.
Where was the company based?
San Francisco, California. Its 2026 successor terms gave 55 Francisco Street as principal place of business.
Who owned Obviously AI?
Obviously AI, Inc. was a private, venture-backed Delaware corporation. Exact shareholder percentages were not publicly disclosed.
Does Obviously AI still operate?
The founders announced Zams (previously Obviously AI) would wind down in August 2026. A formal legal dissolution date was not verified.
Was Obviously AI really no-code?
Its main model-building interface required no programming, but users still needed domain knowledge, appropriate data labels and critical model evaluation.
What predictions did it support?
Classification, regression and time-series forecasting were explicitly advertised on its original site; some features were plan dependent.
Could it forecast sales?
Yes, the historical product described regression and time-series forecasting for sales and related business outcomes.
What was Edge Sharp AutoML?
The company's documented approach to profiling data, shortlisting algorithms, tuning settings and selecting predictive models.
Which algorithms did it use?
It described multiple algorithms and automatic tuning; a full machine-readable verified list of exact model families was not established in this review.
Was Obviously AI generative AI?
The original product centered on predictive ML. Its later Zams offering used AI-agent and natural-language workflow positioning, a different product category.
Did it have an API?
The historical site documented real-time REST prediction APIs. Live access and developer documentation are unverified after wind-down.
What integrations did it offer?
Zapier and Adalo were documented historically; general CRM/database connections were discussed. Other named native integrations require case-by-case proof.
Was there a free plan?
The legacy pricing page displayed a free tier. Post-wind-down service availability is not confirmed.
How much did it cost?
A 2021 report cited a $75/month starting point. Later legacy pages were partly sales-led; no reliable current price exists after the wind-down.
Did it provide data scientists?
Yes. Company pages and historical user reviews describe a software-plus-human-data-science model.
Which companies used Obviously AI?
Named historical evidence includes Dai Nippon Printing and customer testimonials from Learning Leaders, Sound AG, Max Van Trading and others.
How much funding did it raise?
Its 2026 successor website claimed about $10 million. This is a company-reported cumulative figure, consistent with historical disclosed rounds but not audited.
Who invested in it?
Documented investors include TMV, UTEC, B Capital, Golden Gate Ventures, Arka Venture Labs and O'Shaughnessy Ventures.
What was Obviously AI valued at?
No reliable current company valuation was publicly disclosed in the sources reviewed.
What is Zams?
Zams was Obviously AI's 2025 successor brand, focused on AI agents that could act across sales and business workflows.
Did the company train AI on customer data?
Zams' April 2026 privacy policy said it did not use customer data to train its own or third-party AI models without written authorization. This is a policy claim, not an audit.
Was the product SOC 2 / HIPAA compliant?
Its historic security pages claimed SOC 2 Type II, GDPR practices and HIPAA/BAA capabilities. Current audit validity after wind-down was not established.
What are the closest alternatives?
For historical no-code predictive workflows, evaluate Akkio and Pecan AI; for broader enterprise ML, compare DataRobot and Dataiku.
Is Obviously AI better than Akkio?
There is no universal winner. Obviously AI's status is historical after the wind-down; Akkio is a currently marketed platform with more recent workflow and predictive features.
SEO details for Artificial Intelligence Files
| Recommended SEO title | Obviously AI Company Profile 2026: Founders, Funding & Zams |
|---|---|
| Alternative title 2 | Obviously AI: Founders, Products, Funding & 2026 Status |
| Alternative title 3 | Obviously AI Company History: No-Code AutoML to Zams |
| Alternative title 4 | Obviously AI: Predictive Analytics, Pricing & Competitors |
| Alternative title 5 | Obviously AI Profile: AI Technology, Customers & Investors |
| Primary keyword | Obviously AI |
| Suggested slug | /companies/obviously-ai/ |
| Suggested meta description | Explore Obviously AI's founders, funding, no-code AutoML platform, customers, pricing history, 2025 Zams rebrand, and 2026 wind-down, with verified sources. |
| Supporting terms | Obviously AI founders, Obviously AI funding, Obviously AI pricing, Obviously AI AutoML, Obviously AI alternatives, Zams AI agents, no-code predictive analytics |
Suggested internal-link topics: Obviously AI Tool Profile, Obviously AI Case Studies, No-Code AI Tools, AutoML Companies, Akkio, Pecan AI, DataRobot and Dataiku. These are topic suggestions, not clickable URLs, because the target pages on Artificial Intelligence Files were not independently checked for existence.
Sources and references
Each entry identifies publisher, title, date and original URL. Access/review date for all sources: 30 October 2026. Undated marketing pages are explicitly identified as such; names and dated statements are not assumed to remain true indefinitely.
- [1] Zams — “Introducing Zams”Nirman Dave / Zams · 11 Feb 2025 · official rebrand
zams.com/blog/introducing-zams - [2] Nirman Dave — personal announcement of wind-downNirman Dave · August 2026 (month corroborated by contemporaneous coverage) · first-person statement
LinkedIn founder announcement - [3] YesPress — “Obviously AI Put a Data Scientist in a Button”YesPress Editors · Aug 2026 · retrospective secondary reporting
yespress.io/products/obviously-ai - [4] Zams — Terms of UseZams · Updated 26 Apr 2026 · legal entity, Delaware status and location
zams.com/terms-of-use - [5] Zams — About UsZams · undated live page · company-reported $10M and leadership
zams.com/about-us - [6] Hampshire College — Founders and $4.7M seedAmy Diehl · 12 Aug 2021 · primary alumni report and founder photograph
Hampshire College news - [7] Obviously AI — Original websiteObviously AI · legacy site, copyright 2025 · historic features and customer testimonials
obviously.ai - [8] Obviously AI — “How No-Code Machine Learning Algorithms Work”Jack Riewe · 14 May 2020 · company technical explainer
obviously.ai/post/how-no-code-machine-learning-algorithms-work - [9] TechCrunch — “Obviously AI … increases seed round to $4.7M”Catherine Shu · 5 Jul 2021 · independent reporting and founder interview
TechCrunch article - [10] Obviously AI — $3.6M seed announcementObviously AI / GlobeNewswire · 3 May 2021 · company press release
GlobeNewswire press release - [11] U.S. SEC — Obviously AI, Inc. Form DSEC EDGAR · 15 Nov 2023 · primary corporate filing
SEC filing detail - [12] O'Shaughnessy Ventures — Investment announcementO'Shaughnessy Ventures / PR Newswire · 15 Dec 2023 · investor announcement
PR Newswire release - [13] Zams — Blog indexZams · latest product-specific dated post identified: 23 Jun 2026
zams.com/blog - [14] Obviously AI — PricingObviously AI · undated legacy page checked 30 Oct 2026 · historical offer limits
obviously.ai/pricing - [15] Obviously AI — Data RequisitesObviously AI · 12 Apr 2021 · structured data requirements
obviously.ai/data-requisites - [16] Obviously AI — AlgorithmsObviously AI · updated 9 Aug 2023 · Edge Sharp AutoML method
obviously.ai/algorithms - [17] Obviously AI — “How We're Democratizing Data Science for SMBs”Obviously AI · historical founder discussion · model validation
Founder discussion - [18] Obviously AI — “Predict Default Rate”Obviously AI · undated official case study · anonymized, unverified outcome metrics
obviously.ai/case-studies/predict-defaults - [19] Zams — Privacy PolicyZams · updated 26 Apr 2026 · customer-data training statement
zams.com/privacy-policy - [20] Obviously AI — Privacy PolicyObviously AI · updated 4 Feb 2025 · legacy data handling disclosures
obviously.ai/privacy-policy - [21] Obviously AI — SecurityObviously AI · official security claims, page carries 2022 and 2024 update labels
obviously.ai/security - [22] G2 — Obviously AI historical product reviewsG2 · reviews dated 2022–2023 · small reviewer sample
G2 user reviews - [23] Akkio — Predictive AI productAkkio · official product page, live 2026 · comparison source
akkio.com/predict - [24] Pecan AI — Predictive AI AgentPecan AI · official product page, live 2026 · comparison source
pecan.ai - [25] DataRobot — Predictive AIDataRobot · official product page, live 2026 · comparison source
DataRobot predictive AI - [26] Dataiku — Product platformDataiku · official product page, live 2026 · comparison source
Dataiku product platform - [27] Fundraising Fox — SEC Form D derived financing summaryFundraising Fox · researched Aug 2026 · third-party filing-derived reading; cross-check SEC
fundraisingfox.com/companies/obviously-ai
Research notes and disclosure
| Research cutoff | 30 October 2026 |
|---|---|
| Pricing verification | 30 October 2026 — legacy page accessible, live sales availability not confirmed |
| Latest dated product post found | 23 June 2026 (Zams blog); not proof of later product activity |
| Latest confirmed public corporate funding event | 2023 SEC Form D / December 2023 investor announcement; $10M aggregate company-reported on later Zams site |
| Latest publicly confirmed valuation | Not publicly disclosed |
| Founding date ambiguity | Work began in 2018; public beta February 2020; datasets sometimes use 2020 as founded year |
| Funding ambiguity | 2021 $3.6M was expanded to $4.7M, not a separate $4.7M round; ~2023 $5.1M filing consistent with total near $10M |
| Current corporate status | Founder-announced wind-down in August 2026; independent verification of legal dissolution not available |
| Models / technical stack | Edge Sharp high-level method documented; precise historical algorithm inventory and exact LLM service providers not independently verified |
| Customers / performance | Named testimonials and 2021 user/model counts are historic company/customer-reported claims; no audited current customer metrics |
| Security | Legacy SOC 2/HIPAA/GDPR assertions sourced to company security site; present audit validity not independently confirmed |
| Inaccessible resources | Legacy developer portal returned an error and help center timed out; API authentication/limits and latest support terms not independently validated |
| Independence | Original research summary; no paid placement or sponsorship claimed |
Editorial standard: “Verified” means supported by a cited primary document or independently corroborated reporting, not that every historical marketing claim was independently tested. Public vendor sites remain accessible after businesses close and may retain old offers; always follow dates and claim classifications. Information reflects the sources reviewed, not investment or purchase advice.