# Bring us the language constraint.

> Share what you are building, where it needs to work, and what is blocking confidence or release. We will identify the right language, engineering, data, media, quality, and program specialists.

## Context makes the first answer better.

Include the product, model, content, or program involved; relevant languages, scripts, markets, and modalities; the current stage; known quality or engineering constraints; expected deliverables; and the working timeline. Rough information is fine. Admas can help turn an incomplete request into a testable scope.

For a guided start, use the project questionnaire. It keeps the answers in your browser and prepares an email in your own email application. Nothing is uploaded or sent to Admas until you choose to send that message. You can also email services@admas.net directly for service, partnership, media, or general inquiries.

## We route the problem before we quote the work.

We review the intended users, locales, content classes, source systems, model or product dependencies, quality threshold, risk, and timing. That first pass helps distinguish translation from transcreation, post-editing from independent review, linguistic QA from functional testing, and a one-time delivery from an operating program.

Please do not send passwords, access tokens, production credentials, regulated personal data, or confidential source files in an unsolicited first email. Describe the material and its handling requirements first so an appropriate transfer method and access boundary can be agreed. Privacy requests can use the same email address with the subject Privacy request.

## Next step

- [Build a project brief](https://admas.net/start-a-project/)
- [Email services@admas.net](mailto:services@admas.net)