Sales desk, name changed
Fieldstone's records desk
A records desk for a sales team: the week's new records sorted into one list, with an alert when a record changes.
- Services
- App or CRM
- Automation
- Stack
- Next.js, Fly.io, Vitest
- Updated

A week of records, all at once
Fieldstone is a fictional name for a real company, and every screen on this page shows sample data.
Its sales desk works from records. A new batch arrives every week, far more than a small team can read line by line, and most of it is not worth a call. The desk needed one place where the week lands already in order.
So every record takes the same short set of fields: a reference, a date, a region, a category, a scope, a size and a contact. Nothing is retyped, and nothing lives in a spreadsheet on one person's laptop.
Features
What it does
Every record carries the same fields, so the table reads the same from the first row to the last.
The list is built once the checks are ticked, and the button shows how many records it will take.
People who asked not to be called are held back before a list is built.
A change to a record becomes an alert that someone marks seen or handled.
The weeks side by side, by region and by category, so the desk can see where the work is moving.
Filters that leave the right records standing
Sorting is the real work. The desk narrows the week by region, by category, by stage and by whether a record is new. Each filter is a chip, and every chip that is on narrows the table further.
Some people should never get a call. The do-not-contact list is applied before a list is built, duplicates are folded into one row, and any single record can be left out by hand. A record that is left out stays on the screen, struck through, so nobody wonders where it went.
Sample
Click through a sample
The app on its own screens, with made-up data. On a computer, the controls work.
| Ref | Dated | Region | Category | Size | Stage | Leave out |
|---|---|---|---|---|---|---|
| HB-2041 | Monday | Harbor | Kitchen | Mid | Approved | |
| FH-1187 | Monday | Foothills | Solar | Small | Submitted | |
| VL-3310 | Tuesday | Valley | Addition | Large | Approved | |
| HB-2057 | Tuesday | Harbor | Roof | Mid | Submitted | |
| VL-3324 | Wednesday | Valley | Kitchen | Small | Approved | |
| FH-1202 | Wednesday | Foothills | Pool | Large | Approved | |
| HB-2063 | Thursday | Harbor | Solar | Small | Approved | |
| VL-3341 | Friday | Valley | Roof | Mid | Submitted |
One list a week, built on purpose
The week ends in a list. The button that builds it stays locked until the checks are ticked, and it shows how many records it will take before anyone presses it. Once it is built, the list is the sales team's work for the week.
The dashboard is the same week from above: what is new, what has been approved, what is on the list and what changed. Under the tiles sits the week day by day, then the short list of records that need a person to look.

Told when a record changes
Records keep moving after the list is built. One is approved, another changes size or moves to a different lane. Each change becomes an alert, and the person on the desk marks it seen or handled, from a phone if that is where they are.
The week now starts with a sorted list, and a change to a record reaches the desk the day it happens.

Stack
- Next.jsthe app, on Postgres
- Fly.ioa worker for the slow jobs
- Vitestthe test suite
Tell us what you are working on.
A few lines about your business is enough to start. We reply with questions and a plain next step.