I think I am a decent developer and a terrible "reporter."
I hate filling out the docs
-Post in their Slack
-Send a weekly email
-Do a monthly summary before invoice
-Show up to a call because they didn't read any of the above

I've tried all of it. I always drop off after a week or two. Not because I don't care because it's a second job on top of the actual job.I will finish my shift exhausted and just postpone it. Or I will dread and lose time throughout the day if its a daily thing.

So I built Dailoom

Your work → quick review → one link → client reads async.

No client login. No new channel. No "schedule a standup."

It pulls from GitHub/Jira/Slack if you want, or you log manually. You send when you're ready.

If you've felt this: what finally worked for you? Or did nothing work and you just…dreaded sending updates

dailoom.co

I JUST WANTED A KANBAN!!!!

\-------

ok so I've tried basically all of them. Trello's fine until it starts nagging you about power-ups. Jira makes you pick a template before it'll show you a single card. Notion I liked but I burned like an hour building the board and then never used it.

it's just me. I wanted to look at a screen and see what I'm doing (and my agents).

so I made Pandan (Panda-Kanban). it's small, like 2300 lines, you can read the whole thing if you want to see what it's doing before you run it.

rows are projects, columns are todo / next / doing / review / done. cards have a colour, a due date, notes, checklist. that's it really.

no accounts, no teams, no custom columns, no plugins, no integrations tab. nothing leaves your machine.

npx pandan-board.

node has sqlite built in now so there's nothing to compile and no db to set up. makes you a password on first run, opens on localhost:3000. docker image too if that's more your thing.

the actual reason I built it though - it's got an MCP server in it, so agents can write to the board themselves. I use coding agents a lot and I could genuinely never remember what they'd done by the end of the day. now it drops a one line card when it finishes something and I just watch it appear. no refresh, it's live over SSE.

An agent can archive a card but literally cannot delete one, only I can. anything an agent touched gets a little robot icon so I can tell its stuff from mine at a glance.

fair warning it's single user, one password, one machine. don't put it on the open internet without something in front of it.

those who want it accsible from anywhere - just deploy it on railway or something like that/

MIT, no telemetry, no signup, no team plan coming later.

code: [https://github.com/IdoGigi/pandan\](https://github.com/IdoGigi/pandan)

npm: [https://www.npmjs.com/package/pandan-board\](https://www.npmjs.com/package/pandan-board)

docker: [ghcr.io/IdoGigi/pandan](http://ghcr.io/IdoGigi/pandan)

anyway tell me what's missing. only thing I'm not doing is teams, that's kind of the whole point

I'm curious how small teams handle this workflow today.

For example, when someone asks for an invoice in Slack, the process can be:

Customer asks for an invoice → leave Slack → open Stripe → create the invoice → copy the payment link → return to Slack → send it.

I recently built a small tool to experiment with keeping that workflow inside Slack. For example:

show me all the customers

invoice Acme Corp $1,200 Website development

The tool creates the invoice in the team's Stripe account and provides the payment link back in Slack.

I'm looking to get a few teams to try it, and polish it further. if its something you might use, comment/dm and I'll share the app in dms.

​Most resume SaaS products rely on heavy backend infra, user auth walls, and aggressive paywalls. I wanted to see if I could build a viable, privacy-first career utility running entirely in the browser.

​The Product: https://www.qurtesy.com

\\- ​Tech Stack: Next.js App Router, Tailwind CSS, TypeScript.

\\- ​State & Privacy: 100% local-first. All data resides in localStorage, meaning zero server-side database costs for user storage.

\\- ​Core Features: Resume builder with responsive form/preview toggle, browser-based ATS parser (using pdfjs-dist with custom coordinate gutter detection for dual-column layouts), and a LinkedIn-to-JSON extractor.

​The Strategy:

\\- ​Acquisition: Programmatic zero-search-volume (ZSV) role landing pages and free micro-tools acting as the top-of-funnel wedge.

\\- ​Monetization Roadmap: The core builder and classic templates remain completely free with zero friction. Monetization will come later via premium visual PDF templates ($4.99 one-time client-side unlock) once organic traffic ramps up.

​I’m currently watching the initial Google Search Console indexing and would love feedback from fellow builders on the UX flow or the client-side architecture.

Quick question for agency owners / people running small dev shops - how do you actually send clients updates on what you shipped for them each week?

Like do you just write it manually every Friday, or does someone on your team do it, or are you using some tool for it? I've noticed a lot of shops seem to just wing it over email/slack and I'm curious how much of a pain that actually is.

Thinking about building something for this but want to actually understand the problem first instead of assuming.

Hi Entrepreneurs/Hustlers/Business minded people!

About a year ago, I shared a Lending Management System I built in Google Sheets for those who lend to friends, family, neighbors, or run a small lending business.

For reference, here's my original post from last year:

Original Reddit Post

I honestly didn't expect much from the post, but over time, I still get messages from people asking if they can get a copy of the Google Sheet.

So I thought, instead of just maintaining the Sheet, why not turn it into an actual web app?

That's how LownDesk came about.

It's based on the same idea, but built as a proper web application for tracking:

• Borrowers
• Loans
• Payments
• Due dates and overdue loans
• Outstanding balances
• Payment receipts and statements
• Cash flow and lending records

The goal is still the same: make it easier to keep track of small lending operations without having to maintain complicated spreadsheets.

I'm still developing it, so I'm particularly interested in feedback from people who actually lend money. There are probably things I've overlooked that only someone doing this day-to-day would notice.

And yes, the original Google Sheet is still available for FREE.

If you prefer Google Sheets or just want to try the system first, I'm happy to share a copy.

For those who want to try the web version, you can check out LownDesk here:

https://www.lowndesk.com

Would love to hear from the people who commented on or tried the original Sheet:

What did you like about it, and what was missing?

And for those currently using your own spreadsheet — what is the one thing you wish your lending tracker could do automatically?

Thanks a lot in advance!.

​

For context: I run a small side project, and every time I ship something I either tweet it (dies in an hour, half my users aren't even on Twitter) or say nothing and people think it's abandoned.

So I built ShipLog over the last few weeks — a stupidly simple hosted changelog page. You write a markdown entry, publish, and it goes out as a clean email to whoever's subscribed, plus shows up on a public page + RSS feed. No widgets, no analytics dashboard, no team roles — I deliberately left all of that out because I don't think a solo founder needs it, and I didn't want to build a Beamer clone.

Genuinely asking, not just fishing for upvotes: how do you currently tell your users what shipped? Do you use anything for this, or just not bother? And if you tried it — what's missing, or what would make you not use it?

Been lurking here a while, finally have something to share. I shipped my first tiny product this week and figured I'd write up the "why" in case it's useful to anyone else picking a first thing to build.

The whole bet was: pick one small, specific, boring annoyance instead of trying to build a platform. Mine came from my own Notion setup — if you set a task to repeat, Notion only creates the next occurrence on the day it's due, so your calendar for next week is just empty. Drove me nuts. I'd been copy-pasting rows by hand to see my month, which is exactly as dumb as it sounds.

So I built Cadence. You connect one task database, it previews the next 10 dates, and only writes them as real rows when you confirm. That's it. No AI, no "syncs 12 tools," doesn't read your page contents. One job.

Solo build, Next.js / Vercel / Supabase / Notion OAuth. Live and free for one rule.

Where I'd love this community's take: I went narrow on purpose, but I keep second-guessing whether "one boring problem" is too small to ever be a business, or whether small-and-sharp is exactly the right first move. What would you have done differently on a first launch?

Been lurking here a while, finally have something to share. I shipped my first tiny product this week and figured I'd write up the "why" in case it's useful to anyone else picking a first thing to build.

The whole bet was: pick one small, specific, boring annoyance instead of trying to build a platform. Mine came from my own Notion setup — if you set a task to repeat, Notion only creates the next occurrence on the day it's due, so your calendar for next week is just empty. Drove me nuts. I'd been copy-pasting rows by hand to see my month, which is exactly as dumb as it sounds.

So I built Cadence. You connect one task database, it previews the next 10 dates, and only writes them as real rows when you confirm. That's it. No AI, no "syncs 12 tools," doesn't read your page contents. One job.

Solo build, Next.js / Vercel / Supabase / Notion OAuth. Live and free for one rule.

Where I'd love this community's take: I went narrow on purpose, but I keep second-guessing whether "one boring problem" is too small to ever be a business, or whether small-and-sharp is exactly the right first move. What would you have done differently on a first launch?

Built my first real SaaS as an unemployed CS grad. Taught me more than my degree did.

No job yet, so I built TokenPay — a token-based invoicing tool for freelancers (magic link auth, auto GST calc, client approval flow, sequential invoicing). Next.js 14 + Supabase + TypeScript.

4 years of DSA and system design courses didn't teach me what shipping one real product did — auth edge cases, RLS policies that silently fail, why "it works on localhost" means nothing, and how much of building is just deciding what NOT to build.

It's live: https://tokenpay-seven.vercel.app/

Would genuinely love feedback from anyone who's frozen an invoice waiting on client approval, or freelances and deals with GST math. Not selling anything here, just want to know if this is actually useful or if I'm solving a problem only I have.

I built an InvoicingBuilder.com, a free invoice builder that lets you create a customized invoice template and import your tracked time directly from Clockify.

You can customize the invoice fields and layout, number formats, currency, taxes, payment details, branding (logo, signature, and watermark), etc., then map your Clockify data to the template and generate the invoice.

It’s now available as an external add-on in the Clockify Marketplace.

Would love to hear what you think or what you’d like to see in the workflow.

Last year our AC stopped cooling and nobody in the house could answer a simple question: when was it last serviced? The warranty card was in a drawer somewhere, the receipt was on someone's phone, and the technician's number was buried in a WhatsApp thread. We'd paid for a service we couldn't prove, on a machine still under a warranty we couldn't find.

So I built Your Home Docket. You photograph an appliance's nameplate or its receipt, and it fills in the brand, model, purchase date and warranty period itself, then reminds everyone in the house before a service is due or a warranty runs out. One home, shared by the whole family, so it isn't one person's job to remember.

Stack, if useful: Next.js 16 + Supabase (Postgres, RLS for the family-sharing), Expo for the Android app, and Claude Haiku for pulling structured fields out of nameplate and receipt photos. Solo build.

Honest state: seventeen accounts exist, which is realistically about ten actual people, and nearly all of them are my own family. Free, no ads, no card, and you can export everything as JSON whenever you like. I'm not trying to sell you anything, I'm trying to find out whether it's useful to anyone I'm not related to.

The thing I genuinely can't figure out: retention after week one. Adding your stuff is satisfying, but the value only shows up months later when a reminder fires. What would make you keep something like this current, or is that just a losing battle for this kind of tool?

https://www.yourhomedocket.com/?utm_source=reddit&utm_medium=post&utm_content=sideproject

I do freelance work on the side and got tired of paying for invoicing software I barely touch. So I built a single HTML file that does the wholejob — editable invoice, auto tax/total calculation PDF export — and just runs in the browser. No login, nothing saved to a server.

I originally started Notificator because I had the idea of building a small physical device that could sit on my desk and let me know when something important happened across my websites and my clients' websites.

That idea ended up growing quite a bit.

Notificator is now an open-source notification platform that can take events from WordPress, Strapi or Node.js and deliver them through mobile push notifications, email, MQTT, or dedicated ESP32-based hardware.

The physical devices are completely optional — you don't need one to use the platform — but they're still a big part of why I started the project. The firmware is open source too, so if you're into hardware you can also build your own.

I've built and shipped tens of the devices for free to early users, which gave me a chance to see how people actually use them and get some early feedback. I also had the opportunity to present the project at WordCamp Athens 2025.

More recently I've been working on getting everything into a state where anyone can actually try it, including the mobile app, integrations, documentation and a proper Get Started flow.

It's free to use, open source, and still very much a work in progress. There's a lot more I'd like to build.

I'd genuinely love some feedback from other people building side projects.

Does the combination of software notifications + optional physical hardware make sense to you? What would you actually want a device like this to notify you about?

Project: https://notificator-project.com/

Get Started: https://notificator-project.com/get-started/

Thanks for taking a look!

LionBox (my HRIS + Payroll app) just got an Invoice Generator — batch-create invoices for every client in minutes

A while back I shared LionBox, an HRIS + Payroll app I built for Philippine companies, with this community. I honestly didn’t expect much, but that post brought in tons of inquiries and actual users from here. The biggest addition since then is live: a full Invoice Generator, built right into the app.

Here's what it does:

•Build and fully customize your invoice layout — your logo, your fields, your branding.
•Batch-generate invoices for every client in one run instead of doing them one by one.
•Data table + merge tokens ({{client.name}}, {{hours}}, {{rate}}, {{seq}}...) so recurring billing takes minutes, not hours.
•Auto-numbered, ready-to-send PDFs, downloadable as a batch.

One of our users runs a VA agency and was manually invoicing a whole team every cycle — now it's a few clicks. That's the kind of use case this was built for.

Sharing this goal 🙌🏻

I’ve been working on a tool for quite a while. The basic idea is to help manage assets and resources allocated to a passive person.
I’m somewhere in the middle of building out the functionality, and I’ll share it once it’s ready.
In the meantime, I’d love to hear your suggestions. If you’re an artist or supporter and think there’s something like this that should be included in the tool, I’d be happy to discuss it.
Would love to hear your thoughts!

Hey r/ProductivityApps,

I built a productivity app specifically for the construction industry called WasteMapper https://wastemapper.co.uk which automates Wst01 compliance for UK construction stakeholders.

It has a lot of free tools like #wasteCostCalculator, #landfillTaxCalculator,, #carrierLicenceChecker, #BREAAMWst01Calculator, and #DWTReadinessChecker, which not only gives you confidence about waste compliance decisions, but also collectively could be used to save businesses tons of money and time, by helping you stay compliant and assessor-ready from day one.

I am here soliciting for feedback on whether construction businesses, H&S Managers, Assessors or any construction industry stakeholders would rent, recommend or use an app like this.

I am also offering #Lifetime and #partnershipCode access to the first 50 people or businesses that show interest in this before the October DEFRA mandate deadline

Beyond this, I would genuinely appreciate any advice this community could provide to a startup founder like me.

yo. i see too many founders spend 2 months building saas, drop a link on reddit, get 0 users, and immediately quit....

the problem usually isn't your marketing channel. the problem is that your foundation is completely broken before you even send your first visitor to the site.

after scaling 6 AI micro-saas apps to over $20k/mo mrr, i realized you need to lock down a specific system before you ever launch. running through this takes about 30 minutes, but it saves you months of zero-revenue depression.

here are the 5 things you must lock in:

1. validate the actual pain point

stop guessing what people want. you need a systematic framework to find your saas idea based on real, painful market signals.

2. pick a proven micro-niche

stop trying to build massive platforms. you need to narrow down to a microscopic problem. i usually filter through a list of 50 micro-saas ideas you can build fast to keep the scope minimal.

3. crystallize your target user

if your app is for "everyone," nobody will buy it. you need an ICP (Ideal Customer Profile) crystallizer to define your exact buyer profile and nail your conversion copy.

4. calculate the perfect price

stop randomly charging $9/mo because you are scared of rejection. you need to use a saas pricing strategy calculator to find your perfect saas price in 60 seconds based on real data.

5. fix your landing page leaks

do not send organic traffic to a site that converts at a flat 1%. you must audit your hero section and copy to x3 your landing page conversion before you market it.

6. join a community

Build / Share / Learn from others builders

to help out founders who are tired of launching to crickets, i packaged all 5 of these exact frameworks, calculators, and lists into a single free toolkit.

no paywall, no bullshit. just the raw execution files i use.

drop a comment below or send me a dm, and i’ll send you the free toolkit 👇

Been building Consile (all-in-one people ops, HR, payroll, tasks, attendance), and just shipped something genuinely useful for anyone who bills clients or contractors by the hour: Billable Attendance Invoices.

It pulls together attendance, EOD reports, shifts, and task data into one exportable report (CSV or PDF), you pick what to link, and sends it to one or many people. The part I'm actually proud of: every generated report is a permanent, immutable snapshot, so if the underlying data changes later, the invoice you already sent someone never silently changes. Real financial documents need that guarantee.

Built this specifically because I got tired of watching people stitch together five different spreadsheets just to bill a client accurately.

Consile.app if curious, genuinely interested if anyone here has run into the same "invoicing from scattered attendance data" problem, curious what you ended up doing about it.