In May 2026 my AI assistant redesigned the KashBoss home page. It looked modern and clean. Then I looked at the navigation bar. Where our logo should have been sat a purple gradient square with a white letter "K". The assistant had invented a logo.
KashBoss has a real logo, a "K" with a check mark and a small stack of coins, in blue and gold. It had been in the project folder the whole time. The assistant needed a logo, did not look for one, and drew one.
It is a small story, but it captures the whole problem of identity in an AI-built product. The AI invents whatever it cannot find, confidently, and slightly differently each time. The fix is to decide your identity once, write it down and make the assistant follow it.
The short answer
To give an AI-built SaaS a consistent identity, put your real logo files in the project and forbid placeholders, write one design file that lists your colors, fonts, spacing and components, and set up a domain email that you have tested with real messages. The design file is what makes screens built months apart look like one product. Domain email needs four records, MX, SPF, DKIM and DMARC, or customer messages can bounce without you knowing.
What identity means for a one-person company
Identity is everything that tells a customer, "this is the same company, and it is serious." It has six parts: the name, the logo, the domain and email, the design system, the voice, and accessibility. For a one-person company, consistency is the cheapest trust signal you have. Customers cannot see that your team is you and an assistant. They can see when buttons have different heights, when three shades of blue appear, or when one table is dense and the next is airy. They may not say what is wrong. They trust you a little less.
With AI, consistency does not happen by itself. Each prompt produces a reasonable screen, and each reasonable screen differs slightly from the last.
How we did it in KashBoss
Give the AI your real brand files
Here is the opening story, written as a lesson.
While redesigning our home page, the assistant needed a logo and drew its own: a gradient square with a letter "K". Our real logo files were in the project the whole time. A fake logo looks amateur, and it also showed me the assistant had not checked what already existed. We replaced it in the next update, and the real files are now listed in our design file with their exact locations and uses.
Use a prompt like this before any design work:
Write the design file
Our look started in April 2026 with a redesign of the web cashier screen. It worked, so it spread to other screens by copying. The color values were pasted at the top of each screen file, so every new screen was close to the original but not the same: a different button height here, a deeper shadow there. No single difference was dramatic. Together they made the app feel unfinished.
On May 28, 2026, we wrote one file, DESIGN.md, at the top of the project. It covers colors, typography, spacing, corner rounding, shadows, components, icons, voice and things to avoid. One section is addressed to the AI: every component must pull from this file, and inventing one-off values is a bug. The spacing rule gives only nine allowed values. That ladder sounds pedantic, yet it is the most effective line in the file, because screens built months apart then line up.
Two rules about change helped as well. First, no big bang: an old screen moves to the new design when we touch it for another reason. Second, a redesign is visual only, so every button, field and confirmation stays where customers expect it.
Name every color from day one
Until September 2026, our management screens had no dark mode. Adding it touched hundreds of files on web and mobile. Dark mode works on a simple idea: every color has a name, such as "ink" for text or "surface" for cards, and each name has two values, one for light and one for dark. A screen never asks for white. It asks for "surface." Any color typed directly into a screen is a trap, because a hard-coded white card stays white on a dark background. Had we used named colors from the first screen, dark mode would have been a switch instead of a project.
Make sure you can receive email
We bought our domain and moved its settings to Cloudflare. The website worked and the app's emails were going out. It looked fine. It was not.
In September 2026 we discovered our domain had no mail-receiving record at all. Every message anyone sent to our support address bounced back to the sender. That address was printed on our privacy policy, in the app and on the account-deletion page that store reviewers check. Any customer who wrote to us got an error, and I never saw their message. I have no way to know how many tried.
We turned on free email routing, which forwards the support addresses to a company inbox, added the records that prove our email is genuine, and sent real test messages to confirm they arrived. Four records matter:
- MX is the mailbox address on your building. Without it, mail has nowhere to go.
- SPF is a public list of the services allowed to send email in your name.
- DKIM is a seal on each message proving it came from you and was not changed.
- DMARC tells receiving servers what to do with messages that fail those checks.
We started DMARC in monitor-only mode, because my own replies from a personal inbox were not yet sealed with our domain. A strict setting on day one would have sent my replies to spam folders.
One voice, and basic accessibility
Pick one voice and one set of words and never mix them. Our customers are companies, so we never call them shops on any screen. Add a short accessibility section to the design file from day one: readable contrast, tap targets of at least 44 by 44 pixels, no status shown by color alone, labels on icon-only buttons and keyboard access on the web. Chapter 8 of the book goes through all six parts of identity.
Key takeaways
- The AI invents what it cannot find. Give it your real brand files and forbid placeholders.
- Test every email address with a real message before you print it anywhere.
- One design file, read before every task, makes screens built months apart look like one product.
- Name every color from the start and dark mode becomes a switch.
- A redesign changes the look, never the buttons customers rely on.
Frequently asked questions
What is a DESIGN.md file and why use one with an AI assistant?
It is a single document in your project that lists your colors, fonts, spacing and components in exact terms. The assistant reads it before building, so each new screen uses the same values instead of inventing new ones.
What are MX, SPF, DKIM and DMARC records?
MX says where mail for your domain should be delivered. SPF lists who may send mail in your name, DKIM seals each message to prove it is genuine, and DMARC tells receivers what to do when a message fails those checks.
Why does AI make up a logo instead of using mine?
If it cannot find a logo file, it fills the gap with something plausible. Tell it where your brand files are, list their uses in the design file, and add a rule to stop and ask when a needed version does not exist.