Product Development
Creator brand product development
A practical development path for creator products, from customer problems and requirements to prototypes, buying signals and launch decisions.
Develop a creator product through four decisions: define a customer problem, turn it into requirements, observe intended customers using a prototype, and assess the response to a realistic offer. The creator may help identify the problem and shape the item. Audience enthusiasm alone cannot approve the product or predict sales.
Draw on existing data
The Australian Bureau of Statistics offers statistics about Australia’s economy, industries, people, jobs, health and environment, plus data about local areas. Austrade’s market search tool helps find overseas markets for products or services planned for export.
Define the product before telling its story
Name the intended user, the situation in which the problem occurs and what that person uses now. Describe the proposed item without the creator’s name. If the description says only who made it, the product brief needs more work.
Speak with people who face the problem, including people outside the creator’s audience when the intended market extends beyond it. Ask about recent behaviour and alternatives before showing a concept. Record how participants were recruited and which concept they saw. A supportive comment may reveal a useful problem, but it is not automatically a requirement or a buying decision.
Business.gov.au suggests describing the product and the problem it solves in one or two sentences. Identify the target customers, what they want and what annoys them about similar products. Check similar products from other businesses to see what they do well and what they could improve. Run surveys or interviews with potential customers and write a report of everything found for later steps.
Turn observations into requirements
A useful requirement states what an intended user needs to do, under what conditions, and how the team will check the result. Separate essential outcomes from preferences about appearance or format. For a hypothetical shared-desk organiser, “easy to clear away” is an observation. The team would need to define which items it should hold and what clearing the desk entails before testing a design.
Record where each requirement came from and any trade-off it creates. Extra capacity, for example, might compete with a smaller footprint. The intended use should guide that decision. Safety, labelling and product claims need checks for the actual category; customer preference does not establish compliance or safety.
The ACCC educates businesses about product safety responsibilities and runs the ACCC Product Safety website. It can require businesses to back up claims made about products or services. It does not test products for safety or compliance, provide legal advice on which standards apply, or resolve individual complaints.
Learn from prototypes
Make a version capable of answering a specific question. A rough form might reveal an awkward shape, while a later sample may be needed to assess assembly or repeated use. Record what each version includes and what it cannot demonstrate.
Give intended customers a realistic task and observe where they hesitate, need help or use the item unexpectedly. Record actions separately from opinions. After a meaningful change, retest the affected task on the new version.
A small recruited group can expose problems; it cannot establish a population success rate. Observations on a prototype also do not replace the checks needed for the saleable product.
Test how the prototype behaves when someone uses it the wrong way, and whether it will break with regular use. A basic version does not have to be perfect, but it should demonstrate the main idea.
Assess the offer
An item may work well in use yet be unappealing at its proposed price or terms. Show a plain description of what is included, its meaningful limits, the likely price and a delivery position the business can support. Ask what the person would choose instead.
Keep praise, requests for updates and orders in separate records. Note who saw each version of the offer and what action was available. A waitlist sign-up is a request for an update; record it separately from orders.
An eligible completed order is evidence of a purchase at stated terms, but it does not establish repeat demand. Do not turn a small test’s response rate into a forecast based on follower count.
Evidence on what drives action
IAB Australia research shows 61% of Australian online shoppers discover brands through creators, rising to 85% among those under 40. The reputation of the promoted brand (86%) and the creator’s own expertise (84%) are the strongest factors Australians weigh before acting, ahead of how entertaining the content is (74%). A paid partnership disclosure has a modest negative effect on intent, but strong brand reputation absorbs most of the cost.
The same research found 92% of Australians use search or an online store somewhere in discovery, research or comparison. 48% of Australian online shoppers use creator or influencer content, rising to 72% among Australian online shoppers aged 18 to 39. Just 23% of Australian AI users have discovered a new creator through an AI-generated result they now follow, the lowest of five markets studied, compared with 64% in India.
Key Insights on Creator Influence in Australian Shopping
- 61%% of Australian online shoppers discover brands through creators — 61%
- 85%% of Australians under 40 discover brands through creators — 85%
- 86%% consider brand reputation when acting on a creator’s recommendation — 86%
- 84%% value the creator’s expertise — 84%
- 23%Only % of Australian AI users discovered a new creator via AI-generated results — 23%
Record each handover
| Handover | Decision | Useful next step |
|---|---|---|
| Research to brief | Is there a defined problem for an identifiable user? | Narrow it, investigate further or stop. |
| Brief to prototype | Are the essential requirements and open risks clear? | Build a specific test version or revise the brief. |
| Prototype to production planning | Did intended users encounter an important failure? | Change and retest, then arrange applicable category checks. |
| Offer review to launch planning | Did people understand the terms and take a meaningful action? | Refine the offer, gather more evidence or proceed in proportion to the evidence. |
These are proposed management decisions, not results of a performed test. Keep the product version, observations, decisions and open questions together. Before sale, check the actual item against applicable safety and labelling requirements, and ensure product and delivery claims are accurate and supportable.
In this guide
- Turning audience problems into product requirementsTurn audience complaints into testable product requirements by checking real behaviour, defining outcomes and recording design trade-offs.
- Testing prototypes with intended customersPlan a prototype task, observe intended customers using the sample, record failures and retest revisions without overstating the results.
- Checking whether early feedback reflects genuine purchase intentAudit early creator product feedback against the exact offer, action, participant context and product version before making the next commitment.
