# A quoting desk for a freight forwarder.

> A studio project. An interface where an agent drafts each freight quote and a planner approves it.

- Sector: Logistics
- Year: 2026
- Project: Tessenby Freight
- Client: Self-initiated
- Services: Product design, Development

Tessenby Freight is a studio project about one desk in a freight forwarder: the place where quote requests arrive. We designed the brand and the interface for an agent that drafts each quote and a planner who approves it.

## In the project

- Name and wordmark
- Palette of four tones
- The quoting desk
- A drafted quote with its checks
- Component set

## The problem

A quote request looks simple and is not. Someone has to read the email, work out the route and the load, find the rate, check that a truck has room, and add the margin. Often those facts live in three places: an inbox, a rate sheet and a planning tool. The reply is as fast as the slowest of them.

The cost is not only time. A quote that arrives late is often a quote that loses, and a planner who spends the morning copying numbers has no time left for the requests that need judgement.

## What we made

A name, a wordmark, a palette of deep navy and signal orange, and the quoting desk on this page. The desk lists the day's requests and opens each one as a drafted quote with its checks. The screens are built in HTML and CSS, the way they would ship. They are not pictures of a design.

## Who it is for

- The planner: Approves quotes all day. Needs to trust a draft in a few seconds, or see at once what to correct.
- The customer: Sent a request and is waiting. Needs a price and a departure day, not an acknowledgement.
- The operations lead: Sets the margin rule. Needs to know it is applied the same way on every quote.

## What we did

### Product design

Used: User interface, User experience, Dashboards.

1. Map the task: From a request arriving to a quote being sent: who touches it, and where it waits.
2. Design the flow: One request open, the rest in a list, and approve as the main action.
3. Draw the screens: The quoting desk and the drafted quote with its checks.
4. Set the components: Buttons, labels, rows and fields in one set.

### Development

Used: Front-end, Astro.

1. Build the screens in code: The desk and the quote are built in HTML and CSS inside Astro components. They are not exported images.
2. Make them scale: Every size is relative to its container, so one drawing works as a card, a cover and a figure.
3. Check on a phone: The same drawing is checked at 390 pixels wide.

## Design decisions

1. Show the checks, not only the price. A price on its own asks for blind trust. The draft lists the three things the agent did: matched the rate sheet, found capacity, applied the margin rule. A planner can approve on evidence. Instead of: A single confidence score. It hides which step is weak.
2. One request open, the rest in a list. The planner works one quote at a time. The list on the left shows what is waiting and its state: drafted, review or sent. Instead of: A table of all requests with inline editing. It is dense, and it is easy to approve the wrong row.
3. Orange means a person is needed. The signal colour marks two things only: the request that is open and anything waiting for review. Everything else stays navy and off-white. Instead of: A colour per status. Five colours on one screen stop meaning anything.
4. Approve is the primary action. The most common outcome is a correct draft, so one button sends it. Editing is one step further away, on purpose. Instead of: Equal buttons for approve and edit.

## How it works

1. Read: The agent reads the request: the route, the load and the pickup day.
2. Check: It matches the rate sheet, looks for capacity and applies the margin rule. Each check is listed on the draft.
3. Review: A planner approves the draft, or edits it and then approves.
4. Learn: Every edit stays beside the request, which is how the next draft improves.

## The principle

A planner should see why the price is what it is.

## What it is built to change

- Time from request to quote: Measured from the time a request arrives to the time its quote is sent, per request.
- Drafts approved without changes: The share of drafts a planner sends as written. It shows how good the drafts are, and it should rise as edits are kept.
