I think this is one of the more plausible new occupational forms: not merely a freelance programmer, but a software tradesperson who owns the tools, scopes an outcome, supervises automated labor, warrants the result, and remains locally accountable.
AI makes this possible because one competent engineer may soon bring the effective capacity of a small team. The “van full of tools” becomes:
- Coding and research agents
- Reusable components and workflow templates
- Sandboxed development environments
- Security scanners and adversarial agents
- Deployment and observability infrastructure
- Domain-specific evaluation suites
- Standard contracts, warranties, and insurance
The customer does not pay for typing or tokens. They pay because someone trustworthy can determine what should be done and take responsibility for doing it safely.
What the jobs might look like
A journeyman could offer relatively standardized services:
- Automate intake and scheduling for a dental practice
- Connect a distributor’s inventory, accounting, and sales systems
- Replace a spreadsheet-based workflow with an internal application
- Migrate a business away from abandoned SaaS
- Build a secure knowledge system over company documents
- Audit an existing fleet of agents and permissions
- Recover or modernize a pile of generated “vibe-coded” software
- Create a temporary application for an event, audit, or research project
- Maintain a family’s or small business’s private digital infrastructure
The engagement might follow something resembling a building trade:
- Inspect the site.
- Identify constraints and hidden legacy problems.
- Produce a quote and specification.
- Obtain access under a controlled permission scheme.
- Have agents generate and test candidate implementations.
- Inspect the work against a standardized code.
- Deploy it incrementally.
- Issue documentation, provenance records, and a warranty.
- Offer ongoing maintenance on a retainer.
The deliverable would ideally include more than source code. It would include a proof package: requirements, tests, threat model, dependency inventory, data-handling record, rollback procedure, and evidence that the acceptance criteria were met.
Why this is not just contemporary freelancing
Freelance developers already quote projects, but the economics are often poor. Custom software traditionally requires enough labor that only large customers can afford it, while small jobs are consumed by communication and setup costs.↳ Freelance Software Developer Economics
Agents could radically lower the production cost while leaving the high-value human parts intact:
- Diagnosing the customer’s actual problem
- Handling messy physical and organizational context
- Negotiating tradeoffs
- Detecting when the customer’s requested solution is wrong
- Validating generated work
- Assuming reputational or legal responsibility
- Being available when something breaks
That could make bespoke software economical for small businesses and individuals, much as standardized power tools let a tradesperson perform jobs that once required a larger crew.
There is also a countervailing possibility: customers generate their own software and call the journeyman only after it fails. That creates the equivalent of remediation work—cleaning up unsafe automations, inaccessible data, tangled integrations, and undocumented agent-generated systems. This may be a very large market.
Guild may be a better analogy than union
A labor union primarily bargains with one or more employers. If these engineers are independent operators, the relevant institution might look more like a mixture of:
- A professional guild
- A trade association
- A worker cooperative
- A certification authority
- An apprenticeship network
- An insurer or bonding organization
- A trusted marketplace
It could establish grades such as apprentice, journeyman, and master, but the credentials would need to represent demonstrated responsibility rather than memorized programming trivia.
Useful standards might cover:
- Minimum security practices
- Client-data segregation
- Credential and agent-permission management
- Backup, export, and disaster recovery
- Dependency and model provenance
- Accessibility and interoperability
- Human override mechanisms
- Documentation and customer ownership
- Disclosure of subcontracted or automated work
- Warranty and incident-response obligations
The strongest guild would not merely certify people. It would provide shared infrastructure: vetted agent configurations, standard contracts, continuing education, incident databases, group liability insurance, peer review, and emergency coverage when an individual practitioner is unavailable.
Its mark could tell a customer: “This person follows an auditable code, carries insurance, will not trap your data, and another member can maintain the system if they disappear.”
Standards may become executable
Building codes can be inspected because many physical hazards are well understood. Software standards are harder because behavior is contextual and invisible. AI could improve this by making much of the “code” machine-checkable.
A guild might require every installation to ship with an executable compliance suite:
- Can the client export all of its data?
- Can the service recover from backup?
- Can an untrusted email cause an agent to transfer money?
- Are production credentials available in the development environment?
- Does deleting a user actually delete the relevant data?
- Can the system explain which model or person performed an action?
- Does it fail safely if an AI provider becomes unavailable?
- Can a different practitioner reproduce the deployment?
Certification would then be attached not only to the engineer but to each completed job.
Where this model is most likely to work
It seems especially plausible for small and medium-sized organizations with specific workflows but no reason to employ a permanent software team:
- Clinics and professional practices
- Manufacturers and repair businesses
- Local government
- Logistics and construction firms
- Laboratories
- Schools and nonprofits
- Retailers and hospitality businesses
- Farms and other geographically grounded operations
It is less likely to replace permanent teams responsible for continuously evolving products, safety-critical infrastructure, or systems whose operation requires deep institutional knowledge. Even there, however, “master engineers” may supervise networks of specialized external practitioners.
The important economic question
Fixed-price work becomes dangerous if the requirement is ambiguous. A successful trade will therefore need ways to separate diagnosis from execution:
- Paid inspection and discovery
- A bounded specification
- Explicit exclusions
- Change orders
- Acceptance tests agreed upon in advance
- Maintenance and warranty terms
- Liability limits and insurance
Otherwise, the practitioner absorbs unlimited uncertainty while the customer treats every newly discovered desire as part of the original quote.
The durable business may also be less “finish the job and vanish” than plumbing initially suggests. Software remains exposed to changing APIs, attacks, regulations, models, and workflows. A better model may combine installation fees with a modest maintenance retainer, while guaranteeing portability and avoiding SaaS-style captivity.
A possible career strategy
For an engineer preparing for this world, the moat would not be possession of a particular coding technique. It would be a combination of:
- One grounded domain whose workflows and failure modes you understand.
- A reusable technical toolbelt that lets you solve common problems rapidly.↳ Workvan Linux
- Evaluation and security competence sufficient to supervise agents.
- A reputation for dependable outcomes, not impressive demos.
- Operational capability: deployment, monitoring, backups, and incident response.
- A network of complementary practitioners to cover gaps and provide continuity.
The most valuable generalist may therefore be a general contractor, not a universal expert: someone who can diagnose the whole problem, become temporarily fluent in unfamiliar details, delegate to human and AI specialists, inspect the result, and remain accountable for the finished system.
In a world flooded with cheap generated software, “a known person who will stand behind this installation” could be a surprisingly scarce and valuable product.