How we work
Doki connects design, development and operations around one project record.
- 01
Scope
We define users, screens, integrations and exclusions together. Acceptance criteria belong to a specific quote version.
- 02
Design
We test the main user flow in a prototype first. Design, content and accessibility feedback is collected by version.
- 03
Launch
Customer approval applies only to the reviewed preview version. Publishing is a separate staff step with recorded outcomes and history.
- 04
Maintenance
Maintenance, modules and security findings have separate records. Applying a fix and verifying it by retest are distinct states.
- 05
Who does what
Design, development, testing and release are Doki's job, and we also prepare the site copy and visuals. Approvals and the necessary access come from the customer; third-party services such as hosting, payments or an ad platform remain the responsibility of their own provider. This split is written into the quote so it does not become a dispute later.
- 06
How decisions are recorded
Decisions made during the project are written into a single project record. A change agreed on the phone or in a meeting is not applied until it is in the record. A request that grows the scope opens a separate change entry, and its effect on time and cost is written down before approval.
- 07
What we do not do
We do not sell ranking or result guarantees. We do not run a security test on any system without written permission and a written scope. We do not use fake reviews, bought links or invented customer examples. The ad budget is paid directly to the ad platform; our fee is for the management service.
Related pages
The team, how we work and the work we have done before.
Let's talk about your project.
Tell us what you need; we will define the scope together.