Project brief
Describe the work that needs to change.
Tell us who does the job today, which inputs and systems it uses, the result you need, and what must remain a human decision. Add budget and timing if they are known.
- How replies work
- How replies workWe review the brief and reply by email with questions or a proposed next step.
- Emailinfo@oyu.ml
Send a brief for
- A repeated workflow that crosses inboxes, forms, spreadsheets, CRM, or approval steps
- A website, mobile app, or SaaS product built around one complete user task
- Data cleanup, recurring reports, decision dashboards, or private search over approved sources
After you send the brief
From the current job to a scoped next step
- 01
We check the brief
We identify the user, current steps, systems, required output, risks, and any missing facts.
- 02
We define a first complete scope
If the work fits, we outline the smallest end-to-end result, its boundaries, and the decisions that stay with your team.
- 03
We confirm before work starts
A meeting is used when needed to confirm owners, access, acceptance checks, timing, and commercial terms.
Common questions
Before you send the brief
You do not need a complete specification. A concrete example of the current work and required result is enough to review.

What happens after I send the form?+
The team reviews the brief and replies by email. The reply may ask for missing details, suggest a narrower first scope, or explain that the project is not a fit.
What should I include in the first message?+
Share who performs the work today, the current steps and systems, example inputs, the required output, sensitive decisions, budget range, and target timing.
Can a project cover Mongolian, English, or Japanese users?+
Yes. A project can be scoped for Mongolian, English, and Japanese interfaces or operating contexts, with language-specific content and review responsibilities defined in the work.