A business website can take 5 to 8 weeks within Mischka Studio's defined scope. Turning that estimate into a launch date requires an agreed start date, ready content, and time for your team to review the work.
If you're planning a campaign or opening a business, ask what the schedule assumes before putting a date on the announcement. An estimate of six weeks doesn't tell you when a project can start, who needs to approve it, or whether copywriting is included.
What the estimate covers
The ranges below come from Mischka Studio's pricing and web design service information. They're planning estimates for the stated scope, not completion statistics or a promise for every project. The written quote confirms the start date and schedule.
| Website type | Planning estimate | Content needed | Implementation scope | Decisions and dependencies to resolve |
|---|---|---|---|---|
| Landing page | 2 to 3 weeks | Final copy and photos for one page with up to six sections | Contact form, analytics, basic technical SEO | One agreed purpose, feedback within two revision rounds, launch approval |
| Business website | 5 to 8 weeks | Supplied content for up to eight pages in one language | Content management system, analytics and Search Console, up to two hours of training | Page structure, consolidated feedback within two revision rounds, launch approval |
| Online store | 6 to 10 weeks | Up to 20 supplied products for one market, language, and currency | Shopify or WooCommerce, one supported standard payment method and one shipping method | Product information, payment and shipping choices, necessary account access and approvals |
| Custom platform | At least 3 months | Content and data requirements defined for the project | Individually scoped features and connected workflows | Agreement on user roles, business rules, integrations, and approval responsibilities |
Copywriting, translation, additional languages, and custom integrations need separate scope. If your project needs them, include them when discussing the schedule. These package boundaries don't mean that every eight-page site takes the same amount of work.
Give each dependency an owner
Final copy is a scheduling input. The layout needs to accommodate the actual service explanation, product information, and calls to action. If those are still being decided, agree who will finish them and by when. A folder of notes may be useful source material, but it isn't approved website copy.
Choose one person to collect feedback and return an agreed response. That person doesn't have to make every decision alone. They do need authority to resolve conflicting comments before sending them back. Set review dates with the people whose approval is required, including whoever can approve launch.
External access also needs an owner. Establish who controls the domain and any accounts needed for the agreed functionality. If another provider holds access, allow for that handover in the plan. Don't leave the first request until launch day.
A new requirement deserves a schedule decision. If a second language or an extra integration becomes necessary during the build, ask for its effect on the agreed delivery date. You can then choose whether to include it now or schedule it after the initial launch.
The delivery team also needs to flag work that is taking longer than planned. Ask which next step it affects and agree a revised schedule before changing your launch announcement.
Two websites with different work behind them
The Instrukcije Eržen project combined a logo and brand guidelines with a WordPress website and service copy. Its scope included separate routes for tutoring, training, and consulting, plus forms and WhatsApp contact.
For a site serving several audiences, the schedule needs to account for decisions about what each visitor should read and where they should go next. Page count alone doesn't describe that work.
Instrukcije Oglasnik involved search by subject, city, and teaching format, tutor accounts with profile editing, and subscriptions paid by bank transfer and confirmed by an administrator. It also included custom administration for subjects, cities, and content.
Those features create connected workflows. Account changes and subscription confirmation need defined rules and testing. A project like this needs an estimate based on those workflows.
These examples illustrate scope. Neither case study reports a delivery duration, so they don't show how long either project took or whether it was delayed.
Before you commit to a launch date
Check these points with the team delivering the site:
- Confirm the start date and which deliverables the estimate includes.
- List unfinished content, with a named owner and delivery date for each item.
- Identify the accounts and external access the project needs, and who can provide them.
- Reserve review time and appoint someone to consolidate feedback.
- Confirm who approves launch and when that decision is needed.
- Agree how added requirements will affect scope and scheduling.
For a launch tied to a campaign or event, give the team that date when requesting a quote. Ask them to confirm whether the required scope fits it. The web design service is the starting point for discussing that scope and getting a written schedule.
Sources: Mischka Studio's Pricing and Web Design service information, checked September 15, 2026, and the two portfolio case studies linked above. The timing advice explains planning dependencies; it does not report measured project durations.
