This product was not featured by Product Hunt yet. It will not be visible on their landing page and won't be ranked (cannot win product of the day regardless of upvotes).
Why I built it: I’m a solo developer handling clients, projects, meetings, deadlines and invoices, and the CRMs I tried were built for sales teams. They’re cloud-hosted, charge per seat, and are full of pipeline features I never used. I wanted something small and fast that keeps all my data on my own machine, with no account and no server, and that fits how developers work, like showing GitHub commit activity next to projects. So I built Tally as a local-only desktop CRM.
Feedback that would help most:
First run and onboarding: Is it clear what Tally does and how to get your first client and project set up?
Workflow fit: Do projects, meetings, deadlines and payments cover how you track freelance or client work? What’s missing, and what’s unnecessary?
Local-only trade-offs: Does keeping everything on your machine, with manual backup and restore, feel like a plus or a dealbreaker? Would you want optional sync?
Pricing and licensing: Would you pay for this? Does the license activation flow feel smooth?
Bugs and polish: Anything that feels slow, confusing or broken, especially in the calendar and the date/time pickers.
The future of Tally
Tally will stay local-first: your data lives on your machine, with no account and no server required. From there, the plan is to make it more useful for developers who freelance or run client work on their own.
Up next:
macOS builds: Tally is Windows-only today, and the codebase is cross-platform Electron.
Further out:
Optional sync between devices: an opt-in way to keep Tally in step across machines, probably through a cloud-backed SQLite replica, while local-only stays the default. For now, backup and restore covers moving your data.
More developer integrations that build on the GitHub connection, so client work and code activity live side by side.
What won’t change: Tally stays a one-person tool. No seats, no sales pipeline bloat, no lock-in. Your data is a single SQLite file you own.
No comment highlights available yet. Please check back later!
About Tally on Product Hunt
“Desktop CRM for Mac and Windows”
Tally was submitted on Product Hunt and earned 2 upvotes and 1 comments, placing #154 on the daily leaderboard. Tally is a desktop CRM for macOS and Windows. Get a lifetime license for a one-time payment of $4.99 at launch (regular price $9.99).
Tally was featured in Productivity (665.8k followers), Developer Tools (523.3k followers) and GitHub (41.5k followers) on Product Hunt. Together, these topics include over 310k products, making this a competitive space to launch in.
Who hunted Tally?
Tally was hunted by Thristan Dave Bumagat. A “hunter” on Product Hunt is the community member who submits a product to the platform — uploading the images, the link, and tagging the makers behind it. Hunters typically write the first comment explaining why a product is worth attention, and their followers are notified the moment they post. Around 79% of featured launches on Product Hunt are self-hunted by their makers, but a well-known hunter still acts as a signal of quality to the rest of the community. See the full all-time top hunters leaderboard to discover who is shaping the Product Hunt ecosystem.
Want to see how Tally stacked up against nearby launches in real time? Check out the live launch dashboard for upvote speed charts, proximity comparisons, and more analytics.
Why I built it:
I’m a solo developer handling clients, projects, meetings, deadlines and invoices, and the CRMs I tried were built for sales teams. They’re cloud-hosted, charge per seat, and are full of pipeline features I never used. I wanted something small and fast that keeps all my data on my own machine, with no account and no server, and that fits how developers work, like showing GitHub commit activity next to projects. So I built Tally as a local-only desktop CRM.
Feedback that would help most:
First run and onboarding: Is it clear what Tally does and how to get your first client and project set up?
Workflow fit: Do projects, meetings, deadlines and payments cover how you track freelance or client work? What’s missing, and what’s unnecessary?
Local-only trade-offs: Does keeping everything on your machine, with manual backup and restore, feel like a plus or a dealbreaker? Would you want optional sync?
Pricing and licensing: Would you pay for this? Does the license activation flow feel smooth?
Bugs and polish: Anything that feels slow, confusing or broken, especially in the calendar and the date/time pickers.
The future of Tally
Tally will stay local-first: your data lives on your machine, with no account and no server required. From there, the plan is to make it more useful for developers who freelance or run client work on their own.
Up next:
macOS builds: Tally is Windows-only today, and the codebase is cross-platform Electron.
Further out:
Optional sync between devices: an opt-in way to keep Tally in step across machines, probably through a cloud-backed SQLite replica, while local-only stays the default. For now, backup and restore covers moving your data.
More developer integrations that build on the GitHub connection, so client work and code activity live side by side.
What won’t change: Tally stays a one-person tool. No seats, no sales pipeline bloat, no lock-in. Your data is a single SQLite file you own.