Project planning8 min read

From First Enquiry to Launch: How a Website Project Works

Published By Ichii GmbH

Contents
  1. The eight steps at a glance
  2. Who does what at each step
  3. Steps 1 and 2: enquiry and first call
  4. Step 3: materials decide the pace
  5. Step 4: put the scope in writing
  6. Steps 5 and 6: draft, corrections, sign-off
  7. Step 7: launch preparation and the late blockers
  8. Step 8: after launch
  9. One example of a concrete process
  10. If you build it yourself
  11. Your next step

A website project for a small business runs through the same sequence almost everywhere: enquiry, call, materials, written scope, first draft, corrections, launch preparation and launch. Providers name the phases differently, but the order is rarely different.

If you run a business in Germany but grew up with another market's habits, the steps themselves will feel familiar. What tends to catch international founders out are the local items that have to be ready before go-live: an Impressum (the legal notice German law requires), a privacy policy written for GDPR, a decision on German, English or both, and access to a domain that may have been registered by someone else.

This guide walks through each step with three questions: what do you do, what does your developer do, and what has to be decided?

In short

  • A typical project has eight steps, from your first enquiry to the weeks after launch.
  • Your main jobs: define the goal and pages, supply final text and images, confirm the scope in writing, give consolidated feedback, and provide domain access and legal-page details.
  • The two decisions that matter most: confirming the written scope before work starts, and signing off before launch.
  • In Germany, plan the Impressum, privacy policy and any cookie consent early. They are the most common last-minute blockers.

The eight steps at a glance

  1. Step 1: Enquiry: You describe your business, what the site should achieve and whether there is an existing site. The developer checks whether the project fits and suggests a call.
  2. Step 2: First call: Together you clarify the purpose of the site, who it is for, which pages and features it needs, which language or languages it uses, and what is out of scope.
  3. Step 3: Materials: You send text, images, logo, your company details for the Impressum and, if relevant, the old site. The more complete this package is, the smoother everything after it runs.
  4. Step 4: Written scope and order: The developer summarises pages, features, price, exclusions and ownership in writing. You confirm, and only then does the build start.
  5. Step 5: First draft: The developer builds the pages with your content. You see the whole site for the first time.
  6. Step 6: Corrections and sign-off: You collect your changes and send them back as one list. After the agreed correction round you approve the site.
  7. Step 7: Launch preparation: Domain and DNS are switched, the Impressum and privacy policy are live, and on a relaunch old addresses are redirected.
  8. Step 8: Launch and after: The site goes live. Then come checks (test the form, review pages) and the question of who looks after the site technically.

Who does what at each step

Use this table as a checklist for your own project. The "decision" column marks where nothing moves until you say yes.

StepYour jobDeveloper's jobDecision
EnquiryName your goal, sector and current siteCheck fit, offer a callCall or not
First callExplain pages, audience, languages, target dateAsk questions, estimate scopeRough direction
MaterialsSupply text, images, logo, company detailsCheck completeness, flag gapsWhat is final?
Scope and orderRead the summary and exclusionsPut pages, features, price, dates in writingConfirm the order
First draftBlock time to reviewBuild pages, check on mobile–
CorrectionsSend consolidated, specific feedbackMake the changesSign-off
Launch preparationProvide domain access and legal textsDNS, redirects, technical checksLaunch date
After launchTest the form, keep content currentHandover, maintenance if agreedMaintenance or not

Steps 1 and 2: enquiry and first call

Your enquiry can be short. Three sentences on your business, what the site should do and your current online presence are enough to make the call useful.

The call is mostly about content, not colours. What services do you want to show? What should a visitor do at the end: call, send an enquiry, book? Which pages does that take? For a page-by-page view, see which pages a small business website needs.

Raise the language question here, not later. If most of your customers speak German but your team works in English, you may need both. A second language usually means separate pages and separate text, so it changes the scope and the price.

If you want to prepare your answers in advance, use our website brief template. A completed brief shortens the call and makes quotes easier to compare.

Step 3: materials decide the pace

This is the step where most of the work is yours. Without content a developer can only build placeholders, and placeholders just move the work further down the line.

Typically you will need:

  • final text for each page, in each language you have chosen
  • images in good resolution that you have the rights to use
  • your logo, ideally as a vector file (SVG or PDF)
  • company details for the Impressum: name, address, legal form, who represents the company, email, and where applicable register number and VAT ID
  • the address of your current site, if there is one
  • access to your domain account, or contact details for whoever registered it

The content of the Impressum is set by § 5 DDG (the German Digital Services Act). Regulated professions, such as doctors or lawyers, have to add professional details. Only your business can supply this information, so gather it early. If your company is registered outside Germany, ask your adviser which disclosure rules apply to your structure.

Tip

One folder, one decision-maker

Put everything in a shared folder and name files by page ("services.docx", "team-photo-1.jpg"). Also name one person on your side who approves content. Projects with three approvers tend to get three sets of contradictory feedback.

Step 4: put the scope in writing

This step looks like paperwork, but it protects both sides. The written summary should list the pages, the features, the number of correction rounds, what is explicitly not included (for example copywriting or a second language), the price, whether that price is net or gross, and who owns the domain, the content and, if relevant, the code.

German providers usually quote net prices plus VAT (Umsatzsteuer). Check which figure you are looking at before comparing quotes from different countries. Our guide on comparing website quotes shows how to line up several offers.

Steps 5 and 6: draft, corrections, sign-off

The first draft is where you see the site as a whole. Book time for it and look at it on your phone too, since that is where many visitors will see it.

For the correction round, one complete list beats five separate emails. For each change, note the page, the place and the exact new wording. Decide internally who has the final say before you send it.

Watch out

Sign-off has legal weight in Germany

For contracts for work (Werkvertrag), German law has a formal acceptance step called Abnahme. Under § 640 BGB, the client must accept work produced as agreed and cannot refuse because of minor defects. Whether and how acceptance is handled in your project depends on your contract. If in doubt, get legal advice.

Step 7: launch preparation and the late blockers

Projects rarely stall on design. They stall just before the finish line. Sort out these points early.

Domain and DNS. To point your domain at the new site, its DNS settings (the records that tell browsers where the site lives) have to be changed. Someone needs access to the account at the domain registrar. If the domain was registered by a former agency, a co-founder or an employee who has left, getting access can take days.

Impressum and privacy policy. Under § 5 DDG the Impressum must be easy to recognise, directly reachable and permanently available. If you collect personal data, for example through a contact form, Art. 13 GDPR requires you to inform people at the time of collection, which is why the site needs a privacy policy. Decide early who writes these texts. Often that is the business itself, using a generator or a lawyer. Templates from your home country rarely fit German requirements as they stand.

Cookies and tracking. If analytics tools or embedded content such as maps or videos store or read information on visitors' devices, § 25 TDDDG generally requires consent unless the storage is strictly necessary. So a consent solution has to be in place before launch, not added afterwards.

On a relaunch there is a fourth point: old addresses should redirect to the matching new pages. An XML sitemap, on the other hand, is not strictly necessary for a small, well-linked site, according to Google, though it does no harm.

Step 8: after launch

Test on launch day yourself. Does a message from the contact form arrive? Do the phone and email links work on a mobile? Can the Impressum and privacy policy be reached from every page?

Don't expect to appear on Google the next day. Google says crawling new pages can take anywhere from a few days to a few weeks, and requesting a crawl does not guarantee inclusion in search results.

Also agree who looks after the site technically: updates, security, small edits. That is usually a separate arrangement and not part of the build price.

One example of a concrete process

At Ichii, the process for a business website looks like this: a Zoom call, you send your materials, we confirm scope and order in writing, you receive a first draft within 7 business days once all materials are in and the scope is confirmed, then one correction round and launch. The 7 days refer to the first draft. They are not a launch date, which depends mainly on when content, feedback and domain access are ready. You can see the same steps on our process page.

For how much time to plan overall and what typically slows projects down, read how long it takes to build a small business website.

If you build it yourself

With a website builder you go through the same steps, but you play every role. For a simple site with a few pages, that can be perfectly adequate. The Impressum, privacy policy and domain remain your responsibility either way.

Your next step

Go through the materials list in step 3 and count how many items you can tick off today. If your text, images and company details are largely ready and you are planning a site of up to 10 pages, look at our business website offer and send us a short enquiry.

Sources

  1. § 5 DDG – Allgemeine Informationspflichten — German Federal Ministry of Justice, gesetze-im-internet.de, accessed 2026-10-09
  2. Art. 13 GDPR – Information to be provided where personal data are collected — dsgvo-gesetz.de (unofficial consolidated text), accessed 2026-10-09
  3. § 25 TDDDG – Protection of privacy in terminal equipment — German Federal Ministry of Justice, gesetze-im-internet.de, accessed 2026-10-09
  4. § 640 BGB – Abnahme — German Federal Ministry of Justice, gesetze-im-internet.de, accessed 2026-10-09
  5. Ask Google to recrawl your URLs — Google Search Central, accessed 2026-10-09
  6. Learn about sitemaps — Google Search Central, accessed 2026-10-09

A business website with up to 10 pages

A one-time €790 net – built on a proven design system with your text and images. The offer page lists everything that is included.

See the website offer