Confirmation, then a considered reply
Enquiries are reviewed on business days. Complex briefs take longer to answer properly than simple ones, and we'd rather send one considered reply than three holding emails.
Tell us what you're trying to build or fix. A written description is more useful than a call at this stage, because it lets us come back with a specific response rather than a list of questions.
Your goal in a sentence or two. Who the users are. What exists today, including any design files or codebase. Your deadline. Your budget range.
The last two are optional, but they change the answer substantially — and clients who include them get a usable reply faster. If you don't know the budget yet, say that. It's a normal answer, and we'll scope to a phase instead.
Duova LLC (Webu) works across web development, e-commerce builds, mobile applications and UX/UI design. Naming which of those you need in the first line saves a round of clarification, especially if the answer is more than one.
Duova LLC is registered in Georgia under registration number 402381025, with clients across Singapore and the wider region.
The form takes your name, email, company and a description of the project. Keep it short if you like — we'll follow up with questions. Nothing here is processed by a payment system and there is no checkout involved. Submitting it does not create a contract or an obligation on either side. It starts a conversation.
A short note is enough to start. If your project spans web development and a mobile app, say so — it changes how we sequence the work.
This is the fastest route for anything with attachments: design files, specifications, existing site URLs, tender documents.
Replies come from a person who'll work on the project, not a shared inbox.
If you'd rather talk first, include a phone number and a window that suits you. Singapore clients get overlap hours in the morning and afternoon. We'll confirm a time rather than call cold.
For projects already in progress, your project contact handles scheduling directly.
You'll get a confirmation that the enquiry arrived, then a written response. That response will either be a set of clarifying questions, a proposed scope with a price, or a straight answer that we're not the right studio for this. All three are real outcomes.
Enquiries are reviewed on business days. Complex briefs take longer to answer properly than simple ones, and we'd rather send one considered reply than three holding emails.
We don't run automated nurture sequences. If we can't help, we'll say so once and leave it. If we can, the reply names the next step and what we'd need from you.
If something is genuinely urgent, say so in the subject line and we'll prioritise it. That is the one shortcut we offer — no queue-jumping forms, no priority tiers.
Short answers to the things clients ask before sending a first brief.
Check the FAQA goal, the users, what exists today, and your deadline. Budget range helps but is optional. If you have design files, a codebase, or a live URL, attach or link them — it saves a round of questions.
Yes. Singapore clients get overlap hours in the morning and afternoon, and we confirm calls rather than ringing unannounced. Written updates cover the rest of the week so nothing depends on a single live call.
No. There is no checkout, no payment step, and no contract created by submitting. It starts a conversation, and either side can stop after the first reply.
That is common. Send what you have and we will scope a first phase — often research and UX/UI design — before any build work is committed to.
If the brief is not ready, read how the studio runs a project or look at recent work first. Both pages explain the shape of a build, so the first message you send can be shorter.