# HAVN — the work behind the night

Private portfolio review · Jean-Christophe Bougnet · 21 October 2026

## The portfolio introduction

Book the artists. Plan the crew. Build the campaign. Run the door and the bar. Follow the money.

HAVN brings these jobs into a family of focused applications, supported by a common portal, a shared people directory and its own hosting platform. The scope reaches from artist discovery and event operations to AI assistance and a desktop instrument for live visuals.

I conceived HAVN as an ecosystem: the tools people use, the relationships between their roles, and the platform that delivers the software. It is my long-term product vision, carried across the detail of individual workflows and the structure of the wider family.

## A portfolio card

**HAVN / THE WORK BEHIND THE NIGHT**

An original product vision spanning artist bookings, crew planning, audience communication, ticketing, venue operations, event finance and live visual creation—with the portal, shared directory and hosting layer behind them.

**Original vision and product conception: Jean-Christophe Bougnet.** Specific implementation and collaborator credits remain to be confirmed.

## A story told through the work

### Book the artist. Prepare the show.

Agency pairs public artist discovery with a private booking desk. Office brings bookings, correspondence and advancing queues into the promoter’s workspace. Production organises tasks and crews by build, show and derig.

Use screens 19 → 18 → 05 → 07. Together they show a product vision organised around the people and stages that make a show possible. Screen 18 contains private booking figures.

### Reach the audience. Run the night.

Newsletter offers a visual campaign editor with desktop and mobile views. Tickets puts event details and ticket categories beside operational routes for orders, attendees and admission. OFF CLUB exposes the venue’s membership, door, till, stock and sales tools. Ledger separates forecast figures, commitments and actual cash.

Use screens 09 → 12 → 03 → 16. This is the ecosystem’s operational story; the walkthrough did not execute a transaction across these apps or establish automatic data transfer between them.

### Make the visuals. Deliver the software.

Pixel Mixer combines four-deck visual mixing, effects, sequencing and pixel animation editing. Its web Space displays computer access and shared creative assets. Portal, Havn ID, Drive and Havn.S reveal the wider platform: app access, people records, files, instances and releases.

Use screens 23 → 26 → 20 → 01 → 13 → 21. These screens demonstrate the breadth of the product conception through actual interfaces.

## Why this belongs in the portfolio

**A vision across the whole system.** The work covers specialist applications and the platform through which they are accessed and operated.

**A structure grounded in real tasks.** Artist advancing, crew phases, ticket categories, a current bar order and unpaid commitments are specific operational concepts visible in the apps.

**Different interfaces for different moments.** A public artist roster, a visual email editor, a focused till and a four-deck mixer each give their task a distinct working surface.

**States that matter.** Missing information, overdue work, forecast versus cash and an unconfigured AI provider are made explicit in the inspected interfaces.

## Evidence behind the presentation

The private collection contains 29 original dark-interface screenshots and use cases for 17 identified products or directions. Fifteen app/platform surfaces were inspected directly. Medical is described on the public website only; HAVN Build is explicitly marked coming soon. Tast Assist’s two light screenshots are omitted because the inspected build has no dark control, while its use case remains documented.

The server listed 13 hosted instances across nine web app types; this is an instance count, not a customer count. No revenue growth, time saving, adoption, production scale, payment reliability or business outcome is claimed. Displayed record counts, model options and health checks are not independent proof of those outcomes.

The walkthrough inspected screens and navigation. It did not execute real payments, campaign sends, admission scans, financial entries, syncs or deployments. AI generation and terminal commands were not run. Features visible in navigation are distinguished from executed workflows in the product evidence notes.

Appearance was changed for the dark capture edition: OFF CLUB’s Starlink Dark preset, Office’s Sober Dark preset, native Newsletter and Connect toggles, macOS Dark for Pixel Mixer and Space, and Production’s existing Custom CSS appearance setting. Screenshot pixels were not recoloured, cropped or reconstructed. The Newsletter canvas retains the existing email’s white content background.

The full images remain unredacted for private review at the owner’s request. They include account, personal, device and commercial information. No material was publicly published or uploaded. Publication requires a separately prepared screenshot selection and confirmed contribution credits. Public prices and conflicting version labels are excluded from the portfolio claims.

## Product use cases

### Agency / HAVN Booking

**Put your artists in front. Keep the booking desk behind them.**

**For:** Artist agent, agency owner and promoter.

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

**Use case:**

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.

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

**Intended value:** A public artist roster, enquiry form and private workspace for shows, fees and commissions.

**Evidence:** Public roster and enquiry form inspected; private overview shows bookings, roster, artist fees, commission and outstanding amounts.

**Boundary:** No enquiry submitted or booking changed. Existing amounts are private context, not verified commercial results.

**Screens:** [18-agency-overview-private.jpg](screenshots/18-agency-overview-private.jpg), [19-agency-public.jpg](screenshots/19-agency-public.jpg)

### Office / MTS

**Every booking has a next step.**

**For:** Promoter, booking coordinator and artist liaison.

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

**Use case:**

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.

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

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

**Evidence:** Dashboard and Advancing inspected. Navigation includes Bookings, Artists, Missing info, Agents, Events, Tours, Messages, Mail and Marketing.

**Boundary:** This tenant is empty. Mail delivery, reminder execution and completed booking workflows were not tested.

**Screens:** [04-office-dashboard.jpg](screenshots/04-office-dashboard.jpg), [05-office-advancing.jpg](screenshots/05-office-advancing.jpg)

### Production / LinkP

**Build. Show. Derig. Know who belongs where.**

**For:** Production manager, crew coordinator and site lead.

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

**Use case:**

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.

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

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

**Evidence:** Overview and Schedule inspected. Menus expose Plan, People, On site, Bar/food/parking and Flow.

**Boundary:** The captured tenant has no crew or tasks. No clock-in, roster change, notification or cost calculation was exercised.

**Screens:** [06-production-overview.jpg](screenshots/06-production-overview.jpg), [07-production-schedule.jpg](screenshots/07-production-schedule.jpg)

### Events / OFF CLUB

**The door. The bar. The night’s numbers.**

**For:** Venue manager, bartender and door staff.

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

**Use case:**

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.

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

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

**Evidence:** Dashboard and till inspected. Sales, Products, Stock, Tickets, Staff and kiosk setup are visible destinations.

**Boundary:** No sale, payment, refund or scan was executed. The tenant is mostly empty and has a test product. Payment and stock consistency are not established by these captures.

**Screens:** [02-offclub-dashboard.jpg](screenshots/02-offclub-dashboard.jpg), [03-offclub-till.jpg](screenshots/03-offclub-till.jpg)

### Havn Tickets / TixoAI

**Your event. Your ticket categories. Your door.**

**For:** Event promoter, ticket buyer and check-in staff.

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

**Use case:**

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.

**Product decision:** Group operational actions around each event, with ticket categories edited alongside event details.

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

**Evidence:** Promoter dashboard and an existing event editor inspected, including published events and ticket category controls.

**Boundary:** No event saved, ticket purchased, attendee scanned or order exported. Existing event names are retained as captured.

**Screens:** [11-tickets-dashboard.jpg](screenshots/11-tickets-dashboard.jpg), [12-tickets-editor.jpg](screenshots/12-tickets-editor.jpg)

### Havn Newsletter / NL Builder

**Build the message. Check desktop and mobile.**

**For:** Promoter, marketer and newsletter editor.

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

**Use case:**

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.

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

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

**Evidence:** Analytics and an existing campaign editor inspected in desktop and mobile modes. Blocks include text, image, event, product, video, HTML and footer.

**Boundary:** No content edited and no campaign sent. Subscriber totals are displayed records, not evidence of engagement; the dashboard shows no campaigns sent.

**Screens:** [08-newsletter-analytics.jpg](screenshots/08-newsletter-analytics.jpg), [09-newsletter-editor.jpg](screenshots/09-newsletter-editor.jpg), [10-newsletter-mobile.jpg](screenshots/10-newsletter-mobile.jpg)

### Connect / Havn ID

**See the person across the apps.**

**For:** Organisation administrator and audience manager.

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

**Use case:**

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.

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

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

**Evidence:** Overview inspected with nine connected-app categories, shared audiences, duplicate review and sync controls.

**Boundary:** No synchronisation, merge or pairing was triggered. Counts reflect this screen’s state; identity accuracy and deduplication were not independently verified.

**Screens:** [13-connect-overview.jpg](screenshots/13-connect-overview.jpg)

### HAVN Ledger

**Know what is planned. Know what is paid.**

**For:** Event producer, business owner and accountant.

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

**Use case:**

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.

**Product decision:** Distinguish the forecast from actual cash and keep supporting documents in the financial workflow.

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

**Evidence:** Financial overview and Reports & tax inspected; navigation also exposes billing, bank, providers, invoices and team/accountant.

**Boundary:** No entries or documents added. The VAT screen explicitly describes a provisional recorded VAT difference and says it is not a statutory Belgian VAT return; this is not proof of a complete accounting system.

**Screens:** [16-ledger-overview.jpg](screenshots/16-ledger-overview.jpg), [17-ledger-reports.jpg](screenshots/17-ledger-reports.jpg)

### Tast Assist / NOVA

**A place for the day. A workspace for the project.**

**For:** Individual professional and project owner.

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

**Use case:**

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.

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

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

**Evidence:** Home and Workspace inspected. Current workspace says “AI provider not connected.”

**Boundary:** No project or reminder created. AI execution in Tast Assist was unavailable at inspection; the separate HAVN AI interface must not be presented as already integrated here. Dark capture pending: this build forces light mode and has no theme control; its two light captures are omitted from the dark edition.

**Screens:** 

### HAVN A.I.

**Choose the task. Choose the model.**

**For:** Creator, researcher, writer and developer.

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

**Use case:**

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.

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

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

**Evidence:** AI home, code starting state and model menu inspected. Modes include See, Generate image, Translate, Talk and Knowledge; a terminal panel was also visible.

**Boundary:** No generation, command or provider call initiated. Listed models, prices and capabilities are app-displayed options, not independently verified availability or pricing.

**Screens:** [24-havn-ai-home.jpg](screenshots/24-havn-ai-home.jpg), [25-havn-ai-models.jpg](screenshots/25-havn-ai-models.jpg)

### Pixel Mixer desktop

**Mix the visuals. Shape the pixels.**

**For:** Visual performer, lighting designer and live-event creator.

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

**Use case:**

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.

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

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

**Evidence:** Existing desktop app opened successfully. Perform and Pixel editor screens captured; existing decks, timeline and pixel frames visible.

**Boundary:** No controls, clips or sequences were changed. Physical LED output, MIDI, audio synchronisation and multi-machine behaviour were not tested.

**Screens:** [23-pixel-mixer-perform.jpg](screenshots/23-pixel-mixer-perform.jpg), [26-pixel-mixer-editor.jpg](screenshots/26-pixel-mixer-editor.jpg)

### Pixel Mixer Space

**A shared home for the creative setup.**

**For:** Studio administrator and visual production team.

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

**Use case:**

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.

**Product decision:** Separate desktop performance from web-based computer access and shared-library administration.

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

**Evidence:** Space dashboard inspected with one connected Mac and shared preset, sequence, playlist, clip and audio setup counts.

**Boundary:** No computer connected, removed or renamed. No library changed. Synchronisation across two machines was not tested.

**Screens:** [20-pixel-mixer-space-private.jpg](screenshots/20-pixel-mixer-space-private.jpg)

### Havn Portal

**One account. Your apps within reach.**

**For:** Organisation owner, administrator and team member.

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

**Use case:**

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.

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

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

**Evidence:** Signed-in My apps inspected with 11 entries. Open actions reached operational apps. Available-plan dropdown inspected without subscribing.

**Boundary:** Billing, purchases, permissions and team changes were not exercised. An Open action reaching an app is evidence of that navigation, not a full authentication audit.

**Screens:** [01-havn-portal.jpg](screenshots/01-havn-portal.jpg)

### Havn.S

**The platform behind the products.**

**For:** Platform operator and release administrator.

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

**Use case:**

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.

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

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

**Evidence:** Overview and Client apps inspected. Overview listed 13 hosted instances across nine app types; desktop installer/licence administration was also visible.

**Boundary:** No update, repair, backup, restart or infrastructure change executed. Health checks and displayed versions are observations, not load tests, uptime guarantees or reconciled release truth.

**Screens:** [21-havns-overview-private.jpg](screenshots/21-havns-overview-private.jpg), [22-havns-client-apps-private.jpg](screenshots/22-havns-client-apps-private.jpg)

### Havn Drive

**Keep the material close to the work.**

**For:** Platform operator and team member.

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

**Use case:**

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.

**Product decision:** Offer familiar file navigation within the broader platform, alongside visible WebDAV settings.

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

**Evidence:** Embedded Drive opened successfully and displayed folders, downloads, sharing actions and storage information.

**Boundary:** No file opened, shared, uploaded, deleted or downloaded. Storage durability, sharing permissions and WebDAV operation were not tested.

**Screens:** [28-havn-drive.jpg](screenshots/28-havn-drive.jpg)

### Hospitality / Medical

**Appointment-based services, in the public product range.**

**For:** Clinic operator and person booking a treatment.

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

**Use case:**

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

**Product decision:** Extend the service-operations idea beyond events to appointment-based businesses.

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

**Evidence:** Public HAVN product card lists treatments, online booking, deposits, reminders and before/after patient photos.

**Boundary:** No live Medical tenant was found in the inspected account, server list or subscription catalogue. This is public-site scope only, not a verified application walkthrough. No patient records accessed.

**Screens:** [30-medical-public-description.jpg](screenshots/30-medical-public-description.jpg), [27-havn-public-products.jpg](screenshots/27-havn-public-products.jpg)

### HAVN Build

**A direction for the next chapter.**

**For:** Organisation needing a tailored workflow.

**Need:** An organisation may need capabilities spanning several specialist products.

**Use case:**

1. Select relevant features from the app family.
2. Apply the organisation’s name and visual identity.
3. Use the proposed single-app delivery model.

**Product decision:** Explore modular capabilities as the basis of a tailored offering.

**Intended value:** The public roadmap describes a custom app assembled from capabilities across the family. It is marked coming soon.

**Evidence:** The public website explicitly labels HAVN Build “Coming soon.”

**Boundary:** Roadmap concept only. No custom build configuration, compilation or deployed result was observed.

**Screens:** [31-havn-build-coming-soon.jpg](screenshots/31-havn-build-coming-soon.jpg), [29-havn-public-home.jpg](screenshots/29-havn-public-home.jpg)

## Source locations

Screens were inspected in the owner’s existing signed-in native/browser sessions. The public website is [havn.website](https://havn.website/). App addresses: [Portal](https://saas.havn.website/app), [Agency](https://agency-test.havn.website/), [Office](https://offic.havn.website/), [Production](https://linkp.havn.website/), [OFF CLUB](https://offclub.havn.website/), [Tickets](https://tixoai.havn.website/), [Newsletter](https://emailling.havn.website/), [Connect](https://connect.havn.website/), [Ledger](https://ledger-beta.havn.website/), [Tast Assist](https://tast-assist.havn.website/), [HAVN AI](https://ai.havn.website/), [Pixel Mixer Space](https://pixelmixer-space.havn.website/), [Havn.S](https://server.havn.website/), [Drive](https://drive.havn.website/). Access may require the owner’s session.