Case Studies
Every record on this page is written from one real project: the requirement we received, the work it took and the result that can be verified. Buyers stay anonymous by default, so a record describes the type of company and the market it sells into rather than naming it.
Anonymous by default
Client names, brand logos and testimonials appear on this website only with the client's written authorization. Until then a record describes the type of company, the market it sells into and the level of customization the project reached — never a name, a logo or a detail that identifies the buyer.
Every published record is based on a real project and meets at least two of the three kinds of evidence below. A project that cannot be shown this way is not published, not indexed and not written up as a marketing story.
01 — Published records
A record states what the buyer needed, what stayed standard in the range and what had to change, and what the delivery actually was. Only projects that can be shown are published here, so this page grows slowly by design.
Sample record for layout review. No real project, client, quantity, timing or result is described on this page: every field holds placeholder text written to show how a record reads, and the fields that would carry a verified figure are left empty on purpose.
Related products: PL-100 Picture Light 600 mm — Sample Data
Applications: Hotels & Hospitality (Sample Data)
Read the recordClient feedback appears only when the client authorized publication. Photographs, quantities, timings and documents behind a record are shared by email when a buyer asks about a comparable project.
02 — How a record is written
Every record follows the same parts, so two projects can be compared on the same facts instead of on adjectives. Each part is filled from the project file, and a part with nothing behind it is left out rather than written around.
Part 1
Who the buyer is in general terms, the market the goods are sold into, the level of customization the project needed, and the products and applications the record belongs to.
Part 2
The part that was not routine: the fitting, dimension, light output, mounting condition or market requirement the standard model did not meet on its own.
Part 3
The model the project started from, what stayed standard, and what was changed for this buyer — and why that was the shortest route to what they needed.
Part 4
The drawing, fixture or tooling work the change required, and the sample rounds it took to reach a sample the buyer could sign off.
Part 5
The checks agreed for that order, and the finish, packing or labelling requirements that had to be met before the run was released.
Part 6
How the order was produced, packed and shipped, and what the delivery actually was against the date that was agreed.
A record carries a figure only when the project file supports it. These are the results a record can state, and not every project reaches all of them.
Order quantity or range
The quantity ordered, or the range the buyer works in, when that is what the project file holds.
Development time
The time from the first technical review of the requirement to the sample the buyer approved.
Sample rounds
How many rounds of samples it took before the buyer signed the sample off.
On-time delivery
Whether the delivery met the date agreed for that order — stated as it happened, not as a general delivery promise.
Repeat order
Whether the same buyer ordered again after the first delivery.
A record states a result because the project file shows it, not because it sounds good: nothing here is an estimate, and no record promises that another project would reach the same quantity, timing or compliance outcome. Schedules, quantities, packing and any compliance question are confirmed per project and per model by email.
03 — What a record does not claim
A record shows what one project was. It does not claim what a different project would reach.
Client names, brand logos and identifying details are published only with written authorization. Where a client is described, it is described by the type of company and the market it serves.
Quantities, timings and outcomes appear as the project recorded them, and no record promises that another project would reach the same numbers, lead time or compliance outcome. Certification for a model and a market is confirmed by email, per model and per market.
The photographs behind a record are taken on that project. Illustrations, renders and photographs from another order are never presented as the evidence for a record shown here.
Customization level
A record names one level: the highest the project reached, so a standard order is never written up as a development project. The levels we work at are:
How far a change can go is answered after a technical review, per model and per project.
Send the model, quantity, finish, target market and the level of customization you need. A normal enquiry is answered within one working day with what we can supply and the next step, and a comparable project reference can be discussed by email.