Client websites, our own working products and native apps. Two selected hospitality and brand concepts are clearly labelled.
LIVE PRODUCT
WE ARE MK STUDIO
A marketing studio with a personal point of view.
About this project
A complete identity and website for Madina Kabidenova’s marketing studio. The MK monogram, blue palette and scroll-controlled film lead into case studies and a callback form connected to Telegram and corporate email.
Our live JD Studio website brings web design, application development and automation into one studio identity, with motion-led storytelling, selected work and a direct project enquiry path.
An artist website for a Bangkok-based DJ performing across Asia. Live-session video, selected SoundCloud mixes and direct Telegram booking bring his sound and identity together.
Learn verbs in your browser. Keep practising on iPhone.
About this project
A language-learning website and native iPhone app for English and other languages. Search verbs, explore conjugation tables, listen to pronunciation and practise active recall with multilingual explanations. The web version works on phones, tablets and desktop browsers.
An offline harmonic-mixing companion for iPhone and iPad. Choose a key on the 24-key Camelot wheel to see compatible neighbours and relative major or minor keys. Includes haptic feedback and VoiceOver support, with no account or advertising.
Browser reconstructions and technical demonstrations, shown separately from our client work and original products. These are not commissions from the brands in the source material. Original source notices and documented limitations are retained; a browser reconstruction is not the original editable project or backend.
Showcase · Stills-only showcase
Orbit Passage
A cinematic environment study shown through two still images. No playable film or recovered UE5 runtime.
A practical scope for website maintenance, monitoring, backups, lead delivery, reporting and accountable support—plus the items that need separate approval.
Map a Google Ads landing-page lead from accepted form to delivery, qualification and customer outcome with a practical search-to-sale measurement plan.
A copy-ready Google Ads landing page brief connecting search intent, ad promise, proof, qualification, tracking, lead routing and launch acceptance before design begins.
A practical framework for deciding whether to redesign the current website, rebuild the platform or improve the highest-leverage pages without replacing everything.
A realistic website redesign or rebuild timeline covering discovery, copy, development, content and SEO migration, integrations, quality assurance and launch.
Web application development typically costs $10,000–$100,000+, depending on workflows, roles, data, integrations and risk. Compare practical 2026 scope bands.
How North Growth Lab designed and built a responsive six-pad rhythm sampler with real audio, rapid retriggering and live waveform feedback for the JDMEET artist website.
Landing page or website for Google Ads? Use a six-check decision matrix, hotel and design-studio examples, and a practical brief to choose the right destination.
A transparent guide to landing-page scope, cost drivers and budgeting for businesses that need qualified leads from paid search—not a decorative one-page design.
A practical decision framework for choosing a website, web application, iOS or Android app—and knowing when the business needs a connected combination.
Compare iOS, Android and simultaneous mobile development by audience, product behavior, device requirements, release operations and commercial evidence.
How we rebuilt our studio website around real projects, distinct service pages and crawlable content, with a practical release record and clear measurement limits.
A realistic website redesign or rebuild timeline covering discovery, copy, development, content and SEO migration, integrations, quality assurance and launch.
The honest answer depends on what redesign means.
Changing a theme and replacing several images can take days. Redesigning an established business website may require customer research, new positioning, a service architecture, original copy, responsive interaction, development, content migration, redirects, integrations, analytics and quality assurance. Both projects may be described as a website redesign, but they do not carry the same responsibility.
For planning, define the workstream and acceptance criteria before discussing the launch date. A date without an approved scope simply moves uncertainty into the final week.
Indicative timeline by scope.
These are planning ranges rather than a North Growth Lab delivery guarantee. Procurement, legal review, photography, translation, accessibility requirements and third-party systems can expand the schedule.
Scope
Focused page refresh
Typical duration
2–4 weeks
What must already be true
Offer and content are stable; platform and integrations remain
Scope
Small-business redesign
Typical duration
6–12 weeks
What must already be true
Decision owner is available; content and migration scope are bounded
Scope
Complex website rebuild
Typical duration
12–24+ weeks
What must already be true
Multiple services, integrations, content types or approval groups are involved
A complete redesign moves through seven overlapping stages.
These stages should overlap deliberately, not chaotically. Development can begin on approved page patterns while later content is completed, but building every page before the message and content model are stable creates expensive rework.
Discovery and current-site inventory: 1–2 weeks.
Positioning, sitemap and measurement plan: 1–2 weeks.
Copy and content production: 2–6 weeks.
UX and visual direction: 2–4 weeks.
Responsive development and integrations: 3–8 weeks.
Content and SEO migration: 1–4 weeks.
Quality assurance, launch and verification: 1–2 weeks.
Build the website rebuild timeline around acceptance gates.
A rebuild adds technical decisions, data movement and cutover risk to the redesign work. The schedule should therefore show what must be true before each stage begins and what evidence allows the team to leave it. Counting design and development weeks without these gates hides the actual critical path.
For a complex rebuild, the twelve-to-twenty-four-plus-week range is not one uninterrupted development block. Content, platform, integrations and migration can overlap, but launch remains dependent on the slowest unresolved item. Record one owner and due date for every gate before promising the public release date.
Rebuild gate
Foundation decision
Evidence required to enter
Current constraints, ownership and roadmap are documented
Acceptance evidence to exit
Approved retain, repair or rebuild decision with explicit scope
Common schedule warning
A platform is chosen before the current system is inspected
Rebuild gate
Content and URL inventory
Evidence required to enter
Pages, search value, proof and owners are exported
Acceptance evidence to exit
Every useful URL is marked keep, consolidate, replace or redirect
Common schedule warning
Pages are discovered only after templates are built
Rebuild gate
Representative production path
Evidence required to enter
Content model, real copy and integration responsibilities are approved
Acceptance evidence to exit
One complete page pattern, form delivery and analytics path work end to end
Common schedule warning
Layouts multiply around placeholder content
Rebuild gate
Migration rehearsal
Evidence required to enter
Staging content, redirect map and test records are available
Acceptance evidence to exit
A sample import, crawl, redirect and event reconciliation passes
Common schedule warning
The first realistic migration is planned for launch day
Rebuild gate
Launch and rollback
Evidence required to enter
Window, owners, backups, access and rollback triggers are confirmed
Acceptance evidence to exit
Forms, canonicals, redirects, analytics, sitemap and lead delivery pass the go/no-go check
Common schedule warning
No named person can stop or reverse the release
Rebuild gate
Post-launch verification
Evidence required to enter
Pre-launch search, traffic and lead baselines are saved
Acceptance evidence to exit
Errors, index signals and lead destinations have assigned checks and response thresholds
Common schedule warning
The project treats deployment as the final milestone
Content is the most common hidden critical path.
Teams often approve the design schedule while assuming existing copy will be reused. During the project they discover that services have changed, proof is incomplete, subject-matter experts disagree and images do not support the new structure. The design then waits for decisions that were never assigned.
Create a content inventory at the beginning. For every page, name the writer, approver, evidence source and deadline. Decide which content is retained, rewritten, consolidated or removed before development depends on it.
Speed up the project by reducing decision latency.
Choose one accountable decision owner and a small review group.
Approve the sitemap and one representative page before multiplying layouts.
Use real content early instead of designing around placeholder text.
Provide platform, analytics, domain and integration access during discovery.
Batch feedback into one prioritized response rather than several conflicting threads.
Define launch blockers separately from improvements that can follow safely.
Do not compress migration and quality assurance to protect a date.
Redirects, forms, analytics, structured data, responsive behavior, accessibility and lead delivery are part of the product. Cutting their verification to recover time can erase the value of the redesign or leave the business unable to measure it.
If the date is fixed, reduce the first-release scope instead. Launch a smaller complete system with a documented second phase rather than a large unfinished website whose most important customer and search paths are untested.
Website redesign and rebuild timeline FAQ.
How long does a complete website rebuild take?
A focused small-business redesign or rebuild often needs six to twelve weeks when strategy, copy, production development and migration are included. A complex rebuild with several content types, integrations, approval groups or data migrations commonly needs twelve to twenty-four weeks or more. These are planning ranges, not a delivery guarantee.
What usually delays a website rebuild?
The common critical-path delays are unresolved platform or ownership decisions, late content and proof, missing account access, unclear integration responsibilities, redirects prepared after development, and launch acceptance without one accountable owner. Track these dependencies separately from design and development effort.
Can a website rebuild launch in phases?
Yes, when each phase is a complete, measurable customer and operational path with clear URL ownership. A phased release should define which content and integrations move, how old and new systems avoid duplication, what is verified after launch, and when the temporary architecture will be retired.