What to expect before, during, and after a Fedrix project
A practical guide to scope, decisions, revisions, deployment, ownership, and handover before starting a Fedrix Studio project.
Scope confirmation
Every project starts by confirming the business context, service fit, deliverables, timeline, decision-maker, and input materials.
Concepts and revisions
A revision round is one consolidated list of feedback applied to the approved direction. It does not include a new concept, strategic direction, page, or feature.
Client content responsibilities
Clients normally provide final business facts, service information, legal text, approved photography, testimonials, product data, and required account access.
Milestones
Default milestones are scope and inputs confirmed, direction approved, coded structure and visual preview, content integration and QA, final payment, launch, then handover.
Code-first workflow
Fedrix designs and develops websites directly in code after the core brand, positioning, and content direction is approved.
Basic SEO and QA
Basic SEO, semantic structure, responsive review, current-browser checks, keyboard behavior, reduced motion, image loading, and console review apply to the agreed pages and features.
Ownership and handover
Client-owned accounts are preferred. Handover may include deployed files, source code, assets, environment-variable list without secrets, deployment notes, and an update guide.
Bug warranty and maintenance
Website Launch packages include a 30-calendar-day bug warranty and a 14-calendar-day complimentary maintenance period covering up to two small content updates or 60 minutes.
Third-party costs
No paid font, plugin, stock asset, API, template, or subscription is charged without written approval.
Portfolio permission
Publication follows an explicit written choice. Fedrix does not publish confidential strategy, unverified results, fake screenshots, or client names without permission.