AE Project brief

Tell us what you're trying to build

Describe it in a few lines: a website, custom software, a WhatsApp bot, an AI assistant. We read it and come back with what we think the work involves. If we are the wrong people for it, we say that too.

Include any system it has to work with. A fuller checklist sits further down this page.

Name, email, what you need and the details are required. We use what you send to reply to you about this project.

Your brief is in. It reached our team with the details you sent. We read it, check scope and fit, and reply to the email address you gave with the next practical step. Continue on WhatsApp hello@alodev.ae

What happens next

  1. 01

    You send the brief

    The form above is all of it. One person reads what you send, and that person is the one who answers you.

  2. 02

    We review scope and fit

    We work out what you are asking for, whether it falls inside a package or needs its own quote, and whether we are the right people to build it.

  3. 03

    We reply with the next practical step

    Usually a direction, plus the questions that decide the price. Sometimes the honest answer is that the project is not ready to build yet, and we will tell you that.

How we handle what you send

  • A person reads the brief and writes the reply. No autoresponder stands in between.
  • An honest read on scope: which of it is a fixed package, which needs its own quote, and which part we would leave for later.
  • You get your answer in writing. If a call would be quicker, we suggest one and you pick the time.
  • Your details are used to answer this enquiry and nothing else.

Other ways to reach us

The same team answers all of them. The form is still the better start for anything with real scope behind it.

Email hello@alodev.ae Best for documents, specs and anything with attachments. Write to us Telegram Message our bot The same capture flow we build for clients, running on our own number. Open Telegram
Before you send

What makes a brief we can answer

None of it is required, and a two-line message is welcome. Cover what you can and our first reply can be an answer instead of a list of questions.

  • What you need built, in your own words
  • The process or problem behind it today
  • Any system it has to work with: a CRM, accounting, an existing site
  • Roughly when you want it live
  • A rough budget, if you have one in mind

Already have something running? Say so in the brief: an existing site, a CRM you will not replace, a half-built system, a spreadsheet the whole team edits. What you already run shapes our answer more than the feature list does, and it is the detail people leave out most often.

Not ready to write a brief?

Read first. These pages answer most of what people ask before they get in touch.