01
A product should explain itself.
If a first-time user needs a call to understand what they are looking at, the design is unfinished. Everything we ship has to be legible in the first minute.
A digital product studio — EU
Software should answer for itself.
We build a small portfolio of digital products that do one useful thing on the first day you open them — and tell you, honestly, where they fell short.
What we believe
02
Design is not the wrapper.
The interface decides what the software is allowed to do. We design the behaviour first and let the screens follow, which is why our products have fewer of them.
03
Small, specific, and in the open.
Narrow products beat platforms. We would rather run five sharp tools than one suite nobody finishes configuring.
04
Data stays where it belongs.
EU-hosted by default, minimal retention, and no training on customer content. Trust is a design constraint, not a policy page.
The portfolio
Live · more in the worksLive
AskConcierge
A concierge for events and venues. Point it at a programme, share a link — and end the day knowing what people needed that nobody had written down.
- Answerretrieval · grounding
- Signalwhat people asked
- Operatorgaps · queues · control
Capability 01
Answer layer
Grounded retrieval over your own material. It answers from what you gave it, or it says so.
Capability 02
Signal layer
Every question is demand data. What people asked, in what language, and what you had not written down.
Capability 03
Operator layer
Gaps, queues and one screen where a human decides. Software that hands work back cleanly.
These are the layers every product we build shares. When one of them turns out to be worth more than the product it came from, it becomes its own company.
The practice
Small team. Short distance between idea and users.
Founder-led, EU-hosted, no growth theatre. We take on a limited amount of partner work when the problem sits close to something we are already building — that work funds the portfolio and sharpens it.
hello@pulsierlabs.com →01
Start with a narrow bet
We write down the single question the product answers. If we cannot state it in a sentence, we drop it.
02
Get something real in front of users
Not a prototype — a link you can put in front of people, with the instrumentation already in it.
03
Ship, then read the misses
We watch what it failed to answer, on a regular cadence, and fix in that order.
04
Keep, spin off, or stop
A product that earns its place stays. One bigger than the studio becomes its own company. The rest we retire in public.