How to use the Brand Architecture Planner.
Brand architecture clarifies relationships between offers. Choose a structure that helps customers understand the range without creating unnecessary names to maintain.
Make the workflow fit your task.
List the offers, audiences and relationships customers must understand. Compare a shared brand, endorsed products and separate brands against audience overlap, credibility transfer and the work required to maintain each structure.
- What you provide
- Existing brands, products and customer relationships.
- What you get
- Options for parent, sub-brand and product naming relationships.
See the input and the result.
Illustrative input and output · a teaching example, not a live WebAct run
Example input
Compare brand structures for an invoicing app and a classroom-planning tool owned by one company. Buyers do not overlap; budget for maintaining separate brands is limited.
Completed example
Option 1: parent brand plus descriptive product names. Benefit: shared communication resources. Risk: parent messaging must accommodate different audiences. Option 2: separate brands. Benefit: focused audience positioning. Risk: duplicated websites, content and recognition-building effort. Working recommendation: test parent endorsement with distinct product descriptions first, given the stated budget constraint. Revisit if customer research shows confusion.
Load this input into the prompt, then copy it to WebAct to try the task. Your result may differ from the illustration.
Decisions and troubleshooting.
When might separate product brands make sense?
Consider them when audiences or promises differ substantially and the organization can sustain separate communication. Make the cost of that separation explicit.
Why is the naming system becoming difficult to maintain?
Remove unnecessary brand layers and define a consistent relationship between parent, product and feature names. Every new name should clarify something.
Try it with your own source.
Replace the example with your material in the task prompt. Keep the requirements you need, then copy the task into WebAct.
Customize and copy the task ↑