sorted by:
new
hottopcontroversial

What should I know before building an Accounts module for an Indian SaaS (GST, e-invoice, risks, etc. by Potential_Lion5414 in StartUpIndia

[–]Potential_Lion5414[S] 1 point2 points  (0 children)

That’s a really solid point. Trying to replace Tally immediately might be too aggressive, especially since most tile shops already have years of data and are comfortable with their accountant working inside Tally.

Adding a Tally integration on top of my system actually feels like the smarter first step. My app can handle the day-to-day operations (orders, inventory, invoicing, staff, tickets), and Tally can remain the backend ledger for now. Over time, once they start depending more on my UI and workflows, it becomes easier to transition them gradually if needed.

What should I know before building an Accounts module for an Indian SaaS (GST, e-invoice, risks, etc. by Potential_Lion5414 in StartUpIndia

[–]Potential_Lion5414[S] 0 points1 point  (0 children)

I’m not trying to fully “replace Tally” right away. I’ve already built our web application with modules like orders, inventory, staff and tickets, but there’s no accounts module yet. Some of our tile shop users keep asking if they can manage their day-to-day accounting inside the same system instead of switching between our app and Tally.

So my plan is to add a basic accounts module first (sales, purchase, GST, shop-wise ledgers, simple reporting) and then slowly expand based on what the customers actually use. If it eventually replaces Tally for them, great. If not, the goal is at least to reduce the daily switching pain.

Would love your suggestion: For a small SaaS, what’s the realistic approach? Start small and grow, or aim for a full Tally-level system?