Pingsy

Inspiration

Remote-first teams (including ours) live in a wall of red dots: 25 Slack DMs, 14 GitHub reviews, 8 Jira mentions, 60 unread emails before lunch. We measured our own workflow and found we were losing 32 minutes per day just to tab-switching and “where was that link?” moments. We wanted a consumer-simple fix, not yet another corporate dashboard that needs admin permissions.

What it does

One OAuth per tool → streams Gmail, Slack, GitHub, and Jira into a Tinder-style inbox.
LLM triage classifies every ping as 🔥 Blocker, 🟡 FYI, 🕒 Later, and highlights owner / due date.
Inline quick actions let you reply to a DM, reply to a GitHub mention, or a Jira comment without leaving Pingsy.
Let AI reply on your behalf by understanding the full context
Zero installs, zero admin scopes, pure browser SaaS, and any individual can turn it on in 30 seconds.

How we built it

We ordered our own pizza since the hackathon is remote. We started with UI design for both landing page and the app itself. We tweeted many times in the build in public and hackathon community. We got feedback and impressions. We scaffold with bolt.new. We created a Supabase DB. We tweet the mock UI pages and got 3 DMs like "When is it live?". We felt we were on the right track. Then, we implemented OAuth connections. We tweeted the connections page again. We got a couple of DMs and reposts from others about more integration requests. We went running to reset our minds and fuel our motivation again. Running was not enough to fuel our motivation fully. Eventually, money talks. That's why we add subscription management and a payment system with Creem. Without AI, SaaS is not SaaS anymore. We have to do that, so we add AI urgency triaging and AI reply with LLM API calls. Then, we tried different design styles of the dashboard page. We did everything in 1 week. Seven days, two pizzas, one 5K run, 30+ tweets and reddit posts, and thousands of impressions later, Pingsy went from whiteboard sketch to a live, paying, AI-powered action inbox ready for the judges.

Challenges we ran into

No “/notifications” endpoint in Jira. Crafted JQL polling plus users.conversations diff logic. See here Hitting the rate limit across four APIs LLM token burn while testing the Auto AI Reply feature to find the best prompt. We could not decide on the gesture for notification card handling. We thought Kanban board first. But we know that knowledge workers don't want to see more Kanban boards. We decided to use a Tinder-style gesture.

Accomplishments that we're proud of

Demo went viral on r/boltnewbuilders → 58 DMs asking “When can I use this?”, "Where is the landing page?" while we are not live. Super-fast replies in Slack less than 180 ms. Finished this application in just 7 days. Implemented all the features in our mind for the MVP. Got 10+ paying customers.

What we learned

API is not equal to reality; docs hide edge cases. User-scoped tokens beat admin installs; doubled conversion once we removed workspace-wide scopes. Prompt engineering is product design: concise context + structured output = cheaper, faster, more reliable AI. Creem.io has a smooth experience for web apps' subscription management.

What's next for Pingsy

Integration Request: Users can request the next connections, like Telegram, Linear, etc. Daily Digest: Daily 60-sec digest lands at 17:00 local, summarising the day and surfacing leftovers. AI auto-reply: For now, AI just drafts the reply, and it is not sent without your consent. We want to make it a Supervised autopilot for routine. Customizable Theme: We want to add different themes for the Tinder-style page showing notification cards. Like brutalist, chromatic, glassmorphic, versatile, sci-fi, culture-based, etc.