The cost of a website project in Paris is rarely just about the number of pages. The real variables are usually the structure, how much content has to be created, whether the site needs to be bilingual, and how much maintenance will be needed after launch.
The main cost drivers
- Landing page or multi-page brochure site
- New site or redesign of an existing website
- Ready-made content or copy that still needs structure
- French only or bilingual delivery
- Ongoing maintenance after launch
A page count is useful, but it does not describe the work inside those pages. A concise service page with approved copy and photographs is different from one that requires interviews, research, writing, image selection and several stakeholder approvals. Navigation also matters. A business with distinct audiences or services needs a structure that helps each visitor reach the right information instead of one long page containing everything.
A simple project can start as a landing page or a small brochure site. For a small business with several services, a stronger structure usually pays off better in the long term. The web development page explains what is included, while the website redesign page covers when an old site should be rebuilt properly.
Content production changes the scope
Ready-to-publish material keeps the project focused on design and development. “We have the content” should mean final text for each page, usable photographs, a logo in an appropriate format and confirmed business details. Notes in emails, old brochures and assorted phone images still need editorial and visual work before they can support a professional site.
Copywriting is more than correcting grammar. The writer must identify what the business does, organise services around customer needs, remove repetition and make each call to action clear. Photography has a similar effect on scope. Existing licensed images can be prepared for the web, while a new photo shoot or extensive image sourcing is a separate piece of work. A quote should say who supplies, selects, edits and licenses the material.
Functions cost more than page labels
A brochure page mainly presents information. E-commerce, booking and reservation systems must also handle user actions, confirmations, errors and business rules. A booking request form is not the same as real-time availability connected to an existing calendar. An online shop adds products, payments, delivery choices, customer messages and an administration workflow. The useful question is not whether the proposal includes a “booking page” or “shop page”, but what the visitor and the owner can actually do.
Bilingual delivery expands the content and quality-control workload as well. Every important page needs adapted copy, matching navigation, language-specific metadata and a clear route between versions. Translation supplied by the client reduces one part of the work, but the developer still has to build and test both structures. If the need is more focused, a landing page may be enough. If the business serves both French and English-speaking customers, the bilingual website page explains what changes in the scoping and structure.
Template, hosted builder or hand-built site
A template or page-builder site is often sensible when the content follows a familiar pattern and the owner values easy visual editing. It reduces design work by starting from an existing system. The trade-off is extra code, dependence on plugins or a theme, and limits that appear when the business later wants a layout or feature the template was not designed to support. Maintenance still matters because the underlying components can change.
A hosted website builder offers an integrated editor, hosting and support under one provider. It can suit a small site that fits the platform’s standard features and whose owner wants to manage it directly. The compromise is platform dependence: exporting the design or moving to another system may be difficult, and specialised performance or technical changes may not be available. The subscription is also part of the ongoing operating cost, not the original build alone.
A hand-built site gives the developer closer control over markup, performance and the exact customer journey. It can avoid unnecessary features and fit a specific brand more precisely. That control requires more design and development work, and the handover must explain how future edits will happen. “Custom” is not automatically better; it earns its cost when the business needs the control, speed or flexibility it provides.
How to compare quotes fairly
Compare deliverables line by line, not just the total. The proposal should identify the pages, functions and language versions included, who provides the copy and images, and how many approval stages are part of the work. Ask whether basic search setup covers page titles, descriptions, heading structure, image text, indexing controls and redirects where relevant. A vague line marked “SEO included” does not reveal what will be done.
Image licensing should be explicit. Confirm whether supplied photos, licensed stock images or newly commissioned photography will be used, and who retains the proof of licence. Also ask what happens after handoff: who owns the domain, code, design files and CMS account; which third-party subscriptions remain; and whether you receive administrator access. The business should not discover after launch that essential accounts belong only to the supplier.
Revisions need boundaries too. A useful quote distinguishes corrections to agreed work from a new page, feature or direction added later. That protects both sides and makes competing proposals comparable. If one quote includes content preparation, migration, accessibility checks and launch support while another includes only assembled pages, the lower total is not offering the same project.
Hosting and maintenance are separate decisions
Launching the site does not end its operating needs. Hosting keeps it online; maintenance covers defined work such as software updates, backups, security checks, small content changes or technical support. Those services should not be bundled under an undefined annual fee. Ask what is monitored, how backups are restored, what counts as a content update and what work requires a separate quote.
A static brochure site may need little technical upkeep, while a plugin-heavy CMS or e-commerce system needs active maintenance. Ownership also affects the choice. Some businesses prefer to request occasional changes; others need staff to edit pages regularly. Deciding that before the build avoids paying for an editing system nobody uses or receiving a site the owner cannot update.
Choose the smallest scope that meets the goal
Start with the job the site must do: establish trust, explain services, generate enquiries, take bookings or sell products. Then list the content and functions required for that job. Optional features can be separated from launch essentials, making the quote clearer without weakening the core customer journey.
The current service levels are published on the pricing page, which is a better reference than an invented universal figure. A clear brief and an itemised proposal will tell you far more than a headline price. The right website is not the one with the longest feature list; it is the one whose content, technology and ongoing responsibilities match how the business will use it.