Costs, ownership, timelines and what happens after launch

Small integrations start in the low tens of thousands; a full platform is a six-figure programme. Any number quoted before we understand your constraints is a guess, so we scope first and give you a range with the assumptions attached.

Most projects reach a usable first release in three to five months, with something you can click through every two weeks from week three. Where the scope is genuinely unknowable we price a short discovery separately rather than padding the estimate.

You do, from the first commit. Work lands in your repository and your cloud accounts. There is no proprietary framework that only we can maintain, and no exit fee.

Yes, and it is often the better arrangement. We can lead delivery, embed alongside your engineers, or take a specific workstream. What we will not do is run a parallel process that your team finds out about at handover.

Most of our revenue comes from clients past their first release. Support, patching and the next roadmap are a normal continuation, with response times agreed in writing rather than assumed.

You keep everything: code, infrastructure, documentation and a handover session. We would rather you left cleanly and came back than felt locked in.

Yes. The first 30-minute call is free and carries no obligation. You speak with the person who would lead your project, not a salesperson.

Message us on WhatsApp, email arbpra@tripleatech.in or fill in the contact form. We reply within one business day to book your free consultation.

Yes. Send us your NDA or use ours, and we will sign it before you share anything confidential.

Our office is in Barasat, Kolkata, West Bengal 700124, India. We work with clients across Kolkata and India, and in Australia, the UK and the USA.

Yes. Clients in Kolkata and North 24 Parganas are welcome to meet us by appointment. Call or message us on WhatsApp from the contact page to arrange a time.

We break the work down, estimate the pieces, and publish the assumptions each number depends on. When an assumption turns out to be wrong you hear that week — the estimate changes rather than the quality.

Something deployed that you can use, in an environment that resembles production. Not a slide, and not a branch that only runs on a developer machine.

Changes are normal. We price them against the agreed scope so the trade-off is explicit: what comes out if this goes in, or what the date and cost become if nothing does.

Laravel and PHP for most back ends, React, Vue or Angular on the front end, AWS or Azure for infrastructure. We pick well-supported technology by default and justify anything unusual in writing.

Yes, and they are in the estimate rather than an upsell. It costs less to write a test than to debug the same bug in production twice.

Yes. We build to WCAG 2.2 AA as a default constraint. Retrofitting accessibility after launch costs several times more than designing within it.

Fixed price against a fixed scope where the scope is knowable, and time and materials where it genuinely is not. We will tell you which one your project is.

Payment is staged against delivered increments, not calendar months. If we stop delivering, you stop paying.

Yes, including public-sector frameworks and security questionnaires. We plan around sign-off cycles rather than being surprised by them.