Implementation
UI and trust refresh
A new design for one existing page, on desktop and mobile, with organised content and development notes.
Ongoing support / Product Design · Frontend coordination
VAT-exempt under section 19 of the German VAT Act
Design implementation support
Your developers are implementing an approved design. We compare two interim versions with the design and discuss agreed implementation questions.
US$1,349.00
Total price · one-offVAT-exempt under section 19 of the German VAT Act
- An approved design with up to five screens or states
- One development team and a provided staging environment
- One handover check and two consolidated design-to-implementation reviews
Your enquiry is non-binding. An order is created only when you accept our quotation .
Image 1 of 4
Service scope
Your result
- Documented comparison of two implementation versions with the design
- Decision guidance on differences and answers to agreed implementation questions
Included
- An approved design with up to five screens or states
- One development team and a provided staging environment
- One handover check and two consolidated design-to-implementation reviews
- Written clarification of up to ten specific implementation questions within four weeks of the agreed start
- Documented differences, decision guidance and one written follow-up round about the results
Excluded
- No code development or production-system changes
- No on-call availability, SLA or unlimited questions
- A design package's normal handover and follow-up round remain included there
- Reviews already included in frontend optimisation are not offered again
Which projects does this service suit?
Suitable if …
- Your existing team implements the work and needs additional design support.
- Design and review versions can be supplied within the agreed period.
Not suitable if …
- You want to commission code development or complete project management.
- No agreed design exists, or you need ongoing on-call service.
Possible overlaps with: UI and trust refresh, Frontend optimisation. If you enquire about these services for the same project, we check for duplicated work before commissioning. Your selection also shows a notice.
What this covers
Why does the developed website look different from the design?
The test version lacks an error message from the design, and navigation shifts on a phone. We compare implementation with the approved design and clarify differences with your development team.
Design implementation support compares an approved design of up to five screens or states with two intermediate staging versions. One handover check and written clarification of up to ten specific implementation questions within four weeks form the agreed scope.
Assess differences by their significance for use
Not every difference matters equally. Slightly different spacing differs from a missing error message or inaccessible button. The review connects observed implementation with design intent. Development receives documented differences and decision guidance rather than taste-based judgements.
Support requires an identified development team, accessible staging and two agreed checkpoints. It includes neither code development nor production changes. A design package's normal handover and follow-up remain included there; additional reviews are separate. Already agreed frontend optimisation checks are not sold twice.
Does this sound familiar?
Development interprets details differently
The design shows a completed form; development asks about its error state. We collect such open implementation questions against the approved design and clarify them in writing.
The staging page differs from the design
In staging, explanatory guidance appears below the button; the design places it before. We compare implementation with the approved version and identify which differences change interaction.
Questions are scattered across channels
A comment is in Figma, a decision in chat and a question in a ticket. Consolidated reviews bring relevant points into one documented state.
How we approach it.
Define the approved version and questions
We define which screens or states and staging version to review. The approved design is the basis. A new design is outside this comparison.
Compare handover and staging
The handover check and two consolidated reviews compare the approved design with staging implementation. For each issue, we record whether the team needs to clarify a decision or correct a difference.
Record clarifications in writing
Within the agreed period, we answer up to ten specific implementation questions in writing. The final follow-up round concerns the result. Code changes and production-system access are excluded.
After handover
Link documented differences to development tickets. The next review can then identify which design version a decision refers to. Normal design-package handover and follow-up, and already commissioned checks, remain included in their existing scope.
Record a process we can reproduce: which page do you open, what do you click and what happens next? For operational questions, name the tools used and describe how changes reach the server.
Passwords, repository tokens and production data must not be included in the enquiry. We agree required documents and suitable access separately.
Terms used in this service
What does that mean?
- Handoff
- Transfer of the design to development. Alongside views, the team needs guidance on interactions, error states and decisions behind the design.
- Design comparison
- Comparison of the approved design with the development version. Differences are documented at the relevant location and assessed by their significance for the task.
- Staging
- The test environment where we review development progress. Each comparison needs a clear version and a statement of which functions are already implemented.
Before your enquiry
Questions about the offer.
What is included, what do you need and what happens after your enquiry?
The process in detail →Do you code missing parts?
No. Support documents differences and clarifies agreed implementation questions. Your development team changes the code. Technical implementation by us would require a separately defined commission.
Does normal design handover now cost extra?
The handover and follow-up already included in a design package remain part of it. This support covers additional, expressly agreed reviews during development. Identical work is not offered again.
Can we ask unlimited questions throughout development?
The package covers up to ten specific written implementation questions within the agreed four-week window and two reviews. It is not an open-ended support allowance and includes no constant availability.
Do we need an approved design already?
Yes. Comparison needs a shared basis with up to five screens or states. While the fundamental design is still being developed, design work is the suitable service. Implementation support cannot replace a missing design decision.
How do the two reviews work?
Reviews are consolidated around the supplied staging environment and agreed design version. Relevant differences and questions are recorded in writing. This creates a traceable overview rather than unlimited spontaneous individual reviews throughout the project.
What counts as a specific implementation question?
A question should concern an identified location or state within the agreed scope. For example, information order or intended interaction can be clarified. An entirely new function or page type is not one small follow-up question within this framework.
When does work begin?
Four weeks from the agreed start. The two reviews and required intermediate versions are scheduled before commissioning.
Which access is needed?
An approved design with described states An identified development team and accessible staging Two agreed checkpoints within the four-week window Credentials must not be included in the enquiry. Details are agreed only after written commissioning.
What happens after handover?
One written follow-up round is included. The service scope lists the analyses, designs or technical changes covered by the package. We agree additional work with you before it begins.
Read more on this topic
AI prototype before launch: what a focused check can do
What must work before the first use? Review a user journey including failure cases and record which technical questions remain afterwards.
Read the guide ↗Related services
These may fit too.
Implementation
Frontend optimisation
Up to three agreed changes to your existing frontend. We work in a test environment and document the results.