07
TL;DRA translation order has many questions before work starts → five steps on the site with the exact sample, language and speed, priced before payment → paid orders land in the translators' Telegram, exactly once.
Live site- Role
- Designer and full-stack developer
- Client
- Dokee · Kazakhstan and Ukraine
- Year
- 2025–2026
- Stack
- Next.js, React 19, TypeScript, MongoDB

In one paragraph
A fixed-price translation service for personal documents: a five-step order wizard with exact samples, three speeds with guaranteed times, and an admin where the owner sets every price. Customers order and pay without a conversation, and the owner changes prices, limits and documents without a developer.
Context
Dokee translates personal documents from Kazakhstan and Ukraine: passports, certificates, diplomas and apostilles, at a fixed price.
Problem
Every order needs the document type, the exact version of it, the language pair and a deadline before the price is known, and the team can only take so many urgent jobs a day.
What I did
- 01
Five steps
Country and document, the exact sample, language and speed, photos and the names in Latin letters, then the total and payment.
- 02
The exact sample
An old passport and a new one are different jobs, so the customer picks the sample that matches theirs and the price is fixed before paying.
- 03
Speeds with limits
Next morning, the same day or 2–3 hours, each with a delivery time in Astana time and a daily limit the owner sets.
- 04
Orders that arrive once
Photos are compressed in the browser and uploaded straight to storage; paid orders go to the translators' Telegram with a lock against duplicates.
- 05
One app
I later moved the separate Express backend into Next.js route handlers, so the service runs as one app on Vercel.
Results
5
steps from document to payment
7
language groups, each with its own prices
3
speeds with guaranteed times and daily limits








Stack
- Next.js
- React 19
- TypeScript
- MongoDB
- MUI
- Vercel Blob
- Vercel