Nuxsol
Start a conversation

Worknuxsol.eu/work/plainsheet/

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.

Plainsheet: Named in the answer.
Sector
Software
Year
2026
Project
Plainsheet
Client
Self-initiated

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 case

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.

The visibility panel: buyer questions, which assistants name the product, and who is named most.

Who it is for

  • The marketing leadReports on visibility. Needs a number that can be followed from month to month.
  • The content writerDecides what to write next. Needs to see which questions leave the product out.
  • The founderAsks whether the work is paying off. Needs one chart.

What we did

By service: what was used in this project, and the steps of execution.

Marketing & growth

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.

  • SEO, GEO and AIO
  • Reports
  1. 01

    List the questions

    What buyers ask an assistant about the category.

  2. 02

    Record who is named

    A mark per assistant, for each question.

  3. 03

    Chart it

    The product against the others, on one screen.

Development

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
  • Astro
  1. 01

    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. 02

    Make them scale

    Every size is relative to its container, so one drawing works as a card, a cover and a figure.

  3. 03

    Check on a phone

    The same drawing is checked at 390 pixels wide.

Build decisions

Each with the reason for it, and what we chose not to do.

  1. 01

    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 ofA dashboard of scores per assistant.

  2. 02

    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 ofSentiment scores, which invite argument.

  3. 03

    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 ofA colour per competitor.

  4. 04

    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 ofReporting a single reading as a result.

The identity: mark, colours, type and voice.
The component set, in Plainsheet’s own colours and words.

The system

Four tones, each with one job. Contrast is measured, not judged by eye.

  • Ground#F4F1EAPaper: the panel.
  • Ink#1C1B19Near-black: questions and labels.
  • Signal#3B5BFFInk blue: a filled dot, and the product’s own bar.
  • Soft#E7E2D6A darker paper: the chart card and the frame.
Contrast ratios of the palette
PairContrastPasses
Ink on ground15.3 : 1AAA
Ink on soft13.3 : 1AAA
Label on signal5.1 : 1AA
Signal on ground4.5 : 1AA
Type
Geist Mono for the wordmark, a nod to the spreadsheet. Geist for questions and labels.
Voice
Counts, not opinions.

How it works

  1. 01

    Questions first

    The list of questions buyers ask.

  2. 02

    Who names you

    A mark per assistant for each question.

  3. 03

    Compare

    A chart of who is named most in the category.

The principle

Start from the questions buyers ask.

Buyer questions, with a dot for each assistant.

What it is built to change

  • Share of voiceThe share of panel questions in which the product is named, per assistant.
  • Questions without a mentionThe rows where no dot is filled. This is the list the content plan starts from.
Next case An espresso store rebuilt on Shopify.

Show us the page you want machines to understand.

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.