Your design works. Your OpenAPI is there. But agents don't see your product.

product designer ·job application ·copenhagen ·may 2026

agent.opensverige.se scan of spektr.com, 6/14 PARTIALLY READY, 1 critical issue, 5 warnings, 6 ok

$ scan spektr.com
› 6 / 14  PARTIALLY READY
› 1 critical issue
› 5 warnings
› fix-eta: week one

6/14 PARTIALLY READY. I co-built the scanner. I'll build what closes the gap.

the data

1 critical issue
no markdown negotiation

5 warnings
no /llms.txt, cookie gap…

6 passing
robots.txt, OpenAPI, sitemap…

I ran spektr.com through agent.opensverige.se, an open-source scanner I built. It scores public surfaces on how legible they are to LLM agents, MCP clients, and discovery protocols.

The OpenAPI spec is there. That's already half the battle. Most B2B SaaS in this category hasn't shipped it. What's missing is the protocol-layer surface beneath the marketing site.

case

Problem

A compliance officer asks Claude "what does Spektr do?" Claude fetches spektr.com, parses 3000 lines of HTML, and guesses.

Without /llms.txt, agents scrape and infer. The summary they return is shallow, partly invented, and varies every time. Spektr has no control over how it's described to the agents its own customers use.

what Claude says today, without /llms.txt
"Spektr appears to be a compliance software platform
for financial institutions. It may offer AML or KYC
features. I couldn't find specific details about
pricing or integrations."

Solution

Six additions to the existing surface. Zero redesign. One week of focused work.

Protocol-layer changes, not marketing changes. They make the existing product visible to the agents Spektr's customers already use, without touching the visual design or the product itself.

Outcome

Spektr controls what agents say about Spektr. A procurement agent's first ping returns 14/14.

When a Tier 1 bank's procurement agent pings /.well-known/mcp, Spektr lands in the "auto-eligible" bucket, not "needs manual review." That's the work the role names.

week one

critical Markdown content negotiation at the CDN. Agents get markdown when Accept: text/markdown is set. ~80% token reduction. Cloudflare shipped this in their own scanner in April 2026. ~1 week.
important /llms.txt, a structured brief of what Spektr offers. Every agent that queries it gets a vendor-controlled summary, every time. Afternoon.
important /llms-full.txt, a markdown concatenation of the site. Anthropic, Cloudflare, and Stripe all ship this. Cuts integration scoping from days to hours. 1 day.
warning Cookie/consent declaration for non-human user agents. Agents fetching the site hit a consent layer that isn't declared for bots. Half day.
warning Article 22 framing on the marketing surface. For a compliance company selling to EU financials, the right to human intervention in automated decisions deserves named placement. Afternoon.
bonus /.well-known/mcp + server-card.json scaffolding (SEP-1960 / SEP-1649). MCP discovery manifest. Cloudflare added theirs in April 2026. 1 hour.

why this is a designer's problem

The job post says: "Designing for AI: This is the frontier." Here's what that actually means.

A bank's compliance officer asks their AI assistant: "what does Spektr do?" The AI fetches your site, reads what it can, and answers. What it says is a design decision, but right now, Spektr isn't making it.

An automated procurement tool compares vendors. It checks which ones have machine-readable capability docs. Spektr doesn't have them. A competitor does. That's not a sales problem. It's an information architecture problem.

A developer's AI coding tool looks for compliance APIs to connect to. It finds your OpenAPI. It can't find the rest. The gap between "discoverable" and "fully connected" is a design surface.

Structure, naming, hierarchy, capability articulation. Classical design problems. New medium.

the frontier has a protocol layer. that layer is undesigned. that's the work.

Gustaf Garnow · application to Spektr · May 2026

what I bring

10 years Full-stack design. Print, digital, motion, product. 7 of those years at AMF Pension, Sweden's largest pension provider. Compliance-adjacent product is not new.
AI-native Claude, Cursor, MCP servers, agent pipelines, public APIs as part of normal work. Not a side project.
solo op I ship in days, not quarters.
the scanner I built agent.opensverige.se. The same tool that scored Spektr 6/14 would bring it to 14/14.
the product Spektr's design work is case review flows, risk screening UX, and alert triage for compliance analysts under regulatory constraint. 7 years at AMF Pension means I've sat in that room. Regulated product is not a new medium for me.
location Currently Stockholm. Skåne if this lands. Øresund commute is 35 min.

This page is the work sample.

Claude · MCP · OpenAPI · llms.txt · Next.js

email: gustaf.garnow@gmail.com
linkedin: linkedin.com/in/gustafgarnow
discord: @baltikum
github: github.com/Baltsar
portfolio: headless.design

full report ↓ /llms.txt /llms-full.txt