Hey Hunters,

Zyvia's intent-based task platform built mainly for:

• Devs

• Solo founders

• Vibe coders

• Small dev-heavy teams

The core idea is simple:

You research something.
You get an idea.
You type the intent.

The system turns it into structured, actionable tasks instantly.

No boards to configure. No 10-field forms. No ceremony.

The goal is to support this flow:

Research → Convert to tasks → Execute (with context) → Ship

The Architecture Decision

Originally, the structure was:

Workspace → Teams → Tasks

It made sense from a traditional SaaS perspective.

But in practice, our early users (mostly solo devs) didn’t think in “teams.”
They thought in:

• Repos

• Experiments

• Side projects

• Features

So we rebuilt the architecture to:

Workspace → Apps → Tasks

An “App” is basically a focused container.
It can represent:

• A repo

• A project

• A specific initiative

• Or just a clean task space

This reduced onboarding friction a lot. Instead of asking, “Create your team,” we now ask, “Create your app.”

It feels more intuitive for builders.

Current Status

• Core AI-driven task creation + querying live

• Real users managing real work

• ~10 paying users

• Still early, but retention looks more promising after the shift

Where I’d Love Feedback

1. Does “Apps” feel clearer than “Teams” for a dev-focused SaaS?

2. Is intent-based task creation something you’d actually adopt long-term?

3. If you landed on a site describing this, what would confuse you?