The Brand
Launch Playbook
Every new brand starts from zero.
A new brand lands and the work gets improvised. Someone builds a page, someone else writes product notes, and the AI assistant is bolted on at the end with whatever information happens to be lying around. The result is slow, inconsistent, and different every time — and the knowledge that should power the assistant ends up scattered across chats, docs and people's heads.
We run a portfolio of brands, so we stopped improvising. This is the single path we follow to launch any brand — website to chat assistant — so the order is never guessed again.
The brand stack.
| Piece | What it is | Required? |
|---|---|---|
| Website | The brand's story, products and SEO — the public face. | Required |
| Shop | The online store, where the brand actually sells. | Optional |
| Knowledge base | The facts your chat assistant answers from. | Required |
| Chat assistant | AI that answers visitors and passes you only warm leads. | Required |
One team owns the public surfaces — the website, the shop and the assistant's knowledge. The live assistant itself runs on a separate AI platform. Knowing who owns what before you start is half the battle.
Collect → website → shop → KB → assistant.
| 1 | Collect info | Brand facts, product list, positioning, policies, contacts — in one place. |
| 2 | Build the website | The public site. Building it forces you to organise the brand's core information. |
| 3 | Build the shop | If the brand sells, stand up the store. This is where prices, SKUs and stock live. (Optional.) |
| 4 | Build the knowledge base | Assemble what the assistant answers from — drawn from the website, the shop and your support knowledge. |
| 5 | Launch the chat assistant | Define how it behaves, load the knowledge base, set the allowed domain, and go live. |
Website first. Knowledge base after.
Your KB is a superset.
| Source | What it adds | Examples |
|---|---|---|
| The website | Your public content. | Brand story, products, ingredients, the science. |
| The shop | The commerce facts. | Prices, SKUs, stock, shipping & returns. |
| Support knowledge | Answers that never made it onto the site. | FAQs, usage & troubleshooting guides, policies, the replies your support team gives daily. |
KB = website + shop + support knowledge. Most real questions live in that third bucket — capture it, or your assistant will sound thin.
Keep the assistant's brain in version control.
Your assistant runs on an AI platform — but its brain (how it behaves, its settings, and its knowledge files) should live as plain files in your site's code repository, versioned like everything else. The running copy is uploaded from there.
Two rules you can't skip.
The launch checklist.
| 1 | Collect | Gather brand, product, policy and contact info in one place. |
| 2 | Website | Build and publish the site — it organises the core information. |
| 3 | Shop | If selling, stand up the store (prices, SKUs, stock). |
| 4 | Knowledge base | Assemble website + shop + support knowledge into knowledge files. |
| 5 | Assistant | Write its behaviour and settings, load the KB, set the allowed domain, go live. |
| 6 | Guard | Block the knowledge folder from public view; confirm no customer data sits in the repo. |
Built for founders and teams launching brands in Malaysia who want every launch faster and more consistent than the last.
Free. No form. No email.
How the work moves while you build.
This playbook covers what to build and in what order. Its companion covers how that work travels between your AI projects — without you becoming the courier between your own sessions.