# One useful experiment, before a larger partnership

**A conversation brief for Ness Labs · Prepared by Smart Tech CTC · 5 November 2026**

## Start with a problem worth solving

We would like to understand which digital initiatives, AI experiments, or everyday workflows matter most to Ness Labs—and whether a focused contribution from our engineering team would be useful.

Your essay [*The Omnipotence Dilemma*](https://nesslabs.com/omnipotence-dilemma) prompted a question: when ideas become easier to start, what helps a team decide which ones deserve to be finished? The community app and team dashboard you mentioned are useful conversation starters. We would first ask whether they still matter, what you have learned since, and what your team needs today.

## Why we wanted to connect

Our founder spent five years in business development at Emotiv in Vietnam, working around EEG applications and consumer research. That commercial experience informs an interest in cognition and how technology affects people. Your work at Ness Labs adds a practical question we share as founders: how can we learn from small experiments before committing to a bigger direction?

CTC brings software engineering experience. We would value your perspective on the problem, the people affected, and the parts of their work that should remain human.

## Choose one small test

A useful starting point could be one recurring task where the current approach creates avoidable effort or errors. We would map that task with its owner, consider whether a process change is enough, and identify what a prototype would need to demonstrate.

For example, if preparing a recurring team summary is a real difficulty, we could compare the current process with a small prototype using the same synthetic input. Completion time, factual errors, and review effort would make the trade-offs visible. This is an illustration, not a diagnosis of Ness Labs’ needs.

## A possible 14-day pilot—after scoping

If there is a suitable task, we could agree on a bounded pilot with:

- **A named owner on each side**, one task, and a written scope.
- **A baseline and success measure**, including quality and review effort.
- **A demonstrable prototype using synthetic data**, with limitations made explicit.
- **An agreed review date and go/no-go decision:** continue, revise, or stop based on what we learn.

The proposed duration would be confirmed after scoping. Pricing, IP, content permissions, data access, handover, and ongoing support would be agreed before work begins. Production deployment would require a separate readiness decision.

## An optional illustration

[TinyExp](https://tinyexp.smarttechctc.io) is an independent prototype inspired by *Tiny Experiments*. It is not affiliated with or endorsed by Ness Labs. A 60-second walkthrough may help illustrate an idea if it is relevant to our conversation; its production readiness has not been established here.

## A useful next step

A short conversation could establish whether there is a worthwhile problem and who should help scope it. If there is no current need, that is a useful conclusion too. Over time, we would also welcome relevant opportunities to support founders or researchers in your network.

[Smart Tech CTC](https://smarttechctc.io) · [PowerIT engineering](https://powerit.smarttechctc.io/en/) · [AI Studio](https://aistudio.smarttechctc.io)