Digital tourism service for a team in Moscow
Booking platforms for tours, stays, activities and transfers with payments and partner accounts.
Delivery focus: Align roles, data and ownership across several participants.
What we discuss first
customer journey, booking, content, languages, payments, roles and freshness sources.
What we accept in the result
search or catalogue, key booking path, notifications and content administration.
Boundaries and dependencies
freshness of external offers, suppliers and payment terms need separate agreement.
Web project coordination in Moscow
For a web project, we confirm the visitor journey, content and next action; city coordination helps agree materials with the team in Moscow. Remote sessions follow Moscow time, UTC+3. Delivery is remote; OTON does not claim an office, employees or local representation in this city.
Brief prompt
Who decides, provides data and approves the result?
Hand-off check
Confirm roles, access, data flows and acceptance criteria.
Offer geography
Before work starts, we confirm whether the offer is intended for Moscow, Russia or several markets. This affects language, form fields, required information, analytics and campaign settings; no unsupported local promises are added.
Local delivery context
If the site collects data through forms or an account, discovery records the fields, processing purpose and decision owner; the customer or its counsel confirms the applicable requirements. Официальный интернет-портал правовой информации.
City context
Moscow's official programme describes mos.ru as a unified portal for city authorities, services, guidance and official enquiries. Discovery separately records the user journey, identity step, required information and hand-off from the interface to the accountable process. Acceptance checks journey clarity, statuses, accessibility and correct enquiry completion, not only page appearance. Official portal of the Mayor and Government of Moscow.
Question before the brief
Can it launch for one destination? Yes, to validate demand and process before expansion. Can approval be split across teams? Yes, with an owner defined for every decision.