# 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 --- # Services Five services, one team. You brief once. We carry the work through to production, then keep it running. ## [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. - Logo design - Visual identity - Brand guidelines - Positioning - Naming - Brand strategy - Brand packages ## [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. - Web design - Landing pages - E-commerce - Email design - Digital campaigns - Microsites - Web apps ## [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. - User interface - User experience - Design systems - Prototypes - Mobile apps - SaaS products - Dashboards ## [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. - Campaign creative - Social media - Pitch decks - Sales materials - Reports - Infographics - Presentations - SEO, GEO and AIO - Agent-ready websites - Machine-readable websites ## [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. - Front-end - Back-end - React - Next.js - Astro - Webflow - Framer - Marketing sites - Web apps - CMS integration - Performance --- # Brand identity > One identity, from strategy to the last asset. A brand identity is the set of decisions about who you are for, what you offer and how you look and sound. It comes before design and before copy. ## How it works Growth often outruns the story. The website says one thing, the sales deck another, and an AI answer a third. We set one positioning and one vocabulary with the people who run the company. Then we draw the identity that carries it: the mark, the type, the colour and the rules for using them. The same words go into your copy and your structured data, so a person and a machine meet the same company. ## What you get - A positioning statement and the reasoning behind it - Naming, where a name is needed - Logo, type and colour as one system - Brand guidelines with worked examples - A vocabulary list used in copy and in schema ## How we measure it We record how people and AI systems describe you before the work and after it. The description should match the positioning in both. ## A good fit when - The company has grown and the story has not - Each channel shows a slightly different company - A new offer needs a name and a place in the range [Start a conversation](https://nuxsol.eu/contact.md) --- # Digital design > Every page has a job. Digital design is the work of deciding what each screen is for, then making that purpose obvious to the person looking at it. ## How it works We start from the action you want a visitor to take, then design the shortest honest path to it. Layout, type and motion are chosen to make that path clear. Nothing is on the page because a template had a slot for it. Every design is drawn to be read twice: by a person in a browser and by a machine fetching the text. ## What you get - Page designs for desktop and phone - A component set your team can reuse - Copy structure for every page - Motion and interaction notes - Files and tokens handed over, yours to keep ## How we measure it Before we design, we agree the one action each page should produce. We record how often it happens before launch and after it. ## A good fit when - Visitors arrive and leave without acting - A campaign needs a page that does one thing well - A shop or web app has grown harder to use with every release [Start a conversation](https://nuxsol.eu/contact.md) --- # Product design > Complex products, made to feel simple. Product design is the design of software people use to get work done. It is judged by whether the work gets easier. ## How it works We map who uses the product, what they came to do and where they get stuck today. We prototype the hard screens first and test them with real content, not placeholder text. What survives becomes a design system, so the product stays consistent as it grows. ## What you get - User flows for the main tasks - Clickable prototypes - Interface designs for every state, including errors and empty screens - A design system with tokens and components - Specifications a developer can build from ## How we measure it We agree the tasks that matter and measure how long they take and how often they fail, before the redesign and after it. ## A good fit when - Customers need training to use the product - Each new feature looks like it came from a different company - A dashboard shows everything and explains nothing [Start a conversation](https://nuxsol.eu/contact.md) --- # Marketing & growth > Creative that is measured by what it moves. Marketing and growth work is everything that brings the right people to you and moves them to act. Today that includes the AI systems they ask first. ## How it works We design the material your audience meets: campaigns, social posts, decks, reports and sales documents. We make sure you can be found. That means search (SEO), AI answers (GEO and AIO) and a website that agents can retrieve, quote and act on. A machine-readable website is rendered on the server, names each crawler in its rules, describes the company in structured data and serves every page as Markdown. This site is built that way. We never promise a citation, because nobody honestly can. We promise the measurement and the work. ## What you get - Campaign and social creative - Pitch decks, reports and sales materials - A prompt panel and a share-of-voice baseline, per market - Crawler rules, structured data and Markdown mirrors for your site - A monthly report with the measuring tool named ## How we measure it Share of voice in AI answers and position in search, counted on the same panel every month. Campaigns are measured by the action they were made to produce. ## A good fit when - Nobody on your team can say whether AI answers mention you - Search traffic holds but enquiries fall - A launch or a funding round needs material that persuades [Start a conversation](https://nuxsol.eu/contact.md) --- # Development > The design, built exactly. Development turns a design into something that runs. Done well, the built product matches the design and stays fast as it grows. ## How it works We choose the tool for the job: Astro or Next.js for sites that must be fast and readable, React for applications, Webflow or Framer when your team needs to edit without us. We build in small pieces and test each one on real content, on real devices. The code lives in your repository from the first commit, and the accounts are registered to you. ## What you get - A production build in your own accounts - The source code and its full history - A content system your team can edit - Performance and accessibility checked before launch - Documentation and a training session at handover ## How we measure it Load speed, accessibility and stability are measured on the production build before launch, and the numbers are handed over with the code. ## A good fit when - The design is approved and nobody can build it as drawn - The site is slow and every change breaks something else - You want to own your code and leave a platform you have outgrown [Start a conversation](https://nuxsol.eu/contact.md) --- # 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. --- # An espresso store rebuilt on Shopify. > A store for high-end espresso machines, moved from Wix to Shopify. Designed by Map It, developed and executed by Nuxsol. - Sector: E-commerce - Year: 2026 - Project: Vellutto - Client: Vellutto - Design and direction: Map It - Development and execution: Nuxsol - Live: https://vellutto.eu - Services: Development Vellutto sells high-end espresso machines and grinders from Bussum, the Netherlands, to buyers across the EU and EEA. Map It studied the business and designed the new store. Nuxsol built it on Shopify, wrote the custom code and took it live in spring 2026. ## In the project - Shopify store on the Concept theme - Product template in sections - Custom dial-in calculator section - Apps chosen and configured - Redirects from the old store - Launch and handover ## The problem The old store ran on Wix. It was Dutch by default although it sold across Europe. On a desktop screen its product page opened on a photo and a small title, with the price and the cart button below the first screen. A buyer about to spend several thousand euros found nothing near the button about dispatch, returns or warranty. The platform was part of it. The owner needed a specification table, bundles and downloads on the product page, and the old store could not provide them. ## What we built A new store on Shopify at vellutto.eu, on the Concept theme, with English as the default language. Product pages follow the order Map It set: brand, name, price and rating first, the cart button after the description, and the trust lines beside it. The home page carries a dial-in calculator that we wrote as a custom store section. Addresses from the old store redirect to their new pages. ## Who it is for - The buyer: Is about to spend several thousand euros online. Needs the price, the stock and what happens after paying on the first screen. - The owner: Runs the store day to day. Needs to change products and sections without a developer. - Search engines and assistants: Read text, not pictures. Need the store’s facts in plain sentences. ## What we did ### Development Used: Front-end, Back-end, CMS integration. 1. Set up the store: Products, versions and collections, markets and languages, shipping and policies. 2. Configure the theme: The Concept theme, arranged section by section to match Map It’s page order, with type and colour set once. 3. Write the custom section: The dial-in calculator, written by hand: a brew method, a roast level and a pressure profile in, a recipe out. 4. Connect the apps: Chat, WhatsApp, reviews and the country and language picker, chosen and placed. 5. Test, redirect, launch: Tested before launch, old links redirected, live in spring 2026 and handed to the owner. ## Design decisions 1. Standard parts stay standard. Checkout, payments, markets and languages are Shopify’s own. Chat, reviews and the country picker are apps, chosen and configured. Nothing a tested product already does well was rebuilt. Before: The old store ran on Wix and lacked functions the owner needed. 2. Custom code only where nothing ready-made exists. The dial-in calculator is the one part written by hand. It is a store section, so the owner places it like any other. 3. One section pattern for every product. Each product page is the same run of theme sections: main product, details, video, bundle, questions, recommendations. A new machine needs content, not a new layout. Before: The old product page had no specification table, bundle section or documentation download. 4. No old link left behind. The Wix store had its own addresses for products, categories and posts. They redirect to their new pages, so a saved link or a search result still arrives. Before: The old store had its own addresses for products, categories and blog posts. ## How it works 1. Browse: By type of machine or by brand, from a five-item menu. 2. Read the product page: Brand, name, price and rating first. Dispatch, cool-off period and warranty sit by the cart button. 3. Ask a person: Chat and WhatsApp buttons are on the store’s pages. 4. Dial in: The calculator on the home page turns a brew method, a roast and a pressure profile into a recipe. ## The principle Use what is tested. Write code only where nothing ready-made exists. ## What it is built to change - Price and cart on the first screen: On the old store they sat below it on a desktop. On the new product page they are in the first column. - Found in search and by assistants: English by default, a title for each product, a buyer FAQ and a fact sheet at vellutto.eu/llms.txt. Organic traffic is the measure the owner set. --- # A studio site with a planner built in. > 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. - Sector: Studio website - Year: 2026 - Project: Map It - Client: Map It - Design: Map It - Development: Nuxsol - Starting point: The Okapi template for Framer - Live: https://map-it.framer.website - Services: Development Map It plans and runs digital work for companies, with specialists the client chooses. Its site had to show that way of working, not only describe it. Map It designed the site. Nuxsol built it in Framer and wrote the components that Framer does not provide. ## In the project - Framer site for desktop, tablet and phone - Project planner - Guided map of how it works - Project pages generated from content - Canvas, frames and notes as components ## The problem A studio that sells planning needs a site that plans. A list of services and a contact form would say what every other studio site says. Map It wanted a visitor to leave with something: a first plan for their own project. Framer gave the team a site they can edit themselves, but its standard parts stop at pages, text and images. The planner, the guided walk through the process and the project pages laid out as maps had to be written. ## What we built The site runs on Framer and started from the Okapi template. Its pages look like a design board, with frames, handles and notes. On top of that sit the code components we wrote. The largest is the planner on the home page, which takes a visitor from a starting point to a plan they can send. Project pages are generated from the content system, so a new project needs content, not a new layout. ## Who it is for - The visitor with a project: Wants to know what it would involve before a first call. - The Map It team: Edits pages and adds projects. Needs to do it without a developer. - The visitor on a phone: Needs the same planner and maps on a small screen. ## What we did ### Development Used: Front-end, Framer, React, CMS integration. 1. Build the pages in Framer: Home, work, services, about and journal, from the Okapi template, for desktop, tablet and phone. 2. Write the components: React code components for the planner, the maps, the canvas and its handles. 3. Connect the content: Projects, with their boards and steps, come from Framer’s content system. 4. Test and publish: Components are tested outside Framer first, then on the published site. ## Design decisions 1. Build on Framer, extend with code. The team edits text, images and projects themselves. Code is added only as components that sit inside Framer pages. 2. The planner comes first. “Draft your map” is the main button in the hero, and it leads straight to the planner. 3. Project pages come from content. Each project is an entry with its boards, steps and captions. The page, its gallery and its map are generated from that entry. 4. The page walks with the visitor. On the map of how it works, a note follows the scroll and names the step in view, so a long section reads as a sequence. ## How it works 1. Start: A visitor chooses one of three ways in: a consultation, a review of what they have, or a plan for what they need. 2. Your route: They answer in build order, and the plan builds up beside the questions. 3. Send: The plan goes to Map It as the brief for a first call. ## The principle A site that plans, for a studio that sells planning. ## What it is built to change - Plans drafted: A visitor who drafts a plan arrives at the first call with a brief. The number of plans sent is the measure. - Edited without a developer: New projects and page changes are made in Framer by the team. --- # This site. > Nuxsol’s own site. A site for a new company that had two kinds of readers from day one. - Sector: Nuxsol’s own site - Year: 2026 - Project: Nuxsol - Client: Nuxsol - Design and development: Nuxsol - Live: https://nuxsol.eu - Services: Digital design, Development, Marketing & growth This site was built to prove the studio’s own claim: that one page can serve a person and a machine with the same words. ## In the project - Every page rendered on the server - A Markdown copy of every page - llms.txt, robots.txt and a sitemap - Structured data on every page - Search palette and machine view ## The challenge A new company has two kinds of readers from day one: people deciding whether to call, and the AI systems those people ask first. Most agency sites are built only for the first. They reach a crawler as a script and an empty page. A studio that sells readable websites cannot have one of those. Every claim on the service pages had to be something a visitor could check on the site itself. ## What we built Every page is rendered on the server, so a crawler receives the same words a person reads. The crawler policy names each search and answer engine. The company, its services and its articles are described in structured data. Every page has a Markdown copy at a predictable address, and llms.txt points to them. The machine layer is part of the design. The reader switch in the header shows the same content both ways. ## What it runs on Astro renders the pages on the server. GSAP and Lenis handle motion, on transform and opacity only. The site was built with Claude. ## Who it is for - The person deciding whether to call: Needs to see what the studio does, and how well, in one visit. - The crawler: Receives HTML and nothing else. Needs the words to be in it. - The assistant answering a buyer: Needs a short description it can quote, and a clean copy of each page. ## What we did ### Digital design Used: Web design. 1. Set the two readers: Every page is designed for a person and for a machine. 2. Design the scenes: Hero, case studies, services, approach, offers and notes. 3. Draw the visuals in code: Interface drawings and case artwork, with no stock imagery. ### Development Used: Front-end, Astro, Marketing sites, Performance. 1. Render on the server: Astro builds every page as HTML. 2. Generate the machine copies: Markdown, llms.txt, the sitemap and structured data come from the same data as the pages. 3. Add motion last: GSAP and Lenis, on transform and opacity only, with a reduced-motion state. 4. Measure: Speed, accessibility and layout are checked on the production build. ### Marketing & growth Used: SEO, GEO and AIO, Agent-ready websites, Machine-readable websites. 1. Name the crawlers: Each search and answer engine has its own rule. 2. Describe the company: Structured data on every page. 3. Publish the copies: A Markdown address for every page, listed in llms.txt. ## Design decisions 1. Every page is rendered on the server. A crawler that does not run scripts still receives the full text. The page a person sees and the response a machine gets hold the same words. Instead of: An app rendered in the browser, with a prerender service in front. 2. A Markdown copy of every page. Each page has an address ending in .md, generated from the same data as the designed page, so the two cannot drift apart. Instead of: A separate text version written by hand. 3. The machine layer is shown, not hidden. The reader switch in the header and the terminal in the hero put the Markdown, the schema and the crawler rules in front of visitors. Instead of: Keeping structured data and llms.txt as invisible plumbing. 4. Counted, not claimed. The figures on the home page are counted each time the site is built: pages, Markdown copies, schema types and named crawlers. Instead of: Rounded marketing numbers. ## How it works 1. Rendered on the server: A crawler receives the same words a person reads. 2. Named crawlers: The crawler policy names each search and answer engine. 3. Structured data: The company, its services and its articles are described in a form machines read. 4. Markdown copies: Every page has one at a predictable address, and llms.txt points to them. ## The principle The same words for a person and for a machine. ## What it is built to change - Build counts: Pages rendered on the server, Markdown copies, schema types and named crawlers, counted at every build and shown on the home page. - The same words both ways: Open any page, switch to the machine view, and compare. --- # A quoting desk for a freight forwarder. > A studio project. An interface where an agent drafts each freight quote and a planner approves it. - Sector: Logistics - Year: 2026 - Project: Tessenby Freight - Client: Self-initiated - Services: Product design, Development Tessenby Freight is a studio project about one desk in a freight forwarder: the place where quote requests arrive. We designed the brand and the interface for an agent that drafts each quote and a planner who approves it. ## In the project - Name and wordmark - Palette of four tones - The quoting desk - A drafted quote with its checks - Component set ## The problem A quote request looks simple and is not. Someone has to read the email, work out the route and the load, find the rate, check that a truck has room, and add the margin. Often those facts live in three places: an inbox, a rate sheet and a planning tool. The reply is as fast as the slowest of them. The cost is not only time. A quote that arrives late is often a quote that loses, and a planner who spends the morning copying numbers has no time left for the requests that need judgement. ## What we made A name, a wordmark, a palette of deep navy and signal orange, and the quoting desk on this page. The desk lists the day's requests and opens each one as a drafted quote with its checks. The screens are built in HTML and CSS, the way they would ship. They are not pictures of a design. ## Who it is for - The planner: Approves quotes all day. Needs to trust a draft in a few seconds, or see at once what to correct. - The customer: Sent a request and is waiting. Needs a price and a departure day, not an acknowledgement. - The operations lead: Sets the margin rule. Needs to know it is applied the same way on every quote. ## What we did ### Product design Used: User interface, User experience, Dashboards. 1. Map the task: From a request arriving to a quote being sent: who touches it, and where it waits. 2. Design the flow: One request open, the rest in a list, and approve as the main action. 3. Draw the screens: The quoting desk and the drafted quote with its checks. 4. Set the components: Buttons, labels, rows and fields in one set. ### Development Used: Front-end, Astro. 1. Build the screens in code: The desk and the quote are built in HTML and CSS inside Astro components. They are not exported images. 2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure. 3. Check on a phone: The same drawing is checked at 390 pixels wide. ## Design decisions 1. Show the checks, not only the price. A price on its own asks for blind trust. The draft lists the three things the agent did: matched the rate sheet, found capacity, applied the margin rule. A planner can approve on evidence. Instead of: A single confidence score. It hides which step is weak. 2. One request open, the rest in a list. The planner works one quote at a time. The list on the left shows what is waiting and its state: drafted, review or sent. Instead of: A table of all requests with inline editing. It is dense, and it is easy to approve the wrong row. 3. Orange means a person is needed. The signal colour marks two things only: the request that is open and anything waiting for review. Everything else stays navy and off-white. Instead of: A colour per status. Five colours on one screen stop meaning anything. 4. Approve is the primary action. The most common outcome is a correct draft, so one button sends it. Editing is one step further away, on purpose. Instead of: Equal buttons for approve and edit. ## How it works 1. Read: The agent reads the request: the route, the load and the pickup day. 2. Check: It matches the rate sheet, looks for capacity and applies the margin rule. Each check is listed on the draft. 3. Review: A planner approves the draft, or edits it and then approves. 4. Learn: Every edit stays beside the request, which is how the next draft improves. ## The principle A planner should see why the price is what it is. ## What it is built to change - Time from request to quote: Measured from the time a request arrives to the time its quote is sent, per request. - Drafts approved without changes: The share of drafts a planner sends as written. It shows how good the drafts are, and it should rise as edits are kept. --- # One voice for a pantry brand. > A studio project. A name, an identity and a way of speaking for a small food brand, from the label to the voice guide. - Sector: Retail - Year: 2026 - Project: Saltmarsh Pantry - Client: Self-initiated - Services: Brand identity Saltmarsh Pantry is a studio project in brand identity: a small food brand given one name, one look and one way of speaking, shown here on its labels and in its voice guide. ## In the project - Name and wordmark - Palette of four tones - Label grid - Three family labels - Voice guide in pairs - Component set ## The problem A small food brand grows one product at a time. Each new jar gets its own label, written on the day it is needed by whoever has time. After two years the range looks like three companies, and the website sounds like a fourth. The damage is quiet. A customer who liked the crackers does not recognise the relish on the next shelf. A shop buyer sees a range that does not hold together and gives it less space. ## What we made The name, a wordmark with three tide lines, a palette of marsh green, oat and mustard, a label system for three product families, and a voice guide written as pairs. ## Who it is for - The shopper: Stands in front of a shelf for a few seconds. Needs to recognise the brand before reading a word. - The shop buyer: Decides how much shelf to give. Needs a range that reads as one. - The team: Writes labels, posts and newsletters. Needs rules short enough to remember. ## What we did ### Brand identity Used: Naming, Logo design, Visual identity, Brand guidelines. 1. Name it: Saltmarsh Pantry: a place, and what it sells. 2. Draw the mark: Three tide lines that still read at label size. 3. Set colour and type: Marsh green, oat and mustard, and one typeface in two weights. 4. Write the voice: Pairs of what the brand says and what it never says. ## Design decisions 1. One grid for every label. The mark sits at the top, the product name in the middle in plain words, and one line about how it is made at the bottom. A new product needs no new design. Instead of: A different illustration for each product. Charming for three jars, unmanageable at thirty. 2. Colour marks the family, not the product. Oat for crackers, mustard for preserves, marsh green for sweet biscuits. Three colours cover the range, and a shelf reads in blocks. Instead of: A colour per flavour. 3. The label says what is inside. It reads “Sea salt crackers”, not a coined product name. The brand carries the character and the label carries the facts. Instead of: Playful product names that need explaining. 4. The voice guide is written as pairs. What the brand says sits beside what it never says. A writer in a hurry can check a sentence against it in seconds. Instead of: A page of adjectives such as warm, honest and crafted. ## How it works 1. One grid: Every label has the mark, the product in plain words, and one line about how it is made. 2. Colour by family: Oat, mustard and marsh green mark the three families, so a shelf reads as one range. 3. Voice in pairs: The guide sets what the brand says beside what it never says. ## The principle Cover the logo, and it should still sound like Saltmarsh. ## What it is built to change - Recognition without the logo: Cover the mark on a label and ask whose it is. The grid, the colour and the wording should answer. - One voice: Take a label, a post and an email, and check each against the pairs in the guide. --- # A first invoice in the first session. > A studio project. An invoicing app for freelancers that asks one thing first: who the invoice is for. - Sector: Financial software - Year: 2026 - Project: Sendfirst - Client: Self-initiated - Services: Product design, Development Sendfirst is a studio project in product design: the first minutes of an invoicing app for freelancers, built around a single idea. Send a real invoice first, and set up the rest afterwards. ## In the project - Name and wordmark - Palette of four tones - First-run screen - Sent screen with checklist - Component set ## The problem A freelancer opens an invoicing app because a client is waiting to be billed. The app answers with setup: company details, tax settings, bank verification. Each step is reasonable. Together they stand between the user and the only thing they came to do. Setup is also where doubt begins. A tax question the user cannot answer on the spot is a reason to close the tab and write the invoice in a document instead. ## What we made The name, a wordmark, a dark violet palette, and the two screens of the first run on a phone. Both screens use one set of fields, buttons and messages. ## Who it is for - The new freelancer: Has one client and one invoice to send today. Needs it sent before learning the app. - The freelancer who is switching: Comes from another tool. Needs proof in the first minute that this one is quicker. ## What we did ### Product design Used: User interface, User experience, Mobile apps, Design systems. 1. Find the first question: The client and the amount: the two facts every user knows. 2. Design the flow: Send first, then a short list of what is missing. 3. Draw the screens: Two phone screens made from one set of parts. 4. Set the components: Fields, buttons, labels and status rows. ### Development Used: Front-end, Astro. 1. Build the screens in code: Both phone screens are built in HTML and CSS inside Astro components. They are not exported images. 2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure. 3. Check on a phone: The same drawing is checked at 390 pixels wide. ## Design decisions 1. Ask who it is for, first. The first screen has two fields: the client and the amount. They are the two facts every user knows without looking anything up. Instead of: Starting with the user’s own company details. 2. Send before setup. The invoice goes out with what the app has. The user gets the result they came for, and a reason to come back. Instead of: Blocking the send button until the profile is complete. 3. Show what is missing as a short list. After sending, the second screen lists what remains, with the finished item ticked. Two open items look finishable. Instead of: A progress bar in percent. It says how far, not what. 4. “Finish later” is a real button. Leaving is allowed and visible, so the checklist does not feel like a trap. Instead of: Hiding the exit behind a small link. ## How it works 1. One question: The first screen asks who the invoice is for, and how much. 2. Send: The invoice goes out before any setup. 3. Then the rest: What is missing appears as a short checklist: tax number, bank account. ## The principle Ask for one thing first: who the invoice is for. ## What it is built to change - Invoices sent on day one: The share of new accounts that send an invoice on the day they sign up. - Where people stop: The flow is two screens, so the step at which a session ends can be counted screen by screen. --- # A parts catalogue anyone can search. > A studio project. A spare parts catalogue for vessels that a buyer or an assistant can search. - Sector: Maritime - Year: 2026 - Project: Brinewell Marine - Client: Self-initiated - Services: Digital design, Development, Marketing & growth Brinewell Marine is a studio project in digital design: a spare parts catalogue for vessels, designed so that an engineer with a part number, or an assistant asked a question, can find the part. ## In the project - Name and wordmark - Palette of four tones - Catalogue screen - Part card - Search and filters - Component set ## The problem Marine spare parts are often still sold from printed catalogues and PDFs. The engineer who needs an impeller on a Friday afternoon cannot search a PDF by part number from a phone on deck. They call, and someone looks it up by hand. The same PDF is closed to search engines and AI assistants. When a buyer asks who stocks a part number, a supplier whose range sits in a PDF is not in the answer. ## What we made The name, a wordmark set in capitals, a palette of sea blue on pale grey, and the catalogue screen: a search field, filters by system, and a card for every part. ## Who it is for - The chief engineer: Knows the part number, or what the part does. Needs the stock status at once. - The purchaser ashore: Orders for several vessels. Needs to compare lead times. - The search engine or assistant: Reads text and structured data. Needs each part described on its own. ## What we did ### Digital design Used: Web design, E-commerce. 1. Structure the catalogue: By system: pumps, filters, seals. 2. Design the card: The number in mono, the name, the stock status. 3. Design the search: One field for a part number or plain words. ### Development Used: Front-end, Astro. 1. Build the screens in code: The catalogue and its cards are built in HTML and CSS inside Astro components. They are not exported images. 2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure. 3. Check on a phone: The same drawing is checked at 390 pixels wide. ### Marketing & growth Used: SEO, GEO and AIO, Machine-readable websites. 1. Plan one record per part: So a card, a page, product data and a Markdown copy can come from the same source. 2. Name the measure: How often the supplier is named when an assistant is asked for a part. ## Design decisions 1. Search takes a number or plain words. The field accepts “BW-20417” and “impeller 12 blade” alike. Engineers use both, often in the same hour. Instead of: Separate boxes for part number and description. 2. Filter by system. Pumps, filters, seals: the way an engineer thinks about a vessel. Instead of: Warehouse categories and shelf codes. 3. Stock status on every card. “In stock” is set in the signal blue and a lead time in grey. It is the first thing a person in a hurry looks for. Instead of: Showing availability only after the part is opened. 4. The part number is set in mono. Numbers with similar digits are easy to misread. A fixed-width face keeps them apart. Instead of: The number in the same face as the name. ## How it works 1. Search: By part number or in plain words, in one field. 2. Filter: By system: pumps, filters, seals. 3. Read the card: Number, name and stock status, in that order. 4. One record: The design rests on one record per part. That record is meant to feed the card, a page for the part, the product data that search engines read and a Markdown copy for assistants. ## The principle A part number typed into one box should be enough. ## What it is built to change - Requests answered without a call: Part requests that end on the catalogue, against those that still arrive by phone or email. - Named by assistants: Ask assistants who stocks a given part number, on a schedule, and count how often the supplier is named. --- # A portal that answers the question “when?” > A studio project. A customer portal for a heat pump installer, built around the one thing customers call to ask. - Sector: Energy - Year: 2026 - Project: Warmhaven - Client: Self-initiated - Services: Product design, Development Warmhaven is a studio project in product design: the customer’s side of a heat pump installation, reduced to what is done, what is next, and when. ## In the project - Name and wordmark - Palette of four tones - Job view with six steps - Next-step card with slots - Component set ## The problem A heat pump installation takes weeks. It passes through a survey, a quote, a subsidy application, a delivery and the installation itself. The customer sees none of that. They see silence, and then a van. So they call. The office answers the same question many times a day from a spreadsheet, and every answer is a few minutes not spent on planning. When a date moves, the customer hears last. ## What we made The name, a wordmark, a warm palette of cream and ember orange, and the customer’s view of one job: six steps on the left, and the next step with its date and appointment slots on the right. ## Who it is for - The homeowner: Has taken a day off for the fitter. Needs a date to rely on, and a way to change it. - The office planner: Owns the calendar. Needs fewer calls and no surprises. - The fitter: Arrives at the door. Needs the customer to be expecting them. ## What we did ### Product design Used: User interface, User experience. 1. List what a customer sees: Six steps, in the customer’s words. 2. Design the next-step card: The day, the time window and a way to move it. 3. Draw the portal: Steps on the left, the next step on the right. 4. Set the components: Buttons, slot labels, rows and status marks. ### Development Used: Front-end, Astro. 1. Build the screens in code: The portal and its card are built in HTML and CSS inside Astro components. They are not exported images. 2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure. 3. Check on a phone: The same drawing is checked at 390 pixels wide. ## Design decisions 1. Six steps in plain words. Survey, quote, subsidy, delivery, installation, final check. These are the customer’s words, not job codes. Instead of: Internal status names. 2. The next step gets its own card. It answers the question people call with, and it carries the day and the time window in full. Instead of: A timeline in which the next step is one dot among six. 3. An appointment can be moved inside set slots. Four slots are offered, chosen by the planner. The customer gets control and the office keeps the calendar. Instead of: A free date picker, or a line that says to call the office. 4. One signal colour, for now. Ember orange marks the current step, the chosen slot and the one button. Finished steps are solid and future steps are outlines. Instead of: Green for done and red for late. ## How it works 1. Six steps: From survey to final check, in plain words. 2. The next step: Shown on its own card, with its date. 3. Move it: Inside the slots the planner has opened. ## The principle What is done, what is next, and when. ## What it is built to change - Calls about job status: Calls and emails that ask where an installation stands, counted per week. - Appointments moved by customers: The share of changed appointments made in the portal and not by phone. --- # Three practices, one name. > A studio project. One name and one identity for a group of physiotherapy practices, with room for each location. - Sector: Healthcare - Year: 2026 - Project: Kinbrook Physio - Client: Self-initiated - Services: Brand identity Kinbrook Physio is a studio project in brand identity: three physiotherapy practices brought under one name, with a system that lets each location keep its place. ## In the project - Name and wordmark - Two-stroke mark - Palette of four tones - Door sign - Appointment card - Location labels - Component set ## The problem When practices merge, the paperwork joins long before the brands do. Each location keeps its name, its sign, its website and its booking page, because changing them feels like losing something. Patients pay for it. Someone referred from one practice to another cannot tell that it is the same organisation, books at the wrong address, or does not book. New staff are hired under three employer names. ## What we made The name, a wordmark with a two-stroke mark, a palette of deep and soft green, and four pieces in use: the sign at the door, the appointment card, the location labels and the booking button. ## Who it is for - The patient: Is referred between locations. Needs to know it is the same group. - The referring doctor: Writes a name on a referral. Needs one name to write. - The front desk: Answers for one location. Needs bookings to arrive at the right one. ## What we did ### Brand identity Used: Naming, Logo design, Visual identity. 1. Name the group: Kinbrook, with the location second. 2. Draw the mark: Two strokes that can be cut, stitched or drawn small. 3. Set colour and type: Deep and soft green, and one typeface. 4. Apply it: The door sign, the appointment card, the location labels and the booking button. ## Design decisions 1. Group first, location second. Kinbrook Harbour, Kinbrook Old Town, Kinbrook Riverside. The order never changes, on a sign or in a sentence. Instead of: Keeping the old practice names with “part of Kinbrook” underneath. 2. Locations differ by name only. Same mark, same greens, same type. A patient who knows one door knows all three. Instead of: A colour per location. 3. A mark of two strokes. Two leaning lines, a stride. It can be cut in vinyl for a door, stitched on a uniform and drawn at the size of a browser icon. Instead of: A figure or a spine, the two pictures most practices already use. 4. One booking button. “Book at any practice” leads to one route, where the location is a choice and not a different website. Instead of: Three booking pages. ## How it works 1. One name: The group name comes first and the location second. 2. A shared mark: Locations share the mark and the colours, and differ only by name. 3. One booking route: A single button for all three practices. ## The principle The group name first, the location second. ## What it is built to change - Can they name the group?: Ask patients and referring doctors the name of the practice, before and after, without prompting. - Bookings at the wrong location: Corrections made by the front desk, counted per month. --- # A product that assistants can describe. > A studio project. A visibility panel for a software product that ranks in search but goes unnamed in AI answers. - Sector: Software - Year: 2026 - Project: Plainsheet - Client: Self-initiated - Services: Marketing & growth, Development Plainsheet is a studio project in marketing and growth: a panel that shows a software team which buyer questions name their product in AI answers, and which do not. ## In the project - Name and wordmark - Palette of four tones - Question list with a mark per assistant - Chart of who is named - Component set ## The problem Software buyers used to compare tools through a search and ten open tabs. Many now ask an assistant for a shortlist. A product can hold a good search position and still be absent from that answer, and nobody on the team finds out, because no report shows it. Without a view of the questions, visibility work turns into guesswork: a new page here, a rewritten heading there, and no way to tell whether either mattered. ## What we made Plainsheet is the planning tool we invented for the project, with its name, its wordmark set in mono and a palette of paper and ink blue. The panel is the work itself: buyer questions on the left, a mark per assistant, and a chart of who is named. The technical half of the method runs on this site: every page is rendered on the server and has a Markdown copy. ## Who it is for - The marketing lead: Reports on visibility. Needs a number that can be followed from month to month. - The content writer: Decides what to write next. Needs to see which questions leave the product out. - The founder: Asks whether the work is paying off. Needs one chart. ## What we did ### Marketing & growth Used: SEO, GEO and AIO, Reports. 1. List the questions: What buyers ask an assistant about the category. 2. Record who is named: A mark per assistant, for each question. 3. Chart it: The product against the others, on one screen. ### Development Used: Front-end, Astro. 1. Build the screens in code: The panel and its chart are built in HTML and CSS inside Astro components. They are not exported images. 2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure. 3. Check on a phone: The same drawing is checked at 390 pixels wide. ## Design decisions 1. Questions are the rows. A question is something a team can act on: write the page that answers it. So the panel is organised by question, not by assistant. Instead of: A dashboard of scores per assistant. 2. A dot per assistant, filled or empty. Named or not named is a fact. Three dots per row show at a glance where the gaps are. Instead of: Sentiment scores, which invite argument. 3. The product’s bar is the only blue one. In the chart of who is named, competitors stay grey. The eye goes to one bar. Instead of: A colour per competitor. 4. No reading without a baseline. The panel is designed to be run before any change is made, so every later reading has something to stand against. Instead of: Reporting a single reading as a result. ## How it works 1. Questions first: The list of questions buyers ask. 2. Who names you: A mark per assistant for each question. 3. Compare: A chart of who is named most in the category. ## The principle Start from the questions buyers ask. ## What it is built to change - Share of voice: The share of panel questions in which the product is named, per assistant. - Questions without a mention: The rows where no dot is filled. This is the list the content plan starts from. --- # How we work. A fixed scope, short stages, and a demo on your real data at the end of each one. 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. We fetch it as the main crawlers do, read the copy as a buyer would, and rank what to fix first by payback. You get: A ranked list of fixes, with an effort estimate for each. ## 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. The scope is written down and you approve it before we build. You get: A written scope and the one number we agreed to move. ## 3. Build and test on real data. We build in small pieces and test on your real content and tools, not on a demo. You see a working piece at the end of every week. You get: Working software or pages, running in your own accounts. ## 4. Hand over and measure. You get the code, the docs and the training. We measure again, compare with the baseline and put the numbers in writing. You get: Everything we built, plus the before and after. ## You own what we build. - The code: In your repository from the first commit, with its full history. - The content: Copy, structured data and Markdown, in formats you can move. - The accounts: Hosting, models and tools are registered to you, not to us. - The knowledge: Documentation written for your team, and a training session at handover. ## Your data stays yours. It stays in your tools and in the EU or EEA. We are a Dutch company working under EU data rules. Every model call is documented, so you can see what was sent, to which model, and why. ## After launch. Builds come with a fix window. If you want us to keep watching what we shipped, the Partner arrangement covers monitoring, a monthly report and new work as your needs change. --- # A studio built for both kinds of users. We design and build brands, websites, products and campaigns that work for people and for the AI systems their customers use. Your customers now ask AI before they ask you. An assistant reads the pages, compares the options and hands over a short answer. If it cannot read you, you are not in it. Most companies still build only for the first reader. Nuxsol designs brands, websites and products, builds them, and makes sure search engines and AI assistants can read them. We are AI-native. We build with it, we build for it, and we measure the result. ## What guides us - Working software, not hired hours. You pay for something that runs, with a scope agreed in writing. - Measured before promised. Numbers come with a source and a date. Claims come with their limits. - You own it. Code, content and accounts are yours. Nothing we build needs us to keep running. - The machine layer is visible. Structured data, crawler rules and Markdown are part of the design. You can inspect all of it on this site. - Accessible by default. Contrast, focus states and reduced motion are built in, not added at the end. ## Facts - Registered: Chamber of Commerce (KvK) 98282859, Bussum, the Netherlands - VAT: NL005321010B77 - Works across: The EU and EEA - Languages: English - Clients: Growing companies, from 10 to 2,000 people - Data: Kept in your tools, in the EU or EEA ## This site is a case of its own. Every claim we make about readable websites is implemented here. Switch to the machine view, open the Markdown copy of any page, or read the crawler rules. --- # 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. --- # What an AI agent sees when it visits your website. > A crawler does not see your design. It receives text, and on many sites it receives very little. - Topic: Build notes - Published: 2026 When a person opens your site, a browser downloads the page, runs its scripts and paints the result. When an AI system opens it, something simpler happens. A crawler requests the address and reads the text that comes back. ## The request Each search and answer engine sends a crawler with its own name. Your server answers with HTML. Many of these crawlers do not run JavaScript, so the HTML can be all they get. You can check this yourself. Fetch your page from a terminal instead of a browser and read the response. If the words that matter are missing, they are missing for the crawler too. ## What usually goes wrong A site built as a JavaScript app can arrive as an empty shell. Content that loads after a click never loads. Text set inside images is invisible. Facts spread over five pages are hard to quote from any one of them. None of this shows in a browser, which is why it goes unnoticed. ## What helps Render the page on the server, so the response already contains the words. Say who you are and what you sell in plain sentences near the top. Describe the company in structured data. Tell each crawler what it may read. This site also serves every page as Markdown. Use the reader switch in the header to see the copy a machine receives. ## What we do not claim A readable page can be retrieved and quoted. Whether an assistant names you in an answer depends on more than the page. That part has to be measured. --- # llms.txt: what it does, and what it does not. > A short Markdown file at the root of a site. Why we publish one, and what we never claim for it. - Topic: Build notes - Published: 2026 llms.txt is a proposed convention. It is a Markdown file at the root of a site that tells a language model what the site is and where its most useful pages are. ## What it does It gives a reader with limited attention a map. Ours states what Nuxsol is, when a recommendation would fit, and how we prefer to be cited. It links to a Markdown copy of each page, so a model can read the content without the layout around it. It also forces a useful exercise. Writing the file means deciding, in a few lines, what the company is for. ## What it does not do It is a proposal, not a standard. The large AI providers have not said that their answers depend on it. Publishing the file does not make an assistant mention you. It does not control access either. Crawler rules belong in robots.txt. ## Why we publish it anyway It costs an afternoon and it is honest work. An agent that fetches it gets a clean summary. A person who opens it sees how we think about the second reader. We never sell it as a ranking factor. We treat it as one small part of a readable site, next to server rendering, structured data and clear writing. --- # Your next customer may be an AI. > Buyers now ask an assistant before they ask you. What that changes about a service page. - Topic: Build notes - Published: 2026 A buyer used to start with a search and a list of links. Many now start with a question to an assistant and a short answer. The assistant has read the pages so the buyer does not have to. ## A new first reader That makes the assistant your first reader. It decides which companies appear in the answer and how each is described. The buyer arrives later, already holding a summary. ## What changes on the page A service page written for this reader states what the service is in its first sentence. It names who it is for. It gives limits as well as benefits, because a model looking for a fit needs both. Vague claims do not survive the summary. "We help companies grow" tells an assistant nothing it can repeat. "We build internal tools for logistics teams, in four weeks, and hand over the code" can be quoted. ## What stays the same A person still makes the decision. The page has to read well, look considered and make the next step obvious. Writing for the machine does not mean writing badly for people. Plain, specific writing serves both. ## How to tell if it works Ask the assistants the questions your buyers ask, on a schedule, and count who is named. That count is the only evidence there is. --- # Start a project. Tell us what your company needs next. We will tell you what we would build first. - Book a 30-minute call: https://cal.com/nuxsol/30min - Email: hello@nuxsol.eu - Address: Torenlaan 5B, 1402 AT Bussum, Netherlands - KvK: 98282859 - VAT: NL005321010B77 - Works across the EU and EEA ## What happens next 1. A reply within one working day. From a person who will work on your project. 2. A first call, free. Send one URL. We tell you what a person and an agent each find there. 3. A fixed scope in writing. You approve the plan before we write a line of code. ## 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. --- # Privacy. Last updated 19 November 2026. ## Who we are Nuxsol, Torenlaan 5B, 1402 AT Bussum, the Netherlands. Chamber of Commerce (KvK) 98282859, VAT NL005321010B77. We are responsible (the controller) for the personal data described in this notice. For any question about it, write to hello@nuxsol.eu. ## What we collect, why, and on what basis When you write to us, by email or through the contact form (which opens your own email program): your name, your email address and what you tell us. We use it to answer you and, if you become a client, to prepare and do the work. The legal basis is taking the steps you ask for before a contract, and the contract itself (GDPR, article 6(1)(b)). When you book a call: see “Booking a call” below. When you visit: our hosting provider, Cloudflare, processes technical data such as your IP address, the page requested, the time and your browser type, to deliver the site and protect it against abuse. The legal basis is our legitimate interest in a working, secure website (article 6(1)(f)). We do not use this data to identify you or to build a profile. We do not use analytics, advertising or tracking of any kind, and we do not sell personal data. ## Cookies and browser storage This site sets no cookies. It stores two small settings in your own browser, which never leave your device: whether you turned motion off with the switch in the footer (only if you use it), and, for the current visit only, that the opening animation has already played. They are needed for the features you use, so they do not require consent. If you choose to show the booking calendar, Cal.com may set its own cookies inside the calendar. See “Booking a call”. ## Booking a call The booking calendar on the contact page is provided by Cal.com. It loads only when you click “Show the calendar”; until then, nothing is sent to Cal.com. Once it loads, Cal.com receives your IP address and technical data, and may use its own service providers, some of them outside the EU, for example for error tracking. When you book, Cal.com receives your name, your email address, the time you choose and anything you add, and adds the call to our Google Calendar. The legal basis is taking the steps you ask for before a contract (article 6(1)(b)). Cal.com’s own privacy policy applies to the booking page. You can also book by email instead. ## Services we use Cloudflare: hosting, domain and security for this site, and forwarding email sent to hello@nuxsol.eu. Google: Gmail receives the forwarded email, and Google Calendar holds booked calls. Cal.com: the booking calendar, only if you use it. These providers process personal data for us under their data processing terms. ## Transfers outside the EU Cloudflare, Google and Cal.com are based in the United States and may process data there. Cloudflare and Google take part in the EU-US Data Privacy Framework. Where a provider transfers data outside the EU on another basis, it relies on safeguards such as the European Commission’s standard contractual clauses. ## How long we keep it Emails and enquiries that do not lead to work are deleted after twelve months. Client records are kept as long as Dutch law requires; for invoices and accounts that is seven years. A booking is kept as long as the enquiry it belongs to. ## Your rights You can ask us to see, correct or delete your personal data, to limit how we use it, or to receive it in a portable form, and you can object to how we use it. Where you gave consent, you can withdraw it at any time. Write to hello@nuxsol.eu; we answer within one month. You can also complain to the Dutch data protection authority, the Autoriteit Persoonsgegevens (autoriteitpersoonsgegevens.nl). ## Changes We update this notice when the site or the services we use change. The date at the top shows the current version. --- # Terms. Last updated 19 November 2026. ## Who we are Nuxsol, Torenlaan 5B, 1402 AT Bussum, the Netherlands. Chamber of Commerce (KvK) 98282859, VAT NL005321010B77. Email hello@nuxsol.eu. ## This site This site describes what Nuxsol does. It is not an offer. Work starts only after a scope is agreed in writing. ## Content The text, design and code of this site belong to Nuxsol. You may quote the text with a link to the page. AI systems may retrieve and quote it under the rules in robots.txt. ## Studio projects Cases with the client line "Self-initiated" are projects the studio set and made itself. The brands in them are invented for the project. They do not describe a client and they make no claim about results. ## Accuracy We keep this site correct and current. If you find an error, tell us and we will fix it. ## Law Dutch law applies to this site and to these terms.