The studio’s design tools.
Design decisions, drawings and accounting stay in their established systems. The pilot doesn’t try to replace the whole practice.
Alder & Row / Case study
The chair that
changed in one place.
What happened at Alder & Row between
choosing a finish and issuing the spec.
Practice
18 people
Project
A 28-room hotel
First workflow
FF&E selection to issue
Delivery
A bounded pilot
The problem
One change,
five documents.
A finish change reached the presentation board. The specification still showed the old selection.
Alder & Row is an interior design practice delivering Larch House, a 28-room hospitality project. Its designers had good tools for design and accounting. The difficulty was the repeated work between them.
Product selections lived in one sheet, room schedules in another, and images and notes were copied into a branded specification book. Each late change depended on someone remembering every place it appeared.
The scoped response
Keep their tools.
Fix the hand-off.
One selection record.
Each item gets a stable code, location, finish, quantity and supplier reference. Draft outputs read from that record.
Review before issue.
A revised selection returns to review. Issuing creates a fixed snapshot, so the team can recover exactly what was sent.
What the pilot delivers
What they got, and
what they own.
- A shared record
- The agreed item fields, approved naming rules and a checked import of the pilot project’s selections.
- Studio outputs
- A room schedule, a presentation-board view and a branded specification template.
- A review trail
- Draft, review and issue states, with changes visible and issued versions retained.
- A usable handover
- Team training, export instructions, source-code documentation and a defined support arrangement.
Where to start
Tell us where
the retyping happens.
Describe the task your team dreads and we'll tell you whether it's a setup fix, a connection or a build.