The things people ask before they sign.
Demos, rollout time, pricing, what happens to your data and who picks up the phone. If yours is not here, ask us directly — the same people answer both.
Getting started
Can we see it on our own data?
Yes, and we prefer it. Send a sample of your masters — items, employees, students, vehicles — and we will load them into a sandbox tenant before the demo.
How long until we are actually using it?
Most customers are transacting inside two weeks: tenant provisioned and masters imported in week one, first real invoice, payroll run or admission in week two.
Do we need anyone technical on our side?
No. Setup is guided and the imports are spreadsheet-based. If your data is messy we will clean it with you rather than hand you a template and wish you luck.
Can we move off our existing system without losing history?
In most cases yes. Tell us what you are on today and what you need carried across — opening balances, past invoices, student records — and we will tell you honestly what is portable and what is not.
Products and fit
What if we need something the product does not do?
Tell us. If it makes the product better for everyone in that industry, it usually ships. What we will not do is maintain a private fork for one customer — that customer stops receiving improvements, and everyone loses.
Can we run more than one Oadbox product together?
Yes. Every product sits on the same core, so accounts, roles and reporting behave the same way across them and your team only learns one set of conventions.
Do you work outside India?
The products are built around Indian statutory rules, so India is where they are strongest. Talk to us anyway — the core is not India-specific, and some products travel better than others.
We are a single branch. Are we too small?
No. The products are configured rather than implemented, so a single branch is a normal week-one rollout, not a scaled-down enterprise project.
Data, security and compliance
Where does our data live, and who can see it?
Each organisation gets its own database schema on our AWS infrastructure, encrypted at rest. Access inside Oadbox is limited to the engineers who operate the product, and only for support and maintenance.
Is our data ours?
Yes. You own what you put in. You can export it while you are a customer and on the way out, and we delete it on request as described in our privacy policy.
What happens to compliance when the rules change?
Tax rates, statutory slabs and return formats live in the shared engine, so a rule change is applied once and inherited by every product rather than patched product by product.
Do you keep backups?
Yes — point-in-time backups, plus monitoring and alerting on the services themselves. Restores are our job, not yours.
Pricing and support
How is it priced?
Per product, on a subscription, sized to how much of it you actually use. There is no implementation fee for a standard rollout. Ask us for the current numbers for the product you are looking at.
Is there a long lock-in?
No multi-year commitment is required. If the product is not earning its place, we would rather hear that early than hold you to a contract.
Who answers support?
The team that built the product. There is no tier-one queue between you and someone who can read the code.
How do we reach you?
Email or phone — both are on the contact page, and they reach the same team that ships the releases.
Still not answered? Ask the people who built it.
Send the question that is actually blocking the decision. You will get a straight answer, not a brochure.