The questions people actually ask
Most people arrive here with a problem, not a brief. These are the questions we get asked before a project starts, answered the way we would answer them on a call — no sales copy, and no numbers we cannot stand behind.
Before the project starts
I need a website. Where do we start?
With what the site has to do, not with how it looks. A site that has to sell a product, a site that has to book appointments and a site that has to convince an investor are three different builds, and the difference shows up in the structure long before it shows up in the design. Write down the one thing a visitor must be able to do, and who that visitor is. That single sentence decides most of the rest, and it is the first thing we ask for.
How much does a website or an app cost?
We do not publish prices, and any studio that quotes you before understanding the scope is guessing. What actually drives the number: how many distinct page types there are (not how many pages), whether the content already exists or has to be written, how many languages, whether it needs a CMS someone else will edit, and whether it has to talk to systems you already run. A brochure site and a customer portal can differ by a factor of ten for reasons that have nothing to do with design. Tell us the scope and you get a real figure, not a range.
How long does it take?
The build is rarely the slow part. Waiting on content, photography, legal review and a decision-maker's availability is what stretches timelines, and it is worth planning for honestly. A focused marketing site with content ready is measured in weeks; a product with accounts, payments and an admin side is measured in months. We would rather commit to a date we control than one that depends on approvals we do not.
Who will actually do the work?
The people you talk to. The studio is four senior people, and there is no layer between the person who scopes your project and the person who writes the code. This is the whole reason to hire a small studio rather than an agency: nothing gets translated through an account manager and quietly handed to a junior.
Websites
Can you rebuild our existing site without losing our search rankings?
Yes, and it is mostly a matter of discipline rather than luck. Rankings are attached to addresses, so every old address must either survive or redirect permanently to its closest new equivalent — one hop, not a chain. Before anything is switched, the old site's addresses and their traffic get exported so nothing valuable is quietly dropped. Sites lose rankings in a redesign when nobody keeps that list, not because the design changed.
Do you build multilingual sites, including Hebrew?
Yes, and Hebrew is a layout question before it is a translation question. A right-to-left language mirrors the whole page — navigation, arrows, the side a form label sits on — and a site that only swaps the words reads as broken to a Hebrew speaker even when every sentence is correct. This site itself is built in English, Hebrew and Russian on the same system, which is why we know where it costs more than people expect.
Can our team edit the site ourselves afterwards?
Yes, when that is what you actually want. A CMS is worth it if someone on your side will genuinely publish regularly; if the content changes twice a year, a CMS adds a system to maintain and a way to break the layout in exchange for very little. We would rather ask that question honestly up front than sell an admin panel nobody logs into.
Business systems and automation
What can business automation actually replace?
The work that is repetitive, rule-based and currently done by a person copying data between two places. Taking an order from an email into a spreadsheet, generating the same document from a form, chasing an unpaid invoice, moving a lead from a message into a CRM — these are the cases where automation pays back quickly and predictably. Judgement calls, negotiation and anything where being wrong is expensive stay with a person. The honest test: if you can write the rule down as a sequence of steps, it can be automated.
Can it connect to the systems we already use?
Usually yes, and that is normally the point. Most business software has an API, and the ones that do not can often still be reached through their own export or a scheduled job. The real question is not whether a connection is possible but where the source of truth lives: two systems that both think they own the customer record will drift apart within weeks. Deciding that first is most of the work.
Can you build a chat or Telegram bot?
Yes — for support, for orders, for internal requests, and as an interface to a system your team already uses. A bot earns its place when the alternative is a form nobody fills in or a person retyping the same answer. It is worth being clear about the boundary before building: what the bot answers itself, what it hands to a human, and what it must never attempt.
AI
Can an AI assistant answer from our own documents?
Yes, and this is the most common useful case: an assistant that answers from your policies, price lists, manuals or past projects rather than from the open internet. It works well when the source material is written down and reasonably current, and badly when the real knowledge lives in people's heads. Preparing the material is usually the larger half of the work, and it is worth doing regardless — the same effort makes your own team faster.
Where does AI not belong?
Anywhere a confident wrong answer costs more than no answer at all. Medical, legal and financial specifics, final numbers on a quote, and anything a customer will act on without checking — those need a person or a hard rule, not a model. We say this as the people who would be paid to build it either way.
After launch
What happens once the project ships?
Software that is live is either maintained or slowly rotting; there is no third state. Dependencies get security updates, browsers change, and the business asks for things nobody imagined at the start. We hand over everything — code, accounts, domains — so you are never locked in, and we stay available for the work that follows. Owning your own infrastructure is a condition of working with us, not an upsell.
Do you work with clients outside Israel?
Yes. The studio is based in Israel and works worldwide; most projects run remotely, and the time zone matters far more than the country. What we need is a decision-maker who is reachable — a project stalls on unanswered questions long before it stalls on distance.
Still not the question you had?
Ask it directly. A real answer comes back from one of the four of us, not a template.
Ask us