Frequently Asked Questions

OrionSuite is based in Uttar Pradesh and currently serves businesses across India. We can discuss projects with clients in other Indian states. An enquiry from outside India does not create a commitment to accept an overseas engagement.

We provide business websites, custom software and business automation. A project can be one focused website or workflow, or a larger system delivered in agreed stages. Start with the business problem and the outcome you want.

Email info@orionsuite.in with your business, the task or system you want to improve, the tools you currently use and any important deadline. We clarify the requirements and prepare a scope before asking you to commit to a build.

No. A description of the problem, current process and desired outcome is enough for an initial discussion. We still need a written scope and acceptance criteria before delivery work starts.

Yes. A focused page, module or automation can be delivered first. We agree what the initial stage includes and how it can be extended without treating possible future features as part of the current price.

Responsive behaviour and supported screen sizes should be stated in the website scope and checked during review. We test the agreed pages and journeys at relevant sizes; requirements for particular devices should be raised before building.

Yes, subject to reviewing the existing site, access and licence restrictions. We agree which content, features, URLs and integrations must be preserved and plan the change so the current site is not replaced without approval.

These can be discussed, but they are included only where the proposal says so. Technical metadata and sensible page structure are different from an ongoing search campaign. We do not guarantee a search ranking or lead volume.

Yes. We define the roles, permitted actions, business rules and approval process with you. The implementation and testing should cover direct actions as well as what is visible in the interface; the scope determines which modules are delivered.

We first check available APIs, account permissions, provider limits and licensing. A supported connection can be scoped; a tool with no suitable access method may need a different approach. We do not promise every integration before checking it.

Only where your approved process permits it. A workflow can route requests, send reminders and prepare information while leaving a decision with the responsible person. Your approval rules should be recorded before implementation.

The scope should specify logs, alerts, retries and any manual recovery step appropriate to the system. Some failures depend on external services. We test agreed failure paths instead of assuming that every automation always succeeds.

Depending on account access, available APIs and the agreed scope, we can build workflows around tools such as Forms, Sheets, Gmail, Drive and Calendar. Subscription fees, permissions and provider quotas still apply.

OrionSuite is currently not registered under GST and does not charge GST. We issue ordinary commercial invoices, not GST tax invoices. Our standard quotations and invoices are in Indian rupees (INR). If our registration status changes, our invoices and policies will be updated to reflect applicable requirements.

The price depends on the scope, integrations, design and delivery requirements. We provide a quotation rather than a universal price for every website or system. Ask for external costs such as hosting, licences and domains to be identified separately.

Our proposed standard is 40% before work starts, 40% after the review milestone defined in the proposal and 20% before final handover. A different schedule can be agreed in writing. Invoices state their due dates and payment details.

We describe the extra work, cost and timing before proceeding and ask for written approval of the change. A request does not silently increase the original scope or price.

Cancellation is assessed against payments received, completed agreed work and approved non-recoverable costs. An unused balance is refundable where due; the deposit is not automatically forfeited. Service defects and applicable legal remedies are considered separately. Read Payments, Cancellation & Refunds.

We estimate after reviewing the scope and dependencies. Content, feedback, access, integrations and testing can affect the schedule. The proposal should identify milestones and any deadline requirements.

After full payment, the client owns the bespoke code and custom deliverables created for the project, with transfer recorded in the agreement. Third-party components retain their licences; pre-existing materials must be identified before they are included.

The proposal should list the repository or source archive, deployment instructions, assets, access and operating guidance to be handed over. Extensive training or manuals are included only if scoped. Read Project Delivery & Handover for the practical checklist.

AWS EC2 is our stated hosting platform. We agree the account owner, region, instance, recurring costs and operational responsibilities for your project. Using AWS does not mean every deployment keeps all information in India.

Our proposed standard provides 30 calendar days after written handover to report reproducible defects in the agreed scope. New features and ongoing hosting or maintenance require their own arrangement. A covered report submitted during the window remains eligible for assessment.

We can agree a plan for defined updates, monitoring, backups or enhancements. Frequency, fees, access and response arrangements belong in that plan. There is no automatic 24/7 support promise or recurring subscription in the standard handover.

The current public website source has no analytics script or advertising pixel. It may use first-party session and security cookies. Read the Privacy Policy and Cookie Policy for the current setup; new tracking requires a review and an updated notice.

Do not put credentials, payment details or private datasets in a general enquiry email. First describe the requirement; we agree the authorised access and sharing method if the project needs it. Use sample or anonymised data where possible.