Common situations and how we handle them

Version: 1.0.0
Table of contents

Scope changes

Scope changes happen when the task grows after the start (new pages, new animations, more languages, extra integrations). We keep quality high by separating “included work” from “additional work”.

Rule
If a change affects time, complexity, or deliverables, it becomes a new item with a separate estimate.
+ new section / page + new language + extra integrations + new design direction

Missing assets

If key assets are missing (logo files, images, product data, copy, access), we can still move forward with placeholders — but final quality depends on real materials.

What we do
Use placeholders to keep structure moving. Mark missing items clearly and provide a checklist.
What you do
Deliver final assets in agreed format (PNG/SVG, 2x images, copy text, links, credentials).
Quick checklist
  • Brand: logo, colors, fonts
  • Content: headings, descriptions, CTA labels
  • Media: images in high resolution
  • Access: admin panels, integrations, DNS/hosting

No access / blocked accounts

If we don’t have access to your platform or your account is blocked, we switch to a safe delivery mode: copy-paste blocks, export files, and step-by-step implementation instructions.

Safe delivery
You keep control. We deliver everything ready for installation without requiring admin access.

Revisions and approvals

Revisions are normal. The best workflow is clear approval checkpoints: confirm layout, then content, then details. This prevents endless loops and keeps the final build consistent.

Checkpoint 1: structure
Spacing, hierarchy, responsiveness, overall layout.
Checkpoint 2: content
Text, links, language, assets, SEO basics.
Checkpoint 3: polish
Micro-animations, hover states, edge cases.

Timeline shifts

Timelines shift when assets arrive late, feedback is delayed, or scope changes. We keep the project stable by updating milestones and prioritizing what must ship first.

Shipping priority
Launch-critical → customer-facing quality → enhancements. Optional features can be shipped in a later iteration.

Quality expectations

VITON13 aims for premium delivery: clean UI, consistent typography, stable behavior on all devices, and maintainable code. If the input references require “pixel-perfect”, we build around exact spacing and interactions.

  • Responsive: desktop, tablet, mobile
  • Performance: optimized images, minimal overhead
  • Safety: scoped CSS/JS, no global conflicts
  • Consistency: same tokens, same patterns across pages
Was this page helpful?