Question 1

What is your typical engagement model?

Accepted Answer

Two models. End-to-end delivery, where we assign a product manager, lead engineer, designer and the developers a build needs and ship it in two-week sprints. Or team extension, where our engineers embed into your existing team, sprint cadence and tooling.

Question 2

How long does a typical build take?

Accepted Answer

An MVP is usually 8–12 weeks from design to deployment. Enterprise platforms and complex SaaS products typically run 3–6 months of active development. A design-only or audit engagement can be as short as 2–3 weeks.

Question 3

What does the discovery process look like?

Accepted Answer

A scoping call to understand goals, constraints and the systems you already run, followed by a written proposal covering scope, timeline, team composition and pricing model. Nothing is billed until you sign that off.

Question 4

What happens if requirements change mid-project?

Accepted Answer

Scope changes go through a written change request that adjusts timeline and cost before any work starts. We do not silently absorb scope creep, and we do not silently bill for it either.

Question 5

Do you provide support after launch?

Accepted Answer

Yes, on an SLA-backed retainer covering monitoring, incident response, dependency patching, framework upgrades and a capped pool of hours for small improvements. Response times are tied to severity, defined by customer impact rather than technical category.

Question 6

Can you take over a project someone else started?

Accepted Answer

Often, yes. We begin with a technical audit of what we would be inheriting — architecture, test coverage, dependency health, deployment story — and give you an honest read before committing to a timeline. Sometimes that read is "this needs a rewrite", and we will say so.

Question 7

What technology stack do you specialise in?

Accepted Answer

React and Next.js on the frontend. Node.js, Python (FastAPI) and Go on the backend. Cloud-native infrastructure on AWS, GCP or Vercel, backed by PostgreSQL or MongoDB. We pick from that set rather than chasing whatever is new.

Question 8

How do you handle security and compliance?

Accepted Answer

Security is built into the CI/CD pipeline from day one: end-to-end encryption, dependency auditing, OWASP practices and least-privilege access. We can architect to HIPAA, SOC 2 or GDPR requirements where a project needs it.

Question 9

Do you build AI features, or just integrate APIs?

Accepted Answer

Both. We integrate LLMs from OpenAI and Anthropic, and we build the parts that actually decide whether it works — retrieval pipelines, vector stores, chunking strategy, reranking and evaluation harnesses. Most disappointing AI features fail at retrieval, not at the model.

Question 10

Do you write tests and documentation?

Accepted Answer

Yes, as part of delivery rather than as a line item. Unit and integration coverage on critical paths, plus architecture and setup documentation handed over with the source.

Question 11

Who handles infrastructure and deployment?

Accepted Answer

We set up CI/CD, staging environments and monitoring as part of the build, so launch is not a one-time event you are then left to maintain. Infrastructure can be handed fully to your team, or we can keep running it on a retainer.

Question 12

How is pricing structured?

Accepted Answer

Defined-scope projects are fixed-bid against an estimated effort. Ongoing development and team extension run on a time-and-materials retainer. Blueprint lets you configure the project yourself and see an instant ballpark before you talk to anyone.

Question 13

Who owns the intellectual property?

Accepted Answer

You do — 100% of it. On completion and settlement of invoices, all source code, assets and IP transfer to your organisation. This is in the contract, not a promise.

Question 14

Do you sign an NDA and MSA?

Accepted Answer

For anything beyond an initial scoping conversation, yes. We sign a mutual NDA and a Master Services Agreement covering confidentiality, IP assignment and liability before technical details or code change hands.

Question 15

What currencies and payment terms do you work with?

Accepted Answer

We invoice in INR or USD. Fixed-bid projects are billed against milestones; retainers are billed monthly. Terms are agreed in the contract before work starts.

Question 16

Where is your team based, and what timezones do you cover?

Accepted Answer

Our studio is in Chennai, India. We work with clients across US, European and APAC timezones by building overlap hours into the sprint cadence rather than expecting you to adapt to ours.

Question 17

How do we communicate during a project?

Accepted Answer

You get a named point of contact plus direct access to your lead engineer, on whichever channel you already use — Slack, email or WhatsApp — alongside scheduled sprint check-ins. Not a ticket queue.

Question 18

Can we see progress without asking for it?

Accepted Answer

Yes. Clients get Client Portal access showing live project status, approvals, invoices and documents, so you are never dependent on a status email to know where things stand.

Question 19

Who will actually work on our project?

Accepted Answer

You will know your lead engineer and product manager by name before the contract starts. Any team change mid-project is communicated in advance, not discovered after the fact.

Question 20

Do you build with accessibility in mind?

Accepted Answer

Yes. Accessibility is checked against WCAG AA as part of code review rather than audited at the end. Touch targets, focus states, keyboard paths and safe-area insets are handled as we build, and forms ship with real inline validation rather than colour-only error states.

Question 21

How do you stop performance regressing after launch?

Accepted Answer

Core Web Vitals and Lighthouse checks are wired into CI, so a regression fails the build instead of surfacing months later. On a maintenance retainer we also re-measure on a schedule, because sites decay as content grows and dependencies age.

Question 22

Can you support SSO for our enterprise customers?

Accepted Answer

Yes — OAuth 2.0, SAML SSO and TOTP multi-factor, with a role and permission model and an admin interface to manage it. We build this into the product rather than bolting it on when your first enterprise buyer asks.

Question 23

What stops one customer seeing another customer’s data?

Accepted Answer

Tenant isolation is enforced at the data layer, not trusted to application code — row-level isolation in the database itself, so one customer cannot read another’s rows even if a query is written wrong. Indexes and partitioning are designed around the tenant key from the start.

Question 24

How do you know an AI feature is actually working?

Accepted Answer

We establish a baseline and an evaluation harness before any training or tuning, so improvements are measured rather than felt. Retrieval answers cite the source documents they came from, forecasts report backtested accuracy against periods the model never saw, and anything uncertain hands off to a human.

Question 25

What happens if a release goes wrong?

Accepted Answer

Production releases are one reviewed click with a rollback that takes seconds, and staging is kept at parity so it genuinely predicts production. Schema changes are split into expand-and-contract steps so a rollback is never blocked by a migration.

Question 26

Do you test your backups, or just schedule them?

Accepted Answer

They are tested. Backups run automatically and the restore procedure is exercised periodically, because an untested backup is a guess. Slow query review, index tuning and storage forecasting are part of the same cycle.

Question 27

What do we actually receive at the end of a project?

Accepted Answer

All source code, assets and intellectual property transfer to you on completion and settlement — that is a contract clause, not a promise. It arrives with unit and integration coverage on the critical paths, plus architecture and setup documentation, delivered as part of the work rather than quoted as an extra.

Ask the awkward ones.

Still have a question?

Want to see it priced first?

Happy Deepavali.

Ask the awkward ones.

01Engagement & processWhat is your typical engagement model?

02Engagement & processHow long does a typical build take?

03Engagement & processWhat does the discovery process look like?

04Engagement & processWhat happens if requirements change mid-project?

05Engagement & processDo you provide support after launch?

06Engagement & processCan you take over a project someone else started?

07TechnologyWhat technology stack do you specialise in?

08TechnologyHow do you handle security and compliance?

09TechnologyDo you build AI features, or just integrate APIs?

10TechnologyDo you write tests and documentation?

11TechnologyWho handles infrastructure and deployment?

12Pricing & contractsHow is pricing structured?

13Pricing & contractsWho owns the intellectual property?

14Pricing & contractsDo you sign an NDA and MSA?

15Pricing & contractsWhat currencies and payment terms do you work with?

16Team & communicationWhere is your team based, and what timezones do you cover?

17Team & communicationHow do we communicate during a project?

18Team & communicationCan we see progress without asking for it?

19Team & communicationWho will actually work on our project?

20TechnologyDo you build with accessibility in mind?

21TechnologyHow do you stop performance regressing after launch?

22TechnologyCan you support SSO for our enterprise customers?

23TechnologyWhat stops one customer seeing another customer’s data?

24TechnologyHow do you know an AI feature is actually working?

25Engagement & processWhat happens if a release goes wrong?

26Engagement & processDo you test your backups, or just schedule them?

27Team & communicationWhat do we actually receive at the end of a project?

Still have a question?

Want to see it priced first?

Happy Deepavali.