Software That Never Breaks: OutSystems CEO Woodson on Building Enterprise-Grade Apps at AI Speed
Summary
OutSystems’ AI thesis is that faster code generation only matters if enterprises can preserve the promise that software “never breaks.” Coding agents work against an abstract model of application intent, after which the platform deterministically generates software with security, role-based access, reuse, and governance built in. For investors, the proposed moat is not merely superior generation—it is 25 years of primitives and customer trust that AI-native startups cannot reproduce quickly.
AI has already produced a step-change in OutSystems’ development velocity: four major features in Q4 became 19 in Q1 and 26 in Q2. Token spending peaked in June and July, then declined after the company introduced internal tooling and an LLM gateway that routes work away from frontier models such as Opus 4 when cheaper models suffice. Martin also says some tasks are better handled by deterministic code. His conclusion is that enterprises can return to using “AI in everything,” but only if they do it intelligently.
Enterprise AI adoption is being constrained less by model capability than by governance, liability, and organizational “ossification.” Martin sees completed agent systems sitting in compliance queues while companies investigate model-training provenance, data permissions, and auditability—even when the task is merely extracting structured data from PDFs. The constraint is rational in lending and other high-stakes regulated decisions, but partly “old-fashioned conservatism” elsewhere.
AI is turning legacy modernization from a six-year proposition into a six-month one, potentially unlocking a backlog that enterprises previously refused even to contemplate. AI can help interpret COBOL, AS/400, and Lotus Notes systems, rewrite requirements, build replacements, test them, and support deployment. Simpler work is becoming self-service—“Hey, Claude, take this spreadsheet, make me a dashboard”—creating a second opportunity around standardizing the resulting sprawl.
The most important enterprise-agent question is still not how to build, but “what exactly to do.” OutSystems’ new “agent factory” analyzes application telemetry, architecture, and data flows to propose which manual workflows should become agentic, estimate time savings and ROI, and generate an initial implementation. That shifts the platform’s value proposition from development acceleration toward capital allocation and workflow redesign.
Martin expects software interfaces to fragment rather than collapse into a universal chatbot. Conversational agents may invoke small, contextual interface elements, but maps, regulated bank workflows, and other visual or privacy-sensitive experiences will still need purpose-built software. His example is a $30,000 pre-approved loan initiated in a Claude conversation and continued seamlessly inside a bank app, with one agent spanning both contexts.
As every software vendor accumulates the same AI primitives, competitive advantage should migrate toward specialization and execution inside particular industries. Martin calls the current market an “ocean of the same,” where Highway 101 billboards contain the same five words under different logos. OutSystems intends to differentiate through regulated-industry capabilities, model and cost optimization, and expertise in banking, insurance, government, healthcare, transportation, logistics, energy, and utilities.
Deep dive
1. OutSystems’ original promise has become more valuable in the AI era
Woodson Martin traces the company back to Paulo Rosado’s 2001 frustration with enterprise projects that ran years late, exceeded budgets, and produced rigid systems requiring another major project whenever the business changed. Rosado’s answer was deceptively simple: “build faster, reliably every time,” then evolve software at business speed without breaking it.
Martin argues that generative AI strengthens rather than supersedes that founding premise. When agents can produce vastly more software, enterprises inherit vastly more systems to secure, operate, and change; consequently, the “never breaks” requirement becomes more—not less—important.
The leadership fit combined continuity with scale experience. After 18 years at Salesforce across European marketing, the core sales product, and HR leadership, Martin believed he knew “ways we could turn on the afterburner,” while preserving the platform foundations and unusually strong customer attachment that drew him to OutSystems 16 months earlier.
2. Enterprise-grade AI begins beneath the generated code
OutSystems takes a different route from conventional AI coding tools: agents manipulate an intermediate abstraction of application intent rather than directly editing the eventual code. The platform then generates the asset deterministically, carrying forward role-based access control, security requirements, reusable components, and existing enterprise controls.
Martin’s concrete test is whether a company must recreate GDPR- or HIPAA-compliant controls for every new application. His preferred model is to “take what works, add the necessary features,” and move into production knowing that every generated asset inherits the organization’s established controls.
The platform’s range is illustrated by two sharply different workloads: Asian banking apps used for balances and bill payment, and a Rotterdam oil-terminal system that prevents diesel from entering pipes previously carrying kerosene. The latter coordinates pumping, quality control, cleaning, and flushing around products worth millions of euros.
Labenz’s pushback—worth keeping—is that fast-growing model providers have shown enterprises will tolerate weaker conventional uptime when a product has enough “flavour.” Martin’s answer is that critical autonomous workloads remain different: availability matters, but so do privacy, contractual obligations, data lineage, model permissions, and provable control over every step of a six-system workflow.
3. Compliance queues reflect both legitimate risk and institutional inertia
Martin sees sophisticated agent systems waiting for approval to use a particular model while compliance teams ask whether its training data was legally obtained. Even PDF-to-structured-data systems can stall because enterprise readiness now includes model provenance alongside the familiar requirements of security, availability, and governance.
His distinction is workload-specific. Automating internal IT-resource allocation carries a different risk from making lending decisions that regulators may challenge; the latter requires a defensible record of “what and how was decided at each stage.” Slowness therefore combines prudent due diligence with organizational “ossification” and “old-fashioned conservatism.”
Labenz asks whether model-provider indemnities or AI insurance can unblock adoption. Martin has spoken with agent-insurance entrepreneurs and thinks insurance “could potentially be a breakthrough,” but OutSystems is not yet seeing meaningful customer demand: for regulated enterprises, insurance itself remains another immature, untested dependency.
Labenz emphasizes that trust is not merely a technical scorecard: a regulated European enterprise also weighs privacy, contractual obligations, regulatory scrutiny, and the vendor’s history of delivering robust systems. Martin agrees that this accumulated reputation is “very hard for a startup to get.”
4. Security and token costs both reward consolidated infrastructure
On cyber risk, Martin rejects the idea of an endpoint: “There is no finish line when it comes to security and cyber threats.” Better technology strengthens both attackers and defenders, while large companies still operate 60-year-old COBOL systems alongside AS/400 and Lotus Notes estates.
A consolidated portfolio built from common components can remediate one vulnerability once and propagate the fix broadly. The alternative—hundreds of AI-generated systems built on unrelated frameworks, stacks, and open-source packages—makes it difficult even to locate exposure, much less eliminate it quickly.
OutSystems is adding security resources, using powerful AI for penetration testing, and automating more testing inside build, test, and deployment workflows. Martin expects defensive model usage and white-hat hacking to remain a permanent source of token consumption rather than a temporary tax that disappears after an 18-month cleanup.
Token expenditure peaked in June and July after an internal push to “translate everything into AI.” The spending produced measurable output—major feature releases rose from four in Q4 to 19 in Q1 and 26 in Q2—but also taught OutSystems that many tasks could be performed far more cheaply.
5. Model routing—not universal frontier-model use—drives enterprise economics
OutSystems built internal engineering tooling loaded with company context plus an LLM gateway that routes tasks by need. “Not all tasks should go to, say, Opus 4”; those optimizations brought third-quarter spending below forecast without surrendering the development acceleration.
Martin’s strongest cost claim is that almost no ordinary business-operation workload needs an advanced model. He distinguishes those tasks from creating new software products; many of the former are “actually quite boring” and can run on deterministic code, open-weight models, or base models already three years old.
Geographic attitudes complicate the model portfolio. Some clients use Chinese models, launch their own versions, distill models, or retrain them for cost reasons, while attitudes differ substantially across Europe and Asia; “not everyone is thrilled about trusting their data to American companies.”
Mentor hides much of this optimization. Users can work through the OutSystems IDE or access its MCP services from a coding agent of their choice, while backend model selection and platform-specific tuning reduce the workload imposed on whichever external model sits on top.
6. AI is clearing old backlogs while creating a new governance layer
Legacy systems that organizations were afraid even to place in the backlog are becoming tractable because AI accelerates each stage: understanding old behavior, translating it into modern requirements, turning manual work into agent work, building the replacement, testing it, and deploying it. Martin cites insurers reframing a six-year modernization as a six-month project.
At the other end of complexity, employees no longer wait in a development queue for dashboards and similar tools. They can ask Claude to turn a spreadsheet into one immediately; the tradeoff is proliferating applications that lack shared definitions, integrations, and role-based access standards.
The resulting opportunity is not simply faster development but structured cleanup. Self-service experiments reveal what users actually need because they “kept talking to Claude until they got the result”; a platform can then rebuild those observed needs around common data and security foundations.
Martin offers Axos Bank and YESCO as early productivity examples, while refusing to claim their financial outcomes. Axos is accelerating digital capabilities used to compete for deposits, customers, and lending; YESCO says higher productivity lets it accept business that its prior resource base could not serve. The hedge remains important: productivity takes time to reach financial statements, and “not all investments people make will pay off.”
7. The agent factory tackles the harder problem of choosing what to build
Mentor began in 2018, before generative AI, as an effort to apply machine learning throughout the development lifecycle. Its implementation has changed dramatically, but Martin says the enduring strategic problem is still deciding “what exactly should I create” to solve a real business problem.
OutSystems’ new agent factory uses telemetry, application structure, and data flows from portfolios containing thousands of applications. It identifies manual work that might become automated, estimates ROI through time savings and related measures, and offers a button that lets AI create the first version for normal development, testing, validation, and trials.
Labenz questions whether aggressive experimentation wastes effort when the next model generation may make today’s difficult engineering trivial—he cites later models described as “55 or Astra” potentially recreating earlier work in 10% of the time. Martin’s answer is to concentrate experimentation where workflow transformation offers the greatest expected return, rather than treating technical novelty as the objective.
8. Interfaces will atomize, while competitive advantage moves upward
Martin still expects to have more than 100 phone apps in a year because conversation is not ideal for every task. Google Maps could join an AI dialogue, but users may still benefit from seeing spatial structure and what they will encounter along the way; privacy, compliance, and preference likewise preserve multiple interaction models.
What may change is the monolithic portal containing 80 features. Capabilities could become widgets delivered exactly when needed, as in OutSystems’ demonstration of a home-renovation conversation with Claude surfacing a $30,000 loan pre-approval and handing the customer into a bank app without restarting the process or requesting documents the bank already holds.
Labenz’s competitive concern is that vendors are expanding into every adjacent niche until each becomes a horizontal “everything” platform. Martin agrees that the market currently resembles an “ocean of the same,” but expects shared primitives at the bottom and specialization at the top—in customization, distillation, model economics, industries, and workflows.
For OutSystems, specialization includes regulated-industry knowledge and what Martin calls roughly “37 features” beyond the basic checklist that determine whether a first solution can actually be deployed. Martin is also bullish on young professionals who have grown up with these technologies, while noting that companies must pair their fresh perspective with industry knowledge. OutSystems is leaning toward a full-time-employee model and asks whether each task belongs to a person, an agent, a team, or a combination; it is also replacing the traditional few-day-or-week introductory course with more timely, just-in-time onboarding.