Workflow
Here's a guide for Webflow Developers.
Last updated
Was this helpful?
Here's a guide for Webflow Developers.
Last updated
Was this helpful?
The client will fill out an implementation checklist. This allows us to give them upfront prices and recommendations.
Based on the checklist, provide any recommendations, pricing information, and the timeline before the Creative Director submits a proposal to the client. Recommendations can also include various external paid features such as integrations, monthly memberships, etc.
Additionally, check the technical requirements for what they are requesting and ensure we have the time and talent resources to provide it.
Attend the to catch any desired implementations that could cause extra cost or that are not within our ability to provide. During breaks and free-time, pursue any necessary research to find pricing and any pre-existing options that may be available. Provide information on any extra time or cost before the end of the workshop and discuss with the client if they would like to move forward.
Before user research begins, the Website Designer will share their progress with you. This allows you to help inform the user interface and how things will be built. Make sure to provide constructive feedback as needed.
Attend or listen to recording of and provide feedback if necessary.
As soon as the front-end has been cleaned up and is within your understanding, you can start building. This is the case, even before the static mobile version is complete.
The platform we use is Webflow, and the account is typically created by the client. They will share the login information with you.
When beginning to build, take the following elements into consideration:
Inspect Figma - You will be given access to the project's Figma. Use the Inspect Tab to view the website design and build based on the vision created.
Use Native Webflow Functionality - For the sake of both saving time and allowing the client to modify the website in the future, try to use native Webflow functionality as much as possible.
Before submitting the final product, test the website on multiple mobile and desktop devices, as well as multiple browsers. This will ensure any bugs are caught and that the website is accessible and well-crafted regardless of the methods used to access it.
Additionally, test all accessibility features. Follow the accessibility checklist to make certain all bases have been covered.
At the Final Presentation Workshop, you will have the opportunity to spend 5-10 minutes presenting a static version of the website or the full build if it is ready. If the full build is not ready, make sure to indicate when the delivery of the final product can be expected.
See the Final Presentation page for more information:
Once the full build is complete, create a Webflow walk-through for the client. Use a recording software or plugin, such as Loom, and discuss various features to help familiarize the client with what was created. The walk-through doesn't have to be extensive. Simply include any key features and links you think are noteworthy. Additionally, include any resources you believe will be helpful if they want to modify something. For this, it may be helpful to build a small resource library that can be used across projects.
The recording will be included in an email sent by the Creative Director to deliver the final product.
Once you have finished building, submit the final product to the Creative Director and they will ensure it is received by the client. Make sure to include the Webflow Walkthrough.
Prioritize Accessibility - It is critical to make sure the website is accessible to anyone. To help with this, make sure the website has accessibility features. An accessibility checklist can be found at
Have Questions? There are many options for finding information on Webflow. Webflow offers a where you can find answers to any question you have or issues you run into. Additionally, platforms such as are often very useful for finding the information you're looking for.