Beautiful Business

Read the campaign story

Xero announced Beautiful Business on 6 June 2018, broadening its earlier Beautiful Accounting Software tagline. The company’s release explained the change as reflecting a platform connecting small businesses with advisers and other services. The promise concerned the experience of running a business, not only the appearance of software. This case treats the positioning and its later creative expressions as one family rather than adding each market execution separately.

A documented 2020 film campaign made that promise concrete through short, comic administrative scenarios. Xero’s in-house team created the work, with Eight producing and Steve Saussey directing. Contemporary coverage describes familiar film conventions used to set up a problem quickly before showing a relevant feature. The 2020 films did not launch the original tagline, and the sources do not independently establish how much time or money customers saved.

Editorial interpretation: broadening a brand promise can create ambiguity unless the customer still understands the practical offer. Beautiful business could mean almost anything in isolation. A recognisable task, such as preparing an invoice, gives the phrase an observable meaning. The creative challenge is to preserve the emotional appeal while showing enough of the actual operation that a viewer can connect the promise to a specific problem worth solving.

Editorial interpretation: comic exaggeration can make administrative friction visible without requiring a long explanation. Yet the resolution must not erase the work customers still need to do. Financial records require accuracy, appropriate setup and review. A responsible adaptation would use the joke to create recognition, then show a realistic next step and the conditions under which the feature helps. The audience should understand the improvement without being encouraged to abandon necessary checks.

Translate the adjective into a task-level promise

Take the broad word in your positioning and ask what a customer would notice if it were true. For simplicity, that might mean fewer repeated entries; for confidence, a clearer status indicator. Choose an observable improvement rather than another adjective. This gives creative teams a useful brief and gives product teams a claim they can verify against the real experience.

Borrow familiar conventions without hiding the feature

A recognisable genre can establish a situation quickly, but it should not consume the whole advertisement. Reserve enough attention for the product’s relevant action and its limits. Test whether viewers can identify the task being solved after the joke. If they remember only the setting, the creative may entertain without helping them understand why the service belongs in their consideration set.

Keep historical scope and current capability separate

A long-running platform accumulates different features, markets and product names. Date each example and check what was available in the period being discussed. When adapting the lesson for a current campaign, verify the present workflow rather than relying on an old film. Avoid combining years of product development into a fictional single launch or an inflated claim of immediate transformation.

A small test for another brief

Proposed test: a small software company could choose one repetitive administrative task and compare a short comic explanation with a plain demonstration, both using the same verified feature and realistic setup.

Measure task understanding, correct expectations and willingness to try the feature on a safe sample. If testing usability, compare completion and errors separately from advertising preference or claimed enjoyment.

Stop if the story implies effortless compliance, hides important prerequisites or encourages users to trust financial outputs without the appropriate review.

• Observe the task with consenting users and identify one specific friction.
• Write the product claim in literal language before developing the creative treatment.
• Show the setup requirements and review step in the companion explanation.