Before you send the brief, read this
Project fit assessment
What kind of companies do you work with?
Igorev works with B2B companies, SaaS teams, technology companies, professional services, agencies and premium digital brands that need a clear, scalable Webflow website. We are usually a good fit for teams that need stronger website structure, sharper positioning, cleaner design, reliable Webflow development, CMS flexibility and long-term control after launch. We also work with selected B2C, ecommerce, healthcare, real estate, hospitality, media and service-based businesses when the project needs a premium website and a structured process.
Are you only focused on B2B, SaaS and technology companies?
No. B2B, SaaS and technology companies are a strong part of our positioning because those projects often need structure, CMS logic, clear messaging and scalable Webflow systems. That does not mean we only work in those markets. We also work with premium consumer brands, service businesses, healthcare, wellness, real estate, logistics, ecommerce and creative companies when the project fits our standards. The main filter is not the industry. The main filter is whether the website needs clarity, structure, quality execution and a serious approach.
What makes a good client fit for Igorev?
A good fit usually has a clear business reason for the website work. That can mean launching a new website, redesigning an outdated site, moving from another platform to Webflow, cleaning up a messy CMS, improving SEO structure, preparing a better marketing site, or turning a rough AI-built MVP into something more polished and usable. We work best with clients who want a reliable partner, clear communication and quality work rather than the cheapest possible execution.
Who is not a good fit?
We are probably not the right fit if you need the cheapest possible website, tiny one-off edits with no clear scope, unlimited revisions, or a team that simply says yes to every idea without thinking through the impact. We are also not the right fit if decisions cannot be made, content is not available, or the project needs to move without clear feedback and approvals. Good website work needs trust, structure and decision-making on both sides.
What makes Igorev different?
Igorev is a founder-led Webflow agency focused on clear website structure, clean execution and long-term control after launch. We are not trying to be a large agency with unnecessary layers. We stay focused so clients can work closer to the people responsible for the result. The work combines website strategy, UX/UI design, Webflow development, CMS architecture, SEO-ready structure, integrations, motion and launch support.
Why not just hire a freelancer?
A good freelancer can be a strong choice for isolated tasks. But a full website often needs more than one skill. Strategy, UX, design, Webflow development, CMS planning, SEO setup, responsive QA, integrations and launch support all need to work together. Igorev gives you one structured process, shared context and a consistent standard from planning to handoff.
Why not hire in-house?
Hiring in-house makes sense when you need the same role every day for years. For a website project, that is often not the case. You may need strategy, design, development, CMS, SEO and QA for a focused period, not a permanent internal department. Working with Igorev gives you access to a flexible website team without building that whole setup internally.
Project scope overview
What do you actually help with?
We help with full website projects, website design, Webflow development, Figma to Webflow, Webflow redesigns, Webflow migration, landing pages, CMS architecture, SEO & AEO setup and AI MVP cleanup. Depending on the project, we can also help with content structure, visual assets, icons, AI-assisted imagery, Lottie, GSAP interactions, forms, analytics, third-party integrations and launch preparation. Some clients hire us for one focused service. Others need the full website process from early structure to launch.
Do you design only, or can you also build?
We can do both. Some clients come to us for website design only. In that case, we focus on structure, UX, visual direction, responsive layouts and a build-ready Figma file. Other clients need the full Webflow build too. In that case, we take the project through development, CMS setup, integrations, QA and launch support.
Can you work from an existing Figma design?
Yes. If your design is already approved, we can handle Figma to Webflow development. Before development starts, we review the design structure, responsive behavior, CMS needs, interactions, assets and technical requirements. If something is missing or unclear, we flag it early instead of discovering problems halfway through the build.
Can you redesign an existing website?
Yes. Webflow redesigns are one of the main types of projects we handle. A redesign can include updated structure, page hierarchy, UX improvements, visual design, CMS planning, new Webflow development, SEO-safe redirects and launch support. The goal is not only to make the website look newer. The goal is to make the website clearer, easier to manage and better aligned with how the business works now.
Can you migrate a website to Webflow?
Yes. We can migrate websites from WordPress, Wix, custom code, older Webflow builds or other platforms into a cleaner Webflow setup. Migration needs to be planned carefully. We review the current structure, content, URLs, CMS needs, SEO risks, redirects, forms, integrations and launch requirements before rebuilding the site.
Can you help with Webflow CMS architecture?
Yes. CMS architecture is important when a website needs case studies, blog posts, services, industries, locations, team pages, resources, filters or dynamic landing pages. We plan the collections, fields, templates and relationships so the website can grow without rebuilding the same layouts again and again. A good CMS should make the site easier to update, not harder to manage.
Can you help with SEO and AEO?
Yes. We can help structure Webflow websites for search engines and answer engines. This can include metadata, headings, internal linking, schema recommendations, FAQ structure, page hierarchy, redirects, indexation checks, Google Search Console setup, GA4, technical cleanup and answer-ready content blocks. SEO is strongest when it is planned before launch, not added after the site is already built.
Can you help with AI-generated websites or MVPs?
Yes. If you used AI tools, templates, no-code builders or vibe-coding to create a rough MVP, we can help clean it up. That can mean improving UX, redesigning the interface, rebuilding parts in Webflow, organizing content, cleaning the visual system, improving responsiveness, setting up CMS logic and preparing the site for a more serious launch. AI can help you start faster. We help make the result clearer, cleaner and more usable.
Can you work with our existing team?
Yes. We can work with founders, marketers, internal designers, product teams, developers, SEO specialists or external agencies. Sometimes we lead the full website process. Sometimes we design while your developers build. Sometimes we handle Webflow development from your existing Figma file. Sometimes we support one specific part of the project. The important part is clear ownership, clear feedback and clear approval points.
Pricing and payment
How much does a website project cost?
Monthly sprint engagements typically begin in the $4k–$8k/month range for dedicated senior design and Webflow support. For projects that involve larger-scale websites, sophisticated CMS setups, custom functionality, third-party integrations, advanced interactions, SEO execution, or several concurrent initiatives, pricing is adjusted to reflect the scope and complexity of the work. Every engagement is tailored around the outcomes required, the level of expertise involved, and the most efficient way to move the project forward — rather than fixed hourly allocations or unlimited request models.
Do you charge hourly or fixed price?
Both are possible. For clearly defined website projects, we usually work with a fixed project price based on the agreed scope. For smaller updates, consulting, ongoing improvements or flexible support, we can work hourly. The pricing model is chosen based on what gives the clearest structure for the work.
Do you require an upfront payment?
Yes. After the scope, timeline and price are agreed, we request a 50% advance payment before starting. The remaining 50% is paid after project approval and before the final project transfer. This keeps the process clear for both sides and protects the project timeline.
What is included in the price?
The price includes only the agreed scope. Depending on the project, that may include strategy, sitemap, wireframes, website design, Webflow development, CMS setup, responsive adaptation, animations, basic SEO setup, integrations, QA, launch support and handoff. Third-party tools, paid fonts, stock assets, Webflow hosting, apps, plugins, external subscriptions or paid integrations are not included unless clearly agreed in the scope.
What counts as additional work?
Any request that expands the approved scope is treated as additional work. Examples include new pages, new sections, new functionality, extra CMS collections, additional animations, major layout changes after approval, new integrations, new content work or changes to already approved stages. We support revisions inside the agreed scope, but scope expansion is estimated separately.
Can we start small?
Yes. A smaller first step can be useful when the project is not fully clear yet. That can be a website audit, structure review, design direction, landing page, CMS planning, Figma to Webflow build or focused Webflow cleanup. Starting small is useful when you need clarity before committing to a larger website project.
Process and communication
What happens after I reach out?
First, we review your current website, brief, goals, timeline and materials. Then we clarify the scope, recommend the right service and explain what the project would require. If there is a good fit, we agree on the scope, timeline and price. After the first payment and required materials are received, we start the work.
What is your usual project process?
The process depends on the service, but most projects follow a clear sequence:
- Discovery and scope
- Structure and content planning
- Website design or design review
- Webflow development
- CMS setup and integrations
- Responsive QA and SEO checks
- Launch preparation and handoff
At each key stage, we share interim drafts for approval before moving forward.
How do revisions work?
Each stage includes one-two rounds of revisions. This means we collect feedback, apply the requested changes inside the agreed scope and move forward after approval. Once a stage is approved, we do not revisit it unless requested. Changes to approved stages are treated as additional work and charged separately. This keeps the project moving and prevents late-stage changes from disrupting the timeline.
How do you communicate during the project?
We keep communication structured and direct. Depending on the project, we use email, Google Meet, Figma comments, Notion, Webflow comments, shared documents or other tools agreed at the start. You will see progress at each major stage, and we will flag unclear points before they become bigger issues.
How often do we have calls?
Calls depend on the project scope. Some projects only need a kickoff call and review calls. Larger projects may include regular syncs during design, development and launch preparation. We avoid unnecessary meetings, but we use calls when they help make decisions faster.
Who will I work with?
Igorev is founder-led, so you work close to the people responsible for the result. Depending on the scope, the project may involve Webflow developers, UX/UI designers, SEO specialists, content support, motion designers or technical partners. We do not add people just to look bigger. We add people when the work needs them.
What do you need from us to start?
Usually we need a clear goal, your current website if there is one, brand materials, content or draft copy, references, design files if they exist, access to required platforms, and one person who can collect feedback and approve decisions. You do not need everything perfectly prepared before the first conversation. But before production starts, missing materials can affect the timeline.
What can slow the project down?
The most common blockers are slow feedback, unclear decision-making, missing content, changing priorities, late scope changes, missing access, or too many people giving conflicting feedback. We can move quickly when the scope is clear and feedback is consolidated. Good websites are not only built by the agency. They are built through a clean process on both sides.
Timelines
How fast can you start?
Start time depends on current availability and the scope. Sometimes we can begin within a few days. Larger projects may need to be scheduled a few weeks ahead. If your timeline is urgent, we will tell you what is realistic and what can be done without damaging the quality of the work.
How long does a typical website project take?
A focused landing page or small Webflow development task can take days or a few weeks. A full website project usually takes several weeks, depending on the number of pages, design complexity, CMS structure, content readiness, integrations, revisions and launch requirements. We define the timeline before the project starts and adjust only if the scope changes or required materials are delayed.
Can you work on urgent launches?
Sometimes, yes. Urgent projects require a tighter scope, faster feedback and clear priorities. They may also require a higher rate depending on the timeline. If everything cannot be done properly before the deadline, we will help separate what needs to launch now from what can wait for a second phase.
Do you work in phases?
Yes. Phased work is often the cleanest way to handle larger websites. For example, the first phase can include the homepage, core pages, CMS structure and launch essentials. Later phases can include additional landing pages, case studies, resources, integrations or SEO content. Phases help launch faster without forcing everything into one overloaded scope.
Ownership, Webflow and launch
Do we own the website after the project?
Yes. After the final payment is received, the agreed deliverables belong to you. For Webflow projects, we transfer the project to your Webflow account after full payment. We can also help connect the hosting plan and domain if that is part of the agreed scope.
Why do you build on your Webflow account first?
We usually start development inside our own Webflow account to keep production clean, controlled and efficient. After the website is approved and the final payment is completed, we transfer the project to your Webflow account. This is a standard part of our process and keeps ownership clear.
Can we edit the website ourselves after launch?
Yes. That is one of the main reasons we use Webflow. We structure websites so clients can update content, CMS items, case studies, blog posts, services, industries or other dynamic content without asking a developer for every change. For more complex design or layout changes, developer support may still be needed.
Do you provide training?
Yes. After launch or before handoff, we can provide a walkthrough explaining how to manage key parts of the site. This can include editing pages, updating CMS content, publishing posts, replacing images, managing forms or understanding the basic Webflow setup.
Do you handle hosting and domain setup?
Yes, if included in the scope. For Webflow websites, hosting is handled through a Webflow hosting plan. We can help connect the domain, configure DNS records, connect SSL and publish the site. Webflow hosting, domain fees and third-party subscriptions are paid by the client.
Can you export the site from Webflow?
Webflow allows code export for static pages on certain plans, but CMS content and Webflow’s editor experience do not transfer in the same way. If you need to keep CMS editing, hosting on Webflow is usually the right setup. If you export and host elsewhere, you may lose the ability to manage the site easily through Webflow.
Do you help after launch?
Yes. After the project ends, we remain available for questions, fixes, improvements and additional tasks. Small post-launch support can be handled hourly or as a separate scope. Larger ongoing work can be planned as a monthly support arrangement.
Do you offer ongoing support?
Yes. Ongoing support can include new pages, CMS updates, landing pages, SEO improvements, design improvements, integrations, analytics setup, performance checks or general Webflow maintenance. This is useful when the website will continue evolving after launch.
Legal and practical details
Do you sign NDAs?
Yes. We can sign an NDA before reviewing private materials, unreleased products, internal documents, roadmaps, financial information or sensitive project details.
Can you work with confidential or unreleased projects?
Yes. We can work with private websites, unreleased SaaS products, internal tools, confidential campaigns, fundraising materials and projects that are not ready to be public. If the work is confidential, we will not publish it in our portfolio without permission.
How do you handle third-party tools, fonts and assets?
If the project uses paid fonts, templates, plugins, scripts, stock images, AI tools, Lottie files, icons, libraries or third-party integrations, we clarify what is included and what needs to be purchased or licensed separately. No one wants licensing problems after launch.
Can you use our existing tools?
Yes. We can work with your existing tools when needed. This can include Figma, Webflow, Notion, Google Drive, Slack, Google Meet, Calendly, HubSpot, Airtable, Zapier, Make, GA4, Google Search Console and other tools depending on the project. We do not force a new workflow if your current setup works.
What if we already have content?
Good. We can work with your existing content and structure it for the website. If the content is rough, outdated or too long, we can help organize it, recommend edits and shape it into clearer page sections. If full copywriting is required, it should be included in the scope.
What if we do not have content yet?
That is common. We can help define what content is needed for each page, create structure, suggest section logic and help organize rough notes into a usable content direction. Full copywriting, content strategy or SEO content production can be included as a separate part of the scope.
Still got questions?
Send us the context and we will tell you what makes sense.
Share your website, idea, Figma file, current problem or launch goal. We will help you understand whether Igorev is the right fit, what the project needs and what the next step should be.





