TL;DR: We shipped two things on the same day. First, a design sweep across every page in datavessel — same typography, same neutral palette, brand color reserved for actual data. Second, a Shopware connector that can write back into the shop, not just read from it. Both are decisions about restraint.
An analytics product shouldn’t ship with five shades of brand color fighting the data on the chart. For most of the last quarter, ours did. The settings page used a tinted icon background. The agents page used a tinted hover state. The reports tab used a tinted active indicator. Each one was reasonable in isolation. Together they made the actual data — the line on the chart, the rank position next to a query — work harder than it should have to be seen.
So the brand color went on a diet. Across chat, sources, agents, citations, settings, reports, memory, history, public reports, signup, and login, we pulled the orange out of everything decorative and pushed it into the one place it earns its keep: signaling a customer’s own brand. Their rank position in a citations dashboard. Their line on a competitor comparison chart. The eyebrow on a public report header where they want to feel the product is theirs. Everywhere else went neutral gray.
The buttons are dark gray-950 rounded pills now, not orange. The icon tiles on empty states are neutral. The active tab indicator is a thin vertical bar in gray-900 against a gray-100 background. Headlines run in Geist with tight tracking. Cards round at 3xl. Empty states have a small amount of motion to signal the page is alive while it’s loading. None of this is dramatic on any one page. The point is that the same logic applies on every page.
Icons That Stopped Lying
The other thing we did in the sweep was fix a few icons that were quietly misrepresenting what they sat next to. The Reports tab used a bar chart icon. Reports are PDFs — they get exported, signed off, sent to clients. A FileText icon describes that. The bar chart icon described a different product.
The Agents tab used a robot icon. The things on that page are scheduled multi-step automations: run this query weekly, post the result to Slack, alert if something moves more than 20%. That’s a workflow, not a chatbot. The Workflow icon describes the actual thing. The chat assistant in the conversation surface still uses the robot, because in chat, the thing replying to you literally is one. Icons should match the noun underneath them, not the category the feature lives in.
The Memory section had a brain icon, which made it sound mystical. Memory in datavessel is a list of notes and decisions you wrote down — “we decided to deprecate this campaign,” “Q3 baseline is 14k visits.” It’s a notepad. NotepadText says that. The brain icon was selling the wrong story.
Restraint as a Feature
The reason to do all this in one sweep, rather than nudge surfaces individually, is that consistency compounds. When every page uses the same active-tab treatment, you stop teaching the user a new page each time they navigate. When the brand color only ever marks the user’s own data, the brand color starts to mean something. That’s the logic behind the design work, and it’s also the logic behind which connectors we choose to build.
Shopware, and Why It’s a Write Connector
The new connector is Shopware. It sits alongside the existing Shopify and WooCommerce integrations, but with one important difference: it’s wired for write access. datavessel can generate SEO landing pages directly into a Shopware shop, not just pull data out of it.
Connecting is straightforward — admin client id and secret, store access key, an optional default sales channel id if you want generated content scoped to a specific channel. The tedious part is configuration, not auth. We did the work to make the connection minimal so the work that actually matters — writing pages worth shipping — gets the attention.
The reason Shopware is interesting beyond the connector itself is what it represents. Most analytics tools stop at read-only because read-only is safe. You can’t break anything by reading. The product never has to take a position on what should happen next; it just shows the user the chart and walks away. That’s a fine product, but it’s not the product we’re building.
datavessel is built around the idea that the interesting work happens after the question is answered. “Organic traffic to /running-shoes is down 30% — should we draft a refreshed landing page?” should not require switching to a different tool, copying a brief, opening the CMS, pasting, formatting, and publishing. The agent that noticed the drop should be able to draft the page, write it into the shop, and tell you it’s there for review.
WordPress, HubSpot, and now Shopware are the write-capable destinations that make that flow real. Each one is one connector, deliberately picked, not ten. The same restraint that pulled the orange out of the active tab indicator is the restraint that picks one e-commerce platform to add at a time, gets the write path right, and moves on.
Notice the Change
If you have an account, log in and click around — the difference is the kind you feel before you can name. If you run a Shopware shop, the new source is in the connector list and ready to wire up.
Sources
- 12 Plain-English Questions for Shopify Owners — Companion piece on what the e-commerce connectors actually let you ask.
- WordPress Integration — The other write-capable destination already in production.
- AEO Software and Citation Tracking — Context on the AEO surface where the brand color now reserves itself for own-brand citation data.
Leave a Reply