How to choose an app development company in Baku: 12 questions and a contract check (2026)

Bu rehber şimdilik İngilizce olarak mevcut.

Samad Muradli12 dk okuma

When you choose an app development company in Baku, look at three things before the price: a portfolio of live, regularly updated apps in the App Store and Google Play, a contract that puts the source code and store accounts in your name, and a team that can connect the app to sales after launch. If any of the three is missing, the cheap quote usually ends up expensive.

This guide is for retail, education, real estate and service companies about to order an app: how to check whether you need one at all, which 12 questions to ask a vendor, what to look for in the portfolio and the contract, and how to connect the app to CRM, payments, ASO and ads after launch.

First check: do you need an app, or will a website or bot do?

An app takes up space on the customer's phone, and people only keep apps for brands they use often. So the first question is not technology but frequency of use.

An app usually pays off when you have:

  • Repeat purchases. Customers order several times a month: groceries, cosmetics, pet supplies, a café or fashion chain. A bonus balance, loyalty card and push notifications work directly on repeat sales.
  • Daily use. In a training centre: timetable, attendance, payment reminders, notifications for parents.
  • Resident and customer service. In a residential complex: utility payments, maintenance requests, building announcements.
  • Bookings and queues. Beauty salons, clinics, car service centres — customers book several times a year and want to see the appointment on their phone.
  • Phone features. Camera, GPS, NFC, offline mode — things that work poorly or not at all on a website.

You do not need an app if:

  • customers buy from you once a year or once in a lifetime (an apartment, furniture, expensive equipment). For a developer, a website with an apartment picker and a WhatsApp line will bring more sales than an app;
  • most sales happen in Instagram DMs and order volume is small — build a website or chatbot first;
  • the budget covers development only, not promotion and support. An app nobody downloads is just a cost;
  • the app would only repeat what your website does. A mobile-friendly site or a PWA (a website that opens like an app on the phone) is enough.

If in doubt, start with an MVP — a first version with only the core feature — instead of the full product, and watch how real users behave.

Types of app development company in Baku: freelancer, studio, agency, offshore team

Four types of vendor offer mobile app development in Baku. Each is the right choice for some projects; problems start when the wrong vendor is matched to the wrong project.

Vendor Best for Strength Main risk
Freelancer simple MVP, internal tool flexibility, direct contact design, backend and testing rest on one person; if they leave, the project stops
Development studio companies with a ready specification strong engineering, separate roles marketing, CRM and analytics after launch stay with you
Full-service agency businesses that see the app as a sales channel app, ads, CRM and analytics in one team may be more than you need if you only want code
Offshore team large, complex platforms big resources time difference; little experience with Azerbaijani language, local payment systems and local buyer behaviour

The key question: who will be responsible for downloads, sign-ups and sales once the app is ready? If you have an in-house marketing team, a strong studio is enough. If not, the setup where one company builds the app, another runs ads and a third does the CRM loses the most money — each blames the other.

Advertol is a digital marketing and IT agency in Baku, Azerbaijan: Meta and Google ads, SMM and content production, websites and mobile apps, CRM systems and AI automation (WhatsApp/Instagram bots, AI agents) in one team. For a company building an app as a sales channel, the advantage of this model is that the app, the ads that promote it and the CRM that receives the leads sit under one responsibility. Details are on the websites and apps service page.

What to check in the portfolio: live store listing, reviews, last update

Mock-ups and Behance shots do not prove a team can ship apps. Ask for links to live apps and check:

  1. Is it in the store? You need an App Store and Google Play link, not a screenshot.
  2. Whose name is shown as developer? The store page shows the account that published the app. If it is the vendor's name rather than the client's, ask whether the client actually owns their app.
  3. Last update date. An app not updated for over a year is either abandoned or the vendor no longer supports it.
  4. Rating and reviews. Look for complaints like “won't open”, “payment fails”, “crashes after the update”, and see whether the company replies.
  5. Download count. Google Play shows an approximate download range — it tells you whether people really use the app.
  6. Test it yourself. Launch speed on an older Android phone, sign-up, quality of the Azerbaijani and Russian text, behaviour on a weak connection.
  7. References. Ask for a contact at one portfolio client and ask: were deadlines met, and did the team stay reachable after launch?

Experience in your niche is a bonus: a team that built a loyalty app already knows bonus logic, and one that built an education app already knows parent notifications.

The technology question: native, Flutter or React Native

The vendor should choose the technology for your project, not out of habit. In short:

  • Native (Swift for iOS, Kotlin for Android). Top performance and full access to device features, but two separate codebases — development and support cost more. For heavy graphics, complex camera work or AR.
  • Flutter. One codebase for iOS and Android, with the interface looking the same on both. A rational choice for most retail, loyalty, booking and education apps. A detailed comparison is in What is Flutter.
  • React Native. JavaScript-based; if your web team works in React, part of the code can be shared.

Most users in Azerbaijan are on Android, but the iPhone share is high among premium audiences, so most businesses need both platforms. That often makes a cross-platform approach the sensible one.

The more important question: in three years, could another team continue this code? A widely used technology and tidy documentation keep you from depending on one vendor. “We use our own platform, we can't hand over the code” is a separate risk signal.

12 questions to ask before you order a mobile app

Ask every candidate these questions in the same order and write down the answers — comparison becomes easy.

  1. Which apps you released to the stores in the last two years can I look at right now?
  2. Who will work on the project — your own team or subcontractors? Who will be the project manager?
  3. Which technology do you propose, and why that one?
  4. Who builds the backend and admin panel, and where will the server be hosted?
  5. Which repository will hold the source code, and in whose name?
  6. In whose name will the App Store and Google Play accounts be opened?
  7. How is testing done: on which devices, who checks, where do you track bugs?
  8. Which stages is the work split into, what will I see at each, and what is the payment schedule?
  9. Who is responsible for passing store review? If the app is rejected, who pays for the fixes?
  10. How long is the warranty after launch, and on what terms is support provided afterwards?
  11. Have you integrated with a CRM, online payments, 1C or a warehouse system? Show an example.
  12. What is the post-launch plan for downloads and sales — ASO, ads, analytics — and who will do it?

A good vendor gives concrete answers to most of these at the first meeting. If you hear “we'll see later” a lot, that uncertainty will end up in the budget and the timeline.

Contract clauses that matter: source code, store accounts, support

The biggest losses in app projects come not from technical bugs but from ownership questions the contract never addressed.

Source code and intellectual property

The contract should state that the source code, design files (for example, in Figma) and documentation pass to you after full payment. Best practice: the repository (GitHub, GitLab, etc.) is created in your company's account from day one and the vendor is invited to it. That way the code stays with you throughout.

App Store and Google Play accounts in your name

The account that publishes the app owns it. The Apple Developer Program requires a legal entity and a D-U-N-S number to enrol as a company and charges an annual fee; a Google Play Console account is opened with a one-time registration fee. Both accounts should be in your company's name, with the vendor added as a user. If the app is published under the vendor's account, transferring it later takes time and puts reviews, rating and download history at risk.

Server, domain and third-party services

The server, domain, Firebase project, payment system, SMS and map services, and the API keys should also be in your name. List them in an annex to the contract.

Acceptance criteria and staged payments

Each stage should have a verifiable result: “design approved”, “test build in TestFlight and Google Play internal testing”, “app published in the store”. Do not pay everything upfront — tying payments to stages protects both sides.

Warranty and support

iOS and Android are updated every year, and Google Play requires apps to target newer API levels. Spell out the warranty period (bugs found during it are fixed free of charge), the support format after it and response times.

Personal data

If the app collects names, phone numbers, addresses and payment details, record who is responsible for compliance with Azerbaijan's personal data legislation and store rules (privacy policy, in-app account deletion).

How the app connects to sales: CRM, push notifications, payments, ASO and ads

An app published in the store is not yet a sales channel. Five connections turn it into one:

  • CRM. Every sign-up, order and enquiry should land in the CRM so a sales rep sees the customer and you can measure app sales separately.
  • Push notifications. Not one message to everyone but by segment: abandoned carts, bonuses about to expire, students who did not book a class.
  • Payments. For physical goods and services, local bank payment gateways plus Apple Pay and Google Pay; for digital content and subscriptions, check Apple's and Google's in-app purchase rules in advance.
  • Analytics. Firebase or GA4 should track events such as sign-up, cart and purchase; otherwise ads will optimise for installs, not purchases.
  • ASO and ads. The store listing's name, keywords, screenshots and reviews affect whether people find the app — see What is ASO. Meta and Google app campaigns speed up installs, but the goal should be an in-app purchase or sign-up, not the install itself.

In Advertol's projects the logic is the same: every channel flows into one sales panel. For example, the custom CRM built for Momento Travel brings several WhatsApp numbers, Instagram and Facebook into one sales panel. An app should not sit outside such a system — it plugs in as one more channel.

Red flags and what drives price in the market

Signals to walk away:

  • an exact price and a “ready in two weeks” promise with no specification or screen list;
  • a portfolio of mock-ups only, with no live app in any store;
  • refusal to hand over source code, or an offer to open the store account in the vendor's name;
  • no testing stage and no project manager;
  • a demand to pay the full amount upfront;
  • silence about support and updates after launch;
  • a ready-made template presented as custom development (templates are fine; hiding it is not).

In the market, app development cost is mainly driven by: platforms (iOS, Android or both), the number of screens and user roles, backend and admin panel complexity, integrations (CRM, payments, 1C), how custom the design is, the number of languages (Azerbaijani, Russian, English) and post-launch support. Prices in AZN vary widely — we break down the cost structure in How much does mobile app development cost. Remember that the ad budget is separate from development cost.

Advertol publishes no packages or price lists: every company gets an individual proposal after a free strategy call. If your app is meant to be part of your sales and you want it built together with advertising, CRM and AI automation, book a free strategy call — we will start by checking whether you need an app at all.

Frequently asked questions

How long does it take to build a mobile app?

It depends on the number of features, integrations and how fast decisions are approved. An MVP with core features usually takes a few months; an app with payments, CRM and an admin panel takes longer. Also allow time for store review.

Should I receive the source code?

Yes. After full payment the source code, design files and documentation should pass to you, and the contract must say so. The safest route is to create the repository in your company's account from the start.

Can I launch on Android only first?

You can — Android users are the majority in Azerbaijan. But if your audience is premium, you risk losing iPhone users. Cross-platform technology such as Flutter covers both platforms with one codebase.

What costs remain after launch?

The annual Apple Developer Program fee, server and third-party services, adapting to OS updates and support, plus the ad budget for promotion. Plan these together with the development budget.

Does Advertol build mobile apps?

Yes. Advertol in Baku builds websites, mobile and web apps and connects them to sales in the same team through Meta and Google ads, CRM and AI automation. There are no packages — the proposal is prepared individually after a free strategy call.

Bir projeniz mi var?

Ücretsiz bir strateji görüşmesiyle başlayalım.

İletişime geçin

İlgili makaleler

Web siteniz Google'da çıkmıyor mu? 15 neden ve adım adım çözüm (2026)Siteniz Google'da yoksa ya henüz bulunmamıştır ya engellenmiştir ya da rakiplerinden zayıftır. 15 nedeni, Search Console durumlarını ve çok dilli sitelerde yapılan hataları adım adım inceleyin.Ucuz web sitesi neden pahalıya patlar: hazır şablon mu, özel tasarım mı? (2026)Ucuz web sitesinde kısılan şey tasarım değil; sahiplik, hız, SEO, analitik ve destektir. Gizli maliyet tablosu, ödeme öncesi 10 soru ve hazır şablonun ne zaman uygun olduğu.Web sitesi yaptırmak: teknik şartname örneği ve sözleşme kontrol listesiWeb sitesi yaptırmadan önce: 16 bölümlük teknik şartname şablonu, sözleşmede bulunması gereken 13 madde, alan adı ve kodun kime ait olması gerektiği, sitenin kabulü ve tehlike işaretleri.