Software FAQs: Cost, Ownership, Timelines & Support

After a short paid discovery (1–3 weeks), you receive a fixed price with milestones — most small-business platforms land in staged phases so you can stop after any working release. Discovery is credited toward the build if you proceed.

Every custom software project starts with a short paid discovery, typically 1–3 weeks, that produces a written scope, milestones and a fixed price. The discovery fee is credited toward the build if you proceed, so there is no big-bang commitment.

Yes — most engagements start with a paid discovery or pilot, then scale to a build or monthly support once value is proven.

Yes. Fixed-scope builds are staged so you can stop after any working release and keep everything delivered so far. Monthly plans renew until you cancel with a month's notice — code, docs and access stay with you either way.

Core builds are fixed-price per stage. Dedicated developers and support are monthly rolling. Reviews and roadmaps are short fixed-price work — not open-ended hourly retainers.

USD for international clients and INR for India, with published planning ranges on the pricing page. Your written quote states currency and tax treatment before you sign.

Third-party licences, app-store fees, paid cloud or AI APIs you elect to use, and out-of-scope change requests — all called out separately so nothing is a surprise invoice.

You do, under a signed IP-assignment agreement. We build in your repositories with pull-request reviews and hand over documentation, tests, credentials and access lists at the end — so your team can run everything without us.

No — mention it in your brief and we sign before you share anything sensitive.

Yes, after a paid code review covering architecture, tests, security basics and deployment. We list risks, quick wins and what not to touch — then propose a step-by-step modernization plan that keeps the business running.

In your GitHub or GitLab organisation from day one, with your access keys — so continuity never depends on our internal tooling.

No. Your custom code is assigned to you. We may reuse generic patterns and open-source components we already had, but not your business logic or data models.

Least-privilege accounts in your cloud and repo, secrets in your vault or secret store, and a full access list transferred at handover.

One overlapping standup per week plus written updates, with a live demo of working software every week. Serving India, the USA, UK, Australia and Canada, we schedule in your timezone so you can redirect scope early.

Builds run in weekly sprints with a live demo every week, so the first usable release arrives early. A typical discovery runs 1–3 weeks, and the first working release ships within weeks of that. Timelines per service are listed on the services page.

Within 12 hours with clarifying questions and a discovery quote — no retainers, no spam.

What it should do, who uses it, current tools or stack, and your timeline. Screenshots or sheets help but are optional.

Yes — dedicated developers join your board, standups and repo with your process. Fixed-scope builds run in your repositories too, so nothing lives only on our side.

Whatever you already use — typically GitHub or GitLab, Jira/Linear/Notion, and a weekly video demo. We adapt to your board rather than forcing ours.

A named decision-maker on your side signs off acceptance criteria before a stage starts and demo sign-off before the next stage is invoiced.

TypeScript and Next.js, React and Node.js, Python and FastAPI, Flutter for iOS and Android, PostgreSQL, and Kubernetes with Terraform on AWS, Azure or GCP. AI features use hosted APIs for measured pilots unless you ask otherwise.

Yes — monthly support for fixes and small improvements, or a clean handover with a runbook and walkthrough if your team takes over. Both options include documentation and access transfer.

NDA first, least-privilege access, dependency scanning in CI, secrets never in git, and a risk-ranked checklist before launch — deeper reviews are scoped as cybersecurity engagements.

Yes — we produce evidence packages, architecture notes and control mappings your auditors can use (SOC 2 / ISO preparation is a common adjacent engagement; certification itself stays with your auditor).

Support plans cover monitoring, patches and small fixes with agreed response windows. Critical issues on an active engagement are handled through your normal escalation path.

Through technical SEO for rankings plus answer-engine and generative-engine optimization for AI Overviews, ChatGPT and Perplexity — clear service pages, FAQs, schema markup and a 90-day content plan. Ecommerce builds and PPC or social campaigns are scoped in the same plan.

Yes — conversion-focused pages and tracking sit in the same delivery plan as SEO when paid search is in scope.

We ship clean information architecture, FAQ schema, llms.txt and crawlable HTML so agents can cite your pages accurately — without cloaking or hidden text.

Yes — mention it in the brief and we sign before you share anything sensitive. Mutual NDAs are standard.

AnyPlace (Hisar, Haryana, India). Invoices and the IP-assignment agreement name AnyPlace; international clients can be billed in USD.

The engagement letter states governing law and venue — typically Indian law for India-based work, with clear written terms for cross-border clients.

Optional. For larger fixed builds we can arrange escrow or dual-control access so your team is never locked out mid-project.

Small and senior-led: an architect plus one or two developers per project, with QA and DevOps shared across engagements. You always know exactly who works on your project.

We serve growing businesses in India, the USA, UK, Australia and Canada — with overlapping hours and written updates so time zones never block progress.

Yes before kickoff for dedicated teams; for fixed builds you meet the scope owner and lead builder in discovery.

You always have a named lead. If a role changes mid-engagement, we replace from the same senior pool and hand over board context in writing.

Yes — embedded pods of 1–2 developers plus shared QA/DevOps, or a larger squad for multi-track programs after discovery.

In your cloud accounts and repositories by default. We do not park production data on shared agency tenancies.

No. Client code and data are not used to train foundation models. AI features you commission run under your chosen provider's enterprise terms.

Handover pack stays available per the engagement letter; we purge working copies of sensitive datasets after agreed retention windows.

Yes — architecture diagrams, control notes and remediation lists for buyer or auditor questionnaires are a standard part of security-review engagements.

We engineer to those control families where the engagement requires them (access control, encryption, logging, data residency). Formal certification remains with your auditors.