Questions people ask.

Yes. Most of our design work is handed to someone else's developers. You get Figma files with named components and tokens, a short handover call, and we stay on WhatsApp for questions while they build.

Both, but the tests decide. We recruit 5 people who match your users — a shopkeeper in Paro, a civil servant in Thimphu, a tour guide — and watch them use the prototype on their own phones. What trips someone in Bhutan matters more than a pattern that works in Singapore.

Yes. We design the layouts to hold both, since Dzongkha runs longer and needs a Tibetan-script font such as Noto Serif Tibetan. You supply the translation; we set it and check it on real phones.

Yes, as long as you supply the Dzongkha text. We set it in a Unicode Tibetan-script font, check the line breaks with you and export it as outlines so the printer cannot swap the font.

We brief the printer, send print-ready files and check the proof with you. You pay the press directly, so you are not paying us a margin on paper. We work regularly with presses in Thimphu and Phuentsholing.

Yes. We build a set of templates in Canva or Figma, sized for Facebook, Instagram and WhatsApp status, and show your team how to fill them in. After that you only pay us for new formats.

Yes, and we design for it from the first sketch rather than adding Dzongkha later. Tibetan-script letters are taller than Latin ones, so a lockup that treats both fairly takes real work; we test it at signboard size and at 32 pixels.

We check the company name against the registry, the .bt and .com domains, and social handles before we show you a shortlist. For a trademark search and filing with the Department of Intellectual Property you need a lawyer; we prepare the artwork they need.

It is, from about Nu. 12,000, but we will tell you what you are giving up: no rules for colour and type, so the next brochure drifts. Most clients who start with a logo come back for the system within a year.

Yes. Neither exports cleanly, so we rebuild the pages, copy the text and images across, and set up redirects so old links and Google results keep working. This is our Website migration service; if you need a new design as well, it becomes a WordPress project.

Yes. We set up 2 languages with a switcher and a Unicode Tibetan-script font that renders on every phone without installing DDC fonts. You supply the Dzongkha; we do not translate.

Page builders are why your last site is slow and hard to edit. We use the block editor that ships with WordPress, so there is no yearly licence, no plugin that breaks on update, and any WordPress developer in Bhutan or abroad can maintain it after us.

Through the RMA payment gateway, yes, but your bank has to approve the merchant account first and that can take weeks. We quote it separately and start the paperwork early. Bookings by form, WhatsApp and bank transfer work from day 1.

It answers from your own pages, prices, policies and FAQs, and nothing else. Ask it about your Punakha itinerary and it quotes your page; ask it the weather in Punakha and it says it does not know and offers WhatsApp. It cannot take a booking, take a payment or change a date.

Less than you would fear, but not never. We limit it to your content, test it with 200 real questions before launch, and set it to say so when unsure rather than guess. You read the log each month. If it gets a price wrong, that is a page to fix, and we fix it.

It can read and reply in Dzongkha, but the quality is well below English and depends on how much Dzongkha content your site has. We recommend English with a clear WhatsApp hand-off for Dzongkha speakers until the models catch up.

The AI provider bills usage at cost, usually Nu. 800 to 3,000 a month for a tourism site and a few hundred more for a busy shop; we pass it through with no margin. Hosting is on our Hosting plan. There is no per-seat licence.

Abroad, for most sites. Bhutan's international traffic exits through India, so a server in Mumbai or Singapore with Cloudflare in front is quick from Thimphu and everywhere else. If a regulator or a tender requires the data to stay in Bhutan, we can host at a data centre in Thimphu; it costs more and we quote it separately.

The monitor pings us within a minute and we look. Most outages are a plugin update or a full disk and are fixed within the hour. If it needs you, we message on WhatsApp in the morning. Nightly backups mean the worst case is losing one day of edits.

Yes, if it is WordPress or a static site. We check it for outdated plugins and known malware before it moves; if it is already compromised, cleaning it is a separate job we will quote first.

.bt if you serve Bhutan and want to say so; a tour operator or a Thimphu shop is stronger on .bt. .com if your customers are abroad or you may expand. Many take both and point one at the other. .bt costs more, about Nu. 2,000 a year, because the registry is small.

If it is in their name, it is theirs to transfer. We draft the request, tell you what the transfer code looks like and move it into an account in your name the day it arrives. If they will not cooperate, we register a new domain and redirect once you have the old one. Do not let it expire.

Usually because SPF, DKIM and DMARC were never set. Gmail and Outlook now reject mail without them. We add the 3 records, test with a real send to Gmail and Outlook, and show you the pass.

Not if every old URL redirects to its new page, which is most of the work. We map them all, test each one and send Google the new sitemap. Rankings may wobble for 2 to 3 weeks and then settle. Sites that skip the redirects are the ones that lose.

Usually. If you have the hosting or domain login, we can take a full copy. If you have neither, we rebuild from the live site, page by page, and register a domain in your name; it takes longer and we say so up front.

No. The new copy is built on a temporary link while the old site keeps running. The switch is a DNS change that takes minutes, done on a weekday morning so we are awake if anything needs a hand.