Six months after its public release in May 2025, Claude Code reached $1 billion in run-rate revenue. More interesting than the revenue figure is how developers at Anthropic are using it.<\/p>\n\n\n\n
The most striking demonstration of Claude Code\u2019s capabilities came just days ago with the launch of Claude Cowork. This new tool is essentially \u201cClaude Code for non-developers\u201d – an AI agent that works within the Claude Desktop app to handle knowledge work tasks like organising files, creating expense reports, analysing documents, and managing data across applications.<\/p>\n\n\n\n
What makes this newsworthy isn\u2019t just what Cowork does, but how it was built. When asked on social media how much of Cowork was built using Claude Code, Boris Cherny\u2019s response was simple: \u201cAll of it.\u201d The entire product was developed in approximately 10 days, with 100% of the code written by Claude Code itself.<\/p>\n\n\n\n
This represents a significant milestone: an AI coding tool successfully building a completely new AI product from conception to launch in under two weeks. Cowork wasn\u2019t a simple script or prototype\u2014it\u2019s a production-ready feature now available to Claude Max subscribers, capable of autonomous task execution with access to files and applications on users\u2019 computers.<\/p>\n\n\n\n
Claude Code operates differently from typical code completion tools. It works through a command-line interface and takes a more autonomous approach\u2014understanding context, planning implementations, writing features, and iterating based on feedback rather than just suggesting the next line of code.<\/p>\n\n\n\n
The fact that it successfully built an entirely new product autonomously suggests the tool has reached a level of reliability that goes beyond experimental use. This represents a practical shift in how code can be written at scale.<\/p>\n\n\n\n
When AI handles most of the code writing, the developer\u2019s role shifts towards architectural decisions, code review, and strategic planning. According to Anthropic\u2019s observations, this doesn\u2019t necessarily reduce headcount\u2014it changes where developers spend their time and can increase overall development velocity.<\/p>\n\n\n\n
The Cowork example is particularly instructive: a small team identified a use case, architected the solution, and let AI handle the implementation\u2014shipping a complete product in 10 days. This development velocity fundamentally changes what\u2019s possible for product teams.<\/p>\n\n\n\n
If you\u2019re considering integrating AI coding tools into your development workflow, here are practical steps based on what\u2019s working in production environments:<\/p>\n\n\n\n
Start with Well-Defined, Contained Projects<\/strong><\/p>\n\n\n\n Don\u2019t try to transform your entire development process overnight. Begin with specific use cases where AI coding tools can deliver immediate value. Good starting points include building internal tools, creating API integrations, writing test suites, or developing proof-of-concept applications. As your team builds confidence and understanding of the tool\u2019s capabilities and limitations, you can expand to more critical systems.<\/p>\n\n\n\n The Cowork development approach offers a useful model: the team had a clear product vision, well-defined requirements, and an existing architecture pattern to build upon. This allowed AI to focus on implementation rather than ambiguous requirements.<\/p>\n\n\n\n Establish Clear Review Processes<\/strong><\/p>\n\n\n\n AI-generated code still requires human oversight, but the review process looks different from traditional code review. Your team needs to focus on architectural soundness, security implications, and business logic correctness rather than syntax and formatting. Create checklists specific to AI-generated code that cover security vulnerabilities, edge cases, performance considerations, and maintainability.<\/p>\n\n\n\n Even though Cowork was 100% AI-written, it still went through review and testing processes before shipping. The difference is that reviews happen faster when you\u2019re checking generated code rather than writing it from scratch.<\/p>\n\n\n\n Invest in Prompt Engineering Skills<\/strong><\/p>\n\n\n\n The quality of AI-generated code depends heavily on how you communicate with the tool. Your developers need to learn how to write effective prompts that provide sufficient context, specify requirements clearly, and include relevant constraints. Provide training on how to break down complex requirements, reference existing code patterns, and iterate when the initial output isn\u2019t quite right. Developers who master prompt engineering can be 5-10x more productive than those who treat AI tools as simple autocomplete.<\/p>\n\n\n\n Redefine Developer Roles and Expectations<\/strong><\/p>\n\n\n\n As AI handles more implementation work, your team\u2019s value shifts to higher-level thinking. Developers become more like architects and product engineers\u2014spending time on system design, technology selection, performance optimisation, and ensuring code aligns with business objectives. This requires adjusting job descriptions, performance metrics, and career paths. Instead of measuring lines of code written, focus on features delivered, problems solved, and system improvements made.<\/p>\n\n\n\n The Cowork team\u2019s role wasn\u2019t writing TypeScript\u2014it was making architectural decisions, defining requirements, reviewing output, and ensuring the product met quality standards. These skills don\u2019t disappear when AI writes code; they become more important.<\/p>\n\n\n\n Build Internal Guidelines and Best Practices<\/strong><\/p>\n\n\n\n Every organisation has different security requirements, coding standards, and architectural patterns. Create documentation that guides how AI tools should be used within your specific context. This includes which types of code can be AI-generated with minimal review, which require extensive human oversight, and which shouldn\u2019t use AI at all (such as security-critical authentication logic). Update these guidelines regularly as you learn what works.<\/p>\n\n\n\n Monitor Code Quality and Technical Debt<\/strong><\/p>\n\n\n\n AI can generate code quickly, but speed without quality creates problems. Implement automated testing, code quality metrics, and regular technical debt assessments. Track whether AI-generated code introduces more bugs or maintenance issues compared to human-written code. Monitor dependencies that AI tools introduce\u2014sometimes they\u2019ll pull in unnecessary libraries or use outdated approaches. The goal is to maintain or improve code quality while increasing velocity.<\/p>\n\n\n\n Plan for Knowledge Transfer and Documentation<\/strong><\/p>\n\n\n\n When AI writes most of your code, institutional knowledge can become fragmented. Developers may understand what the code does, but not why certain architectural decisions were made. Emphasise documentation of design decisions, trade-offs considered, and business context. Use AI tools to help generate documentation but ensure humans review and refine it. This becomes increasingly important as codebases grow rapidly with AI assistance.<\/p>\n\n\n\n Address Security and Compliance Proactively<\/strong><\/p>\n\n\n\n If you\u2019re in regulated industries like financial services, healthcare, or government, AI-generated code requires additional scrutiny. Establish clear policies about data that can be shared with AI tools\u2014many organisations run local or private instances to ensure sensitive information doesn\u2019t leave their environment. Conduct security audits of AI-generated code, particularly for authentication, authorisation, data handling, and external integrations.<\/p>\n\n\n\n For development teams<\/strong>, this shift means focusing less on syntax and implementation details, and more on problem-solving, architecture, and code quality. The developers who adapt successfully will be those who can think strategically about systems and communicate effectively with AI tools.<\/p>\n\n\n\n For engineering managers<\/strong>, the challenge is restructuring workflows, adjusting expectations, and ensuring quality standards are maintained while velocity increases. When products can be built in 10 days instead of months, planning cycles and roadmaps need to adapt.<\/p>\n\n\n\n For business leaders<\/strong>, AI coding tools offer the potential to accelerate product development, reduce costs, and enable smaller teams to accomplish more. However, the benefits require investment in training, process changes, and potentially new tooling infrastructure.<\/p>\n\n\n\n For consultants and service providers<\/strong>, this represents both an opportunity and a responsibility. We can deliver solutions faster and more cost-effectively, but we need to ensure we\u2019re solving the right problems and building maintainable systems. The value proposition shifts from \u201cwe can build this\u201d to \u201cwe know what to build and how to architect it effectively.\u201d<\/p>\n\n\n\n The organisations that will benefit most are those that approach this transition thoughtfully, experimenting with AI tools, learning from results, adjusting processes, and gradually expanding usage as they build confidence. This isn\u2019t about replacing developers; it\u2019s about amplifying their capabilities and allowing them to focus on higher-value work.<\/p>\n\n\n\n The Claude Code and Cowork milestones show us that AI-generated code isn\u2019t a future possibility\u2014it\u2019s current reality. Products are being built entirely by AI, shipping to production, and serving real users. The question isn\u2019t whether to adopt these tools, but how to do so effectively within your organisation\u2019s specific context and constraints.<\/p>\n\n\n\n Are you using agentic coding tools in your projects? I\u2019d be interested to hear your experiences \u2014 what\u2019s working and what challenges you\u2019ve encountered.<\/em><\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Six months after its public release in May 2025, Claude Code reached $1 billion in run-rate revenue. More interesting than the revenue figure is how developers at Anthropic are using it. Claude Cowork: AI...<\/p>\n","protected":false},"author":1,"featured_media":236,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[14],"tags":[10,11,12],"class_list":["post-233","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-ai","tag-ai","tag-artificial-intelligence","tag-technology"],"_links":{"self":[{"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/posts\/233","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/comments?post=233"}],"version-history":[{"count":1,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/posts\/233\/revisions"}],"predecessor-version":[{"id":237,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/posts\/233\/revisions\/237"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/media\/236"}],"wp:attachment":[{"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/media?parent=233"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/categories?post=233"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/smartapp.co.uk\/blog\/wp-json\/wp\/v2\/tags?post=233"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}What This Means for Different Stakeholders<\/h3>\n\n\n\n
Looking Ahead<\/h3>\n\n\n\n