Pascal DegutProduct & e-commerce Book a call
>

Home Product and web applications Web application

A web application written before it is coded

Business tool, back office, dashboard, prototype to put in users' hands. The project starts with usable documents (specs, Figma mockup, Linear backlog) and ends in production, with one point of contact in between.

Book a 15-minute call See pricing
15 mindiscovery call,
free, no obligation to continue
from €8kmockup, artefacts and specs,
deliverables are yours to keep
from €20kfor the full implementation,
through to production
1single point of contact,
from scoping to production
What it really costs

Agency, contractor, fixed price. What actually changes.

For an equivalent scope, here are the orders of magnitude on the French market and what you pay here.

Agency or IT services firm
€50k to €150k, 6 to 12 months
  • Three to five people involved, including at least a salesperson and a project manager.
  • You pay for the coordination time between them, not just the code produced.
  • Code often built on an in-house framework or on the agency's infrastructure.
  • A recurring maintenance contract sold afterwards: dependency is built into the model.
Freelancer on a day rate
€500 to €700/day, open-ended
  • The budget risk and the risk of drift stay with you.
  • They build what they are asked to, not what would save budget or time.
  • When you don't know what you don't know, you pay for execution without the advice.
  • No commitment on the result, only on attendance.
Fixed price, here
From €8k for the mockup and specs, from €20k for the full build
  • One person, from scoping to production. No intermediary.
  • Price and date written in the quote. If I overrun, that's my problem, not yours.
  • Documented code, standard stack, in your repository. You own it.
  • No mandatory maintenance contract: you come back if you want to.
Why this is possible

Today's tools have merged the role of the person who scopes and the person who codes. An organisation without that chain bills for three people's coordination to produce one person's work. It isn't bad faith, it is its business model.

The first two columns are orders of magnitude on the French market, given as a benchmark: your situation may differ. The third is the rate applied here.

Process

Write the application before coding it.

Most application projects go off track because development starts on a need that was never fully written down. Here, the first half of the work produces documents, not screens, and you can stop at the end of each phase.

1 · SCOPE Specs and artefacts specification, interactive prototype 2 · DESIGN Figma mockup clickable journey, components 3 · BUILD Cycles and delivery a demo at each cycle
Three phases, each with its deliverable: a document, a mockup, then an application in production.

Scope

A free 15-minute call to set out the problem, the users, the deadline and the budget. Then the creation of artefacts: interactive models we iterate on before committing to the implementation.

Design and break down

The screens are designed in Figma from the approved specification and artefacts, linked together, with every state planned: empty, loaded, error. Once the journey is approved, the scope is broken down into epics and tickets in Linear, each with its acceptance criteria.

Build and deliver

Cycles of one to two weeks, with a version viewable online at the end of each one. Then the move to production on your infrastructure, the handover of access, written documentation and a recorded walkthrough. No mandatory maintenance contract.

Design

Figma, the stage where the design is locked before the build.

Before the first line of code, the user journey is clear and precise. Risks are neutralised, because every important decision was made upstream, when a change still has no financial impact.

Site map and user journey in Figma

The journey first

An interactive prototype to clarify the user journey, rather than pretty standalone pages.

Figma component library

A component library

Buttons, fields, tables: reusable components with all their states, in auto layout. Every iteration builds on the work done upstream.

Screens and components laid out in Figma

Every screen covered

Every screen answers an identified problem, with several variants proposed at the approval stage.

Crypto Excel dashboard: portfolio, summary and transactions

Pixel-perfect build

The components and states approved in Figma are reproduced identically, screen by screen.

A design system from the mockup stage. Colours, typography, spacing and components are defined once, with all their states, then reused on every screen and in the code. The first directions can be explored with Claude Design before being taken up and locked in Figma.

Pricing

2 ways in, one commitment at a time.

The split is deliberate: you decide to build once you know what to build, not before.

To start the project

Mockup, artefacts and specs

from €8,000
fixed price, depending on the number of screens and the complexity of the project
  • Functional specification in Linear (epics, user stories, acceptance criteria)
  • Figma mockup with built-in prototype
  • Interactive artefacts produced with Claude Code

All the assets needed to start development.

Discuss it
Most requested

Full implementation

from €20,000
fixed price, confirmed once the mockup and specs are approved
  • Everything in the standard offer
  • Code delivered to your GitHub repository
  • Supported move to production and handover

Development through to production. A scope, a price and a date written down before we start, and one point of contact from the first call to delivery.

Book a 15-minute call

No VAT charged: VAT exemption scheme for small businesses, art. 293 B of the French General Tax Code.

QUESTION 3 OF 5 Your result Service Budget Timeline
Online questionnaire

Not sure yet which format you need?

Five questions, 20 seconds. You get the service that fits, a budget range and a timeline. No email address asked. The questionnaire is in French.

Take the questionnaire
FAQ

Before we start.

What is an artefact?

An interactive prototype produced with Claude during the discovery phase: a first version of the application that you use, challenge and evolve over a few iterations before moving on to the technical implementation. We approve something that works, not a document.

What does the mockup, artefacts and specs offer include?

The written functional specification, the screen map, the data model, the user journeys with their edge cases, the matching Figma mockup and the project spec written in Linear. It is what a development team needs to start in the best conditions.

Why use Claude to produce the specs and artefacts?

Because the long part of scoping isn't the thinking, it is the write-up: rephrasing, breaking down, checking consistency between the screens and the data model, writing the edge cases one by one. An assistant does that in hours where it used to take days. The trade-offs remain mine, and I review every document before sending it to you.

Can I take the mockup and specs and have it built elsewhere?

Yes, that is even the point of the first offer. The Figma files, the specs and the Linear backlog belong to you. You can hand them to your in-house team, an IT services firm or another freelancer: they are written to be read by someone other than me.

What makes the implementation price vary?

The number of screens, the complexity of the data model, the integrations with your existing tools and the level of requirements on permissions and roles. The 15-minute call gives a first order of magnitude; the exact figure is set once the mockup and specs are approved, before the first line of code is written.

What if the project stops after the mockup and specs?

Then it stops. You have paid for a closed batch and you leave with usable deliverables. That is precisely the point of splitting it: you commit €8,000 to know what you are building, not €40,000 to find out along the way.

Which tech stack?

Standard, chosen so that any developer can take over: TypeScript, a mainstream front-end framework, a relational database, conventional hosting. The code lands in your GitHub repository from day one. No in-house framework, no dependency on a tool only I would know how to handle.

A business tool to build?

Fifteen minutes to set out the problem, the deadline and the budget. If the scope is clear enough to be priced, you receive a proposal within 48 hours.

Book a 15-minute call Write a message