Co-owner
NNVEN AB
Agent-first e-commerce behind cigge.se and elekcig.se. Content, SEO and operations run with AI in production.
AI agent consulting · Gothenburg, Sweden
Production AI agent systems for content, SEO and e-commerce.
I design and ship AI agent systems the same way I run my own companies — scoped pilots, private keys, draft-first publishing and clear human review. The patterns on this page come from running agent-first operations across NNVEN AB (Cigge / Elekcig e-commerce) and Optagonen AB, not from slide decks.
Scoping calls are free. Pilots are fixed-price and agreed in writing before any key is issued.
Operating layer
Public discovery · Private actions
Public MCP
Read-only discovery
Pilot key
Scoped content and SEO workflow
Owner MCP
Private content operations
Human review
Draft-first publishing boundary
27
Owner tools behind auth
4
Public read-only tools
9
Locales in pipeline
Operator track record
These aren’t slides. They’re the systems I run every day.
I’m an operator first, consultant second. The agent-first patterns sold on this page are the same ones running my own e-commerce and education companies — and this website.
~11.4B
Cursor tokens consumed last year
Production usage, not lab experiments.
2
Operating companies on agent-first stack
NNVEN AB (Cigge / Elekcig e-commerce) and Optagonen AB (cultural workshops).
500+
Pages on the multi-agent pipeline
This site, in 9 locales, drafted and maintained by agents.
Founder
Optagonen AB
Cultural workshops for schools across Sweden. Internal operations and outreach automated through agents.
Reference implementation
uygarduzgun.com
Public MCP, owner MCP, multi-agent content pipeline. The page you are reading is part of the proof.
Where it’s deployed
One scoped workflow first. Expansion follows results.
The first pilot is almost always an AI content and SEO workflow — it has the clearest inputs, the most measurable output and the lowest integration risk. Once the system has earned trust, the same architecture extends to e-commerce operations and bespoke internal processes.
Content and SEO workflows
Topics, products, videos and briefs become research-backed drafts, metadata, internal links and SEO recommendations a reviewer can sign off on.
E-commerce operations
Product copy, category pages, campaign drafts, research and reporting — connected to your data without opening broad write access.
Custom internal workflows
One repeatable process at a time, wired into approved APIs, data sources and human checkpoints before any production rollout.
Engagement model
A 2–4 week pilot. Fixed price. Reviewable output.
Pilot keys are intentionally narrow. They prove one workflow before any deeper system is touched, and write access, publishing and owner tools stay private throughout.
- Scope and price agreed in writing before kick-off
- One workflow, one API surface, one review gate
- Clean handover at the end — keep going or close out
- 1
Week 1
Scoping and key issuance
Define the workflow, inputs, outputs and review gate. Issue a pilot key with the narrowest useful scope.
- 2
Week 2
First reviewable output
Run the workflow on a real input from your business. Return drafts, metadata and recommendations for human review.
- 3
Week 3–4
Iterate or close out
Tighten prompts, scope and integrations. End the pilot with a written handover, or plan a production engagement.
Technical reference
This site is the reference implementation.
Every architectural claim on this page is something this domain already does in production: machine-readable discovery, a public read-only MCP, a separate owner MCP behind auth, and a multi-agent content pipeline with draft-first publishing.
Read the technical write-upPublic agent card for machine-readable discovery
Read-only public MCP for site and blog discovery
Owner MCP protected by a separate bearer key
API catalog, OpenAPI metadata, llms.txt and markdown rendering
Private customer keys for scoped pilot workflows
Multi-agent content pipeline with draft-first publishing
Security posture
Designed so your security team can sign it off.
Discovery, customer pilots and owner operations are intentionally separated. Code-level review is welcome before the first key is issued.
Scoped keys
Pilot access is separated from owner and admin credentials.
No public write access
Public tools are read-only by default.
Human oversight
Publishing stays draft-first by default.
Auditable layers
Discovery, customer API and owner tools stay separate.
FAQ
Buyer and technical questions, answered straight.
Direct answers to the questions that come up before signing.
Is anything write-capable open to the public?
No. Public discovery is read-only. Any workflow that creates, updates, publishes, translates, generates images or spends AI budget requires a private key.
Who is already running these patterns?
I am. NNVEN AB (Cigge / Elekcig e-commerce) and Optagonen AB (cultural workshops) both run agent-first operations. This site is the public reference implementation — public MCP, owner MCP and a multi-agent content pipeline are all live.
What does a pilot cost?
Pilots are scoped to a fixed price agreed before any key is issued, sized to the workflow. Discovery calls are free. Pricing is shared in writing during scoping.
How long does a pilot take?
Most pilots ship in 2 to 4 weeks. Scoping and key issuance in week 1, first reviewable output in week 2, and iteration or handover in weeks 3–4.
What does a first pilot usually include?
A scoped AI content and SEO workflow. It has clear inputs, measurable output and low integration risk, so it is the fastest way to validate fit before connecting deeper systems.
Can technical teams review the architecture?
Yes. There is a technical proof article that explains the discovery layer, MCP split, auth model and private workflow boundaries. Code-level questions are welcome before signing.
Ready to scope a pilot?
Book a scoping call. We define the workflow, the key’s scope and the success criteria in writing — before any contract or kick-off.
Based in Gothenburg, Sweden. Working with European and global teams.