2
3 Comments

I built an async standup app — no Slack required, $8/month flat.

I'm launching Surfboard on June 23rd and wanted to get some real feedback before then.

What it is: A standalone async standup app for remote teams. Your team posts their did/doing/blockers whenever they're ready. Everyone sees a shared board. A daily digest lands in inboxes at 9 am. No meetings. No bots. No Slack required.

Why I built it: I was paying ~$40/month for a Slack bot (Standuply) for an 8-person team. Half the team had it muted. The bot pings at 9 am, but half the team was async in different time zones. The "standup" became a ghost channel. I looked for alternatives and found that every option either requires Slack/Teams or charges per seat — which gets expensive fast.

What makes it different:

  • Standalone web app — no Slack, no admin rights needed

  • Flat pricing: $8/month for unlimited members (not per seat)

  • Free plan: 3 members, no credit card

The stack (since IH always asks): React + Express + Turso (SQLite at the edge) + Resend for transactional email + Stripe + Magic link auth + Vercel

Where I'd love feedback:

  1. The landing page — does the anti-corporate/no-micromanagement angle land? Does it make you want to try it? dailywave.app

  2. The onboarding — does the free sign-up flow feel frictionless? app.dailywave.app

  3. The positioning — "no Slack required" vs "flat pricing" — which hook resonates more with you?

  4. Anything that feels off — pricing too high/low, features obviously missing, anything that made you bounce

Thanks for looking.

— Jason


posted toAvatar for product Surfboard
Surfboard
  1. 2

    One thing I'd be careful with:

    The interesting question may not be whether teams want async standups.

    It may be whether they're adopting DailyWave to replace a standup, or to solve a different problem that standups happen to sit inside.

    Those can lead to very different positioning decisions.

      1. 1

        Possibly.

        The reason I find it interesting is that those two situations can produce very similar user behavior at the beginning while pulling the product in very different directions later.