Questions founders ask us

We're a product and tech partner for startups. We build web and mobile products, automate operations with workflows and AI, and run hosting and engineering teams long term.

Our team is based in India and works with clients across India and internationally. Most collaboration happens remotely, and we visit for workshops when useful.

Mostly founders from pre-seed to Series A, plus established businesses that want to automate operations or modernise software.

Yes. We keep the number of new partners small so every team gets senior attention. Book a call to check availability.

Yes. We overlap working hours with the UK, Europe, the Middle East and part of the US day.

It depends mostly on four things: how many user types you have, which integrations you need, whether you need web, mobile or both, and any compliance requirements. Answer a few questions on our estimate page and we'll send a written estimate within two working days.

Yes, for MVPs and well-defined scopes, agreed in writing after discovery. Ongoing product work is usually a monthly team, which works better when priorities change often.

Yes. The estimate questionnaire or a 30-minute call is enough for a first estimate. A firm figure comes after discovery, when we both know exactly what we're building.

Yes. We start with a code audit so you both know what you're inheriting before committing to a larger engagement.

Not instead of payment. Occasionally we discuss part of the fee as equity alongside cash; ask us if it's relevant.

A five-day high-level review of security, performance, scalability, cloud cost and automation opportunities in an existing product, with a written report.

MVPs take 8–12 weeks. Larger launches take 3–5 months. Ongoing partnerships run as long as they're useful.

About two to three hours a week: a weekly call, a fortnightly demo and quick answers in Slack. More during discovery.

Daily written updates, a weekly call and a working demo every other Friday. You have access to the code and staging site throughout.

Yes. Changes are planned into the next sprint. On fixed-scope projects, we estimate the change and get your OK before building it.

You'll know early, with the reason and your options. How overruns are handled is written into your contract before work starts.

Mostly React, Next.js, Node.js, Python, React Native, Flutter and PostgreSQL on AWS, Google Cloud or Azure. We choose per project and explain why.

Usually, yes. We'll tell you honestly if something should be replaced and what it would cost.

Yes, usually from one codebase with React Native or Flutter.

Yes, as tools that help our engineers write and review code faster. Every change is still reviewed by a person.

Yes: document reading, chat assistants, search over your own data and classification, with safeguards for mistakes.

Every build includes 30 days of fixes. After that, monthly plans cover maintenance, updates and new features.

Yes, through our managed hosting service, in cloud accounts owned by you.

Yes. Response times and uptime targets are agreed and written into your hosting or support plan.

Yes. We monitor performance and cost, and plan scaling work before it becomes urgent.

Yes, a mutual NDA before any detailed discussion. Just ask when you book a call.

You do. The contract assigns the IP in what we build to your company as each milestone is paid, and the code lives in repositories in your name from day one.

Least-privilege access, encrypted secrets, device security for our team and access removed when engagements end.

Yes. We design consent, data access and deletion flows to support DPDP and GDPR requirements, and sign data processing agreements where needed.

Milestones are paid on delivery of working software, so you only pay for what you've received. Contract terms cover disputes in detail.