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).
Replies
Best
Maker
📌
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.
Replies
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.