Landscape Architects
How landscape architects are reshaped as AGI capability advances.
The bottom line
Roughly 85% of the work in Landscape Architects is information-shaped — already within reach of AI delivery. The question here is not whether it shifts, but which tasks go first and who staffs the residual.
Why: Landscape Architects operate primarily in a digital environment, driven by software rather than physical labor. Their tool distribution is heavily skewed toward information technology, with 29 of 30 tools falling into UNSPSC segment 43 (prior=0.85), including AutoCAD and Adobe Creative Cloud. Furthermore, top work activities like 'Drafting, Laying Out, and Specifying' (4.55) and 'Working with Computers' (4.10) map directly to desk-bound knowledge work, confirmed by work contexts like 'E-Mail' (5.00), 'Indoors, Environmentally Controlled' (4.70), and 'Spend Time Sitting' (4.25).
grounded in the economy graph · digital scalar 0.85 · digital
Business-as-Code
Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
The work of Landscape Architects engages 41 activities — the executable steps that, decomposed, reveal what becomes Code, what stays Human.
+29 more via engagesIn
Landscape Architects involves 41 work activities — the generalized motions beneath the role, each scored against the AI-deliverability frontier.
+29 more via involvesActivity
Autonomous Agents as digital employees
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Landscape Architects performs 19 tasks on the graph — the atomic work units that become the job description for a digital employee, promoted to autonomy on track record.
+7 more via performs
Landscape Architects is typically employed by 19 company types — the demand side that decides which of this role's tasks get handed to agents, and on what authority.
+7 more via typicallyEmploys
Landscape Architects is employed across 31 settings — the places where this role's work is done, and where digital employees first sit beside the humans.
+19 more via employs
Headless SaaS for Agents
The software here going agent-consumable — where the API, not the UI, becomes the way the work gets done.
Landscape Architects uses 7 tools today. As each gains an agent-consumable surface (API / MCP / SDK), the human UI stops being the only way in — and the work routes straight to an agent.
Landscape Architects relies on 35 products. The headless dimension of each — whether an agent can call it without a screen — is what decides how much of this work goes hands-free.
+23 more via uses
The software Landscape Architects reaches for already exposes 12 agent-callable actions (via uses → exposedBy) — typed surfaces an agent invokes directly, no human screen in the loop. The work routes to the API, not the UI.
The problems this exposes
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
- Client Rendering Iteration Costs
- Client Visualization Modeling
- Design-Build Bid Competition
- Design-Build Integration Threats
- Design-Build Market Competition
- Design Revision Churn
- Hardscape Material Lead Times
- LEED Accredited Recruitment
- Licensed Drafter Shortage
- Linear Hardscape Estimation Errors
+18 more problems on the graph
Where Landscape Architects sits
Related articles
No articles yet for this entity.
Recent capability events
No capability events for this entity yet.
Problems
- Topographic Survey Conversionops
- Stormwater Compliance Permittingcompliance
- Plant Material Sourcingsupply-chain
- Design-Build Bid Competitioncompetitive
- Licensed Drafter Shortagetalent
- Milestone Phased Billing Delayscapital
- Client Rendering Iteration Costsretention
Opportunities
- Autonomous CAD DrafterAgent
- Stormwater Permitting ServiceService-as-Software
- Headless Landscape RendererHeadless SaaS
- Plant Procurement AgentAgent