Question 1

Will any of this get outsourced offshore?

Accepted Answer

No. The people on the call are the people committing code, in New York. There is no delivery arm in another timezone and we are not reselling somebody else's team. The honest tradeoff: we only run a couple of builds at once, so sometimes the answer is that we can't start for a few weeks.

Question 2

How long will it take, and what will it cost?

Accepted Answer

Builds start around $8,000, and that floor is real: an app with accounts, a database, and an admin view is rarely less. If what you describe is actually a website with a form, we will tell you and quote the cheaper thing instead. After the call you get a screen list with one fixed number against it, usually inside a week. If one piece is genuinely unpredictable, we scope that piece on its own and say why.

Question 3

What happens after launch?

Accepted Answer

Your call. You can take the keys and hand the whole thing to your own developer, or keep us on for fixes and small changes at an agreed monthly number, quoted separately from the build. The repo, hosting and domain are in your name before launch day, so leaving is a decision, not a hostage negotiation.

Question 4

Do I have to hire you for ads to get an app built?

Accepted Answer

No. App work carries no spend qualifier and no attached retainer. Our ad plans start at $2,400/mo and none of that applies here. If you already run Google or Meta we'll mention anything we notice, but the build is scoped and priced on its own.

Question 5

You have no app case studies. Why should I hire you?

Accepted Answer

Fair. Margian was founded in 2026 and has no app case studies to show you, so don't take our word on the outcome. Take the scope document instead. It's free, and you can hand it to any other shop for a competing quote. That's a better test than a testimonial we wrote ourselves.

Question 6

What if we start and it isn't working out?

Accepted Answer

The scope gets broken into pieces, each one ending in something you can click. Stop after piece two and you keep piece two: the code, repo access, and a note on how to run it. We'd rather end early than bill through a project both sides already know is wrong.

Talk with Margian