Questions to ask a SaaS development company vendor before you sign

Ask a SaaS development company vendor five things: who owns the code and the cloud account, how multi-tenancy is isolated, what the monthly run cost will be at ten times today's load, who answers at 2am after launch, and what happens to the codebase if you leave. Those five answers predict the project better than any portfolio deck.

What follows is the question bank we would use if we were the buyer, grouped by the meeting it belongs in, with the answer that should reassure you and the answer that should not. It is written for a founder or a CTO who has three shortlisted vendors and one week to choose.

Why the usual vendor questionnaire misses

Most SaaS development company due diligence is a procurement form: years in business, headcount, client logos, ISO certificates. None of it distinguishes a firm that has operated a multi-tenant product in production from one that has built twenty single-tenant projects and called them SaaS. The difference only shows up in the second year, when the twentieth customer wants single sign-on, the third wants their data in a separate region, and nobody planned for either.

A useful question has a wrong answer. "Do you follow agile?" has no wrong answer. "Show me the migration you ran to add a tenant_id to a table with fifty million rows, and tell me how long the lock was held" has several, and most of them are silence.

So the questions below are deliberately specific. You are not testing knowledge; you are testing whether they have been there.

The five questions that separate builders from resellers

• Draw your tenancy model on the whiteboard. A vendor who has shipped will name the model without hesitation: shared schema with a tenant column and row-level security, schema per tenant, or database per tenant. They will tell you which one they are recommending for you and what it costs to change later. If the answer is "we will decide in the sprint", the decision will be made by whoever writes the first query. The trade-offs are set out in multi-tenant SaaS architecture.
• What is the monthly cloud bill at ten times this load? Ask for a number, not a shrug. A team that has run a product knows roughly what their database, object storage, egress and observability cost per thousand active accounts, and can say which line grows linearly and which grows with a step.
• Which release did you roll back last quarter, and how? This tests whether they have feature flags, a migration strategy that survives partial rollout, and the humility to admit a failure. Feature flags and beta cohorts are the normal answer.
• Who owns the repository, the cloud account and the domain on day one? The correct answer is you, from the first commit, not at handover. Ownership retrofitted at the end of a project is the most expensive kind.
• What happens in week one after launch when something breaks at 11pm IST? You want a named escalation path, a rota, a response time and a resolution time that are different numbers. Vague reassurance here is the most reliable predictor of a bad year two.

What a good answer sounds like

Use this table during the call. Write the vendor's answer in the middle column and compare afterwards.

What should a SaaS build cost, and what should be fixed?

A scoped SaaS or cloud-native application build with Eazyware starts at $31,500 or ₹20,80,000 and runs to $126,000 or ₹84,00,000 for a platform with billing, roles, admin tooling and integrations. That range, and every other starting price, is published on the pricing page rather than quoted after a discovery call, which is itself a question worth asking your shortlist: will you publish a number before you have seen my budget?

Ask what is fixed and what is not. We fix scope, price and date, and treat change as a named process rather than an argument, which is the model described in fixed price versus time and materials. Ask whether the quote includes design, environments, load testing, data migration and the first month of hypercare, because a quote that excludes four of those is not cheaper, only later. The hidden costs that quotes leave out lists the usual omissions. If you want the full budget picture including cloud and support, read SaaS development cost before the commercial meeting.

Questions for the things that appear after launch

Running costs and metering

Ask how usage is metered, because you cannot price a plan you cannot measure. If your product has per-seat, per-transaction or consumption tiers, the meter is a first-class feature, not a reporting job, and it has to be accurate enough to invoice against. Ask the vendor to show you a metering schema from a product they built.

Support cover and escalation

Ask for the response and resolution commitments in writing and check they are separate numbers. Our care plans run from $1,000 or ₹68,000 a month for business-hours cover with an eight-hour response through to $5,250 or ₹3,40,000 a month for 24x7 cover with a one-hour response and a named engineer, set out on the maintenance and support page. Ask what happens when the named engineer is on leave.

Security posture

Ask which application security standard they build against and whether they can show you the checklist. The OWASP Application Security Verification Standard publishes graded requirements a vendor can be measured against, and a firm that has never heard of it is telling you something. For a product handling Indian personal data, ask how consent, retention and deletion are modelled before you ask about penetration tests.

When these questions are the wrong ones

If you are buying a two-week integration or a marketing site, this list is theatre. Tenancy models and escalation rotas do not apply, and asking them will make you look like you have mistaken a small job for a large one.

They are also the wrong questions when you have not yet decided what the product is. A vendor cannot give you a tenancy recommendation for a product with no defined customers, and pressing for one produces a confident answer built on nothing. In that case buy a discovery engagement first: our discovery sprint is ten days at $3,250 or ₹2,00,000 and is credited against the build, which is a cheaper way to find out that your idea needs reshaping than a fixed-price contract is.

And if the honest answer from a vendor is that a configurable platform covers eighty per cent of what you need, take it seriously rather than treating it as weak salesmanship. That judgement is worked through in build or buy.

What a real evaluation looks like

The strongest signal is not an answer; it is a working session. Give each shortlisted vendor the same two-hour slot, the same three real problems from your backlog, and access to one engineer on your side. Ask them to sketch a solution live. You will learn more about how they think in two hours than in six weeks of proposal documents.

Ask for one reference where the engagement went badly and what they changed afterwards. A firm with no such story has either not shipped enough or is not telling you. Then read the case studies for shape rather than for logos: the in-app copilot for a field-service SaaS shows what a scoped engagement inside an existing product looks like, including what was deliberately left out.

Your pre-signature checklist

• The repository, cloud account and domain are in your name from day one
• The tenancy model is named in the proposal, not deferred to delivery
• Scope, price and date are fixed, with a written change process
• Test coverage of billing, authentication and tenant boundaries is a stated deliverable
• Response and resolution commitments are separate numbers with hours of cover
• The named engineers are named, with their other commitments disclosed
• Data residency and retention are answered for every store, including logs and backups
• Handover includes a runbook and infrastructure as code, not a final archive

Related reading

How to choose an AI development company covers the wider vendor shortlist, red flags when hiring a development partner covers the warning signs this article assumes you already know, and who owns the code, prompts and models covers the contract clauses. If you are ready to run the comparison, the SaaS and cloud-native development service page sets out how we scope and what is included.

The vendor worth signing is the one whose answers get more specific the harder you push, not less.