The existence of artificial intelligence does not eliminate the need for software-development companies. It changes what clients need from them.

That distinction matters, because the honest version of this argument comes with a qualification: not every boutique software firm will survive. Companies that primarily sell programming hours, generic websites, basic applications, or inexpensive staff augmentation are going to face real pressure. AI is very good at exactly those things.

But that is not the whole story. AI can generate code, create prototypes, explain technical concepts, and accelerate many development tasks. A functioning business system requires much more than generated code. It requires someone to understand the business problem, decide what should be built, translate operational and regulatory requirements into system behavior, choose an architecture, protect sensitive data, integrate external services, migrate records, test the product, deploy it reliably, train users, respond to failures, and remain accountable for the system over time.

Code is becoming abundant. Successful software is not.

An amplifier, not a replacement

AI has substantially accelerated software creation. DORA's 2025 research reported that roughly 90% of surveyed technology professionals were using AI at work, and more than 80% believed it increased their productivity. But DORA's more important conclusion was that AI behaves as an amplifier: it magnifies the strengths of well-managed organizations and the dysfunctions of poorly managed ones. Faster code generation lets a competent team move faster — or lets an inexperienced team create a larger problem more quickly.

The labor outlook reflects the same split. The U.S. Bureau of Labor Statistics projects employment for traditional "computer programmers" to decline about 6% from 2024 through 2034, while employment for software developers, quality-assurance analysts, and testers is projected to grow about 15%. Repetitive code production is becoming less valuable. Broader responsibility for designing, validating, securing, and operating software remains valuable.

That is the space a boutique firm should occupy: not programming as a commodity, but software product engineering as an accountable professional service.

Why boutique firms keep the advantage

1. Clients often don't know exactly what to build

A client may know that enrollment is inefficient, records are scattered, attendance is inaccurate, or customers can't see their account information. That is not yet a software specification. Someone has to uncover the real workflow, find the exceptions, reconcile competing stakeholders, separate essential requirements from preferences, and decide what the system should do. AI can help document those decisions. It cannot independently accept responsibility for whether they are correct.

Our work on ATLAS illustrates this. The hard part is not producing an attendance screen. The hard part is understanding state-mandated program and course hours, cohort schedules and session-level allocations, makeup-hour policies, clinical hours that don't use normal scanning, transcript reconstruction, student identity and Google Classroom integration, and the payment plans, disclosures, signatures, and administrative overrides underneath it all. Someone unfamiliar with the business could build an attractive application that is operationally or legally wrong.

2. An application is not a dependable product

Fast, informal "vibe coding" is excellent for prototypes, internal utilities, and narrowly defined workflows. A production product must also address authentication, authorization, audit trails, data integrity, backups, recovery, accessibility, performance, monitoring, error handling, privacy, upgrades, documentation, and support. NIST's Secure Software Development Framework treats security as a set of practices deliberately integrated throughout the lifecycle — and those responsibilities don't disappear because AI generated part of the code.

A buyer can generate a prototype. What the buyer often cannot confidently answer is:

  • Is it secure?
  • Will it preserve the data correctly?
  • What happens when an external API changes?
  • Can another developer maintain it?
  • Does it meet the applicable business rules?
  • What happens when the original AI conversation is gone?
  • Who responds when it fails on Monday morning?

A boutique firm sells the answers to those questions.

3. AI expands the market for custom software

As development becomes less expensive, custom software becomes economically possible for organizations that previously couldn't afford it. That can grow the addressable market for a boutique firm rather than shrink it. Small businesses are already adopting AI quickly — in the U.S. Chamber of Commerce's 2025 research, 58% of small businesses reported using generative AI, up from 40% in 2024 and 23% in 2023. But adoption is not the same as a governed, integrated production system. The common progression is: "Could we automate this?" → "I made a prototype." → "Now how do we make it secure, reliable, integrated, and usable by the whole company?" That third stage is where a professional firm becomes valuable.

4. Boutique firms sit closer to the customer

Large firms often introduce layers — account managers, business analysts, project managers, architects, offshore teams — and information degrades as it passes through them. A boutique firm can offer direct access to decision-makers, faster clarification and approval, continuity from discovery through implementation, and quicker adaptation when requirements change. That closeness matters most to the small and midsize clients who don't have their own product managers, architects, or security staff.

5. Specialized knowledge is a real moat

AI has broad knowledge, but it generally doesn't possess a company's accumulated operating context. A firm focused on a defined market — say private career schools, massage schools, and other clock-hour institutions — can accumulate knowledge about enrollment and admissions, attendance compliance, course-hour requirements, cohort scheduling, transcripts, student finances, instructor workflows, regulatory reporting, accreditation evidence, and document retention. A generic developer begins every engagement by learning the industry. A specialist begins with an established domain model, reusable components, proven workflows, and a library of known risks. That's a defensible advantage that doesn't depend on a secret language or a proprietary model.

6. Customers still need someone accountable

AI cannot sign a contract, carry insurance, provide an SLA, attend an implementation meeting, answer a support ticket, explain a failure, or make a customer whole. Business owners generally don't want to become software-development managers. They want a vendor who will take responsibility for the outcome. This becomes one of the most important promises a firm can make: you are not buying generated code — you are hiring an accountable company to deliver and support a working business system.

7. AI may strengthen a small firm more than a large one

A small, senior team can use AI to do work that once required separate junior developers, documentation specialists, test writers, designers, and analysts. That creates a structural opportunity: lower overhead, more senior involvement per engagement, faster delivery, better margins without enterprise pricing, and the ability to support smaller niches and build reusable vertical products. AI doesn't need to be hidden from customers. It can be part of the value proposition — modern AI-assisted engineering that reduces development time while retaining human review, testing, security controls, and accountability.

What AI genuinely disrupts

The argument is more credible if it concedes what AI will erode. AI reduces the value of basic coding, simple websites, standard CRUD applications, uncomplicated mobile apps, low-complexity integrations, boilerplate documentation, and early prototyping. Customers will increasingly expect those things faster and cheaper. So a firm should avoid positioning itself as "a company that can write custom code for you." That description is too easy to commoditize.

The other risk is that AI lets many new competitors produce impressive demonstrations. The way to stand apart is to distinguish a demo from a durable product — through disciplined architecture, documented requirements, testing, source control, CI/CD, security reviews, monitoring, backup and recovery, and formal customer support.

The conclusion

AI will probably eliminate some software-development work. It will not eliminate the need for software-development companies. It will divide them into two groups: firms that sell code production, and firms that take ownership of business outcomes. The Horizon Works Group intends to be unmistakably in the second group.

In the next piece, I'll get specific about what that means for how we actually build and price our work — the model behind the firm.

Sources

  • DORA (DevOps Research and Assessment), 2025 State of AI-assisted Software Development.
  • U.S. Bureau of Labor Statistics, Occupational Outlook Handbook (Computer Programmers; Software Developers, QA Analysts, and Testers), 2024–2034 projections.
  • NIST Secure Software Development Framework (SSDF), SP 800-218.
  • U.S. Chamber of Commerce, Small Business AI adoption research, 2025.