Organisation setup

An organisation is the customer entity and website being analysed. Its profile, evidence connections, projects, reports, stakeholders, and team access stay together in one workspace.

1. Open the application sidebar.
2. Select Add organisation.
3. Enter the organisation name and website URL.
4. Choose the organisation type and country, then add the initial description requested by the form.
5. Save the organisation. UX Robot opens its setup sections in the sidebar.

Account owners can create organisations while their subscription or trial provides access. Team members can work only in organisations to which they have been invited and cannot create customer organisations on the owner’s billing account.

Open the organisation’s Profile section and select Edit profile. Complete the fields that help a reviewer understand the organisation before reading behavioural evidence.

• Identity: name, legal and trading names, website URL, organisation type, country, timezone, and primary language.
• Market context: sector, sub-sector, lifecycle stage, business models, and pricing models.
• Narrative: description, mission, value proposition, products or services, target market, differentiators, and current positioning.

Write for an analyst who has never worked with the organisation. Prefer specific statements such as “members renew online each July” over broad claims such as “we value our customers.” Keep the website URL current because it is used throughout evidence and report context.

Goals tell UX Robot which outcomes matter. Constraints prevent recommendations from ignoring operational, legal, brand, accessibility, technical, budget, or timing realities.

To add a goal:

1. Open Goals and select Add goal.
2. Describe the website outcome in measurable, user-centred language.
3. Choose its priority and mark it primary only when it should lead trade-offs.
4. If GA4 is connected, select the matching analytics key event where one exists.
5. Add notes explaining how the organisation recognises success, then save.

To add a constraint:

1. Open Constraints and select Add constraint.
2. Choose the closest type, severity, and whether it should affect recommendations.
3. State the limitation or requirement and add enough notes for a reviewer to apply it correctly.

Review goals and constraints before every materially different project. Old context can make an otherwise well-supported recommendation impractical.

The remaining organisation sections help UX Robot interpret evidence and deliver recommendations to the right people.

• Tech Stack: record the website platform, CMS, frontend and backend frameworks, CRM, hosting provider, and technical contact. Leave unknown fields blank rather than guessing.
• Stakeholders: add the people who shape, approve, implement, or receive the work. Add an accurate email only when that person may receive a report.
• Competitors: add relevant competitors, benchmarks, or reference websites and explain why each is useful. A reference need not be a direct commercial competitor.

For stakeholders, select Receives reports only for people who should be sent the private stakeholder and full-report links. Update this before every report distribution.