Everything you need to know about templates, customization plans, implementation scope, operational limitations, support policies, and project workflows within the W-Forge system.
W-Forge Studio is a digital studio focused on professional website templates and customization services.
The studio helps clients adapt templates for real business projects through structured customization plans and additional implementation services when needed.
W-Forge focuses on template-based website development instead of fully custom projects from scratch.
This helps keep projects more organized, faster to launch, and more affordable compared to many traditional custom website workflows.
No.
W-Forge mainly works with existing templates and template-based customization.
Fully custom websites, applications, and large custom systems are handled separately as custom development requests.
The studio does not provide:
These types of projects are discussed separately when needed.
Each customization plan includes a specific amount of work.
This helps keep projects clear, organized, and easier to manage for both sides during the implementation process.
It means customization services are organized through clear plans with defined types of work included in each option.
This makes the process easier to understand before the project begins.
Unlimited revisions often make projects difficult to manage and slow down the implementation process.
Instead, customization is organized through structured plans that can always be expanded later if additional work is needed.
An implementation cycle is the amount of work included within a selected customization plan.
Additional customization can always be added later if the project needs further improvements or expansion.
The goal is to keep the project process clear and organized from the beginning.
Instead of endless revision loops, the work is completed within the selected customization scope, with the option to continue expanding the project later if needed.
The system is designed to keep projects more organized by using clear customization plans, structured workflows, and defined implementation scope.
This helps make the process easier to manage throughout the project.
Yes.
The studio works with startups, agencies, solo professionals, service businesses, and other clients looking for professional template-based website solutions.
Yes.
Templates and customization services are available for international clients depending on the project requirements and communication workflow.
Each purchase includes one licensed Webflow website template for one final website project.
The website is delivered as an editable Webflow project transferred to the buyer’s Webflow Workspace.
The downloadable Gumroad files contain the delivery instructions, license terms, and setup documentation.
The exact pages, CMS structure, components, assets, and features included are listed on the individual template page.
After payment, the buyer downloads the delivery instructions and license from Gumroad and provides the email address connected to their Webflow account.
W-Forge Studio prepares a customer copy of the purchased template and transfers it directly to the buyer’s Webflow Workspace.
A Webflow account and Workspace are required to receive the template.
No.
The downloadable Gumroad files contain the license, delivery instructions, and supporting documentation. The editable website itself is delivered separately as a Webflow project transferred to the buyer’s Workspace.
Yes.
Templates are sold as standalone digital products and can be used independently without purchasing customization services.
Yes.
Templates are provided in the condition and structure shown in the preview at the time of purchase.
Yes.
Templates can be customized independently or through additional customization services if professional help is needed.
Most templates are designed to be easy to work with, including for users with limited technical experience.
However, some familiarity with website editing platforms may still be helpful.
All website templates currently sold by W-Forge Studio are built in Webflow and delivered as editable Webflow projects.
A Webflow account is required to receive, edit, and publish the purchased template.
W-Forge Studio templates are delivered without CMS functionality by default. CMS can be added separately through the appropriate CMS Extension.
CMS installation for a W-Forge Studio template can begin only after the purchased template has been transferred to the client’s Webflow Workspace. The client must activate a Webflow Site plan that supports the required CMS functionality and provide W-Forge Studio with the necessary project access.
When W-Forge Studio customizes a third-party Webflow template that already contains CMS Collections, a separate CMS Extension is not required for ordinary content replacement or visual customization within the existing CMS structure.
A CMS Extension is required when the existing CMS must be expanded or restructured, or when the project requires new Collections, new dynamic content types, new Collection Template Pages, additional relationships, filtering, or other CMS functionality.
The appropriate CMS Extension is selected after reviewing the required structure and complexity.
Templates may include demo content, images, graphics, and videos used to present the design and page structure.
The right to reuse individual media assets depends on their original license. Any assets intended only for preview purposes must be replaced before the website is published.
Available asset information is provided with the template documentation where applicable.
One template purchase includes one license for one final website project.
The same template may be customized and used for one personal project or one client project under a single license.
If the template is used for:
additional licenses are required.
Templates may be freely customized for the licensed project, but they cannot be resold, redistributed, shared, or republished as standalone template products.
Yes.
Templates are designed and structured for responsive behavior across modern desktop, tablet, and mobile devices.
However, final responsiveness may also depend on:
Yes.
Basic multilingual translation can be generated during the multilingual setup process using AI-assisted translation tools as part of the implementation workflow.
If the client prefers custom-written translations, professional localization, or manually prepared language versions, the translated content can also be provided separately by the client.
Additional language editing, advanced localization, or custom translation work may require separate discussion depending on the project requirements.
Templates are built with basic SEO structure in mind, including semantic layout organization and editable metadata fields where supported.
Yes.
You can edit, customize, and adapt the template for your own project after purchase.
If the template is modified incorrectly, some functionality, layouts, responsiveness, animations, integrations, or visual structure may stop working properly.
Professional customization or technical assistance may then be required to restore, rebuild, or restructure the affected parts of the template.
In such cases, additional customization plans or extensions may need to be purchased depending on the amount of required work.
No.
Support does not include troubleshooting or fixing custom modifications made after purchase.
A template bug refers to a problem that exists in the original template before any client modifications are made.
This may include broken layouts, missing functionality, or technical issues present in the original delivered version.
Bug fixes are provided only for the original template structure and functionality in the condition it was delivered.
If the template has been modified, edited, restructured, or affected by third-party code, fixes and corrections are handled through paid customization services.
If third-party code, external scripts, plugins, integrations, or independently added functionality affect the template structure, responsiveness, animations, layouts, or functionality, the original template may stop working correctly.
Such issues are not considered template bugs or original template errors.
Restoring, rebuilding, correcting, or restructuring affected parts of the template may require paid Customization Pro services, additional customization plans, or extensions depending on the amount of required work.
Restoring, rebuilding, correcting, or restructuring affected parts of the template may require paid Customization Pro services, additional customization plans, or extensions depending on the amount of required work.
Free support is provided only for correcting verified bugs or technical errors that exist in the original template source version before any client modifications are made.
Support without paid customization is generally limited to verified template bugs or original technical issues.
No.
Additional implementation help, modifications, integrations, and project improvements are handled through paid customization services.
Once a template is heavily modified, original support eligibility may no longer apply because the project structure has changed from the original delivered version.
Template updates may be released when W-Forge Studio makes improvements, corrections, or compatibility adjustments to a supported template.
Existing customers can receive available template updates without purchasing the same template again. Lifetime updates do not guarantee a fixed update schedule or continuous development of new features.
Updates are not applied automatically to Webflow projects already transferred to client Workspaces. Installing or adapting an updated version within a customized client project may require separate paid work.
Templates are built directly in Webflow and use the platform features available at the time of delivery.
Future Webflow updates may affect individual features, integrations, or project behavior. Updates are not applied automatically to template copies already transferred to client Workspaces.
If a future platform change requires technical adjustments, the necessary work is reviewed separately.
Yes.
After purchase, W-Forge Studio prepares a customer copy of the template and transfers it to the Webflow Workspace connected to the email address provided by the buyer.
After accepting the transfer, the buyer controls the project in their own Workspace.
Professional customization and implementation services can be requested separately if needed.
After receiving the template, the client can contact W-Forge Studio through the website chat or project request form and describe the required changes.
The studio reviews the requested scope and recommends the appropriate customization package and any required extensions.
After the scope has been agreed, the client receives a secure payment link. Work begins after payment.
If the template has already been transferred, the client provides W-Forge Studio with guest access to the relevant Webflow project. The project remains in the client’s Workspace, and no account password is required.
Professional Customization is a paid service for adapting a W-Forge Studio or third-party Webflow template to a real business project.
It may include content and branding replacement, visual adjustments, layout changes, structural changes to approved sections, additional sections, responsive improvements, multilingual setup, and work with existing CMS structures.
New or expanded CMS functionality requires the appropriate CMS Extension. The project scope is reviewed and agreed before payment.
Customization uses either a W-Forge Studio Webflow template or a third-party Webflow template purchased from another seller as the foundation of the project.
Full custom development creates a new design system, website structure, functionality, or platform from scratch. Requests that exceed reasonable template-based customization are reviewed separately.
Requests involving fully custom platforms, applications, SaaS systems, backend infrastructure, advanced custom-coded systems, large standalone architectures, or functionality that cannot reasonably be implemented within an existing Webflow template are reviewed separately as custom development requests.
A section is an individual content or visual block within a page layout.
Examples may include:
Section modification means changing the existing structure, layout, content arrangement, visual composition, functionality, or organization of a section beyond standard content and branding replacement while preserving its original structure.
Section-level customization means applying structural or visual changes to individual sections within an existing template rather than rebuilding the entire website structure from scratch.
Modification limits are measured as a percentage of the sections included in the selected template:
The specific sections and required changes are agreed before payment.
This approach keeps the project scope, pricing, and implementation process predictable. It also allows clients to choose the appropriate level of customization without paying for a completely custom website build.
Yes. Some section modifications may be simple, while others may involve larger visual or structural changes.
All modifications must remain within the agreed project scope. New functionality, integrations, CMS architecture, or other additional requirements may require the appropriate Extension or separate paid work.
No. Once a section is included in the agreed customization scope, deeper editing of that section does not consume an additional section allocation.
However, the work must remain within the approved result for that section. New functionality, additional sections, or requirements introduced after the scope has been agreed are treated as additional work.
Each customization package and Extension has a clearly agreed implementation scope. Once that scope has been completed, the purchased work is considered delivered.
Further expansion may require:
The studio performs the requested implementation work for each approved modification point within the purchased customization scope.
If the client later requests repeated rework of the same sections by changing the originally approved conditions, experimenting with alternative versions, repeatedly changing direction, or demanding additional improvements without new implementation justification, such requests may increase the amount of work beyond the originally approved scope.
In such cases, the project may require:
The final decision regarding such additional work is determined individually by the studio team and the responsible implementation specialist.
If the project requires additional work beyond the included scope of the purchased plan, further implementation requires the purchase of additional customization plans or the required extensions.
Yes.
Projects can be expanded at any time through the purchase of additional customization plans and the required extensions depending on the amount and type of work needed.
Customization plans are organized around fixed amounts of work and clearly defined implementation scope.
This helps keep projects understandable, transparent, and easier to manage throughout the customization process for both the client and the studio.
Projects are organized through structured plans, clearly defined implementation scope, and staged customization workflows.
Essential Webflow Template Setup is designed for adapting the template to the client’s content and branding without changing the existing page structure
Content replacement is included in Essential Webflow Template Setup only when the new content is reasonably comparable in size to the original template content and does not require layout, spacing, card, grid, or responsive adjustments.
This may include:
Essential Webflow Template Setup does not include:
Essential Webflow Template Setup assumes that replacement text does not exceed the original text volume and does not require larger font sizes.
If the new content exceeds the original text volume, requires larger font sizes, additional elements, or any structural modifications, the project may require re-evaluation and a different customization plan.
If the final content exceeds the original layout capacity and requires structural or responsive modifications, the affected section may be reclassified as a structural modification and additional customization may be required.
Structural or layout changes require a higher customization package. New or expanded CMS functionality and multilingual setup require the corresponding Extensions.
No.
Essential Webflow Template Setup does not include section modification or restructuring.
The existing template structure remains unchanged.
Essential Webflow Template Setup allows content and visual adaptation within the original template structure.
This may include:
No.
Layout restructuring and section modification are not included in Essential Webflow Template Setup.
Essential Webflow Template Setup includes replacing content, images, logo, favicon, contact information, and links within the original template structure.
Content, images, logo, favicon, contact information, links, brand colors, and basic typography can be adapted within the original template structure. Structural changes, section restructuring, and major visual redesign are not included.
Webflow Template Customizationallows deeper customization of the template structure and visual layout.
This may include:
Webflow Template Customization allows modification of up to 50% of the sections within the project scope.
Once a section enters the customization process, the required work for that section is performed within the scope of the selected plan.
Each section that requires structural, visual, functional, or layout modification is counted as a modified section within the project scope.
When you contact the website chat to determine the most suitable customization plan for your project, the system analyzes the sections within the purchased template together with the requested project modifications and calculates the required implementation scope automatically.
Based on this analysis, the appropriate customization plan and required extensions are recommended for the project.
For this reason, the studio recommends using the website chat when selecting the required customization plan.
Yes.
Webflow Template Customization may include significant visual and structural changes within the included section modification scope.
Yes.
Webflow Template Customization allows partial layout restructuring and section reorganization within the included scope of the plan.
If more than 50% of the template’s sections require structural modification, the project requires the Advanced Webflow Customization package. Extensions are purchased separately only when the project also requires functionality covered by a specific Extension.
Advanced Webflow Customization allows full customization of the template structure within the included project scope.
This may include:
No.
Advanced Webflow Customization includes up to 100% section modification within the project scope, but it does not include unlimited revisions or unlimited ongoing work.
It means all sections within the project scope may be customized, modified, or restructured as part of the implementation process.
Yes.
Advanced Webflow Customization allows complete transformation of pages within the included project scope.
Advanced Webflow Customization still works within the limits of the purchased implementation scope.
Backend systems, applications, SaaS platforms, and large custom-coded infrastructures are not included.
Advanced Webflow Customization does not include:
These requests are handled separately as custom development work.
A project becomes custom development when it requires building completely new systems, advanced backend functionality, standalone platforms, applications, or large custom infrastructures beyond template-based implementation.
Extensions are additional implementation services that expand the customization scope of a project beyond the standard customization packages.
They are used when a project requires additional functionality, infrastructure, languages, pages, integrations, or implementation work not included in the purchased package
Extensions help expand projects gradually without requiring a complete rebuild or unnecessary overpayment for work that is not needed.
They also make it easier to calculate and organize additional implementation scope during the customization process.
Yes.
Extensions can be purchased at any stage of the customization process if the client wants to continue expanding, restructuring, improving, or modifying the project beyond the amount of work included in the purchased customization package or previously purchased extensions.
No.
Many projects can be completed within a standard customization package without additional extensions.
Extensions are only used when the project requires additional implementation scope or functionality.
CMS Extensions are additional services used to create or expand Webflow CMS functionality within a website or template project.
This may include:
No.
HTML templates do not include built-in CMS functionality by default.
CMS functionality is added separately through CMS Extensions during the customization process.
The client is responsible for activating and maintaining a Webflow Site plan that supports the required CMS functionality. CMS work is performed in the client’s Webflow Workspace after W-Forge Studio has been provided with the required project access.
Not when the third-party Webflow template already contains the required CMS structure and the work is limited to content replacement or visual customization within that existing structure.
A CMS Extension is required when the existing CMS must be expanded or restructured, or when new CMS Collections, dynamic content types, Collection Template Pages, relationships, filtering, or other CMS functionality must be created.
Simple CMS Integration includes:
Examples:
Advanced CMS Integration includes:
Premium CMS Integration is intended for large or complex CMS structures requiring advanced dynamic content organization, expanded content architecture, and multi-level CMS implementation within the project structure.
Multilingual Extensions are services used to create multilingual versions of a website or template project.
Yes.
Basic multilingual translation can be generated during the implementation process using AI-assisted translation tools.
Clients may also provide their own translated content if preferred.
However, multilingual implementation still requires additional setup and integration work, including:
Multilingual adaptation of an existing CMS structure may be included. Creating new CMS Collections or expanding or restructuring the existing CMS requires the appropriate CMS Extension.
For this reason, multilingual projects are handled through separate Multilingual Extensions regardless of whether the translated content is generated during implementation or provided by the client.
If the selected multilingual solution requires a paid Webflow Localization plan or another service subscription, the client is responsible for purchasing and maintaining it before implementation begins.
Includes:
Includes:
Includes:
Page Customization Extensions are used when a client needs additional customization work beyond the limits of the purchased customization package.
These extensions are intended for deeper customization of existing template pages and existing page structures.
They are typically used when:
A Page Customization Extension is appropriate when only one existing page requires a higher level of structural or visual customization and upgrading the entire project to a higher customization package would be unnecessary.
For example, most pages may remain within Essential Webflow Template Setup, while selected pages receive Advanced Page Customization or Premium Page Customization.
No.
Page Customization Extensions apply only to existing template pages and existing page structures.
Creating completely new pages from scratch is considered separate development work and is discussed individually outside the standard customization system.
Advanced Page Customization is an extension designed for projects where a specific existing page requires deeper customization without upgrading the entire website to the Advanced Customization package.
Advanced Page Customization includes:
Advanced Page Customization does not include:
Premium Page Customization is an extension designed for projects where a specific existing page requires Premium-level customization without upgrading the entire website to the Premium Brand & Website Setup plan.
Premium Page Customization includes:
Premium Page Customization does not include:
Yes.
Page Customization Extensions may be applied to approved connected page groups listed in the template structure when the same customization logic and implementation structure are used consistently across those related pages.
No.
These extensions apply only to existing template pages and existing template page structures.
Creating completely new pages from scratch is considered separate development work and is discussed individually outside the standard customization system.
Before customization begins, the client must provide all required project materials needed for implementation.
This may include:
No.
The client is responsible for providing the content required for the project unless separate content creation services are discussed individually.
Yes.
Clients may provide their own:
The client is responsible for the accuracy, legality, ownership, and quality of all provided project materials.
No.
The client is responsible for ensuring they have the legal right to use all provided content, media, branding assets, and materials.
Missing materials may delay the implementation process until the required project assets are provided.
Yes.
Temporary placeholder content may be used during implementation if the final project materials are not yet available.
Yes.
Each language version requires separate translated content unless AI-assisted translation is used during the multilingual implementation process.
Yes.
Basic AI-assisted translation may be used during multilingual implementation depending on the project requirements and selected extensions.
The client is responsible for reviewing and approving all translated content before final publication.
Major content changes after implementation has started may require additional customization package or extensions depending on the amount of additional work created by those changes.
Yes.
Project materials should be provided in a clear, organized, and implementation-ready format whenever possible.
Basic content organization may be possible during implementation, but heavily unstructured, incomplete, or disorganized materials may require additional customization scope.
Yes.
The client is responsible for providing the final versions of:
Yes.
Downloadable files such as PDFs, brochures, guides, presentations, or documents can be integrated into the project when provided by the client.
The standard customization system does not include:
Such requests are discussed separately outside the standard customization workflow.
No.
Clients are expected to provide their own logo and branding materials unless separate design work is discussed individually.
No.
Customization plans focus on adapting templates for implementation purposes and do not include full branding development.
No.
Marketing strategy, advertising campaigns, SEO consulting, and business strategy services are not included in the standard customization system.
The standard customization system focuses on website implementation and template customization.
Basic website publishing and deployment to standard hosting environments may be possible depending on the project.
However, backend systems, server-side applications, databases, SaaS infrastructure, and complex server architecture are not included in the standard customization system and are discussed separately.
No.
Applications, SaaS platforms, and standalone software systems are outside the standard customization system.
No.
Large custom-coded systems and standalone technical infrastructures are handled separately as custom development work.
Basic third-party integrations may be included within customization plans or extensions when they work within the existing template structure.
Examples may include:
However, integrations requiring:
are treated as separate development work outside the standard customization system.
A project may become a Custom Development Request when it requires:
Creating completely new structures from scratch usually requires separate planning, architecture, design, and development processes beyond standard template customization.
Yes.
However, fully custom page development is treated as separate development work outside the standard customization system and is discussed individually.
Yes.
The studio may decline requests that fall outside the available implementation scope, technical direction, or operational structure of the studio.
Customization packages work within clearly defined implementation scope and measurable amounts of work.
This helps keep projects understandable, transparent, and manageable throughout the implementation process.
Projects are organized through customization plans, extensions, and clearly defined implementation scope.
Additional work beyond the purchased scope requires additional customization packages or extensions.
The implementation process usually follows these steps:
After payment, the studio contacts the client using the email address provided during the project discussion or payment process.
The agreed project scope and required materials are reviewed before implementation begins. Depending on the project, the required materials may include:
Once the required materials are received, the implementation process begins.
Projects are evaluated based on:
The required customization package is determined after the client submits the project requirements through the website chat or contact form.
The studio reviews:
Based on this review, the appropriate customization package and required Extensions are recommended.
Implementation is usually performed step-by-step according to the approved project scope and purchased customization package.
Sections included in the customization scope are processed individually based on the required implementation work for each section.
Yes.
However, additional changes beyond the purchased implementation scope require additional customization packages or extensions.
If the client requests additional work after implementation has started, the new work is reviewed separately.
If the requested changes exceed the purchased scope, continuing the additional work may require:
Additional work begins only after the new scope has been reviewed, agreed, and purchased.
Additional requests are evaluated separately based on the required implementation scope.
If additional work exceeds the purchased scope, additional customization packages or extensions are required.
A project is considered completed once the purchased implementation scope and approved customization work have been finished.
Yes.
After the amount of work included in the purchased customization package or extension has been completed, the customization project is considered finished.
If the client wants additional modifications, restructuring, improvements, or further work after that point, the client must purchase an additional customization package or extension.
Once the purchased implementation scope has been completed, any further work requires additional customization packages or extensions.
No.
Implementation timelines may vary depending on:
Projects are generally processed according to the current implementation queue, project scope, and active workload at the time of the request.
Templates are purchased through Gumroad using the purchase links provided on the website. After payment, the buyer receives delivery instructions and license terms through Gumroad. The Webflow template itself is transferred separately to the buyer’s Webflow Workspace after the buyer provides the email address associated with their Webflow account.
Template purchases are processed through Gumroad. Customization packages and Extensions are paid through a secure payment link sent by the studio after the project scope has been reviewed and agreed. Available payment methods may depend on the selected payment provider and the client’s region.
Refund eligibility depends on the purchased product or service, its delivery status, the amount of work already completed, the applicable refund policy, Gumroad’s rules, and mandatory consumer protection requirements. The applicable conditions are provided before purchase or included in the agreed project terms.
Customization services are provided through fixed customization packages and separately purchased Extensions. After the project requirements have been reviewed and the scope has been agreed, the studio sends the client a secure payment link.
Payment is required after the project scope has been agreed and before implementation begins.
No.
Template purchases, customization packages, and Extensions are paid in full before template delivery or implementation begins.
If the client stops communicating or does not provide the required materials, implementation may be paused. Completed work, payment conditions, and any later project restart are handled according to the agreed project scope, the applicable refund policy, and the project terms. Additional work required after the project resumes may require an additional customization package or the appropriate Extensions.
The purchased customization package or Extension includes the amount of work approved before implementation begins.
Minor adjustments, simple corrections, and small content updates may be performed during the implementation process if they remain within the purchased customization scope and do not create additional section modifications, restructuring, integrations, or expansion of the approved work volume.
Any new requests that:
are considered additional work that changes the original implementation conditions.
Such requests are reviewed separately by the studio team. Depending on the additional scope, the client may be offered a package upgrade, an additional customization package, or the appropriate Extensions.
For template purchases processed through Gumroad, payments, applicable taxes, and buyer receipts or invoices are handled through Gumroad. For customization services and Extensions, payment and invoicing are handled according to the agreed payment method and applicable regulations.
W-Forge Studio works with Webflow templates and Webflow-based website customization. Templates are delivered as Webflow projects rather than HTML or ZIP website downloads.
Yes. A Webflow account is required to receive the template in the client’s Webflow Workspace. The client must also provide the required project access when customization or CMS implementation is performed in their Workspace.
No.
Webflow hosting, subscriptions, workspace plans, and related Webflow services are paid separately by the client.
Yes. A template can be transferred to and edited in the client’s Webflow Workspace without a paid Site plan. A paid Site plan is required to publish the website to a custom domain. A Webflow staging subdomain may be used within the limits of the available Starter Site plan.
Templates are structured for modern responsive website performance and standard frontend optimization practices.
However, final performance may also depend on:
Some templates may include animations, transitions, interactive effects, or motion elements depending on the template design and structure.
Yes. Custom code may be added later depending on the project structure and agreed implementation scope. Some Webflow custom-code features may require an eligible Workspace plan or an active Site plan. More advanced functionality may require the appropriate Extension or a separately agreed development scope.
The studio is not responsible for failures, instability, API changes, subscription problems, platform limitations, or technical issues caused by third-party services or external integrations.
Additional troubleshooting or restructuring caused by third-party systems may require an additional customization package, the appropriate Extensions, or a separately agreed development scope.
Yes.
Templates are designed for responsive behavior across desktop, tablet, and mobile devices.
Yes. CMS structures may be created, expanded, or restructured through the appropriate CMS Extension. This work is performed after the template has been transferred to the client’s Webflow Workspace. The client must provide the required project access and maintain a Webflow Site plan that supports the required CMS functionality.
No.
External scripts, third-party plugins, external code libraries, and independently added integrations are not officially supported by the studio unless they were implemented directly as part of the purchased customization work.
Yes. A project may be transferred to another Webflow Workspace. Migration to another platform is reviewed separately because some Webflow-specific functionality may require rebuilding or separate content migration.
Basic accessibility practices may be considered during implementation where reasonably possible within the selected customization scope and template structure.
Free support covers verified technical errors in custom code originally included by the studio in the delivered template. Troubleshooting client-added custom code, third-party scripts, plugins, external integrations, or independently added functionality is not included in free support and is reviewed separately as paid work.
Technical support is limited to reviewing and correcting verified problems related to the original template structure or functionality.
A verified template bug is a technical problem that:
No.
Client-made modifications, restructuring, added integrations, custom code, or independently changed template structures are not covered by free error correction.
No.
Troubleshooting custom code, third-party scripts, external integrations, plugins, or independently added functionality is not included in free support.
Free support applies only to the original Webflow template structure, functionality, and technical implementation delivered by the studio.
Troubleshooting, fixing, or supporting:
is not included in free support and is handled through paid customization services.
No.
Ongoing maintenance, continuous updates, monitoring, administration, or long-term project management are not included after purchase.
Additional fixes, troubleshooting, restructuring, implementation work, and technical corrections are reviewed separately. Depending on the required scope, the studio may recommend a customization package, the appropriate Extensions, or a separately agreed development scope.
Additional implementation help, technical corrections, restructuring, integrations, project improvements, and post-purchase modifications can be requested through the website chat or contact form. The studio reviews the required scope and recommends the appropriate customization package, Extensions, or separately agreed development work.
Verified bugs or technical errors that exist in the original Webflow template delivered by the studio are corrected as soon as reasonably possible during the studio’s working hours based on Spain time.
Emergency fixes are not guaranteed for:
Such work may require an additional customization package, the appropriate Extensions, or a separately agreed development scope, depending on the required work.
Support requests are reviewed based on:
A request may be considered custom development when it requires:
Custom requests are reviewed individually based on:
Standard customization packages are designed for structured template customization within predictable implementation scope.
Custom systems, standalone applications, backend platforms, and completely new technical architectures require separate planning and development processes.
Yes.
However, completely new pages created from scratch are considered separate development work outside the standard customization system.
Yes.
However, fully custom systems are reviewed individually and are not included in standard customization packages or extensions.
Standard customization packages and extensions do not include:
Requests involving such systems are treated as separate custom development work.
Standard customization packages and extensions do not include:
Embedding or connecting standard third-party services inside the existing template structure may be possible if they work without rebuilding the project architecture.
Requests involving external application logic, platform infrastructure, or independently managed external systems are treated as separate custom development work.
Yes.
If a project grows beyond the limits of structured template customization, it may later transition into separate custom development work depending on the client’s goals and technical requirements.
Custom development projects are evaluated and priced individually based on:
No.
The studio may decline requests that:
Custom development projects usually require individual evaluation, planning, technical architecture discussion, and separate implementation strategy beyond the standard customization system.