Choice Hotel websites in Armenia: direct bookings or OTAs only
Hotel website in Armenia: how much OTAs and banks take from a 100,000 ֏ booking, when a direct site pays off, and bank requirements for payment pages.
Cookies on this site
The site stores what it needs itself: your theme, your animation setting and this choice. Analytics, marketing and external services switch on only with your consent. You can change your mind at any time. More about cookies
Choice
A landing page takes me 2–3 weeks, a company website takes 3–5, and an online store takes 6–12. These timelines come from my pricing page and apply to the baseline scope of work. In Armenia, what holds up a website longest usually isn’t the developer. It’s waiting on copy in multiple languages, your approvals, and bank payment integration.
| Project type | Timeline | Starting price |
|---|---|---|
| Single-page landing page | 2–3 weeks | 200,000 ֏ |
| Company website | 3–5 weeks | 350,000 ֏ |
| Online store | 6–12 weeks | 500,000 ֏ |
I give timelines as a range because design and scope affect delivery far more than code does. I send the exact timeline and price in an estimate after our first conversation, before you pay anything and before work starts. If the timeline in the estimate differs from the table, trust the estimate: the table describes the baseline scope.
Many clients in Armenia want their site in Armenian, Russian, and English. To me, that doesn’t mean building one page and multiplying it by three. Each language needs to be written or translated, proofread, and checked in the layout (word lengths vary across languages, so a button that fits Russian text might break in Armenian), then submitted to search engines with its own title and description. You can read how Google links these localized versions in my article on websites in three languages.
That’s why I price languages separately in the estimate: a second and third language add to both cost and turnaround. If you send ready-to-use copy in all languages, the timeline is shorter. If I need to handle translation, the timeline grows to include translation and your review: I don’t publish copy in a language neither of us reads.
Web development doesn’t happen without your input. I need your logo, company details or finished copy, photos, and domain access. While I’m waiting on any of these, the project is paused. These are the most common bottlenecks:
| What is needed | Where it gets stuck | How to avoid delays |
|---|---|---|
| Copy for each language | Left for last and written after the layout is finished | Send a draft in one language before we start, and prepare other languages in parallel |
| Photos | Photo shoots get scheduled after work has already begun | Take photos before our first conversation or decide in advance to launch without them |
| Domain access | The domain is registered to a former contractor | Check who owns the domain registration before getting an estimate |
| Layout approvals | Multiple stakeholders weigh in, each with conflicting edits | Appoint one person who has the final say |
A quick note on the domain: if it isn’t registered in your name, everything else grinds to a halt. I explained how registration works and what to check in my article on registering a .am domain.
An online store’s timeline includes factors outside the developer’s control. Under Ameriabank’s internet acquiring terms (edition 9, clause 2.8), the bank registers and issues integration credentials within 10 business days of signing the agreement, provided there are no grounds for refusal. The bank transfers customer payments to the merchant within 5 business days after transaction authorization. On the Telcell Business partner page, application review takes 2 days.
These steps run alongside development if you request integration on time. If you apply to the bank only after the store is finished, you’ll add another two banking weeks (10 business days) of waiting on top of the 6–12 weeks. That’s why I recommend signing the merchant agreement with the bank before we build the checkout page. You can read more about bank requirements in my guide on accepting online payments in Armenia.
A fixed deadline, such as a store opening or a promo campaign, changes my work plan. Let me know about it during our first conversation so the expedited timeline is listed as a separate line item in the estimate. Skipping testing on real mobile devices or omitting credential handoffs is out of the question: without those, a website isn’t actually ready. But we can trim the scope.
| What to postpone from version one | What this gives you |
|---|---|
| Second and third languages | Launch in one language, add the others later |
| Part of the product catalog | Upload the first batch of products, add the rest as they’re ready |
| Secondary payment methods | Start with one method (like cards), add digital wallets later |
| Blog and news section | Publish them after launch; they won’t delay your release date |
We decide what to cut from the initial release when drafting the estimate. You can always add those features back later, but each part is handled as a separate project that adds to the price.
Calculate it like this: take the baseline timeline from the table, add time for your reviews, and factor in the bank if you accept cards. For an online store taking card payments, bank onboarding takes up to 10 business days on top of development if you don’t start it early. Meanwhile, a single-language landing page doesn’t need a bank at all. The earlier you share your target date and send over your materials, the less time is lost to waiting.
Web development is my full-time work and livelihood. Tell me what kind of site you need and when you need it by, and I’ll send an estimate with a timeline that clearly breaks down what depends on me, what depends on you, and what depends on the bank.
Websites, online stores and landing pages in three languages, so visitors understand your offer and get in touch.
Talk to us
Phone us, write to us or send a short brief. You get a clear next step and, after the first conversation, a written estimate.
Animation is off because your system asks for reduced motion.