Buying, ownership & procurement
Home • Buying & ownership
The questions asked before a file moves. Answered before you commit.
Ownership
Who holds the code, and what happens if you replace us.
Who owns the software after delivery?
You do. Source code, database schema, data and applicable system credentials are handed over on completion and settlement. There is no escrow arrangement to negotiate because there is nothing being withheld.
What happens if we stop working with you?
Nothing stops. You hold the code and the credentials, the technology is mainstream, and the handbook is written so a competent third party can operate the system without us. We would rather be kept because the work is good than because the work stands up.
Do you subcontract the work?
No. The build is done in-house. If we ever needed a specialist for something outside our competence, we would tell you before engaging them, and they would be bound by the same confidentiality terms.
Are the mobile apps published under our name?
Yes. Apps are published to the Play Store and App Store under your organisation’s developer account, so the listing, the reviews and the ownership are yours. We can help you open those accounts if you do not have them.
Money
What is one-time, what recurs, and what is never ours to touch.
What exactly am I paying for, and what recurs?
Four things are worth separating, because they behave differently:
Implementation — a one-time cost, fixed in the proposal.
Licence — there is none. No per-user, per-seat or per-transaction
licence fee, ever.
Maintenance and support — included for the period stated in the
proposal, inside the implementation figure. Beyond that period it is quoted
separately and agreed before it starts.
Third-party running costs — hosting, domain, SSL and notification
delivery are borne by us for the covered period. Payment gateway charges are set
by the gateway and are between you and them.
So "no licence fee" is precise, and it is not the same as "no ongoing cost of any kind". Anything recurring is named in the proposal before you sign it.
How is GST handled?
Quoted amounts are exclusive of GST. GST is added at the prevailing rate at the time of billing and shown separately on the invoice, against our GSTIN. SAC classification is confirmed by your tax adviser before the first invoice — we implement what is confirmed in writing and do not assert a rate as fact.
How are payments staged?
Against milestones, written into the proposal before work starts. Typically the larger share on completion of the interface and data work, the balance on completion of payment integration and training against your acceptance. Invoices are payable within fifteen days. TDS, where applicable, is adjusted on issue of the certificate.
Do you ever hold or route our collections?
Never. The licensed payment gateway settles directly into the account you designate. Odvaya is not the merchant of record and is not in the path of the funds. Our software reads the settlement and reconciles it; it cannot touch it.
Operations
Where the data sits, who answers the phone, and what happens to the paper.
Where does our data live?
On servers in an Indian region. No application data leaves the country. Backups stay in the same region. If your department requires hosting on its own infrastructure or a state data centre, we deploy there instead — the software does not care.
Who supports the system after go-live?
Our own team, directly. There is no support desk to route through and no ticket queue behind an SLA you cannot see. The escalation matrix in the proposal names who to call and the response time we commit to.
What about the existing paper register?
It stays. Where a statute or a departmental instruction requires a physical register, the software runs alongside it and can print the entries in the prescribed format. We do not ask an office to break a rule to use our software.
Is the system accessible and bilingual?
Citizen-facing screens, receipts and notifications are delivered in English and Odia. Screens are built to work on a mid-range Android phone on a slow connection, with readable type and large touch targets, because that is what the public actually uses.
Buying
How to put this through a procurement process, and what we need from you.
Can you work through a tender or an empanelment?
Yes. We can supply a technical specification, scope of work and bill of quantities in the format your procurement cell needs, and respond to an RFP or quotation call. We can also help you write the specification before it is floated — and if that means the tender is open to others, that is how it should be.
What do you need from us to start?
Written acceptance, a nominated officer to answer process questions, approved tariff or fee structure, the domain authority if a public portal is in scope, and the payment gateway documentation where collection is involved. Approval of the gateway account is granted by the aggregator and is a third-party dependency.
One caveat, stated plainly. Nothing on this page is a contract. The binding terms are in the proposal issued for your engagement, and where this page and that document differ, the proposal governs.
02How an engagement runs
Four stages, and what you hold at the end of each
Every stage produces something you keep, whether or not you continue to the next one.
Discovery & audit
We sit in the office and map the process as it actually runs — every point where a record is written once and copied somewhere else.
You holdA written process note, and an honest view on what is worth automating.Scope & blueprint
Scope, deliverables, screens and a fixed price, written down and agreed before any code is written.
You holdA proposal your procurement cell can act on, with a bill of quantities.Build & show
Working software weekly rather than a status report, so a change can still be made without rework.
You holdSoftware you have already used before it is called finished.Handover & support
Training at the desk, an operating card at the counter, an administrator handbook, and the source code.
You holdSource code, database, credentials and a named escalation route.03What you can check
Trust signals you can verify, not badges
We do not hold ISO or SOC 2 certification and will not display badges for either. These are the commitments that appear in the contract, where you can hold us to them.
04Before you write to us
Build a scope enquiry in twenty seconds
Four questions. It writes a structured note you can send, or copy into your own file. Nothing is submitted anywhere until you press send.
Scope enquiry
Answer what you can. Anything left blank simply says so in the note.
Your enquiry
This form does not send anything on its own and stores nothing. Pressing send opens your own email programme with the note already written.
05Firm particulars
For your vendor file
- Legal name
- Odvaya Services LLP
- Constitution
- Limited Liability Partnership, registered in Odisha
- Registered office
- 158, Ananta Vihar Phase 2, Pokhariput, Bhubaneswar, Odisha 751020
- Contact for tenders
- business@odvaya.com · +91 79783 73310
- LLPIN, GSTIN, PAN
- Supplied on request with the quotation, and printed on every invoice
- Bank details
- Supplied directly to your accounts section on award, never by email alone
Ask for the capability statement and we will send the particulars above on letterhead, with the technical specification for whichever module you are considering.
Need the particulars on letterhead?
Ask and we will send the firm particulars, the technical specification for the module you are considering, and a quotation in your procurement format.