All projects

Product work across different real constraints.

Explore every project, including working products and in-progress builds.

Back to home

PlifeOS

Working product

Problem

Capturing daily data is slow and fragmented

Decision made

Use a single command input instead of form-heavy flows so daily capture stays fast enough to become a habit.

Trade-off

Cut backend sync and deeper organization in the first version to prove the speed thesis first.

Outcome

Command-based system for fast input and structured tracking

Why it matters

It shows that the core product decision was reducing interaction cost, not adding more features around the same friction.

View case study

RapidPulse

Working product

Problem

People see data but can't trust its freshness or source

Decision made

Make freshness and source visibility part of the product system instead of hiding them behind the interface.

Trade-off

Accepted narrower coverage and more explicit empty states to keep trust higher when information is incomplete.

Outcome

Trust-first data platform with source visibility and fallback logic

Why it matters

It proves that trust can be designed structurally through product decisions, not added later as surface messaging.

View case study

Riya AI

Working product

Problem

Jewellery businesses lose leads through slow WhatsApp handling

Decision made

Constrain the system around escalation rules and trust instead of aiming for open-ended AI conversation.

Trade-off

Reduced automation range in exchange for higher reliability in a sales flow where trust matters more than novelty.

Outcome

Controlled AI sales employee designed around trust and escalation

Why it matters

It shows that a smaller, controlled MVP can be the stronger product decision when the business risk of bad answers is high.

View case study

Dundoo

Working product

Problem

AI answers are fast but often weak on trust and exploration

Decision made

Center the product around evidence and guided understanding instead of answer speed alone.

Trade-off

Accepted a slower interaction model in exchange for higher trust and better depth.

Outcome

Evidence-first knowledge product focused on understanding, not just answers

Why it matters

It demonstrates how the shape of the product changes when trust and exploration are treated as primary needs.

FurryFun

Early build / concept-supported

Problem

Virtual pet apps often feel limited or outdated

Decision made

Focus the MVP on emotional engagement and retention loops instead of broad feature depth.

Trade-off

Chose a narrower product surface so the early experience could feel more alive and repeatable.

Outcome

MVP-first pet product focused on emotional engagement and retention

Why it matters

It shows how product value can come from selecting the right loop first instead of expanding scope too early.