How to Choose a Development Agency (Without Regretting It in 6 Months)

Write down what you are buying. Not the feature list, but the outcome: a working MVP to show investors, a rebuild of a product that has hit its limits, or a design system your own team can extend.

Add four practical facts to that outcome:

• The one to three things users must be able to do at launch.
• Your deadline, and what happens if you miss it.
• A budget range you can actually spend.
• Who on your side will make decisions and review work every week.

The clearer this is, the easier it becomes to spot an agency that is answering a different question from the one you asked. It also makes proposals from different agencies comparable.

A portfolio of polished mockups tells you an agency can design. It does not tell you it can ship. Ask for live products you can open, and for case studies that explain the problem and what changed.

Then test the live products yourself. Open them on your phone, click through the main flow and run them through Lighthouse, Google's free tool for performance, accessibility and SEO audits.

Google's Core Web Vitals give you clear targets to compare against: the main content should load within 2.5 seconds, interactions should respond within 200 milliseconds, and layout shift should stay at 0.1 or less.

For example, Sirius Semiconductors is a microelectronics hub whose site had to win over international buyers in a second language. You can open the live site from the case page and judge the result yourself, which is exactly what you should be able to do with any agency's work.

If a lot of the work cannot be shown, ask why. An NDA on some projects is normal. An NDA on all of them is a signal.

The people on the sales call are not always the people on your project. Ask directly: who designs it, who builds it, and who is your contact day to day? Ask to meet them before you sign.

Watch for the classic handoff, where a senior team pitches and a junior team delivers. It is not automatically bad, but you should know about it up front, not discover it in week three.

At Sakura, a co-founder or the tech lead runs every project and answers to you for the result. Whatever agency you choose, get the equivalent answer in writing: one named person who owns delivery.

Most delays happen in the gaps. Between the designer's file and the developer's build, or between launch day and whoever is supposed to handle fixes and SEO afterwards.

Ask three questions and listen for specifics:

• Does the same team design and build, or is design handed to another company?
• What happens when a design turns out to be expensive to implement?
• Who looks after the product once it is live, and how is that priced?

Specific answers mean the agency has hit these problems before and has a way of dealing with them. Vague answers mean you will be the one dealing with them.

ProAnalizy, a service that explains lab results in plain language, shows why this matters. The upload is the only heavy interaction, so the rest of the first screen renders before any scripts load, and page titles use the test names people actually search for. Those were design, engineering and SEO decisions at the same time.

Two quotes with the same number can describe completely different projects. Compare them line by line, not by the total.

A proposal that is vague about exclusions is not cheaper. It moves the cost to later, when you have less room to negotiate. Our guide on how to read a development proposal walks through each section in detail.

The pricing model matters too. We compare both common models in fixed price vs. hourly development.

Comparing a few offers right now? Send us your brief and you will get a proposal you can put next to the others, line by line.

How an agency behaves before you pay is the best preview of how it behaves after. Watch for a few signals:

• How fast and how clearly do they answer?
• Do they ask about your users and your business, or only about features?
• Do they push back when something in your brief does not make sense?

An agency that agrees with everything on the first call will usually keep agreeing, right up until the deadline slips. Good agencies say "no" or "not yet" early, and explain why.

Pay attention to what they ask you, too. An agency that asks about your budget range, your users and your deadline is trying to shape the scope to your situation, not to its standard package.

Ask for one or two past clients you can talk to, ideally on projects similar to yours. A short call tells you more than any testimonial on a website.

Keep the questions specific, so the answers are hard to polish:

• What went wrong during the project, and how did the agency handle it?
• Did the final cost match the proposal? If not, why?
• Who did you work with day to day, and were they the people from the first call?
• Would you hire them again for your next product?

Listen for how they describe problems, not whether there were any. Every real project has problems. A reference who says "they told us early and fixed it" is worth more than one who says "everything was perfect".

If an agency cannot offer a single reference, ask why. New agencies may have fewer, but they should still be able to connect you with someone who has seen their work up close.

Not necessarily. What matters is overlap in working hours, a shared working language and a clear rhythm of updates, not the address on the contract.

Remote teams work well when the process is explicit: agreed channels, regular calls in overlapping hours and progress you can see without asking. Sakura works this way with founders in different countries, using written updates and calls in the hours both sides share.

There are cases where a local partner helps: for example, when your product depends on local regulations, payment methods or language nuances your team cannot check. In that case, ask the agency how it will cover those details, and who on its side knows the market.

Some answers should end the conversation, however good the price looks:

• A fixed price quoted before anyone has asked about your project.
• No written scope, only a total and a delivery date.
• 100% of the payment required before work starts.
• No access to work in progress until the final handover.
• Code, hosting or app store accounts registered to the agency, with no plan to transfer them.
• Pressure to sign quickly because a discount is about to expire.
• No answer to how they handle security, such as the risks in the OWASP Top 10.

Run through this checklist with the agency you are about to choose. If you can answer yes to all of it, you are comparing serious options.

• Can you open at least a few products they have actually shipped?
• Do you know who will design, build and manage your project?
• Does the proposal list exclusions and explain how scope changes are handled?
• Are payments tied to milestones rather than paid in full up front?
• Will you see working builds regularly, not just at the end?
• Will the code and every account be in your name?

From there, fit and communication decide the rest. Choose the team you would be comfortable calling with bad news, because at some point in every project, someone has to.

If you want to see how we answer these questions, tell us about your project. You will get specific answers and a fixed proposal, not a sales deck.