Digital fulfilment
Service Delivery Policy
NAVASOFT Platforms Private Limited delivers software, digital services and professional services. This policy explains the usual fulfilment approach; the accepted quotation, proposal, statement of work, order or customer agreement (“Engagement Document”) defines the exact delivery for each purchase.
What we deliver
Depending on the engagement, delivery may include:
- digital software, solution components, releases or access to a hosted SaaS service;
- discovery, design, engineering, implementation, configuration or customisation;
- deployment to an agreed environment and related setup or migration work;
- documents, designs, source code, configuration, reports, training or other project deliverables; and
- professional services, support, maintenance or managed operational activities.
How delivery begins
Work ordinarily begins after the applicable Engagement Document is accepted, required information and access are available, and any agreed advance or payment prerequisite is satisfied. NAVASOFT and the customer may confirm a kickoff, delivery plan, authorised contacts and working channels.
Delivery method
Digital deliverables may be supplied through a secure repository, approved file exchange, customer environment, hosted service, account invitation, deployment release or another channel identified in the Engagement Document. Professional services may be delivered remotely, on site where agreed, or through a combination of working sessions and documented outputs.
Timelines, milestones and acceptance
Delivery dates, milestones, dependencies, review periods and acceptance criteria are those in the Engagement Document or an agreed project plan. Dates may depend on customer inputs, access, approvals and third-party services. If a dependency or scope changes, NAVASOFT will communicate the impact and use the applicable change-control process rather than silently changing the commitment.
Customer responsibilities
The customer is responsible for providing accurate requirements, authorised decisions, lawful data and content, necessary access, timely reviews and any customer-owned licences or environments identified in the Engagement Document. Delivery may pause or move when a required dependency is unavailable.
Evidence of delivery
Depending on the engagement, delivery may be evidenced by access activation, release or deployment records, repository or file-transfer records, meeting or training completion, milestone submissions, service reports, customer acceptance, or another agreed record.
Support and maintenance
Support channels, service periods, coverage, response expectations, maintenance activities and exclusions are not assumed from this website. They are defined in the applicable support, subscription or customer agreement.
Physical shipping
NAVASOFT does not ordinarily sell or ship physical goods through this corporate website, so a retail shipping policy is generally not applicable. If a specific Engagement Document includes hardware, media or other physical items, that document will state the delivery location, method, charges, responsibility and acceptance terms.
Delivery questions
For a delivery-status or fulfilment question, contact the authorised NAVASOFT project contact or email connect@navasoft.in with the customer, invoice or Engagement Document reference. Do not send passwords, credentials or payment-instrument details by email.