⚡ Quick answer: “Turnkey” means the studio handles the full cycle — from structure to launch on your domain. Realistic timelines: a landing page takes 1-2 weeks, a corporate site 4-8 weeks, an online store 6-12. The most common cause of a missed deadline isn’t development, it’s client-side content: copy, photos, access credentials. Assign one person inside the company to own materials at the start, and the timeline holds in roughly nine cases out of ten.
Most owners commission a website for the first time and have no picture of what the process looks like from inside. Hence the usual anxiety: how often will I be pulled in, will this drag on for six months, and what happens if I don’t like the result. Let’s go stage by stage.
The phrase sounds self-evident but means different things at different studios. The honest minimum looks like this: site structure, design, front-end build, CMS setup, content population, domain and hosting configuration, basic SEO, and launch.
What usually isn’t included, though clients expect it: copywriting, professional photography, paid stock imagery, ongoing site management after launch, and advertising. That’s not a trick — they’re simply separate pieces of work, and it’s worth asking about them directly at the proposal stage rather than afterwards.
Clarify this before signing. Mismatched expectations about copy cause half the friction on projects.
The first meeting is rarely about design. The questions a competent studio asks sound dull, but they’re what determines the outcome: who is your customer, how do they find you now, what does your competitor do, what action should a visitor take, what objections come up.
Structure grows out of those answers — the list of pages and what belongs on each. This is the cheapest moment to change anything: moving a block in a diagram costs nothing, moving the same block in a finished layout costs money and time.
Timeline: 3-7 days. What’s needed from you is one substantive hour-and-a-half conversation, plus access to whoever actually knows the product — often not the owner but the head of sales, who hears customer objections daily.
A wireframe is a schematic layout of pages with no colour or photography — just blocks and their order. It looks unimpressive, which is exactly why many clients skim past it and approve without really looking.
That’s the mistake that costs most later. The wireframe is where logic is visible: whether the page answers the customer’s questions, whether contacts are buried, whether there’s a call to action where someone is already convinced. Fixing block order here takes an hour.
Timeline: 3-10 days depending on page count.
This is where what clients usually call “the website” appears. The home page is designed first — it sets the tone — then the remaining page types.
Revisions here are normal and built into the process, but they’re best collected as a batch rather than sent one at a time every hour. A working habit: look at the layout, let it sit for a day, gather every comment into one list and send it together. That produces two or three rounds instead of ten.
It’s worth agreeing upfront how many rounds are included in the price. At Netloria that’s usually two full rounds per layout — and on the vast majority of projects that’s enough, because logic was settled at the wireframe stage and design is left with aesthetics.
Timeline: 1-3 weeks. Longer for a store, since there are more page types — catalogue, product card, cart, checkout.
The quietest stage for a client: almost nothing is needed from you except access credentials. The layout becomes working pages, the CMS is connected, forms are configured, integrations are wired up — payments, shipping, CRM, analytics.
What’s worth checking when the stage closes: how the site looks on a phone (not just on the designer’s monitor), whether enquiries actually arrive at a real inbox, whether it works across browsers.
Mobile isn’t an add-on to the main version — it’s what most visitors will see, typically around two thirds of traffic. Ask about it early and review layouts from a phone.
Timeline: 1-4 weeks. Up to 6 for a store with integrations.
This is where projects stall. Development is finished and there’s no copy, because nobody inside the company owns it personally: the marketer is busy, the owner has no time, and copywriting wasn’t budgeted.
There are really three options: write it yourself against the structure the studio provided, commission copywriting separately, or hand drafts to the studio for editing. The worst option is waiting for inspiration. At Netloria we usually advise assessing honestly at the start whether anyone has genuine time for this — and if not, budgeting for copy immediately rather than a month into the delay.
Timeline: from a week to indefinitely. This is the one stage that depends almost entirely on the client.
Before launch the site is checked: forms, links, speed, rendering across devices, analytics configuration. Then migration to the live domain, SSL certificate, search indexing.
One item people forget: if the domain already had an old site, you need a redirect map from old URLs to new ones. Without it, pages that spent years accumulating rankings turn into 404s and organic traffic drops for months.
What to check in the first week after launch: whether the site is indexing in Google (searching site: plus your domain is enough), whether analytics records real visits, and whether enquiries genuinely arrive — send a test one from a phone, not from the developer’s computer. Those three checks take ten minutes and catch most of the problems that otherwise surface a month later.
Timeline: 3-7 days.
| Format | Total timeline | Your active involvement |
|---|---|---|
| Landing page | 1-2 weeks | ~4 hours across the project |
| Corporate site | 4-8 weeks | 8-12 hours |
| Online store | 6-12 weeks | 15-25 hours |
Those hours cover meetings, reviewing layouts and gathering materials. It doesn’t look like much, but it’s distributed unevenly: most of it falls in the first week and during the content stage. If those periods collide with your holiday or peak season, it’s better to move the start than to miss deadlines halfway through.
Which format suits your task is covered separately in our piece on website formats, and the actual figures in the article on corporate website cost.
The list is short, and every item genuinely saves a week:
A question clients almost never ask at the start and deeply regret a year later. Clarify three things before signing: whose name the domain is registered under, who holds administrative hosting access, and whether you receive full admin access to the site itself.
A healthy setup looks like this: the domain is registered to you or your company, you have your own hosting account, and you hold administrator access to the CMS. The studio has its own working access but isn’t the sole owner. An unhealthy one is when everything sits with the contractor, and changing studios means starting from scratch or buying back your own website.
This isn’t about distrusting a particular studio — it’s ordinary hygiene. A contractor can close, change direction, or simply stop replying, and the site needs to remain yours in every scenario.
Comparing proposals by the single figure at the bottom is the fastest route to choosing wrong, because the same total can hide very different scopes. A proper proposal names pages individually rather than saying “a site of up to 10 pages”; states how many revision rounds are included and what each additional one costs; separates out whether copy, imagery and content population are included or are your job; sets timelines by stage rather than one date at the end; and specifies what happens after launch — whether there’s a warranty period, how long it runs and what it covers. If half those points are missing, they most likely weren’t discussed internally either — which means they’ll surface mid-project as extra invoices or slipped deadlines, with nothing in writing to point at.
Another signal: a studio willing to state not only what’s included but what isn’t. A proposal with a scope-limits section is almost always more honest than one listing only benefits.
The most frequent is involving too many people in approvals. When six people review a layout and each has an opinion on the button colour, the project bogs down: revisions contradict each other, the studio receives mutually exclusive instructions, and the timeline stretches. The practical fix is straightforward — appoint one person who collects opinions internally and hands the studio a single agreed list. It isn’t about limiting anyone’s role, it’s about speed: on projects where that person exists, revision rounds drop roughly by half, and at Netloria we ask for them to be named at the brief stage.
The second is judging design on “like it / don’t like it.” The site isn’t built for you, it’s built for your customer. The useful question is whether someone understands what you offer within five seconds and can find where to click.
The third is disappearing for two weeks during approvals and then asking for the timeline to be made up. The process runs both ways, and a client-side pause doesn’t accelerate development.
Launch is a start, not a finish. A site with no traffic produces no enquiries, and separate work begins here: SEO, advertising, filling the blog.
The second thing worth agreeing in advance is technical support. CMS and plugin updates, backups, monitoring — without these a site accumulates vulnerabilities within six months. We covered what support includes and what it costs separately.
If you’re planning a site and want to understand timelines and scope for your specific case — tell us what your business does and what already exists. We’re a web studio based in Ukraine, and we’ll map out stages with real dates rather than an abstract “from two weeks.”
