Consulting

I help lighting manufacturers put their product data in order with a PIM (Product Information Management): a single source of truth.

For lighting manufacturers who still update their data by hand.

If your website, datasheets and price lists still come out of Excel files and manual work, this page is for you. I work with several lighting manufacturers on 4 continents: North America, Australia, Asia and Europe.

Manual M carries the data by hand. Then the supplier changes the driver, and every sheet in the pile has to change too. Automated A changes one record, and the rest follows. In your company, who carries the pile?

Manual M carries a shaky pile of papers. Automated A holds one finished record.

Lighting data is hard. Excel and manual work can't keep up.

Take one luminaire. It carries dozens of attributes and needs many files: datasheets, installation manuals, IES and LDT files, CE documents. Multiply that by every language and a version for each market. Then the supplier changes the driver. Every one of those files, and the website, has to change too.

One luminaire needs dozens of attributes, many files, several languages and a version for each market. 1 luminaire Dozens of attributes Many files Several languages A version for each market
Example: 13 files in 6 languages make 78 files for one luminaire, before any market version.

PIM Steps: from the first call to launch, in five steps.

Step 0 takes about 2 months. Steps 1 to 4 take 3 to 6 months.

  1. Proposal. First I learn the project. Where does the data come from: manual updates, Excel, or your CRM or ERP? Where should it go: the website, datasheets, catalogues, installation manuals? Who will I work with? How many products and languages are there? Then I propose a solution, with a budget and a timeline.
  2. Discovery. Once you sign, I work closely with your team and define the project in detail. Phase 1 stays close to the bare minimum: the website and the datasheets. If the base is weak, everything after it gets harder.
  3. Data structure. I design the data structure and write a brief for each output. Sometimes the product ordering logic needs a rewrite too. At B-K Lighting, I did that rewrite myself, after two factory visits.
  4. Coding and data entry. The coding team builds the integrations and the outputs from the briefs, on sample data first. At the same time, your team enters the full catalogue. This is often the hard part, so I stay close.
  5. Launch. The website and the datasheets go live, and Phase 1 closes. It's often a proud moment. It's also when you start to see the return. Then most clients look at the next manual process: price lists, installation manuals, catalogues, BIM files.
The method as a building. Phase 1 is the foundation: the PIM, the website and the datasheets. Phases 2 and 3 are the floors above it. Phase 1 PIM, website, datasheets Phase 2 Price lists, installation manuals Phase 3 Catalogues, BIM files

I own the project, from Step 0 to launch.

I don't sell a tool and walk away.

Data structure
I design it. When the old product ordering logic doesn't hold, I rewrite it.
Responsibilities
We agree who enters which data, who approves it and who holds the technical information.
Vendors
I manage the PIM vendor and the coding team. If a vendor slows the project down, I say so and propose a change.
The project
The schedule, the meetings, the decisions, and training for your team along the way.
The record
Every project runs in its own Basecamp project from day one. Every decision, file and meeting note sits there, and you keep it. A new team member reads the history instead of asking around.
One owner in the middle: me. Around me: your team, the PIM vendor, the coding team and the Basecamp record. Me, the project owner Your team PIM vendor Coding team Basecamp record

What it costs, and who gets paid.

The budget has three parts.

The PIM licence

The annual Sales Layer subscription, at Sales Layer's own price. It costs you the same when you work with me.

The coding

Paid to the team that builds the integrations and the outputs. If you have your own coding team, this part goes to zero. A team with no PIM experience can slow the project down, though.

My fee

For the project work only. I take no cut from coding vendors, so my advice has no hidden reason.

You see the figures in the Step 0 proposal.

Results

B-K Lighting, a US outdoor and landscape lighting manufacturer

Before PIM, the technical data sat in Excel, the website was updated by hand, and the spec sheets and price sheets were InDesign files. Now the website, the spec sheets and the price sheets all come from the PIM. In December 2025, a big price update went through in a couple of days. Before PIM, the same update took a couple of months.

Read the B-K Lighting case study

B-K Lighting before and after PIM. Before: technical data in Excel, a website updated by hand, spec sheets in InDesign, and a big price update in a couple of months. With PIM: all of it comes from the PIM, and the same update takes a couple of days. Before PIMWith PIM Technical data In Excel Technical data In the PIM Website Updated by hand Website From the PIM Spec sheets InDesign files Spec sheets From the PIM Price update A couple of months Price update A couple of days

Let's talk about your product data.