Observe
Find recurring frustrations, awkward hand-offs, and inefficient workflows worth understanding.
Independent product studio
Finding overlooked problems. Building useful software.
We investigate recurring business frustrations, validate their impact, and build focused software around the opportunities worth pursuing.
Observe → validate → build only when the evidence earns it.
Researching Current state · August 2026
Currently researching opportunities for our first product.
We are studying markets, speaking with people, testing assumptions, and sharing useful findings. There is no launched product or claimed traction yet—only disciplined discovery in progress.
Method
A problem has to earn the build.
Each stage is a decision point. Evidence can move an opportunity forward, narrow it, or stop it before more is built.
Validate
Speak with affected people and measure the frequency, consequence, and limits of current options.
Build
Create the smallest useful solution that can test the central promise in real work.
Launch
Introduce it first to the people who helped shape it, then learn from observed use.
Current explorations
Themes under observation.
These are research themes, not validated opportunities or product announcements. All are currently at the observing stage.
Observing
Repetitive work still managed through spreadsheets
Repeated copying, checking, and reconciliation can turn a flexible spreadsheet into a fragile workflow.
Last updated Aug 6, 2026
Observing
Fragmented workflows across multiple tools
Important context can become scattered when a process crosses several tools, inboxes, and hand-offs.
Last updated Aug 6, 2026
Observing
Reporting and coordination bottlenecks
Routine reporting can depend on chasing inputs, normalising formats, and rebuilding the same view each cycle.
Last updated Aug 6, 2026
Observing
Manual processes that consume small teams’ time
Necessary but repetitive tasks can quietly take time away from customer work and higher-value decisions.
Last updated Aug 6, 2026
Field Notes
Research and decisions, kept in the open.
Durable notes on product discovery, experiments, decisions, and the lessons that remain useful.
What makes a workflow worth investigating
A practical set of questions for deciding whether an awkward process deserves closer product research.
Why we start with problems, not ideas
A useful product is more likely to emerge from a well-understood problem than from enthusiasm for a solution.
Open research channel · 01
Have a recurring problem worth investigating?
Tell us about work that is frustrating, repetitive, expensive, or unnecessarily manual. A useful description is more valuable than a polished pitch.
Share the problem