Send the brief. Get a written scope.

Use the form below, or email us from the address in the contact panel. A consultation request goes through the same form. Write a few lines about the problem. That is enough to start.

What to include

• The problem, in your words. What happens today and what should happen.
• Who uses it. Staff, customers, suppliers, how many roughly.
• What it connects to. Existing systems, accounts, payment providers.
• A date, if one matters, and what causes it.
• A budget range, if you have one. It is optional. We use it to propose a scope that fits.

You can leave out the technical details. We ask for them if we need them.

What happens next

1. We read it. A person reads the brief, not a script.
2. We reply in writing with questions and, if it makes sense, a proposed first step. A call is optional and scheduled inside hours that suit both sides. Our team works in GMT+7.
3. We send a written scope when the picture is clear: features, milestones and an estimate in USD. You decide whether it matches your problem.

If custom software is not the right answer, we say so and point to a cheaper route.

Before you write

• Confidential? Ask for an NDA in your first message. We sign before you send details.
• Not sure which service? See custom software development for the overview, or how we work.
• Need people, not a project? See hire dedicated developers or staff augmentation.
• Want proof first? See the work page.

We do not publish a price list. No two builds match, so the estimate follows the written scope.