Question 1

Who actually does the work?

Accepted Answer

Saai Siddharth T, the founder. Not an account manager, not a team you are introduced to once and never meet again. The person who scopes the project is the person who writes the code and the person who replies to your email. For specialist pieces outside that range — a video edit, a heavy motion sequence — a trusted collaborator may be brought in, and you will be told before it happens, not after.

Question 2

You are one person. What happens if you are unavailable?

Accepted Answer

It is a real risk and worth planning for rather than talking around. Code lives in your repository under your account from the first commit, not on a studio machine. Infrastructure runs in your accounts wherever possible. Every project ships with a written handover — architecture, environment variables, deploy steps — so another engineer can pick it up without an introduction. If something long-term happens, you are not locked out of your own product.

Question 3

Can I see previous work?

Accepted Answer

Publicly, not yet — and inventing a portfolio is exactly the thing this studio refuses to do. What you can inspect right now: this site, the proposal system behind it, and the CRM that runs it, all built here. Ask on a call and specific work can be walked through directly. When there are client case studies worth publishing, with permission, they will appear on this site with real numbers.

Question 4

How long does a project take?

Accepted Answer

It depends on scope, which is why the scope is agreed in writing first. As rough shapes: a marketing site is usually 2–4 weeks, a working MVP 4–8 weeks, and a larger platform 3 months or more. Any date given before the scope is written is a guess, and a guess is not a commitment.

Question 5

What do you not do?

Accepted Answer

Anything that needs a team larger than this studio, on a deadline that assumes one. Also: rescuing a codebase whose owner will not give access to it, projects with no decision-maker available, and work where the timeline is fixed before the scope is. If a project is a bad fit, that is said up front rather than discovered in month two.

Question 6

How do revisions work?

Accepted Answer

Each milestone includes two rounds of revision inside the agreed scope. Changes that alter the scope are quoted separately before any work starts, so no invoice ever arrives as a surprise. What counts as inside the scope is written down at the start, which is the entire point of scoping it.

Question 7

What is included in the quoted price?

Accepted Answer

Design, build, testing, deployment, a written handover, and 30 days of post-launch support for defects. Every quote also lists what is explicitly excluded — third-party subscriptions, paid media, ongoing content — so the number you are given is the number you pay.

Question 8

How is payment structured?

Accepted Answer

In milestones, not one lump sum: typically a deposit to start, then payments tied to agreed deliverables, with the balance on handover. Amounts and dates are written into the proposal before anything begins. Invoices are in INR; international payment is possible and is agreed case by case.

Question 9

Can I get a fixed price?

Accepted Answer

Yes, where the scope can be fixed. A well-specified build gets a fixed price. Open-ended work — ongoing marketing, a product still being figured out — is better on a monthly basis, because a fixed price on an undefined scope is either padded to cover the unknown or renegotiated later. Both are worse for you than being told which one this is.

Question 10

What if the work is not right?

Accepted Answer

Progress is reviewable at every milestone rather than revealed at the end, so problems surface while they are still cheap. If a milestone is not accepted, it is reworked. If the engagement is not working, it can be stopped at a milestone boundary — you pay for what has been delivered and accepted, you keep that work, and you keep the code.

Question 11

What is the stack?

Accepted Answer

By default: TypeScript throughout, Next.js on the front end, Cloudflare Workers and Postgres behind it, Prisma for data access. This site, its API, its CRM and its proposal system all run on exactly that, so the stack is not a recommendation from a slide — it is what is running while you read this.

Question 12

Can you work with my existing codebase?

Accepted Answer

Often, yes. It starts with a paid audit — a short, fixed-price read of the code and infrastructure ending in a written assessment of what is sound, what is risky, and what it would cost to move forward. That is a genuine deliverable you keep whether or not the work continues, and it is a far better basis for a decision than an estimate made without opening the repository.

Question 13

Can you scale if my project grows?

Accepted Answer

Not into a large team, and claiming otherwise would be the easiest lie on this page. This studio is sized for one engineer's throughput plus occasional specialist help. If a project outgrows that, you will be told, and helped to hire — the handover documentation exists precisely so bringing in more engineers does not mean starting again.

Question 14

Do you handle hosting and deployment?

Accepted Answer

Yes, and it is set up in accounts you own — your Cloudflare, your Vercel, your database — with access granted to the studio rather than the other way round. That means the running cost is billed to you directly at cost, with no margin added, and revoking access never takes your product offline.

Question 15

Do I own the code?

Accepted Answer

Yes. On final payment, full ownership of the source code, the designs and the associated intellectual property transfers to you, in writing. In practice you already have it: the repository is under your account throughout, so ownership at the end is a formality rather than a migration.

Question 16

What support is there after launch?

Accepted Answer

Thirty days of defect support is included with every build — if something shipped broken, it gets fixed, at no charge. Beyond that, ongoing support is a separate monthly arrangement, priced by what it actually covers. There is no automatic renewal and no retainer you have to cancel.

Question 17

Will you sign an NDA?

Accepted Answer

Yes, before any detail is shared. Send yours and it will be reviewed and signed, or a standard mutual one can be provided. Client information is not used as a portfolio piece, a case study or a testimonial without written permission — which is a large part of why this site currently shows no client names.

Question 18

Where are you, and what hours?

Accepted Answer

Attur, Salem, Tamil Nadu, India — IST, UTC+5:30. That gives a full working overlap with Europe, Asia-Pacific and the Middle East, and a morning overlap with US Eastern. Email is the record of the project; calls are scheduled rather than expected on demand, and a reply outside working hours is a courtesy rather than a promise.

Output	Duration	Aspect ratio	Resolution	Captions	Source files	Review rounds
iOS App Bundle (.ipa)	Ready for TestFlight	Responsive Mobile	Retina / Super Retina	N/A	Full Git Repository	2 Rounds
Android App Bundle (.aab)	Ready for Play Console	Responsive Mobile	HD / Quad HD	N/A	Full Git Repository	2 Rounds

Output	Duration	Aspect ratio	Resolution	Captions	Source files	Review rounds
iOS App Bundle (.ipa)	Ready for TestFlight	Responsive Mobile	Retina / Super Retina	N/A	Full Git Repository	2 Rounds
Android App Bundle (.aab)	Ready for Play Console	Responsive Mobile	HD / Quad HD	N/A	Full Git Repository	2 Rounds

This page

Build

Marketing

Elsewhere

Legal

Mobile products designed around real user behavior.

The problem it solves

What is in scope, and what is not

What can be built

Choose the Right Mobile Delivery Model

Deliverables and formats

How the work runs

What actually changes

The quality bar

Mobile Apps questions

Scope Mobile App

Related services

On this page