The work
behind
the night

Who it’s for

Artist agent, agency owner and promoter.

A public artist roster and a private booking desk need to tell the same story without exposing commercial information.

The workflow

1. A promoter explores the public roster and artist pages.
2. They send an enquiry with an artist, date and venue.
3. The agency manages the booking, network and finance in its private workspace.

Why it matters

Connect a public discovery experience with a separate operational workspace, keeping the artist and show as the organising concepts.

A public artist roster, enquiry form and private workspace for shows, fees and commissions.

Who it’s for

Promoter, booking coordinator and artist liaison.

Contracts, correspondence and artist logistics are easy to lose when each lives in a separate inbox or spreadsheet.

The workflow

1. Track an artist and booking through the pipeline.
2. Organise events, tours, agents, messages and mail around the work.
3. Use advancing to review overdue requirements, incoming information and reminders.

Why it matters

Make missing information visible as a work queue rather than requiring staff to inspect every booking.

The booking pipeline, artist records, correspondence and advancing queues sit within the promoter’s workspace.

Who it’s for

Production manager, crew coordinator and site lead.

Build, show and derig involve changing teams, overlapping tasks and costs that need to stay understandable.

The workflow

1. Separate the work into build, show, derig or unassigned phases.
2. Plan tasks and their rosters for the selected day.
3. Review running order, presence, hours and labour indicators from the overview.

Why it matters

Use phases and dates as navigation, with task-based rosters and headcount/cost views described by the scheduling screen.

Phase filters, task rosters, running orders and labour indicators give production planning a common structure.

Who it’s for

Venue manager, bartender and door staff.

Membership, entry, bar sales and stock are closely related tasks, often managed with unrelated tools.

The workflow

1. Use the overview to review members, presence, scans, revenue and credit.
2. At the till, choose an event and products for the current order.
3. Select a cash, card or credit/voucher payment route; managers have separate sales and stock areas.

Why it matters

Give the till a focused selling interface while keeping membership, stock and reporting in the administrative navigation.

Membership, tickets, presence, the till, stock and sales have dedicated places in the venue’s admin workspace.

Who it’s for

Event promoter, ticket buyer and check-in staff.

Ticketing needs to bridge event presentation, inventory, orders and admission.

The workflow

1. Create or edit an event’s image, place, date and publishing status.
2. Define ticket categories, prices, capacities and availability.
3. Use the event workspace to reach public pages, orders, attendees, analytics, embeds and scanner.

Why it matters

Group operational actions around each event, with ticket categories edited alongside event details.

Edit the event and its ticket inventory, then reach orders, attendees, analytics and check-in from the promoter workspace.

Who it’s for

Promoter, marketer and newsletter editor.

Visual campaign design, audience organisation and engagement reporting need a coherent workflow.

The workflow

1. Organise contacts with lists, segments and signup forms.
2. Compose an existing campaign with content blocks, rows and body styling.
3. Switch between desktop and mobile modes, then use preview and review controls before sending.

Why it matters

Combine a direct visual editor with device views, campaign history, reusable templates and audience navigation.

Compose with visual blocks, switch desktop and mobile views, and organise the audience with lists and segments.

Who it’s for

Organisation administrator and audience manager.

The same person can be a subscriber, crew member, ticket buyer or artist in different systems.

The workflow

1. Review the shared directory overview and category breakdown.
2. Filter people by their app or role in the organisation.
3. Use the visible connected-app and pairing areas to manage the relationships between systems.

Why it matters

Make people the common reference across apps while exposing source app records and shared audiences.

A shared directory exposes app records, categories, overlapping audiences and duplicate-review tools.

Who it’s for

Event producer, business owner and accountant.

A budget, a commitment, a received invoice and an actual payment represent different financial states.

The workflow

1. Choose an event and review projected revenue, expenses, cash and commitments.
2. Use the entry form to associate amount, provider, VAT, status and invoice with an item.
3. Move to billing, bank reconciliation or reports for the corresponding finance work.

Why it matters

Distinguish the forecast from actual cash and keep supporting documents in the financial workflow.

Event budgets, commitments, actual cash and supporting invoices appear as distinct parts of the financial picture.

Who it’s for

Individual professional and project owner.

Ideas, people, reminders and project context can become scattered across personal tools.

The workflow

1. Use the home screen to reach reminders, calendar, people and memory.
2. Open the workspace and start with a project and its context.
3. Review the AI connection state before expecting generated work.

Why it matters

Separate personal organisation from a project-oriented workspace, with an explicit readiness message.

Reminders, calendar, people and memory sit alongside a project workspace. AI requires a configured provider.

Who it’s for

Creator, researcher, writer and developer.

Different tasks call for different instructions and model choices, while users need visibility into where work runs.

The workflow

1. Choose a task mode such as Chat, Code, Research, Write or Documents.
2. Inspect the model selector’s local-server and cloud groupings.
3. Use the composer, attachments, skills and task-specific starting prompts.

Why it matters

Put task intent and model choice in the interface, with visible local/cloud distinctions.

Task modes, local and cloud model groupings, attachments and skills are visible in one AI workspace.

Who it’s for

Visual performer, lighting designer and live-event creator.

Creating visual material and performing it require precise controls, quick feedback and reusable arrangements.

The workflow

1. Prepare sources across four decks and inspect the program monitor.
2. Use the mixer’s blend, effect, opacity, tempo and crossfader controls.
3. Author clips in the pixel editor and organise scenes with presets and the sequencer.

Why it matters

Bring a four-deck performance layout and a frame-based pixel editor into the same desktop tool.

Four source decks, effects, blend modes, a sequencer and a frame-based pixel editor share one desktop workspace.

Who it’s for

Studio administrator and visual production team.

A desktop tool used on multiple machines needs a way to organise computer access and reusable creative assets.

The workflow

1. Review the computers connected to the organisation’s space.
2. Follow the visible code-based connection instructions for a computer.
3. Review the shared library categories and inherited team roles.

Why it matters

Separate desktop performance from web-based computer access and shared-library administration.

Review connected computers, team roles and shared presets, sequences, playlists, pixel clips and audio setups.

Who it’s for

Organisation owner, administrator and team member.

A collection of independent apps needs a clear way to handle access, subscriptions and desktop licences.

The workflow

1. Open My apps to see the organisation’s available products.
2. Launch a web app through its Open action.
3. Use Team, Billing and Account destinations or manage the desktop download/linking entry.

Why it matters

Present the ecosystem as a set of app cards with consistent access actions and a distinct desktop route.

App cards provide launch actions, with separate routes for team, account, billing and desktop access.

Who it’s for

Platform operator and release administrator.

Running several applications also requires visibility into instances, resources, versions and releases.

The workflow

1. Review cluster status, resource indicators and app health from Overview.
2. Use Client apps to inspect app families, instances, versions and available releases.
3. Reach deployment, backup and update controls from the same operational environment.

Why it matters

Include hosting and release operations in the product vision, rather than leaving the delivery layer invisible.

Cluster health, hosted instances, releases, backups and update controls are visible in the operator dashboard.

Who it’s for

Platform operator and team member.

Creative assets and release material need a discoverable place to live alongside the apps that use them.

The workflow

1. Open Drive from Havn.S.
2. Browse files using search, sorting and list/grid controls.
3. Use the visible Recent, Starred, Shared links and Trash destinations when managing material.

Why it matters

Offer familiar file navigation within the broader platform, alongside visible WebDAV settings.

Searchable file browsing includes recent files, starred items, shared links and trash, inside the HAVN environment.

Who it’s for

Clinic operator and person booking a treatment.

Treatment selection, appointment booking, deposits and reminders need to form a coherent service journey.

The workflow

1. Browse treatments grouped by domain.
2. Book a treatment and follow the deposit flow.
3. Receive reminders while staff manage the appointment context.

Why it matters

Extend the service-operations idea beyond events to appointment-based businesses.

The public site describes treatments, appointments, deposits and reminders. A live Medical app was not inspected.