Read this first: what this is, and isn't
Not a teardown. A map of where a work protocol plugs into what Skanska already does well.
This is a passive, public-source review, normal browsing, public HTTP responses, no login, no probing, prepared ahead of an introduction. Skanska's digital estate is competently built: modern stack (Next.js on Cloudflare), HSTS + a real permissions policy, no console errors or broken requests on the primary pages we visited. That's the baseline. What follows isn't "your site is broken", it's three places where genuinely good underlying work (real emissions reductions, a serious green-building portfolio, an active subcontractor program) isn't yet legible to the systems, search, AI assistants, investor diligence tools, that increasingly do the asking on a partner's or investor's behalf.
What already works: the honest baseline
Three things we noticed, respectfully
Deep links into project & program content don't survive the domain move
Skanska's site moved from usa.skanska.com / group.skanska.com onto a single skanska.com/<market>/<lang> structure sometime in 2026. Several specific, previously-indexed URLs now resolve somewhere other than their own content:
Why it matters: the specific page, the one with the actual proof, is gone; the generic hub is what's left. A search engine or an AI assistant that has the old URL indexed (and given how often these exact pages are cited by third-party procurement guides and industry associations, they are) now serves a dead end instead of the answer. That's lost SEO equity and a lost trust moment at exactly the wrong time, when someone is trying to verify a specific claim.
passive · curl -IL, dated 2026-07-08The named public front door for new subcontractor partners is unreachable from outside
Skanska Plan Room and Prequal, the prequalification inquiry app linked from Skanska's own "doing business with Skanska" guidance and cited by third-party subcontractor associations, currently returns a VPN-required page to an ordinary outside visitor:
apps.skanska.com/prequalinquiry/: HTTP 502, "VPN Required," tagged Environment: PROD / Access Level: Everyone. Screenshot, Chrome headless, 2× DPI, 2026-07-08.
Why it matters: this is tagged "Access Level: Everyone", it's meant to be the public front door, but a subcontractor who finds this link through Google, a diversity-outreach flyer, or a construction-association newsletter today just hits a wall. That's leaked pipeline into the subcontractor program, not a partner who chose to walk away. It may simply be a routing change on Skanska's side we can't see from outside; either way, it's worth a look from someone who can.
passive · normal page load, HTTP 502, dated 2026-07-08Real ESG progress lives in PDF only, no structured, agent-readable format yet
The Annual and Sustainability Report is the single source of truth for Skanska's climate and portfolio numbers: SBTi target, scope 1/2/3 progress, certification counts. There's no API, no structured export, and no project-level or portfolio-level machine-readable dataset behind it. We also checked for the emerging AI-discoverability layer and found nothing yet:
Why it matters: the substance is real and genuinely strong, SBTi 1.5°C alignment is not a small claim. But an investor's diligence agent, an owner's assistant, or a client's own AI can't cite a specific project's number without a human opening a PDF and reading it correctly. That gap is exactly what an Agent Kit closes, and as of this review, no major global GC has one live yet, so it's a first-mover position, not a catch-up.
passive · WebFetch + HTTP probes, dated 2026-07-08Where the protocol plugs in
EcoWealth runs the Ecological Work Protocol (EWP): a family of programs for funded, proof-verified, tCO2e-mapped work, live on Base mainnet, with a 1,000+ definition library that's already standards-mapped and method-backed. Three specific plug points for Skanska:
Procurement & bid legibility
Structured, agent-readable answers about prequalification requirements, active bid opportunities, and subcontractor scope, so an AI helping a small or diverse subcontractor find and prep a bid doesn't dead-end on a PDF or a VPN wall.
ESG / ecological data, agent-readable
An Agent Kit: llms.txt (the file AI assistants read first), an agent card, and MCP tools (the files that let an AI assistant use you correctly), sitting alongside Skanska's public data, project-by-project, cited, tCO2e-mapped, so an investor's or client's AI gets a structured answer instead of a PDF hunt. Skanska already sells green building; this makes the proof queryable.
Subcontractor work-packet coordination
Funded, proof-verified ecological/field-compliance scope (erosion control, native re-vegetation, waste-stream diversion) routed to Skanska's existing prequalified subcontractor network: paid, photo+GPS+method verified, tCO2e-receipted, feeding straight into the sustainability report.
The honest framing: EcoWealth isn't bidding for Skanska's structural work, and isn't asking to be a general contractor. We're proposing the legibility & proof layer underneath, and in exchange, we're asking to route small, funded, tangible ecological work packets through the crews and network Skanska has already vetted. Your labor and network; our protocol and proof. Both sides get more of what they're already good at.
Evidence log: method & dates
| Check | Method | Result |
|---|---|---|
| usa.skanska.com/.../green-building/ | curl -IL | 301 → homepage (not green-building content) |
| usa.skanska.com/.../subcontractor-engagement/ | curl -IL | 302 → generic subcontractors hub |
| apps.skanska.com/prequalinquiry/ | headless Chrome, 2× DPI | HTTP 502, "VPN Required," public-tagged |
| group.skanska.com/.../report-and-ratings/ | curl -IL | 302 → generic sustainability hub |
| skanska.com/llms.txt, /.well-known/agent-card.json, /.well-known/ai-plugin.json | curl status | 404 (none exist) |
| skanska.com/robots.txt | curl | 200, fully open (Disallow: none) |
| 10 primary pages (home, subcontractors, sustainability, projects, prequal) | headless Chrome, console+network capture | 0 page errors; ad-pixel requests aborted only (expected, non-blocking) |
All checks passive: normal navigation or standard HTTP requests, dated 2026-07-08, from a residential/consumer network, no authentication attempted, no parameters fuzzed, no endpoints probed beyond what a real visitor's browser or a real citation link would request.
The ask
A warm introduction and a small, funded pilot, not a system-access request.
See the demo next: the same protocol answering an ESG question and coordinating a work packet, in Skanska's own blue. Then the Agent Kit: the actual files. If any of this is useful, the next step is a fifteen-minute conversation with whoever owns sustainability reporting, procurement technology, or subcontractor engagement.
