Discovery, design, build, QA, launch. In that order, every time.
This page is the whole process with the dates attached. If another agency will not show you theirs at this level of detail, that is worth asking about.
- Stages
- Five, always
- Typical build
- 3 to 12 weeks
- Revision rounds
- Two, included
- Post-launch cover
- 2 weeks, free
What happens, in what order, and roughly when
Nothing here is compressed or skipped to hit a date. If a stage needs longer we tell you in the Friday update rather than at the end.
Discovery
3 to 5 daysBefore anything is drawn we work out what the site has to do for the business, and what is stopping the current one from doing it.
- A 90 minute workshop with whoever owns the decision, not a proxy
- A crawl of your existing site: broken links, duplicate titles, page speed, the URLs worth keeping
- Analytics review where you have it, so we know which pages already earn their keep
- A one-page brief naming the audience, the inquiry path and the pages we will build
- A fixed price and a dated schedule, both signed before design starts
Design
1 to 3 weeksStructure before decoration. We agree the shape of every page as a wireframe, then design it properly once, rather than redecorating a guess.
- Sitemap and wireframes for every unique template, reviewed on a call
- Visual design at 1440px, 768px and 390px so nothing is invented later
- A small design system: type scale, color roles, spacing, buttons, form states
- Comments left directly on the Figma file, with a written response to each one
- Two revision rounds included; a third is quoted rather than absorbed silently
Build
2 to 5 weeksThe Webflow build itself. A staging link goes live on the first day so you can watch the site assemble instead of waiting for a reveal.
- Global classes and variables set up first, page templates second
- CMS collections modeled, fields labeled, and your real content migrated in
- Forms, filtering, conditional visibility and any Logic or third-party wiring
- Custom CSS and JavaScript only where Webflow genuinely stops, and documented when used
- Weekly written update every Friday, whether or not there is good news
QA
3 to 5 daysA full pass against a written checklist. This is the stage most agencies compress, and it is the reason clients find broken pages a month after launch.
- Every page at 360px, 768px, 1024px, 1440px and 1920px, in Chrome, Safari, Firefox and Edge
- Keyboard-only run through the whole site, including every form and the navigation
- Automated accessibility scan plus a manual check of contrast, focus order and labels
- Lighthouse and PageSpeed run on each template, with the numbers written down
- Every form submitted for real, to confirm it lands where it is supposed to land
Launch
1 day, then 2 weeks on callWe do the DNS switch with you on a call, watch the first traffic arrive, and stay close while the search engines catch up.
- A 301 redirect for every URL on the old site, tested before the switch
- DNS and SSL moved in a scheduled window, usually early morning
- Sitemap submitted, Search Console and GA4 confirmed to be receiving data
- A recorded handover walkthrough plus written notes for your team
- Two weeks of same-day fixes at no cost, then a maintenance plan if you want one
Webflow, and as little else as we can get away with
Every tool below is on this list because it solved a problem we could not solve in Webflow itself. We add nothing for novelty, and nothing that would leave you dependent on a subscription you did not choose.
Where we do write custom code, it is plain CSS and vanilla JavaScript, commented, and sitting in your project rather than on a server we control. No build step, no framework, nothing that stops working when we stop working together.
- Platform
- Webflow Designer and CMS
- Webflow Logic for form routing and conditional flows
- Webflow Users where a genuine members area is needed
- Webflow Ecommerce for small, simple catalogues
- Extensions we trust
- Finsweet Attributes for filtering, pagination and accessibility fixes
- Jetboost when native CMS filtering runs out of road
- Swiper for the carousels we could not talk you out of
- Custom code
- Hand-written CSS and vanilla JavaScript, no framework
- Commented in the project so the next developer can read it
- Used only where Webflow genuinely stops, never for convenience
- Integrations
- HubSpot, Pipedrive and Salesforce form handoff
- Zapier or Make for anything without a native connector
- Calendly, Cal.com or your own scheduler, with parameters passed through
- Stripe or Foxy where payments are simpler than full ecommerce
- Infrastructure
- Webflow hosting on AWS behind the Fastly CDN
- Cloudflare DNS where you already use it, otherwise the registrar you have
- SSL and platform patching handled by Webflow, not by you
- Measurement and QA
- GA4, Google Search Console and Looker Studio
- Microsoft Clarity for session replay on the pages that matter
- axe DevTools, Lighthouse, PageSpeed Insights and BrowserStack
- Figma for design, with the file transferred to you at handover
Example ranges, from projects we have actually run
These are the ranges we quote from. Your fixed date comes out of the scoping call, once we know how much of the content already exists.
| Project type | Typical range | What that covers |
|---|---|---|
| Campaign landing page | 2 to 3 weeks | One page, one offer, one form. Usually built inside an existing project. |
| Small business site, up to 6 pages | 3 to 4 weeks | Our Launch package. No CMS, because at this size it adds work rather than removing it. |
| CMS-driven site, up to 14 pages | 6 to 9 weeks | Our Build package. Services, locations, people and articles as collections, content migrated in. |
| Replatform from WordPress, 25+ pages | 8 to 12 weeks | Add a week for every 100 posts or products. The redirect mapping alone is usually four days. |
| Ecommerce or a members area | 10 to 14 weeks | Includes payment testing, order emails, tax and shipping setup, and a soft launch window. |
What actually moves the date
- Whether the copy exists
- This moves the date more than anything else, by a factor of two. Sites where the copy is written and signed off before build hit the early end of every range above.
- How many people approve things
- One decision maker is a three-week design stage. Five people with equal say is a six-week design stage, and no amount of process fixes that.
- Revision rounds beyond two
- Two rounds are included and built into the schedule. A third adds roughly a week and is quoted rather than quietly absorbed.
- Third-party integrations
- A native connector is an afternoon. A CRM with a custom field schema and a sandbox account we need access to is a week, most of it spent waiting for credentials.
- How much content moves across
- Under 40 items is included. Beyond that we script the migration where the source allows it and charge per item where it does not.
What people ask before signing off a build
These come up on almost every scoping call, so they are answered here rather than saved for the meeting.
Can you work from our existing brand or a Figma file we already have?
Yes. If you have a brand guide we design inside it rather than around it, and we will tell you where it does not stretch to a website — most print-first brands have no form states, no focus styles and no small-screen type scale. If you have a finished Figma file from another designer we will quote build-only, after a short audit to check it can actually be built responsively.
What if we do not have the copy written?
Then we work in placeholder-free stages: wireframes carry real headings and real sentence lengths so nothing has to be squeezed in later. You can write the copy yourself against our brief, or add copywriting at $450 a page. What we will not do is build around lorem ipsum and hope it fits.
Do you build in your workspace or ours?
Yours, from the first day. We ask you to create a Webflow workspace, invite us to it, and remove us whenever you like. It means the project, the CMS content and the hosting plan are all in your name, and switching to another developer is a one-click invite rather than a negotiation.
What happens to our old URLs at launch?
Every one gets mapped by hand. We crawl the existing site, export the full URL list with its traffic and ranking data, and write a 301 redirect for each page to its closest new equivalent. Pages that rank well keep their exact URL where we can. The redirect map is tested on staging before the DNS switch, not after.
Can Webflow handle a members area, gated content or ecommerce?
It handles simple versions of all three natively, and we build those regularly: gated resources, a small product catalogue, member-only pages with Webflow Users. Beyond a few hundred SKUs, or with complex subscription logic, we will tell you Webflow is the wrong tool and point you at Shopify or a headless setup rather than sell you a workaround.
Who owns the code and the design files?
You do. The Webflow project sits in your workspace, the Figma file is transferred to you at handover, and any custom CSS or JavaScript we write is documented in the project and yours to keep. There is no license, no lock-in and nothing that stops working if you part ways with us.
Send us your current site and we will show you the crawl
The first thing we do is crawl what you already have: broken links, duplicate titles, load times, and which URLs are worth keeping. You get that report whether or not you hire us.
- Phone
- (303) 555-0184
- Studio
- 2500 Larimer Street, Suite 210, Denver, CO 80205
We reply to every inquiry within one business day.