Straight answers — no sales spin.
Everything buyers ask us before signing: ownership, pricing, timelines, quality and what happens when things change. If your question isn't here, ask it directly — a human architect answers.
At a glance
- 2017
- Founded
- 150+
- Clients served
- 1,550+
- Projects delivered
- 24h
- Response SLA
Why most vendor FAQ pages answer nothing that matters
Most agency FAQ pages exist to be seen, not read: "Do you build websites?" "Yes!" "Do you offer support?" "Of course!" — questions with no real information in the answer, designed to fill a page rather than help a buyer decide. The actual hard questions — who owns the code, what happens if an engineer quits, what a change request costs — go conspicuously unasked.
That evasiveness costs buyers later: a verbal assurance on a sales call about ownership or timelines has no force once a dispute starts, and the FAQ page that promised "flexible, transparent pricing" turns out to have never actually defined what either word means in the contract.
We answer the questions buyers actually ask before signing — ownership, pricing, timelines, what happens when things change — in specific, checkable terms, not marketing adjectives.
Questions worth asking any vendor
Who owns the code and credentials from day one?
What is the response SLA, stated in the contract?
What happens if the assigned engineer leaves?
How are scope changes priced and approved?
At a glance
- Questions answeredGrouped by topic
- 19
- Topic categoriesOwnership to technology
- 5
- Who answersNot a salesperson
- An architect
- Reply timeOn the scoping call
- 1 business hr
Ownership & security
Do we own the code?
Yes — from day one. All source code, documentation and credentials are handed over and belong to you. We work under a signed NDA and IP assignment before any work begins, and you retain access to your own repositories throughout.
How is our data protected during development?
Least-privilege access, encrypted secrets and credentials vaulted — never in code. Your data lives on infrastructure you own, in regions you choose. We never pool, reuse or hold client data, and access is revoked the day an engagement ends.
What happens if we want to leave mid-project?
You can exit cleanly at any point. Code, documentation and credentials are handed over in a documented handover, and there are no penalties or hostage clauses — that's exactly why we can offer it: nothing depends on staying with us.
Pricing & engagement
How much does a custom software project cost?
It depends on scope, complexity and timeline. After a free 30-minute scoping call we send a rough estimate within three business days and a fixed proposal within seven. We offer fixed-bid, dedicated-team, retainer and staff-augmentation models so you can pick the one that fits.
What does a dedicated developer cost per month?
It depends on seniority and specialisation, and we quote it in writing after a 30-minute call — typically 30–40% below metro agency rates for equal experience. Every quote includes the 24-hour SLA, code review culture and replace-anytime guarantee.
Do you charge for scoping and estimates?
No. The scoping call is free, and the written rough estimate within 3 business days is free too. The first paid artefact is the fixed proposal (in 7 days) or the first sprint — you decide which.
Can we start small before committing?
Yes — most clients start with a paid trial slice: one real task on your codebase or a thin-slice prototype. It prices out the fit and the unknowns before any long-term agreement.
Timelines & process
How fast will you respond?
We commit to a 24-hour response SLA on all active projects, stated publicly in every contract. For production incidents on managed-services engagements we target a one-hour first response.
How soon can work start?
For dedicated engineers, typically within 48 hours of the scoping call. For projects, a thin-slice prototype ships in week three and the first production release usually lands in 6–8 weeks depending on scope.
What do weekly demos look like?
Every Friday, a live demo on real software — not a slide deck. You see what shipped, what's next and any decisions needed. It's the same rhythm we run on our own products.
How do you handle scope changes?
In writing, with a priced change note before the work starts. No surprise invoices: if a change affects cost or timeline, you approve it first — that's part of the fixed-bid discipline.
Who do we talk to day to day?
A named architect plus a dedicated Slack channel and shared Jira. The architect who scoped your project stays on it — no hand-offs to a faceless pool, no ticket-queue runarounds.
Technology & quality
What technologies do you work with?
React, Next.js, Angular, Vue, Flutter, Kotlin, Node, Laravel, Django, Python, PHP, Java, MongoDB and PostgreSQL, deployed on AWS and Azure. We recommend the stack that fits your team and constraints — not the one we happen to prefer.
Do you write tests and documentation?
Both, as standard: automated test suites wired into CI on every merge, and documentation written for the engineers who come after us — including a handover walkthrough at project end.
Can you audit our existing system before we commit?
Yes — a paid audit engagement produces a written assessment: what the system does, what's fragile, where the tests are, and a ranked stabilisation plan. The fee is credited against the first sprint if you proceed with us.
What's your QA process?
Risk-based test plans, automated regression suites in CI, real-device mobile testing, and release sign-off checklists. Bugs found after launch are root-caused, not just patched.
Working across locations
Are you based in India? Can you work with overseas clients?
We're headquartered in India, with offices in Pune and Nagpur and a presence in the United States. Our cost base is typically 30–40% below metro agencies, and we routinely work across time zones with US and Gulf clients.
Can you take over a project from another vendor?
Yes. We regularly inherit codebases — we start with a code audit and a written assessment, then propose a stabilization plan before any new feature work. You keep ownership throughout and can exit cleanly at any point.
Which time zones do you work with?
India-first IST hours with overlap windows for US, Canada and the Gulf. Weekly demos are scheduled in your working morning, and communication is async-first with written updates so distance never slows a decision.
Still have a question?
Ask it on a free 30-minute scoping call — a software architect answers, not a salesperson. A reply within one business day.
Contact usBook a scoping call with a software architect — not a sales bot.
You'll get a reply within one business day. We'll send a rough estimate in 3 days and a fixed proposal in 7.
Prefer to talk first? Phone, email and office address are on the contact page.
