# Nuxsol: Built for people. Readable by machines.

> An AI-native design and build studio, registered in the Netherlands and working across the EU and EEA.

We design and build brands, websites, products and campaigns that work for your customers and for the AI systems they now use. You own all of it, with no lock-in.

- [Start a conversation](https://nuxsol.eu/contact.md)
- [Services](https://nuxsol.eu/services.md)

## What an agent finds on this site

Counted when the site was built, 2026-11-19.

- Pages rendered on the server: 28 of 28
- Markdown mirrors: 28
- Schema types published: 8 (Organization, WebSite, WebPage, Service, Article, CreativeWork, FAQPage, BreadcrumbList)
- Crawlers named in robots.txt: 9
- Languages: 1 (English)

## Why two readers

A company now has two kinds of users: people, and the AI systems those people ask first. Everything we build has to work for both.

Nuxsol was founded in the Netherlands by people who kept watching good software, sites and brands fail the moment a machine tried to read them. We build with AI, we build for it, and we measure the result.

- 5 days to a readability report
- 2 weeks to a first working demo, on your real data

## Services

You brief once. We carry the work through to production, then keep it running.

1. [Brand identity](https://nuxsol.eu/services/brand-identity.md): One identity, from strategy to the last asset. Complete brand systems, from strategy to execution. We build identities that say who you are, stand apart in your market and keep working as you grow.
2. [Digital design](https://nuxsol.eu/services/digital-design.md): Every page has a job. Websites and digital experiences built to convert. We design with a purpose, and every journey leads a visitor towards becoming a customer.
3. [Product design](https://nuxsol.eu/services/product-design.md): Complex products, made to feel simple. UI and UX that make complex products feel simple. We balance what users need with what the business needs, so the product just works.
4. [Marketing & growth](https://nuxsol.eu/services/marketing-growth.md): Creative that is measured by what it moves. Strategic creative that drives results, from campaigns to pitch decks. It includes being found: SEO, GEO, AIO and websites that agents and machines can read.
5. [Development](https://nuxsol.eu/services/development.md): The design, built exactly. Clean code that brings the design to life: fast, responsive and exact on every device, with a back end you can rely on.

## Work

Client work first: a store built for Vellutto and the site of Map It. Then our own site, and studio projects in which we pick a problem companies commonly have, set ourselves the brief and carry it through to a name, an identity and working screens.

- [An espresso store rebuilt on Shopify](https://nuxsol.eu/work/vellutto.md) (2026, e-commerce): A store for high-end espresso machines, moved from Wix to Shopify. Designed by Map It, developed and executed by Nuxsol.
- [A studio site with a planner built in](https://nuxsol.eu/work/map-it.md) (2026, studio website): The website of Map It, built in Framer and extended with code components: a project planner, a guided map of how it works, and project pages drawn as maps.
- [This site](https://nuxsol.eu/work/this-site.md) (2026, nuxsol’s own site): Nuxsol’s own site. A site for a new company that had two kinds of readers from day one.
- [A quoting desk for a freight forwarder](https://nuxsol.eu/work/tessenby-freight.md) (2026, logistics): A studio project. An interface where an agent drafts each freight quote and a planner approves it.
- [One voice for a pantry brand](https://nuxsol.eu/work/saltmarsh-pantry.md) (2026, retail): A studio project. A name, an identity and a way of speaking for a small food brand, from the label to the voice guide.
- [A first invoice in the first session](https://nuxsol.eu/work/sendfirst.md) (2026, financial software): A studio project. An invoicing app for freelancers that asks one thing first: who the invoice is for.
- [A parts catalogue anyone can search](https://nuxsol.eu/work/brinewell-marine.md) (2026, maritime): A studio project. A spare parts catalogue for vessels that a buyer or an assistant can search.
- [A portal that answers the question “when?”](https://nuxsol.eu/work/warmhaven.md) (2026, energy): A studio project. A customer portal for a heat pump installer, built around the one thing customers call to ask.
- [Three practices, one name](https://nuxsol.eu/work/kinbrook-physio.md) (2026, healthcare): A studio project. One name and one identity for a group of physiotherapy practices, with room for each location.
- [A product that assistants can describe](https://nuxsol.eu/work/plainsheet.md) (2026, software): A studio project. A visibility panel for a software product that ranks in search but goes unnamed in AI answers.

## How we work

2 calls a week. 1 demo per stage. 4 stages.

Every week we meet twice, once to open the work and once to close it. Between calls we stay reachable in your Slack. After each stage we walk you through what shipped, on your real data, so you see it running before you sign it off.

1. Audit the site and the story. We read your site the way a person does and the way an agent does, and rank what to fix first by payback.
2. Design the system. We agree what runs on its own, what a human signs off, and what every reader, human or machine, should find.
3. Build and test on real data. We build in small pieces and test on your real content and tools, not on a demo.
4. Hand over and measure. You get the code, the docs and the training. We publish the baseline and report the numbers.

Everything we ship lives inside your own tools and runs on your own data. We work under EU data rules, and you keep the code.

## How an agent reads this site

- nuxsol.eu/robots.txt
- nuxsol.eu/llms.txt
- nuxsol.eu/services/marketing-growth.md

Every page is rendered on the server and has a Markdown copy. Scripted illustration. It shows the mechanism, not a promised result.

## Three ways to start

- Readability check (5 days): Where people and machines lose you. Human and agent read of your site; Crawler, schema and content audit; Ranked plan you keep; Effort estimate per fix.
- Build (from 4 weeks): Shipped and handed over. Everything in the check; Brand, design or development work, fixed scope; Tested on your real data; Docs, training, you own the code.
- Partner (monthly): Your AI-native team, every month. Run and measure what shipped; Monthly AI-visibility report; New builds as needs change; Reachable in your Slack.

Every engagement starts with a fixed scope agreed in writing. You approve the plan before we write a line of code. Prices are quoted per engagement, not published.

## Insights

Practical notes about building for people and machines, written by the people who ship it.

- [What an AI agent sees when it visits your website](https://nuxsol.eu/insights/what-an-ai-agent-sees.md): A crawler does not see your design. It receives text, and on many sites it receives very little.
- [llms.txt: what it does, and what it does not](https://nuxsol.eu/insights/llms-txt.md): A short Markdown file at the root of a site. Why we publish one, and what we never claim for it.
- [Your next customer may be an AI](https://nuxsol.eu/insights/your-next-customer-may-be-an-ai.md): Buyers now ask an assistant before they ask you. What that changes about a service page.

## Questions before a first call

### Do we need an AI strategy before we talk to you?

No. Most clients arrive with a feeling that something is too manual or that nobody can find them in AI answers. The readability check turns that feeling into a ranked list, so you do not need a plan before you start.

### How fast can we see something working?

A readability report within five working days. A first working demo of a build within two weeks, on your real data.

### Will AI assistants actually read our site after this?

Search and answer engines will be able to retrieve and quote it. We measure whether they do, and report the share of voice. We never promise a citation, because nobody honestly can.

### What happens to our data?

It stays in your tools and in the EU or EEA. We are a Dutch company working under EU data rules, and every model call is documented.

### Are we locked in after the project?

No. You own the code, the content and the accounts. The docs and training are part of the handover.

### What if something breaks?

Builds come with a fix window. Partners get monitoring and a reachable team in their own Slack.

## Contact

Send us one URL. On the first call we tell you, for free, what a person and an agent each find there, and roughly what it would take to fix.

- [Start a project](https://nuxsol.eu/contact.md)
- hello@nuxsol.eu
- Netherlands, working across the EU and EEA
