Skip to content
Perrine HonoréPerrine Honoré · Websites & web apps

Custom website and web application development

In short

I build custom websites and web applications in React and Next.js: marketing sites, business platforms, e-commerce. No purchased theme, no page builder: code written for your requirement, fast to load and built to be found. A marketing site ships in 1 to 3 weeks, a web application in 6 to 12.

Discuss my project
Book a free call30 minutes · No commitment

At a glance

Technologies
React, Next.js, TypeScript, Node.js, PostgreSQL
Project types
marketing site, business platform, e-commerce, client portal
Timeline
1 to 3 weeks for a marketing site · 6 to 12 weeks for an application
Performance
Core Web Vitals handled during development, not after
Search
structure, structured data and server rendering built in from the start
Deliverable
full source code, hosting in your name

How the project runs

  1. First conversation

    Through the form or a free 30-minute call. You describe your need, I ask my questions and tell you frankly whether I'm the right person to build it.

  2. Scoping: scope, budget, schedule

    I put in writing what will be delivered, what won't, the budget and the schedule. The main screens are approved with you before development. The quote covers that written scope.

  3. Design and development

    The software is built in steps, with regular demos: you test progress as it happens. Any out-of-scope request is priced and approved in writing before it starts, never billed afterwards.

  4. Testing, launch and handover

    You have 7 working days after delivery to report a defect or a mismatch with the scope. Then launch, and handover of the code and access on your own accounts.

After delivery

Defect fixes
30-day warranty after delivery on critical and blocking defects in the delivered code.
Maintenance
Optional, as a monthly package defined in the quote. With an active contract: critical outage handled within 24 working hours, non-blocking defect fixed within 72 working hours.
New features
Each new feature gets an additional quote or amendment, approved before work starts.
Hosting
On your infrastructure or mine, your choice; terms are set out in the quote.
Code ownership and access
The code built for you is yours once fully paid, stored in your own space (e.g. your GitHub account). No technical or contractual lock-in.
Switching provider
You can hand maintenance or new work to someone else at any time: I create no deliberate dependency.

Full details are in the terms and conditions.

Frequently asked questions

How long does it take to build a website?

A marketing site ships in 1 to 3 weeks. A web application: client portal, business platform, e-commerce with specific requirements, takes 6 to 12 weeks. The gap is explained by the number of distinct user journeys and by integrations with existing systems.

Why not use WordPress or a page builder?

For three static pages, they're often the right answer and I'll say so. They stop being the right answer when the site carries something at stake: unused code slows loading, the structure resists change, and plugin dependencies become a maintenance and security cost.

Is search optimisation included?

The technical foundation is: server rendering, metadata, canonical URLs, structured data, sitemap, and Core Web Vitals. These are far cheaper to build in than to retrofit. Content strategy and link acquisition are a separate discipline, and I don't sell them.

Can you redesign a site without losing its search traffic?

Yes, provided it's prepared: a full inventory of existing URLs, a 301 redirect from each old URL to its real equivalent, never all to the homepage, and a position benchmark recorded before launch. Without those three, a redesign can lose a substantial share of its organic traffic.

Who hosts the site once it's live?

You do, on your own account, with the source code handed over. Hosting in your name looks like a detail until the day you want to change provider or work with someone else, at which point it is the only thing that matters.

Custom or template: where the real difference sits

A site built on a theme and a page builder ships fast and costs little. The trade-off usually appears later, in maintenance and flexibility: code you did not write and have to understand before changing it, and a chain of plugins to keep current. If your need fits inside that, it is a good choice, and I will tell you so.

Custom isn't justified for everyone: if three static pages are enough, tell me and I'll say so too. It becomes justified as soon as the site carries something at stake: a conversion funnel to optimise, business data to handle, search visibility to win in a competitive market, or a requirement that will keep evolving for years.

Speed and search, handled during the build

A slow site loses visitors before it is read, and Google knows it: Core Web Vitals are a ranking signal. These constraints are far cheaper to respect while building than to retrofit afterwards: which is why they are part of the work, not an optimisation package sold separately.

Concretely: server-side rendering so the content is readable by a crawler without executing JavaScript, images converted and sized automatically, self-hosted fonts, schema.org structured data, consistent metadata and breadcrumbs, and an automatically generated sitemap.

What a web project actually covers

Beyond the pages themselves, a serious web project includes the parts that decide whether the site stays alive: a content structure your team can actually update, analytics that answer a real question rather than filling a dashboard, and legal compliance, consent, privacy policy, terms, handled before launch rather than after a complaint.

Hosting stays in your name, on your account. It's a detail until the day you want to change provider, and then it's the only thing that matters.

Redesign: the case that needs the most care

A poorly prepared redesign can cost a significant share of organic traffic; a well-prepared one can improve it. The difference isn't the budget, it's three precautions taken before launch: inventory every existing URL, redirect each of them to its real equivalent, and record current search positions so what moves afterwards can be measured rather than guessed.

When another solution will fit better

  • Projects without a decision-maker. If every page needs three approvals, the announced timelines won't hold.
  • Taking over undocumented code without an audit phase. On legacy work, no timeline commitment before a prior audit.
  • Design without development, and search work without development. I build what I design.
  • Content writing. I build the structure that makes content findable; I don't write your copy.

Let’s talk about your project.

Describe what you need in a few lines: I reply within one working day. Prefer a call? It's free and with no commitment.

Prefer to talk it through?

Book a free call30 minutes · No commitment

Required fields. Everything else is optional.

A few lines are enough: who it's for, what it should do, and what already exists.

Optional details

Reply within one working day. Your details are only used to reply to you (privacy).