LabProducts, systems, and experiments
We build the systems we wish existed.
We turn recurring market-development work into tools our teams and clients can use. Services reveal the need. The Lab develops the method. Products such as FAKTOR make that work easier to repeat.
01Why the Lab exists
Client work reveals the pattern.
02The build flywheel
From useful work to a useful system.
Solve
Work on a real commercial objective with a named owner.
Observe
Find the questions, handoffs and research that repeat.
Structure
Make evidence, decisions and relationship context reusable.
Prototype
Test a tool inside the actual analyst and sales workflow.
Review
Learn which outputs help people decide and what creates noise.
Productize
Make the useful workflow repeatable across client teams.
03Featured product
FAKTOR began with qualification. The relationship continues.
Exhibition work brought one question into focus: which companies deserve attention, and why? Economic zones, ports, industrial parks and B2B companies face related questions — with different objectives and longer horizons.
FAKTOR connects the initial case with the context that makes a later conversation useful. Our next work brings ongoing research, meaningful changes and two role-specific assistants into that cycle. We develop it through focused client programmes and pilots.
Explore FAKTORWhat repeats becomes a system. What survives review becomes a product.
04Current work
One connected development path.
FAKTOR — Commercial Intelligence
Company research, qualification, analyst-to-sales review and interaction history form the existing product foundation.
Product foundation02Ongoing relationship development
LND research and client-owned conversations can support continuity now. Monitoring and recommendations are the next product workflow to validate.
Managed programme03Analyst & Sales assistants
Two conversational entry points: what needs researching, and what deserves commercial attention next.
In development04Repeatable client workspaces
A consistent way to configure, deliver and maintain Faktor for different teams as the operating model proves itself.
Development directionEach engagement defines the current software, the work delivered by LND and the product capabilities being tested. Public self-service access is not available at this stage.
05What belongs in the Lab
Five tests.
- 01
It repeats across clients or markets
- 02
It has a structured decision
- 03
The output can become reusable
- 04
Memory improves future work
- 05
The system can create value beyond one engagement
06Build principles
Discipline, written down.
- 01
Product objects before feature lists
- 02
Context before automation
- 03
Human judgment where consequences are high
- 04
Model-neutral domain logic
- 05
Evidence and uncertainty stay visible
- 06
Client data boundaries are explicit
- 07
A platform is earned, not declared
07Ways in
Work with the Lab.
Design Partner
Help shape and test an emerging system.
Pilot Client
Use a bounded product or method on a real commercial problem.
Strategic Partner
Contribute distribution, data, domain expertise, or integration.
Custom Build
Develop a repeatable research or relationship workflow with LND.