Frequently asked questions about building a website, an MVP or a SaaS

You talk directly to the person who designs and builds your startup’s website or MVP, from the first call to launch. We build what you need now: no full platform when one page is enough to test the idea.

One person, from design to code. The person you talk to is the one who builds it: nothing is outsourced and nothing gets lost along the way.

No. Startups come first, but we also work with small and mid‑sized businesses and established companies: website redesigns, custom websites or internal tools.

No. You talk about your business and your customers, we handle the tech. Every choice is explained simply, and you see a live version at every step.

Yes. The studio is near Paris and we work with startups and companies across Europe, in French or English.

With the person who designs and builds your project, from the first conversation to launch: no middleman.

No. We focus on websites, MVPs, SaaS and business platforms. It’s what we do best.

By your project, not a price grid: what must exist at launch, the number of screens, the features (accounts, payments, dashboards) and the level of design. You get a clear quote, and the signed price doesn’t move.

There is no single rate: the price of a website follows the number of pages, the level of design, the features (forms, user accounts, connected tools) and the work on the content. A showcase site of a few pages takes far less than a site with a client area. Describe your project in the configurator to get a first estimate, then a clear fixed‑price quote.

There is no single rate: the price follows the number of pages and page templates, how much of the existing site is kept, the state of the content, the level of design, the features and the migration of old addresses. The more solid the base, the less has to be rebuilt. Describe your site in the configurator to get a first estimate.

The price mainly depends on the number of screens and user roles, payments or subscriptions, connections to other tools and the level of design expected. We start with the useful essentials, then the product grows step by step. Describe your project in the configurator: you get a first estimate within 48 business hours.

It depends on the stage and scope: a validation landing page takes far less than a full website or an MVP. After a first call you get a clear quote (scope, fixed price, timeline), and we tell you honestly if a simpler version is enough to start.

Nothing formal. A few lines about your idea, your customers and your deadline are enough. The configurator guides you in 2 minutes, and we fill in the rest together on the first call.

Allow about 1 week for a landing page, 3 weeks for a showcase website, 2 to 3 weeks for an MVP and 10 weeks for a SaaS. The exact timeline is set in the quote, and you see a live version at every step, not just at the end.

Yes, if we know it from the start. The timeline is set in the quote, with a launch date. If needed, we keep what really matters for launch, and the rest follows.

It depends on the number of pages, the state of the content and how much of the existing site is kept. The initial analysis sets the scope, then the schedule is set out in the quote, with a launch date. You see an online version at each stage, and old addresses are redirected at launch to limit the risk to your search ranking.

It depends on the scope: number of screens, user roles and connections to other tools. We start with the essentials, a first usable version online, then the tool grows step by step. The schedule is set in the quote, with a live version online at each milestone.

Start with a target and a message: what you do, for whom, in one sentence. Set a single goal (demo, waiting list or contact), keep to the pages that matter (home, solution, about, contact) and pick a fast, well‑ranked foundation that can welcome the product later.

Present it before you build it: a landing page with a clear promise and a sign‑up (waiting list, pre‑order or demo), interviews with future users and, if needed, a clickable prototype. The answers shape the MVP, or save you from building it for nothing.

A freelancer is often more flexible and cheaper; an agency brings more resources and process. KODAPT sits in between: a direct contact who designs and codes, a step‑by‑step method and standard, documented technologies (Next.js, TypeScript).

With the smallest product that proves your idea: one journey, sign‑in, payment. We add the rest in stages.

MVP scoping (the essentials, nothing more), accounts, roles and secure sign‑in, subscriptions and payments, dashboards and exports, then hosting, monitoring and iterations. The software moves forward step by step, with a live version at every milestone.

A SaaS is a software product used by or sold to many customers. A custom web application is a tool designed around an organisation’s processes, for its teams or its clients. The technologies are similar; the goal and the users change.

With the process that costs you the most today. We map it, then build first the part that saves the most time. The tool then grows step by step, with a live version at every milestone.

The people you choose. Each account has a role (team, client, administrator) that sets what it sees and what it can do, with secure sign‑in.

Yes, as web applications: client portals, back‑offices, internal tools and automations, built for your teams from your business and your current tools.

Often, yes. We start by reviewing the project (code, hosting, documentation); you then know whether it can be taken over, improved, or whether some parts would be better rebuilt, before any commitment.

Yes. We start by analysing your current website, then rebuild it step by step, with a visible version at every milestone and your content carried over. What works is kept.

It depends on what blocks. If the technology and structure hold, we rethink the design and journeys; if the foundation stops you evolving, a rebuild is healthier. The initial review settles it, before any quote.

It can lower them if it is poorly prepared. We identify the pages that bring visitors, keep their addresses where possible and redirect the others to their new version. Nobody can guarantee rankings, but a prepared migration clearly reduces the risk.

Not to start. Gather your access (hosting, domain name, site management tool), what works or not in your view, your goals and, if you have them, your visit statistics. The scope then takes shape with the review of what exists, before any quote.

You see a live version at every step, not just at the end. You can test it, show it around and give feedback as we go.

That’s normal, especially early on. Your feedback is built in at every stage, before moving on. If the scope really changes, we talk first: you approve the new price and timeline.

Yes. We start with what matters most to your business, with a visible version at every milestone. What comes next is decided together, based on what has been delivered.

We stay. For 3 months after launch, changes are free; after that, maintenance, fixes and new features whenever you need them.

You don’t have to: for 3 months after launch, we make the changes for you, at no cost. And if you wish, you can also change a text or a photo yourself.

Technical SEO is built in from the start: a fast site, well structured for search engines and built around the questions your customers ask. Rankings also depend on your competition and your content: we do not promise a position.

Design is done in Figma. Development relies on standard, well‑documented technologies: React, Next.js, TypeScript and Tailwind CSS for interfaces, Node.js and PostgreSQL on the server, Stripe for payments, GSAP and Three.js for motion and 3D, and Vercel and GitHub for deployment and version control.