Question 1

What kinds of projects do you take on?

Accepted Answer

Mobile apps for iOS and Android, web applications, desktop software for macOS/Windows/Linux, and 2D games. We take work from a four-week MVP to multi-year platform builds. What we do not take is work outside those four disciplines — if you need a hardware firmware team or a data-science lab, we will introduce you to one.

Question 2

How large is a typical Rose IT team?

Accepted Answer

Three to seven people: a lead engineer, two to four engineers, a designer, and a delivery lead who is your single point of contact. Larger platform work runs two such pods in parallel rather than one team of fourteen.

Question 3

Do you work with clients outside Myanmar?

Accepted Answer

Most of our work is international — Singapore, Australia, the UK, the US and the Gulf. We keep a four-hour overlap with every client timezone and run all delivery in English.

Question 4

How do you price a project?

Accepted Answer

Fixed price for anything we can scope precisely, time-and-materials for open-ended platform work. Both come from the same discovery phase, so you see the estimate before you commit to the build. We do not bill for the discovery if you go ahead with us.

Question 5

What does a project typically cost?

Accepted Answer

An MVP mobile app starts around $18,000. A production web platform is typically $45,000–$120,000. A 2D game runs $25,000–$90,000 depending on content volume. Every number here is a real project we shipped, not a bracket we invented.

Question 6

Do you offer retainers?

Accepted Answer

Yes. Post-launch retainers start at $3,500/month for monitoring, maintenance and a fixed monthly engineering allocation. Most clients move onto one after the 30-day hypercare period ends.

Question 7

How long until we see something working?

Accepted Answer

A clickable prototype in week two or three, and an installable build every two weeks after that. You should never be more than fourteen days from something you can hold.

Question 8

Can we change scope mid-project?

Accepted Answer

Yes, and you will want to — the things you learn in week six are the point of shipping early. Changes are re-estimated against the same rate card and go into the next sprint rather than silently absorbing the current one.

Question 9

How do you handle handover?

Accepted Answer

Everything lives in your accounts from day one: your repository, your cloud, your app store listings. Handover is a two-day walkthrough and a written runbook, not a transfer of ownership.

Question 10

Who owns the code?

Accepted Answer

You do, entirely, from the first commit. We work in your repository under your organisation. There are no license fees, no proprietary framework you are locked into, and no escrow clause you would ever need to invoke.

Question 11

What is your testing standard?

Accepted Answer

Unit and integration tests on all business logic, end-to-end tests on the critical paths, and a CI pipeline that blocks merges on failure. We target 80% coverage on the domain layer and do not chase 100% for its own sake.

Question 12

Can you work with our existing codebase?

Accepted Answer

Frequently. About a third of our work is taking over or extending something that already exists. We start with a two-week audit and give you an honest read on whether extending or rebuilding is cheaper — sometimes the answer costs us the bigger project.

Question 13

What happens after launch?

Accepted Answer

Thirty days of hypercare included in every build: we watch the metrics, fix what breaks, and are on call for launch-week incidents. After that you can move to a retainer or take it fully in-house — both are fine with us.

Question 14

What are your support response times?

Accepted Answer

On a retainer: one hour for a production outage, one business day for everything else. Outside a retainer we still answer, but without a contractual SLA behind it.

The questions we get before every project

Still have a question?

The questions we get before every project

Still have a question?