Halo Relay Product demonstration

Less chasing.
More delivering.

One place for the brief, the latest version and the decision that lets your team move forward.

Built by Halo. Self-initiated project, fictional agency and sample data.

Good work.
Shared clearly.

The decision stays with the version you reviewed.

The problem

“Which version did they approve?”

A brief in email. Feedback in a chat. A file called “final-final.” Your team has done the work, but the decision is still missing.

Relay demonstrates a clearer handoff: every request has an owner, every revision has a version, and delivery waits for the right approval.

Create a request with the work needed and a target date. Switch to the team view to assign an owner.

Request a change, prepare a revision and submit it again. An earlier approval never approves a newer version.

Approve the revised work and mark it delivered. The queue and decision history update as you go.

The workflow runs in your browser. There are no accounts to create, and no real client information to expose.

Working here: Request intake, ownership, revisions, feedback, version-specific approvals, delivery status and a session activity log.
Demo boundaries: Fictional data stored in memory; refreshing resets it. The client/team switch previews two perspectives, not authenticated access. Artwork is a sample, not an uploaded client file.
A client build would add: Agreed access controls, secure storage, real file versions, notifications, backups and the integrations your team needs. Each is scoped and tested separately.
Business value to measure: Time spent chasing feedback, approval turnaround and repeated revisions. No time-saving or revenue result is claimed from this demonstration.

Start with one workflow that slows your team down. We’ll agree the users, integrations and acceptance checks before quoting.