Technology · Websites and E-commerce

A site your team can manage, Google can read and your customer can buy from.

Corporate sites, online stores and bespoke platforms, built from the content out and with the performance budget fixed before the first screen.

Let's talk

Why so many new sites sell less than the old ones

Most website projects start with the screen: a visual proposal, three rounds of opinion, and only then does someone ask what the site has to do. Content arrives last, measurement never arrives, and the migration loses half the organic traffic that took years to earn.

And the site gets stuck: every change is a request to the agency, every campaign a new landing page, every integration a patch. By year three nobody wants to touch it.

We start with the architecture: the content map, the URLs, the data model and what will be measured. Design comes after, and arrives at a problem already solved.

We build on a design system in code and a CMS the team edits without calling us. And we launch with the redirect map done and traffic measured before and after, so the new site inherits what the old one earned.

Websites and E-commerce Platforms

What goes into a Jelly website

Corporate websites

Content structure, design system, editable CMS and technical SEO from the start. In Next.js with Payload, or in WordPress when that is what the team already knows.

E-commerce

Shopify, WooCommerce or headless, depending on catalogue and operations. A clean product feed, a measured checkout, invoicing and stock connected.

Bespoke platforms

Customer portals, configurators, online auctions, bookings. When the off-the-shelf product forces the business to bend to fit.

Design system in code

Reusable components, typography and colour as variables. A new landing page takes hours, not weeks.

Measurement from day one

Events, consent and conversions defined before opening. A site without measurement is an expensive brochure.

Compliance

GDPR, cookies and terms with Iubenda, of which we are certified partners. WCAG accessibility from the first component.

Performance

A budget fixed before the first screen and Core Web Vitals measured on real users, not in a lab.

WCAG 2.2 accessibility

Audit, fixes and an accessibility statement, at level AA, with the European Accessibility Act in force.

Migrations without losing traffic

URL inventory, 301 redirect map, titles and structured data preserved, before-and-after measurement.

JellyCARE

After launch: daily security checkup, updates, backups and a monthly report. No lock-in.

How we work

How a site gets made here

  1. Architecture

    Two to three weeks: goals, audiences, content map, URLs and data model. Out comes a document that stands on its own, even if someone else builds the site.

  2. System

    Design system in code and a fixed performance budget. The first approved screen is already code, not a picture.

  3. Build

    Weekly deliveries in preview. The client watches the site grow and loads content while it is built, not at the end.

  4. Launch and migration

    Redirect map, before-and-after measurement, and a close watch for the following four weeks. Then JellyCARE, if you want us to keep looking after it.

Is your site working for the business, or the business working for the site?

Send us the address. We answer with a free technical reading: performance, SEO, accessibility and what we would change first.

Start a conversation

Frequently asked questions

What technology do you build in?

Whatever the project calls for. Corporate and content sites in Next.js with Payload CMS, or in WordPress when the team already knows it. Stores on Shopify or WooCommerce, or headless when the catalogue and integrations justify it. This site is Next.js, Payload and Vercel.

How long does a website take?

A corporate site, eight to twelve weeks from architecture to launch. A store, twelve to sixteen. A bespoke platform is scoped during architecture. What delays most is not the code: it is the content, which is why it starts in week one.

How much does it cost?

It depends on what it has to do, which is why we start with a fixed-price architecture phase. At the end of it there is a scope, a plan and a budget that does not change halfway.

Can my team edit the site on their own?

Yes, and it is an acceptance criterion. We hand over with the CMS configured, recorded training and components that do not break when someone changes a text.

Will I lose Google rankings with the new site?

Not if the migration is done properly: an inventory of the URLs that bring traffic, a 301 redirect map, titles and structured data preserved, and before-and-after measurement. It is the fourth phase of the method, not an extra.

Is accessibility mandatory?

For the public sector, for years. For the private sector, the European Accessibility Act has applied since June 2025 to e-commerce, banking, transport and other services. But beyond the law, it is a share of customers who cannot buy from you today.

What is JellyCARE?

Jelly's active, preventive maintenance plan for websites: daily security checkup, theme and plugin updates, uptime monitoring, broken links, database optimisation and a monthly report. With daily cloud backups on the Plus plan. No lock-in: if you do not like it, you cancel.

Do you do this on sites you did not build?

Yes, and often. We audit, fix and maintain sites on WordPress, Shopify and other platforms, built by other teams.

Do you do design only, or development only?

We do both, and that is how we work best. But we build from third-party design, and design for in-house technical teams, when that is what makes sense.

After launch

A published site is a site to look after.

JellyCARE is the plan that keeps the site standing after we leave: daily security checkup, updates, uptime monitoring, backups and a monthly report. On sites we built and on sites built by others. No lock-in.

See JellyCARE