yellow3 lab / platforms

We go deep into things we believe matter.
Sometimes the outcome is a platform.

yellow3 lab researches markets, technologies and systems where important change is happening. We do the deep work first. When that research exposes a problem that can be solved more practically with software, we build the platform ourselves.

Research tells us what matters. The platform turns that understanding into something people can use.

How we work
01
Problem

Start with something worth understanding.

We look for areas where complexity, new technology or structural change is making important decisions harder than they need to be.

02
Research

Go deep before building.

We map the market, examine the evidence, find what is missing and make the underlying problem visible before deciding whether software is the answer.

03
Platform

Build around the outcome.

When research shows that a repeatable system can help people act, we build the platform around the outcome rather than the technology.

Area 01 / Digital Product Passport

A new transparency requirement created two buyer problems.

Digital Product Passports will change how product information moves through the European economy. That transition creates new obligations, a new technology market and a difficult implementation problem for manufacturers. yellow3 lab approaches that market from the buyer's side.

01
Problem

Who is actually in this market, and what can they demonstrate?

We research the global DPP supplier market independently. We establish who is in the market, what suppliers publicly claim, what can actually be demonstrated and what remains unproven.

Built from that research

DPP Supplier Register

An independent public research database and global supplier register for Digital Product Passport capability. Evidence-led, sourced and open to inspection.

Explore the Supplier Register →
Current yellow3 DPP Supplier Register interface
Public research.
Free to use.

Suppliers cannot pay to appear differently, rank higher or improve an assessment.
02
Problem

How does a buyer turn a regulatory obligation into an implementation programme?

The supplier research exposed the next problem. Buyers still had to establish requirements, understand their own product and data gaps, compare providers on evidence, manage dependencies and determine whether implementation had actually delivered what was promised.

Built from that research

DPP Buyer Platform

A private buyer-side operating platform for organisations planning, buying and implementing Digital Product Passport capability. It brings requirements, product facts, supplier evidence, provider selection, implementation and the decision record into one programme.

Plan what is required. Establish what you already have. Identify what is missing. Compare providers on evidence. Manage implementation. Keep the evidence and decision record.

yellow3 lab does not operate Digital Product Passports. The platform works for the organisation buying and implementing them.

Open the DPP Buyer Platform →
Current yellow3 DPP Buyer Platform interface
Plan.
Source.
Implement.
Prove.

Independent buyer infrastructure.
Area 02 / Software creation

The people who understand the problem should not need to become software engineers.

People inside businesses often know exactly what outcome they need, but cannot translate that knowledge into architecture, code and production software. That keeps useful ideas dependent on scarce technical capability.

03
Problem

What if describing the outcome were enough to start building?

Our work on outcome architecture starts from a different premise: the valuable human input is the definition of the desired outcome. The system should handle more of the translation from direction to implementation.

Built from that work

naffe.ai

naffe.ai turns plain-language direction into working software. It is designed for people who understand the problem they want to solve, not the technology required to build the solution.

Explore naffe.ai →
Current naffe.ai interface
If you can describe the outcome, naffe.ai builds the software.
The platform is not the starting point.

Research comes first.

We do not begin by looking for software to build. We begin with a problem worth understanding. If the problem deserves a platform, we build one.