Questions,
answered

The people building your project. MOHBI is a small independent studio, so there is no account manager between you and the work. That is also why we deliberately run few projects at once.

The United Kingdom, working on UK time. We work remotely with clients across the UK and internationally, provided there is enough working-hours overlap for a real conversation rather than a daily exchange of messages.

We reply to every enquiry, usually within one working day. If you would rather message than email, WhatsApp is on the contact page and is often faster.

It depends on what is already running. Because we keep the number of concurrent projects low, there is sometimes a short wait for a start date. We will tell you honestly on the first call rather than starting your project and then not giving it attention.

Yes, routinely, and we are happy to sign yours before a first call if you would prefer to discuss the detail under one.

On the first call we work out the flows involved, the kinds of user, and what has to connect to systems you already run. That is enough to define a scope precisely and quote against it. You know what is included and what is not before any work starts.

Small changes are expected and are folded in as we go: that is the entire point of prototyping early. Something genuinely outside the agreed scope is discussed and agreed separately, and you decide whether to add it. Nothing appears on your invoice that you did not agree to first.

A first call, real feedback on the prototype, and whatever content you already have. The single most common thing that slows a project down is waiting for copy, images, or access to an existing system, so the earlier those arrive the better.

Yes, if the problem is well defined. A single flow, an integration, or an automation that removes a recurring manual job is often a better first engagement than a large build, for both sides. Describe what you need and we will tell you honestly whether we are the right fit.

We will say so on the first call, and where we can we will point you at someone better suited. Taking work we cannot do well costs us more than turning it down.

Next.js and React for web, React Native and Expo for mobile, TypeScript throughout, and Tailwind with CSS variables for styling. These are mainstream, well-documented choices, which matters: another team should be able to pick your project up without an archaeology expedition.

Yes. The code, the repository, and the domain are yours in your name from the start, and you get written documentation at handover. Hosting is the one part that can go either way: keep it in your own account, or let us run it for you. Either way the project can be moved, and nothing about how we build is designed to make leaving difficult.

Whichever you prefer. Some clients want it in their own account and pay the platform directly. Others would rather never see a server, so we run the infrastructure and handle monitoring, backups, certificates, and updates for them. We usually recommend Vercel or Cloudflare depending on the project, and if you have an existing arrangement we will work with it.

Everything we build is responsive and tested on real devices. For most projects the majority of traffic is on a phone, so mobile is the primary case rather than an adaptation of the desktop layout.

Keyboard navigation, focus management, semantics, and contrast are built into the components rather than audited at the end, which gets you most of the way to WCAG 2.2 AA. If you need certified compliance we scope a formal audit separately.

Often. We will audit it first and give you an honest read on whether extending it or replacing it is cheaper over the next two years, including when that answer is the less profitable one for us.

A period of post-launch support is included in every project, agreed as part of the scope. After that you can move to an ongoing arrangement or simply come back when you need something. We do not require a retainer to answer an email.

Where that makes sense, yes. For content that changes often we build in a content management layer. For content that changes twice a year, a CMS is usually more overhead than it saves and we will tell you so.

Get in touch and we will fix it. Where it matters, we put monitoring in place so we often know before you do. We run our own uptime monitoring product, so this is not a hypothetical interest for us.

We build the technical foundations: server-rendered pages, metadata, structured data, sitemaps, internal linking, and speed. Ongoing SEO is mostly content and links, which is a different discipline. We will be straight about where our work ends rather than charging you for something we are not best placed to do.