At Gravity Group, website packages up to €500 have a delivery time of 5 working days. A webshop is usually ready in around 10 days, depending on complexity. These are the timelines for our offer, rather than an average across all providers. We confirm the start, agreed content and publication date for each project.
If you are starting a business, opening a new location or preparing a campaign, you probably care more about when you can send customers a finished website than how many hours programming takes. It helps to distinguish preparation, development, review and publication. A project can have a short development schedule and still be delayed if the copy or access to the domain arrives near the end.
This guide explains which timeline suits your type of website, what to prepare before development begins and how a five-working-day schedule might look. The aim is to make clear what “finished” means and what happens when you request an additional feature during the project. Compare our current website development offer with the scope you actually need.
How does the timeline depend on the type of website?
The number of pages helps estimate the work, but it is not the only meaningful difference. A business website presents information and receives enquiries. A webshop must support an order and the full purchasing process. A custom application or complex integration needs a separate agreement, even when it appears to be a single page from the outside.
- Project type
- Starter, €300
- Timeline in our offer
- 5 working days
- What needs defining before development starts
- Content for one clear page, photographs and a contact method
- Project type
- Growth, €500, up to 6 pages
- Timeline in our offer
- 5 working days
- What needs defining before development starts
- The page list, content for each page and agreed features
- Project type
- Webshop
- Timeline in our offer
- Usually around 10 days, depending on complexity
- What needs defining before development starts
- Catalogue, product variations, payments, delivery and integrations
- Project type
- Custom functionality or extensive migration
- Timeline in our offer
- Timeline following assessment
- What needs defining before development starts
- Business rules, existing data, external services and testing
| Project type | Timeline in our offer | What needs defining before development starts |
|---|---|---|
| Starter, €300 | 5 working days | Content for one clear page, photographs and a contact method |
| Growth, €500, up to 6 pages | 5 working days | The page list, content for each page and agreed features |
| Webshop | Usually around 10 days, depending on complexity | Catalogue, product variations, payments, delivery and integrations |
| Custom functionality or extensive migration | Timeline following assessment | Business rules, existing data, external services and testing |
For a webshop, the estimate here is approximately ten days. We specify the final schedule and how days are counted in the proposal. A complex store connected to several business systems should not be forced into the same timeline as a straightforward catalogue with properly prepared data.
When comparing prices, also compare the deliverables. Two proposals with the same price may include different content, languages or support. Our guide to how much website development costs explains those differences in more detail. This article focuses on timing and organising the project.
When do the five working days start?
The first conversation and the first day of development are not necessarily the same date. During that conversation, we establish the goal, scope and availability. A reliable schedule requires agreement on what we are building, who provides the content and when we can begin. The exact starting point should appear in the proposal or project confirmation, together with the approval process.
Working days differ from calendar days. If Monday is the agreed first day, with no public holidays or interruptions, Friday is the fifth working day. If the first day is Thursday, the weekend does not count towards those five days. When timing matters for an opening or campaign, request an explicit handover and publication date rather than calculating it from a vague message yourself.
It is also useful to distinguish the first review from public publication. A review on a preview address lets you check the copy, photographs and functions. Public publication follows the agreed approval and technical checks. If the date needs to match a particular event, mention that before development starts so the whole schedule can accommodate it.
Do not assume every change automatically fits within the original deadline. Correcting a telephone number and adding a booking system are different tasks. Agreeing on changes also protects your launch date: it becomes clear whether a request fits the existing scope or needs a new estimate.
What should you prepare before development starts?
A small business website does not require a large presentation or marketing jargon. It needs accurate information that helps visitors understand the offer, decide whether you are a suitable provider and send an enquiry. We guide you through preparation with a short form containing clear questions.
A short form after the deposit is paid
After you pay the deposit, we send you a short form to complete so we can collect everything needed to build your website. It gathers information about your business, website content and materials.
The form makes preparation easier by clearly showing what you need to provide. It lets us review the necessary information in one place and organise development more easily. That makes the whole process simpler for both you and us, with fewer follow-up questions and less searching for details across separate messages.
If you do not have photographs or planned content, we handle all the preparation for you. Based on your form responses, we plan the website structure, write the copy and provide suitable photographs and visuals. Tell us what your business does and what you want to achieve, and we prepare the content for your website.
Your offer, services and service area
Write down what you do, who you work for and where you operate. Instead of saying only “quality services”, name the specific jobs you undertake. For example, a plumbing business can distinguish installations in new buildings from bathroom renovations. That helps establish the content structure before individual sections are designed.
Decide on the main action you want visitors to take. Should they call, send a project description or enquire about availability? A clear decision makes it easier to prepare the form and explain what customers should provide. When every page pursues a different, unrelated goal, reviewing the website becomes slower and less clear.
Photographs, previous work and contact details
If you have your own photographs that you are allowed to publish, a logo or examples of previous work, send them with a short explanation of what they show. Give files meaningful names: a service type and project name are more useful than random identifiers. If you do not have photographs, we handle their preparation.
Check the telephone number, email address, opening hours and service area before sending them. An incorrect form recipient can be a more serious problem than a visual detail. Choose the person who will receive a test enquiry and confirm that the message has reached the right place.
Your domain, existing website and decision maker
If you already have a domain, establish who manages its registration and DNS settings. Include existing business email in the change plan so the new website does not disrupt your messages. Access should be arranged securely; do not place passwords in public documents containing article or website materials.
Choose one person to collect feedback and approve decisions. Several people can review the website, but the developer needs a consolidated list. This avoids situations where one comment requests a paragraph's removal and another requests its return as publication approaches.
What might five working days of development look like?
The schedule below is an illustrative example of organisation, rather than a record of a real project or a promise that every activity always happens on a particular day. It assumes that the scope is confirmed and the basic materials are prepared. Stages may overlap in an actual project, but each should have a clear outcome.
- Working day
- 1
- Main activity
- Confirm the structure and content arrangement
- Result to check
- The page list and destinations of the main buttons are clear
- Working day
- 2
- Main activity
- Visual implementation and initial content entry
- Result to check
- The offer, photographs and contact details take their final shape
- Working day
- 3
- Main activity
- Complete pages and agreed features
- Result to check
- The main visitor journey can be followed and the form tested
- Working day
- 4
- Main activity
- Review on devices and complete consolidated changes
- Result to check
- Identified errors are corrected and the content is approved
- Working day
- 5
- Main activity
- Final test, approval and agreed publication
- Result to check
- The public website is checked and access arrangements are explained
| Working day | Main activity | Result to check |
|---|---|---|
| 1 | Confirm the structure and content arrangement | The page list and destinations of the main buttons are clear |
| 2 | Visual implementation and initial content entry | The offer, photographs and contact details take their final shape |
| 3 | Complete pages and agreed features | The main visitor journey can be followed and the form tested |
| 4 | Review on devices and complete consolidated changes | Identified errors are corrected and the content is approved |
| 5 | Final test, approval and agreed publication | The public website is checked and access arrangements are explained |
The first day is not best spent choosing between ten unrelated examples. It is more useful to explain what you like about particular references: how services are presented, readability or ease of contact. Visual decisions then have a reason beyond personal preference.
On review day, use the website as a customer would. Open it on your phone, find a service, view previous work and try sending an enquiry. Then check the business information. “Change everything to make it more modern” is difficult to turn into a task. “I cannot find the telephone number on my phone” immediately identifies a problem to solve.
If you know you will be unavailable during the review, arrange a replacement decision maker or a different slot beforehand. A short project needs timely decisions, but it does not require you to sit at a computer all week. What matters more is knowing when feedback is expected and who will provide it.
Why does a webshop usually need around ten days?
A webshop is not finished when a product looks attractive on a page. Customers need to select a product, see the correct price, provide their details and complete an order. You need accurate information for fulfilment and a clear way to handle unsuccessful payments or products that are no longer available.
That is why we assess the catalogue first. A few simple products with prepared photographs are different from a catalogue containing sizes, colours and different availability rules. It also matters whether the data is organised in a consistent spreadsheet or must be gathered from separate messages and documents.
Payments and delivery come next. You need to choose payment methods, delivery areas and how delivery charges are calculated. If an external service is involved, the necessary account and access must be available. Approval time at a service provider should not silently be treated as part of the store's development time.
- Webshop question
- Catalogue
- More straightforward implementation
- Consistent data and clear photographs
- What needs an additional assessment
- Inconsistent descriptions, many variations or data cleanup
- Webshop question
- Delivery
- More straightforward implementation
- Known delivery areas and rules
- What needs an additional assessment
- Special exceptions or connections to several systems
- Webshop question
- Payments
- More straightforward implementation
- Agreed method and ready access
- What needs an additional assessment
- Activating a new service or a nonstandard payment journey
- Webshop question
- Stock and business systems
- More straightforward implementation
- An agreed manual management process
- What needs an additional assessment
- Synchronisation with a warehouse, ERP or another catalogue
| Webshop question | More straightforward implementation | What needs an additional assessment |
|---|---|---|
| Catalogue | Consistent data and clear photographs | Inconsistent descriptions, many variations or data cleanup |
| Delivery | Known delivery areas and rules | Special exceptions or connections to several systems |
| Payments | Agreed method and ready access | Activating a new service or a nonstandard payment journey |
| Stock and business systems | An agreed manual management process | Synchronisation with a warehouse, ERP or another catalogue |
The usual estimate of around ten days applies to the agreed implementation after assessment. If the store requires complex integrations, several languages or data migration, we confirm the timeline separately. It is better to establish feasibility early than publish a store where customers discover a problem during the first order.
Before development starts, also describe what a successful order means for your business. What message does the customer see, where does the notification arrive, who checks payment and how does delivery begin? These questions often reveal necessary decisions before they become obstacles during final testing.
What can extend the agreed timeline?
The timeline can change because of content, decisions or external systems. That does not mean every obstacle must stop the entire project. The useful distinction is between something that blocks publication and something that can be completed in a separate phase without undermining the website's essential purpose.
Changing the scope after development begins
If the agreement covers a contact form, a later request for bookings with payment changes the project. Availability, confirmations, cancellations and possible integration with another tool need defining. Assess the feature first, then decide whether to implement it before publication or after the basic website launches.
Materials that remain provisional
“We will send the photographs tomorrow” is not a schedule when repeated several times. Identify which photographs are essential for publication and which galleries can wait. The same applies to copy. One approved version is a better starting point than several unfinished documents with unclear filenames.
Access and approvals that depend on other people
A previous developer, domain administrator or payment provider may need to complete a step. Check these dependencies before starting. If you are replacing an existing website, request a list of important URLs and business functions. Removing the old website before checking its replacement can create additional work beyond a straightforward visual update.
Conflicting feedback
Organise comments by page and problem, and distinguish an error from a new request. “The number is incorrect” is a correction; “let us add another service with its own gallery” may extend the scope. That distinction makes priorities easier to agree and reduces time spent interpreting messages.
Three situations for a small business
A newly established business can begin with a clear description of services, its service area, a few original photographs and a simple contact method. If there is not enough material for several pages, a focused initial scope is more useful than waiting for an extensive company story that answers no additional customer questions.
A company offering several services should decide early which need separate pages. The FlowTech Instalacije project shows different groups of plumbing services and a route towards contact. We reference it as an example of structure, rather than evidence of its price or development duration.

A shop moving online benefits most from preparing its data early. Before choosing the appearance, establish how products are ordered, which variations exist and how availability is checked. Once those questions are resolved, a discussion about timing can be specific. Without them, an unchecked date simply creates a false sense of certainty.
What should you check before calling the website finished?
An agreed deadline is useful only when the deliverables are clear. A website that opens on the homepage but cannot receive messages or leads to an empty page is not a well-completed project. The final review should cover business details, the main visitor journey and technical basics on the actual domain.
- All agreed pages exist, and navigation and buttons lead to the right destinations.
- The telephone number and email are correct; the form has been submitted and receipt confirmed.
- Text is readable on a phone, photographs display correctly and important elements are not cut off.
- For a webshop, the agreed test order, payment and notification have been checked.
- The public domain, secure access and existing business email are confirmed.
- Page titles and basic descriptions match the actual content.
- If old URLs change, necessary redirects have been checked.
- It is clear who has access, what maintenance includes and whom to contact about a problem.
Follow a test enquiry through to receipt rather than stopping at a “successfully sent” message on screen. If form submissions are measured, check that analytics distinguishes a completed action from an ordinary click. The received enquiry matters to your business, so the records should reflect that outcome.
Also record anything left for later, with a responsible person and an agreed way forward. An additional gallery or language can be a separate phase. An unspoken list of unfinished items makes handover harder; a written record clarifies what completion includes.
How can you coordinate the website with an opening or campaign?
If the website needs to support an opening, trade fair or advertising campaign, start with the date when people will first need to use it. Then agree on a review slot and establish what must be complete beforehand. That creates a schedule of decisions rather than just a date at the end of a proposal. Include the domain administrator in that schedule if someone else manages it.
For example, a salon opening bookings on Monday needs to check its telephone number, form and appointment confirmation process before that point. Photographs of the premises may matter, but receiving a booking request correctly directly affects the business. Test the journey to that action first, then check everything else included in the agreed delivery. This is an illustration of priorities, rather than a claim about an actual project.
For a campaign, prepare the destination URL and a message matching the advertisement. Do not print a QR code pointing to a temporary address without agreeing on its final destination. If the advertisement promises a particular service, visitors should find it on the page they reach. Also check where form messages go so spending on visitors does not begin before contact has been tested.
When the date cannot change, distinguish the essential initial version from later additions. That does not mean publishing a broken website. It means agreeing in advance, for example, which services and previous projects are ready to present and which additional language will follow in a separate phase. Record every deferred item clearly so reducing the initial scope does not create an ambiguous obligation.
Finally, allow time for your own review and a technical check of the public address. If the entire schedule depends on an answer you can only provide late on opening day, explain that before ordering. The developer can then assess a feasible date and suggest a schedule matching the actual availability of everyone involved.
Does publication mean the website immediately appears on Google?
Development and Google indexing are separate processes. You can send customers a published website and use it in your communication, but the delivery date does not promise a date of inclusion in search results or a position for a particular keyword.
Google explains that recrawling can take from a few days to a few weeks and that requesting indexing does not guarantee inclusion. See the official documentation on requesting a recrawl. After publication, technical access should therefore be checked separately from organic visibility, which is monitored through data.
A sitemap and meaningful internal links help discovery of URLs. A sitemap alone does not guarantee indexing either, as Google explains in its sitemap documentation. The practical distinction for a business owner is that technical publication is confirmed through inspection, while SEO performance is assessed through subsequent measurement.
Frequently asked questions
How long does a website costing up to €500 take?
At Gravity Group, website packages up to €500 have a delivery time of 5 working days. We confirm the exact start, content and publication date for each project. Working days differ from calendar days, so weekends do not count towards those five days.
How long does webshop development take?
A webshop is usually ready in around 10 days, depending on complexity. Before confirming the timeline, we assess the catalogue, product variations, payments, delivery and required integrations. More complex stores need a separate schedule, and the proposal specifies how days are counted.
Can I order a website before I have all the copy and photographs?
Yes. If you do not have photographs or planned content, we handle all the preparation: the website structure, copy, and suitable photographs and visuals. After you pay the deposit, we send you a short form to learn about your business, services and goals. We use your responses to prepare the content for your website.
Can the deadline change if I add new features?
Yes. A feature outside the original agreement requires an assessment of scope and time. Correcting an existing detail differs from adding bookings, another language or a business-system integration. The effect on price and timing should be confirmed before the change proceeds.
Will I rank first on Google after five working days?
The five-working-day timeline covers development of the agreed website. It does not guarantee first place or a particular indexing date. After publication, technical availability, indexing and relevant organic impressions, clicks and enquiries are checked separately over time.
How can you agree on a realistic publication date?
Send a description of your business, the pages or functions you need, the materials you already have and any important date. If you have an existing website, include its URL and explain what should be retained. That information helps assess whether a package up to €500 suits the project or a separate scope is needed.
For a straightforward website, the starting point is five working days; for a webshop, usually around ten days after assessing complexity. The most useful next step is to send a short project description and your preferred deadline, so we can confirm a feasible schedule and what needs to be ready before development starts.
Sources and further reading
- Google Search Central: Ask Google to recrawl your URLs, checked on 29 October 2026.
- Google Search Central: Learn about sitemaps, checked on 29 October 2026.
- Gravity Group confirmed five working days for website packages up to €500 and usually around ten days for a webshop on 29 October 2026; final scope and timing are confirmed in the proposal.
