Turnkey Website Development: What You Actually Get for Your Money
"Turnkey" is the most abused word in web development. It promises a finished result and usually delivers a template with your logo on it.
Here is what a genuinely turnkey project looks like — what you should receive, what it costs, and the three questions that separate a real developer from a reseller.
What "turnkey" actually means
A turnkey project is one where the client hands over a key and starts using it. That means someone else has dealt with:
- Hosting and DNS, with SSL working from day one
- A content structure that matches how the business actually sells
- Analytics, Search Console and a call-tracking pixel — installed, not "instructions in the email"
- A form that delivers leads somewhere you actually check
- Mobile layout that isn't a scaled-down desktop version
- The deployment pipeline, so updates don't break the site
If any of those are still on the client's to-do list, the project is not turnkey. It's a build.
The realistic price bands
| Scope | Timeline | Price range | What's included |
|---|---|---|---|
| Landing page for one offer | 3-5 days | $250-600 | One page, form, analytics, SSL |
| Business card site (up to 7 pages) | 5-7 days | $400-1,200 | Pages, blog setup, forms, SEO base |
| Corporate site (10-20 pages) | 10-15 days | $900-2,500 | Content structure, multilingual option, CMS |
| Online store (up to 2,000 products) | 15-30 days | $1,500-4,000 | Catalog, payments, delivery integration |
| Custom web app | 6+ weeks | $3,000+ | Auth, data model, admin, API |
If a quote for a 20-page corporate site comes in at $300, someone is going to hit a wall at the first non-trivial request. The price is a signal of how many decisions were actually made.
The 5-day version, step by step
Most clients ask for speed, so here's how a 5-day business website actually runs.
Day 1 — brief, structure, content. We map the pages, agree on what each page must make a visitor do, and collect the text. If the copy isn't ready by end of day 1, the deadline moves. This single fact is the most common reason a "5-day" project becomes a three-week project.
Day 2 — design. Wireframes, then visual design, then approval. One round of revisions is included; five rounds adds three days.
Day 3 — development. HTML/CSS, CMS setup, forms, analytics, tracking pixel. The boring part that takes 60% of the time.
Day 4 — content and SEO. Text placed, meta tags written, images optimized, structured data added, sitemap generated. This is where most rushed projects cut corners — and why they rank on page 5 instead of page 1.
Day 5 — testing and launch. Cross-browser, mobile, speed test, DNS switch, SSL. It goes live.
What you should receive, in writing
Ask any developer for these seven items before paying the final invoice:
- The source code — in a repository you own, not a zip from a contractor's laptop
- Domain and hosting accounts — registered in your name, with access handed over
- A deployment pipeline — so the next update is a pull request, not a panicked FTP upload
- Documentation — how to edit text, add a page, publish a post
- Analytics and Search Console access — in your account, not theirs
- A list of what was deliberately not done — the honest version of scope
- 30 days of warranty fixes — for the things that break after launch, which always happen
Item 6 is the one nobody asks for and the one that saves the most money. A contractor who clearly states "form validation is not implemented, here's how to add it" is more reliable than one who says everything is done.
The three questions that reveal everything
"What happens when I need to change the prices on 40 pages?" — If the answer is "you edit them in the admin panel," you have a CMS. If it's "we'll do it for you," you're locked in.
"Who owns the code and the accounts?" — Everything. Domain, hosting, repository, CMS, analytics. If any of it sits with the developer, that's a dependency and a risk.
"Show me a project you finished six months ago that's still live." — A site from two years ago says more about quality than any portfolio screenshot.
What to avoid
- Templates rebranded. If the demo looks suspiciously like another client's site, that's what you'll get.
- Monthly retainers for a site that doesn't change. If the site doesn't need updates, hosting and a maintenance window are enough.
- Work without a written scope. Every dispute in this industry comes from an unclear agreement about what was included.
- Publishing before testing on real devices. Half your traffic is on a phone; a broken mobile layout costs you the leads you paid for.
A simple way to start
If you're not sure what you need, describe the process a customer goes through right now — from first contact to a finished order. That single walkthrough usually tells you whether you need a landing page, a five-page site, or a store with automation behind it.
Then take the cheapest option that solves that process. You can always add pages later; you can't easily un-spend a bad architecture decision.
Yuriy Astapyev — WebStudio. We build websites that clients can actually run. uriy-as.org
Top comments (0)