Webflow Builds, Held to a Launch Gate.
Five stages, brief to launch gate. Work with me direct and you get a senior developer without the agency markup. Work through your agency and the same build ships white label under your name. Scope and price are fixed before anything is built, and everything stays a draft until you approve publish.
How an Engagement Runs
Every engagement runs the same five stages. Small builds compress them, retainers loop the last two, and what does not change is the order: scope before build, audit before launch, measurement after it.
A build is quoted as one fixed price against a fixed scope and paid in milestones. A retainer runs monthly on a fixed scope. Neither is billed by the hour.
The Brief
You supply: design source (Figma or an existing site), brand assets, copy, and the deadline.
You get back: a fixed scope, a page inventory, a build order, and a fixed price, all of it signed off before anything is built.
Most builds from a finished Figma design ship in three to five weeks.
Not in a Build, so You Are Never Surprised by It
- Design is quoted separately from the build. If the Figma is not finished, that is its own scope, agreed first.
- A blog or any CMS system is a named line in the scope, never implied by "a site".
- Copy is yours to supply. I structure, publish, and verify it, and nothing ships without your approval.
- Off-site local SEO, meaning Google Business Profile and citations, stays with a specialist. I do the on-site half: LocalBusiness schema, consistent name and address, location pages.
- Paid media and ad operations are out.
- Brand and logo design are out.
- This is a Webflow practice, with the same SEO methodology on WordPress. Application code, backends, and native apps are not something I take on.
- Your tag manager, ad pixels, and chat widgets are measured and reported as a performance cost. They change only with your sign-off, because they carry your attribution.
The Build
You supply: approvals at the points you asked for them.
You get back: a staged site on a Webflow subdomain, a Client-First class system your team can keep editing, and CMS collections your editors can run without a developer.
The fixed price is paid in milestones tied to review points: the foundation and one finished page first, so a convention is corrected once rather than on every page, then the remaining pages, then technical QA, and the launch milestone is released after the site is live.
Built in your own Webflow workspace, so you own the site, the workspace, and the domain from day one.
The Audit
You supply: view-only access to Search Console and analytics if they exist. Optional, and the audit is sharper with them.
You get back: every finding with its fix, documented for your team, and the gate results before you approve publish.
The launch gate: Largest Contentful Paint under 2.5 s, Cumulative Layout Shift under 0.1, a single H1 with ordered headings on every page, JSON-LD that validates, and a redirect map with no chains.
One honest definition. Core Web Vitals at handover means a passing mobile PageSpeed run on every template. Google's field data needs 28 days of real visitors, so I confirm it in Search Console over the weeks after launch.
The Launch
What Changes Hands at Launch
Every page titled and described, alt text in place, Open Graph set, the sitemap submitted, and redirects live before the domain changes.
Handover is a short screen recording of the edits your team will actually make, plus a written guide, so nobody scrubs a video for one step.
Then it is yours. A fixed-price build ends at launch; anything after it is a retainer, agreed, not an invoice.
The Program
Most engagements do not end at launch. The retainer keeps a technical partner on the site on a fixed monthly scope, and the same methodology runs on WordPress when that is where your site lives.
A Retainer Month
- Requests estimated and approved before anything touches the live site
- Every change logged with before, after, reason, and date, in a log you can read
- Fixes, new sections and pages from your team's designs, CMS changes, forms and tracking
- A monthly measurement snapshot: Search Console, Core Web Vitals field data, AI citation pulls
- Integrity monitoring and content operations behind the verification gate
- A written audit report whenever a pass is run: metadata, links, schema
Scope is fixed for the month and reviewed every quarter, because the data behind it runs on 28-day and 90-day windows. Three months minimum, so the first report has something real in it.
Ways to Work Together
Direct
You brief me, I build, you approve. No account layer and no agency markup. Fixed scope, fixed price, paid in milestones.
Retainer
Stage 05, run monthly against your live site on a fixed scope: measurement, content operations, integrity monitoring, and the changes your team needs.
White Label
The build ships under your agency's name. I stay invisible to your client, your team gets the documentation, and a mutual NDA is there for the asking.
Have a Build That Needs Shipping?
Thirty minutes, your project on screen. You leave with a scoped plan and a number, whether or not we work together.