Website creation, redesign and migration; custom applications

We begin with your offer, your users’ tasks and existing tools. The benchmark compares businesses in your market and journeys solving a similar problem: finding a service, requesting a quote or following a case.

Compare competitors’ offers and your customers’ searches

The benchmark examines offers, publicly available prices, evidence, content and ease of contact. We look for what visitors are missing and what specific information your business can provide. Competitors’ copy and visuals are not copied.

Keyword research then starts from your services: the need expressed, urgency, relevant location and search intent. We distinguish a service request from a simple information search, then group topics to avoid several pages competing for the same need. Website data and research tools inform priorities; no volume or ranking is assumed.

Choose the pages, evidence to present and actions to measure

You approve the proposed structure, services to present, available evidence and expected action on each page. Qualified enquiries, appointments or sales then provide reference points. The quote specifies the study’s scope, markets and deliverables: an in-depth analysis of several countries is not implicitly included in a standard website build.

• Help your customers understand, choose and take action.
• Reduce duplicate entry and enquiries lost between your tools.
• Track useful contacts, sales and time actually saved.

An ageing website can conceal several different problems: a difficult-to-understand offer, an overly demanding form, a catalogue that is cumbersome to maintain or a quote lost in an inbox. We identify the obstacle before choosing whether to improve a few pages, redesign the website or develop a new feature. A business already receiving the right enquiries does not necessarily need to change technology.

The starting point is concrete: who uses the website, what task they need to accomplish and what currently prevents them. We also examine the work your team performs afterwards. A successful appointment request must reach the right person with the necessary information and a comprehensible response for the customer.

You therefore receive a prioritised scope: what must work in the first version, what can follow and what an existing tool already covers. The industry pages give examples of journeys adapted to different businesses.

Create a website or improve existing pages and journeys

Professional website creation organises your offer, evidence and enquiry process. Redesigning an existing website improves journeys while accounting for content, links and pages already attracting visitors. A WordPress redesign is one option among several, suitable when that tool meets your needs.

Change CMS or create a feature for your customers

CMS migration prepares the transfer of available content, products and features. A custom web application addresses needs such as a customer portal, configurator or case tracking with several roles. An online shop adds specific requirements: catalogue, payments, stock, delivery and returns.

Connect the website to your CRM and other software

The work may include software integration, a CRM and automation, or artificial intelligence features. Each connection has a defined purpose, an owner and error checks.

Sell products or present a campaign offer

E-commerce website creation prepares the catalogue, variants, payments and delivery rules. Landing page creation organises a specific offer with evidence, an appropriate form and monitoring of enquiry quality.

WordPress, WooCommerce, Shopify, PrestaShop, Drupal, Webflow or Wix may be considered according to the project. Their versions, subscriptions, extensions, export capabilities and data access determine feasibility. Custom development may also be appropriate, for example with a React interface and Supabase database. This list opens up choices; it does not mean every feature transfers automatically.

On a small screen, scroll the table horizontally.

A CRM tracks sales relationships. A CMS organises website content. A database stores an application’s information. These functions may be combined in certain products or connected across several tools, but they do not simply replace one another.

Imagine a distributor of professional equipment. Its website presents a PDF catalogue and asks every visitor to call. Employees then copy contact details into a spreadsheet. The priority is to let customers find a reference and send an actionable request without immediately building a complete online shop.

A first version can retain the CMS, structure product pages and create a selection of references to attach to the form. Visitors indicate quantities and timing constraints. A connection sends the request to the CRM, assigned to the right salesperson. The customer receives a confirmation whose content and deliverability must be tested.

If volume warrants it, a second stage adds a business portal with documents, history and authorised prices. Access rights then become central: one customer must never see another’s terms. Online payment is added only when commercial and logistical rules are ready. This fictional scenario shows how to allocate investment around verifiable uses.

A difficult-to-use catalogue does not automatically justify replacing the whole website. For the fictional distributor above, we can compare two approaches using the same tasks: improve the current CMS or create an application connected to the catalogue. The decision rests on what customers and the team can accomplish, then on each solution’s operating cost.

Here is an example assessment sheet the scoping phase may produce. Answers are established during the study; they do not describe validation already performed for your business. Tests use representative references, including variants, an unavailable reference and different customer permissions.

On a small screen, scroll the table horizontally.

The first phase can retain the public website and add only the missing feature

If administration works well and the main shortcoming is selecting references, a limited module may be sufficient. If orders depend on contractual prices, successive approvals and multiple warehouses, a separate application becomes an option to quote. A React interface and Supabase database are among the possibilities; their value must be demonstrated by these needs, not their names.

The decision document compares the two solutions: implementation, data transfer, subscriptions, hosting, maintenance, access management and exit options. It distinguishes confirmed information from points still requiring tests. A significant export or connection limitation therefore emerges before commitment to full implementation.

What you approve before development

Scoping included in the quote may deliver this completed assessment, a mockup of the main journey, first-phase and deferred features, and acceptance criteria. You can decide on each feature while understanding its purpose and cost. A prototype helps decision-making; producing it does not yet mean opening the service to the public. See also our custom web application service and checks to plan when changing CMS.

We suggest selecting one main objective and a few control indicators. For a service website, this may be the number of enquiries genuinely matching your offer, then the proportion becoming quotes and customers. For a shop, we examine purchases, cancellations, margin and acquisition cost. For an internal tool, processing time and error rate are often more informative than login counts.

Before launch, we define the reference period, events to measure and the person responsible for recording sales outcomes. Technical tracking alone cannot tell whether a prospect signed. The CRM or a record maintained by the business connects an enquiry with its outcome using explicit attribution rules.

ROI is calculated from additional gains reasonably attributable to the project, minus its costs, divided by the investment. Costs include implementation, subscriptions and management time. Revenue alone is not profit. The comparison accounts for seasons and campaigns; it guarantees no automatic increase.

Scoping describes audiences, content, screens, integrations and acceptance criteria. We then validate the main journeys using a mockup or accessible first version. You can check wording, photos, understanding of the offer and the placement of each action before the entire website is populated.

Acceptance testing follows real situations: sending an enquiry, finding a confirmation, editing a page, buying a product or accessing a document. We also test errors: a missing field, declined payment, expired login or unavailable external service. A success message must not conceal an unrecorded enquiry.

Planned checks cover mobile display, keyboard navigation, relevant performance, forms and access. Content intended for Google must be accessible and properly linked. For an existing-site project, important old URLs, their destinations and rollback options are prepared before the change. You receive a record of checks and any remaining issues.

The published standard starting prices are €290 excluding VAT for a simple brochure website without administration, €590 excluding VAT for a CMS website or standard redesign, and €990 excluding VAT for standard e-commerce, according to the scope described on the pricing page. A complex migration, customer portal or custom application receives a separate quote. Page count alone does not trigger an automatic surcharge.

Business rules, data transfer, external connections and required tests are among the factors determining effort. The quote distinguishes features, client-supplied materials and operating costs: hosting, licences, transactions, API usage or AI services, depending on the project.

You register, pay for and renew your domain name through your own account; Gloria can perform the initial connection. You can purchase hosting yourself or entrust it to Gloria under a defined option. Maintenance, backups and post-delivery interventions are specified separately, along with access and documentation to hand over.

Launch makes the journey available; it does not create commercial demand on its own. Digital marketing then organises how to attract the right visitors, persuade them and track results. A UX audit can explain recurring abandonment; campaign management connects an acquisition budget with suitable objectives and pages.

Improvements are prioritised from evidence. If visitors understand the offer but wait days for a response, speeding up sales follow-up may be more useful than redesigning the homepage. If enquiries are plentiful but poorly targeted, we examine targeting and the information given before the form.

To present your project, provide your current website, the action you want to make easier, the software used and difficulties encountered. A few concrete examples of enquiries or tasks are enough to prepare a useful discussion. Credentials and confidential documents will be exchanged through an appropriate channel.

For a regulated profession, scoping also identifies the rules applicable to the profession and target countries: service presentation, titles, advertising, contact and data processed. Necessary approvals are defined with you; technical website creation does not automatically constitute legal or professional-ethics approval.

Must we leave WordPress to have a modern website?

Not necessarily. The choice depends on expected features, existing constraints and how you publish. A targeted improvement may be enough. If limitations are structural, we compare redesigning in place, another CMS and a custom solution.

Can we keep part of the website and add an application?

Yes, where the architecture allows. A customer portal or configurator can complement the public website. Connections, user accounts, exchanged data and responsibility for each component must be defined.

Can existing AI products and services be integrated?

Yes, after checking their usefulness, access terms and cost. The project can connect an existing service rather than rebuild everything. Information sent, permissions, errors and human approval are planned during scoping.

How will I know whether the investment is profitable?

We define a baseline, monitoring method and review at an appropriate interval. Useful contacts, sales, margins or time savings are compared with project costs. Available data and external factors sometimes limit precise attribution of the result.