How a customization project actually proceeds

1. Tell us about the business

Start on the contact page, by phone at +91 979 033 8991, or by email at info@saivanajagroup.in. Say what the business does, which records are on paper, and what you hope will be easier. You do not need to know whether you need “an ERP”. If you already use software, say what you kept outside it and why.

2. Walk through one real cycle

A useful session follows a single customer order, job, or purchase from the first note to the outstanding balance. We look at sample forms with sensitive figures removed if you wish. This is the same discipline described in our approach, applied to your documents. Industry pages such as trading and distribution or service businesses list the questions that usually matter, but your answers override those lists.

3. Receive a proposed scope

The proposal names the workflows to build, the workflows to leave as they are, and the records you would need to enter or import. It is a plan for custom development. It is not a license key to a finished Anywhere Anytime application. Cost and time depend on that scope. There is no public rate card, because two billing formats are not the same project.

4. Prepare data and scenarios

Before build or during it, you collect opening balances, party names, item or service lists, and a handful of past transactions that represent normal and awkward cases. The implementation guide and the accounting workflow checklist are there so this preparation is concrete. Imports are possible only when the source data is consistent enough to map. They are not automatic.

5. Test the workflow you described

Testing means entering those sample cases and comparing the result with the rule you stated: the bill total, the party balance, the report row. A passed test shows that the agreed rule was implemented. It does not certify tax law or an accounting standard.

6. Roll out and train the people who do the work

The people who write bills and ledgers today need to know what changes for them. A phased start, one document type at a time, is often calmer than a single cut-over. Support after go-live covers the delivered scope. New reports, new branches, or a redesigned invoice are future work and are estimated separately.

What you can expect to leave with

• A written understanding of the process, before any build is assumed.
• A scope that lists modules, and also lists exclusions.
• If you proceed, software for that scope, tested with your scenarios.
• A route for later changes that is explicit about effort.

Questions about price, mobile access, and imports are answered directly on the FAQ.