Figma just published a video with OpenAI showing how its internal data team built a "Figma Data Assistant" â a self-serve analytics system powered by OpenAI that lets any Figma employee ask data questions in plain English. No SQL. No Jira ticket to the data team. No waiting three weeks for a dashboard that answers the wrong question.
đ Read the full version with charts and embedded sources on ComputeLeap â
Meanwhile, Ramp announced its $750 million Series F at a $44 billion valuation and dropped a number that should stop every CTO mid-sip: its internal AI tool "Inspect" now writes two-thirds of Ramp's production code, and an AI workspace called "Glass" has driven the company to 99.5% AI adoption across all employees â not just engineers.
These aren't isolated product announcements. They're symptoms of the same structural shift: AI has collapsed the skill barrier between "user" and "builder," and every department in your company is becoming an engineering team whether you planned for it or not.
The Three Convergence Streams
Three trends that looked independent two years ago have merged into a single current.
1. Design Tools Became Everyone's Tools
Figma reported that two-thirds of its monthly active users are non-designers. Its CEO Dylan Field frames this as intentional: design is becoming "the new code" for product teams. The company's Q2 2026 earnings showed that over 80% of paid customers with more than $10,000 in ARR were consuming AI credits weekly.
But the more revealing signal is what Figma is building internally. Their Self-Serve Analytics initiative â a multi-phase program covering semantic layer expansion, a Slack bot, an automated evaluation framework, and the "Figma Data Assistant" â is designed to move every team away from filing data requests toward answering their own questions.
This isn't a design company adding a chatbot. It's a design company rebuilding its own operating model around the assumption that non-technical employees can and should be self-sufficient with data.
2. Finance Went Full Engineer
Ramp's trajectory makes the pattern even clearer. At the AI Engineer conference, Alexander Shevchenko presented how Ramp built a smaller, fine-tuned model that beat Claude Opus on finance-specific tasks â not as a research experiment, but as a production system powering the agentic analysis, FP&A, and book-close experiences used by more than 70,000 businesses.
The company's investor materials from ICONIQ describe AI token spend management, real-time budget tracking across every team, and procurement agents that automate purchasing from request to payment. This is a finance platform that has essentially turned its entire product into an engineering system â and expects its customers' finance teams to operate it like one.
Even the job postings tell the story. Figma is hiring a "Strategic Finance, AI Innovation" role. The description? Influencing the finance team's AI adoption strategy, with AI used for analysis, reporting, and forecasting. Not "finance analyst who uses Excel." Finance engineer who builds with AI.
3. The Citizen Developer Population Exploded
The macro numbers confirm what the case studies suggest. According to aggregated analyst data, there are now 16.2 million citizen developers worldwide â people whose primary job title isn't "developer" but who build applications, automations, and analytics with no-code and low-code tools. That's against 28.7 million professional developers.
âšī¸ The citizen developer population has hit 16.2 million worldwide â roughly one citizen developer for every two professional developers. Gartner projects 70% of new enterprise applications will use no-code or low-code tools. Financial services leads adoption at 82%.
Low-code platform revenue hit $65 billion in 2026 and is projected to reach $94 billion by 2028. The most common citizen developer roles? Operations managers (24%), marketing managers (19%), and sales managers (16%) â not a single engineering title in the top three.
What Makes This Wave Different
If you've been in tech long enough, you've heard "the end of coding" before. COBOL was supposed to do it in 1960. Visual Basic in 1995. Dreamweaver in 2000. Low-code in 2018. Each wave crashed on the same rocks: maintenance, debugging, and the irreducible complexity of translating business logic into reliable systems.
So why should this time be different?
AI Changes the Maintenance Equation
The classic failure mode of citizen development is the dashboard graveyard â tools that get built in a burst of enthusiasm and abandoned when the original builder moves on or the data source changes. As Lei Tang, formerly of Lyft's data science team and now CTO of Fabi AI, put it in Data Neighbor, the graveyard is "a monument to wasted effort."
View original post on Substack â
AI analytics tools â what Tang calls "Vibe Analytics" â attack this differently. Instead of requiring users to learn a query language or build a dashboard that crystallizes one moment's understanding, they let users ask questions in natural language against a governed semantic layer. The "dashboard" is ephemeral; the governance layer is permanent.
This doesn't eliminate the maintenance problem. But it shifts it from "who maintains 200 dashboards?" to "who maintains the semantic model?" â and that's a much more tractable engineering challenge.
The Governance Layer Is the Real Product
Here's the non-obvious insight: the companies winning at self-serve analytics aren't the ones with the best chatbot. They're the ones with the best data contracts.
Figma's Self-Serve Analytics program doesn't start with the AI assistant. It starts with semantic layer expansion â defining, in a machine-readable way, what every metric means, where the data comes from, and what the authoritative source is. The AI is the interface. The semantic layer is the product.
Zack Martin makes this point clearly: "Self-service tools, when implemented correctly, automate the simple stuff, freeing you up for the work that truly leverages your expertise." The operative phrase is "when implemented correctly" â and the implementation is all governance.
View original post on Substack â
The Community Isn't Buying It (Yet)
The practitioner community is deeply split on whether this wave will stick. On Hacker News, a recent thread asking about low-code's relevance in the age of Claude captured the divide perfectly.
On one side, muzani called low-code hackathons from 2024 "effectively dead" and described using Claude to turn a phone photo of hand-drawn boxes into a working UI. On the other, codingdave argued that "most non-technical builds fail, and professional teams eventually have to fix the few that succeed."
The skepticism has deep roots. The classic HN thread on "The No-Code Delusion" â 385 points, 323 comments â still resonates six years later. brazzy noted that "claims of no more programmers date back to COBOL around 1960." swalsh compared no-code solutions to "asking your user to communicate using pictographs."
â ī¸ Contrarian Corner: Every self-serve analytics wave has delivered dashboard graveyards, not data-driven cultures. AI makes building faster, but it doesn't solve the real problems: maintenance, governance, and the gap between "I built a thing" and "this thing works reliably in production." The departments "becoming engineering" might actually be becoming bad engineering â all the building, none of the discipline.
The drrob comment in the low-code thread captures a sentiment that doesn't show up in vendor marketing: "I use Retool for internal tools. I want a quiet life." Not everyone building is trying to replace engineering. Some just want to stop waiting for engineering to get to their ticket.
On Reddit, the analytics community has been debating what self-serve actually means in practice. One practitioner noted that real self-serve access is usually limited to "one or two very specific and clean data sources, not the entire warehouse." Another asked when self-serve analytics turns into an excuse for unmanaged technical debt.
A separate r/analytics thread pushed back harder: "nobody has the time to self-serve on top of their actual job responsibilities." The concern isn't capability â it's bandwidth. Even when the tools work, the people using them still have day jobs.
What This Means for You
Whether you're a CTO, an engineering manager, or an individual contributor, this convergence has concrete implications.
If You Lead Engineering
Your job just expanded. You're no longer responsible only for what your team builds. You're responsible for the governance infrastructure that makes it safe for everyone else to build. That means:
- Semantic layer as infrastructure. Invest in a machine-readable definition of every metric in your organization. Tools like dbt's semantic layer, Cube, and Metriql exist for this. This is your highest-leverage investment.
- Data contracts between teams. When marketing builds a self-serve dashboard, what's the SLA on the underlying data? Who gets paged when it breaks? Define this now, not after the third incident.
- Review processes for citizen-built tools. Not full code review, but lightweight governance. Does this tool access PII? Does it create a new source of truth that contradicts an existing one?
If You're an Analyst or Data Professional
Your job is evolving, not dying. As Zack Martin argues, self-serve analytics absorbs the simple requests â "what were last week's sales?" â and frees you for root-cause analysis, predictive modeling, and A/B test design. The analysts who resist self-serve are protecting the least valuable part of their role.
The new critical skill isn't writing SQL. It's designing the semantic models and governance frameworks that make AI-powered self-serve reliable.
If You're a Non-Technical Team Lead
Start building, but build on governed foundations. The worst thing you can do is treat AI analytics tools like a personal spreadsheet â no documentation, no shared definitions, no maintenance plan. Before you build your first self-serve dashboard:
- Ask your data team: "What's the canonical source for this metric?"
- Build on the semantic layer, not raw tables
- Document what you built and who owns it when you move on
đĄ The new critical hire isn't more analysts â it's analytics engineers who build guardrails for non-engineers. Companies like Figma and Ramp aren't succeeding because they gave everyone AI tools. They're succeeding because they built the governance infrastructure first.
The Prediction
Within 18 months, the companies that invested in semantic layers and data contracts will have genuinely self-serve analytics across every department. The companies that just handed out AI chatbot licenses will have a new generation of dashboard graveyards â faster to build, just as fast to abandon.
The future isn't every department becoming engineering. It's every department consuming engineering â infrastructure, governance, contracts, reliability. The departments that thrive will be the ones that understood this distinction early.
Figma and Ramp aren't just building products for this future. They're reorganizing themselves around it. The question for every other company is whether they'll build the governance layer before or after the dashboard graveyard fills up.
For more on how AI is reshaping team structures and productivity, see our guides on vibe coding for founders, how small teams beat large ones with AI agents, and the deskilling debate.
Originally published at ComputeLeap
Top comments (0)