The short answer
Choose a studio by how it handles your scope, not by its portfolio alone. A good team asks about your users and the one job they need done, pushes back on features that can wait, shows you live products it built and still supports, names who will actually do the work, and explains what happens after launch. Be wary of a fixed price quoted before anyone has asked you questions.
Why the portfolio is the least useful signal
Every studio shows its best screenshots. A portfolio tells you a team can make something look good. It does not tell you whether they ship on time, say no to bad ideas, or answer the phone when production breaks at night.
Look past the screenshots. Ask which of those products are live today, which the studio still maintains, and whether you can open them right now. A live product with real users says far more than a polished case study of something that never launched.
Ten questions to ask on the first call
- 01What would you leave out of the first version? A good team cuts. A team that agrees to everything is selling hours.
- 02Who will actually build it? Names and roles, not "our team". Are they in-house or subcontracted?
- 03Which of your products are live, and can I talk to that client?
- 04How will I see progress? Weekly demos of working software beat status reports.
- 05What does "done" mean for each feature? Tested on real devices? Deployed? Documented?
- 06Who owns the code, the accounts and the designs? You should, from day one.
- 07What happens after launch? Who fixes bugs, updates for new OS versions, and watches the servers?
- 08How do you handle changes in scope? Changes will happen. The process for them should be written down.
- 09What could make this project fail? A thoughtful answer here is a very good sign.
- 10What would you build differently if it were your money?
Red flags in a proposal
- A fixed price and timeline given before anyone asked about your users
- Every feature you mentioned is in scope, and nothing is questioned
- No mention of testing, deployment, monitoring or app store submission
- Vague ownership terms, or the studio keeps the code or the hosting accounts
- No plan for after launch beyond "contact us"
- The people on the sales call are not the people who will build it
Worth knowing
Send the same written scope to every team you are considering. When the quotes come back wildly different, the scope was not clear yet, and that is useful to know before you sign anything.
Studio, agency or freelancer?
They suit different jobs. A freelancer is great for a well-defined piece of work. An agency is built for volume and campaigns. A product studio sits in between: a small senior team that designs, builds and keeps improving one product with you. We compared all three in detail in product studio vs agency vs freelancer.
What a good working relationship looks like
- A short discovery phase that ends in a written scope you both agree on
- Working software you can tap or click every week or two
- One shared channel where you can see questions and decisions
- Code in a repository you own, deployed to accounts you own
- A clear, written plan for support after launch
How we work, so you can hold us to it
We are a product studio of three founders covering backend systems, AI engineering and interface design (meet us). Every project runs through discovery, design, development and launch, and our live work is on the home page so you can open it yourself.
If you are comparing teams, book a 15-minute call and ask us every question on this list. If we are not the right fit, we will say so. Related reading: how to build an MVP.
“The best first calls we have had were the ones where the founder pushed back on us. Bring your hardest questions; a team worth hiring will enjoy them.”
Questions people ask us.
Ask what they would leave out of the first version, who will actually build it, which of their products are live, how you will see progress, who owns the code and accounts, and what happens after launch.
A fixed price works when the scope is written down and stable. For a new product that will change as you learn, a phased or time-based arrangement with weekly demos is often fairer to both sides. Either way, the scope must be written first.
You should. The code repository, the cloud and app store accounts, the domain and the designs should be in your name or transferred to you, so you are never locked to one team.
Give every team the same written scope covering users, journeys, platforms and integrations. Then compare what each includes: testing, deployment, store submission and support after launch, not just the headline number.