2
3 Comments

Kanban boards are a second job. I built a deck instead.

At some point my task board stopped tracking the work and became the work. Dragging cards between columns, updating statuses nobody read, grooming the backlog before standup so it wouldn't look feral. I was maintaining the tool instead of doing the thing the tool was for.

Here's the part that stung: I build task software for a living. AgileTask.ai, sprint planning for agile teams. While developing it I kept hitting a need it was never meant to cover: the stuff that arrives out loud, walking out of a call, three things in my head, no sprint in sight. A board wants structure up front. This needed catching first, deciding second.

So I built Riffle. It's a deck, not a board. A separate product for that separate need. Here's the one moment that made me build it.

I'm walking out of a call and I have three things in my head. I open Riffle, hold the button, and say: "ship the pricing page today, ask Marco for screenshots, renew the domain next week." I let go. The AI splits that into three cards, one each. No typing, no fields.

Then I deal. Each card gets one swipe: Now, Next, Later, or Done. Pricing page goes Now. Marco goes Next. Domain goes Later. That's the whole interaction. Cards move only when I deliberately deal them. There's nothing to groom because there are no columns to sit in and rot. A card is either in my hand or it's placed.

End of day I hit Wrap and it writes my standup from what actually moved. Not what I planned, what happened. I stopped writing status updates.

For teams: I throw a card at a teammate by saying their email. First time, they join through an invite link; after that, cards land on their deck directly, each with a receipt trail (delivered), so I'm not chasing "did you see this." And "The Line" shows everyone's Now + Next, live. Nobody maintains it. It just reflects the decks.

What I'm asking

I'm opening 30 founding seats. If you take one:

  • 12 months free, then a permanent founding-member discount after.

  • A seat covers you + 2 teammates. The team features are the whole point, so bring people.

In exchange: use it for real work for a few weeks, and give me one 20-minute feedback chat or e-mail. That's it. First come, capped at 30. When they're gone, the beta closes.

Claim a seat: https://riffle.work

Who it's for (and who it isn't)

It's for solo builders and small teams who think in tasks you'd say out loud, the "here's what I need to get done" kind of person. If you already talk your to-do list to yourself, Riffle just catches it.

It's not for you if you live in Gantt charts, dependency graphs, or heavy enterprise workflows. There's no timeline view, no story points, no swimlane approvals. That's a deliberate omission, not a roadmap gap. If you need that, we'll both be happier if you skip this.

Privacy

EU-hosted, each board isolated at the row level (I tested that adversarially myself). Voice audio is never stored. Only the transcript. Passwordless magic-link login, delete-account actually deletes, no ads, no data sale.

The ask

Grab a seat at https://riffle.work. And drop your questions in the comments. I'll answer every one, including the awkward ones.

One honest note: I built this solo and fast, leaning hard on an AI-orchestrated build process. Founding users will hit rough edges. That's partly what the 20 minutes is for.

Joe
–––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––––
FAQ

Why not just use Trello / a normal board? Because the board is the problem I'm removing. Riffle has no columns to maintain and no statuses to update. A card moves only when you deal it with a swipe. If dragging cards around a board works for you, honestly, keep doing that.

What happens after the 12 months? You keep a permanent founding-member discount for as long as you're around. No surprise "welcome to full price" email.

What's the catch? Real usage for a few weeks and one 20-minute chat. I want people who'll actually run their work through it, not sign up and vanish. If that's not you, leave the seat for someone else.

Don't you already run a task app? Yes. AgileTask.ai, sprint planning for agile teams. Riffle isn't a pivot and isn't AgileTask-lite: it's the tool for what never made it onto the sprint board. Spoken capture, personal triage, tiny-team handoffs. I needed both; maybe you do too.

iOS / Android app? It's a mobile-first PWA. Installs straight from your browser, no app store, works on desktop too. Nothing to download and wait on.

posted toAvatar for product Riffle
Riffle
  1. 2

    The shift from boards to decks is interesting because it changes when organization happens, not just how. I'd keep validating whether people adopt Riffle because it's a simpler task manager, or because it better matches the way unstructured work naturally enters their day before it ever belongs on a project board.

    1. 1

      Yes. Boards force structure too early. Work usually arrives as speech, half-        thoughts, and "we should do X." A deck is closer to that moment. Say it, deal it, then order it. Organization after intake, not before.

      The validation question I am watching: Do people stick because Riffle is a simpler task manager, or because it matches how unstructured work enters the day before it deserves a project board? 

      My bet is the second. If it is only "simpler Kanban," we lose to every free board. If it is "capture → deal → standup writes itself," the founding seats are for teams who live in that mess. 

      Early signal I want: someone using voice or fast capture in a real standup week, not just rearranging cards for fun.

      What would count as proof for you in the first two weeks of a founding seat: 

      1. 1

        Appreciate the context.

        The question around what counts as proof is exactly where the interesting product decisions start, but I don't think I'd do it justice in a public thread.

        If you're open to it, what's the best email to reach you on?