Platforms · Webflow Development
We build Webflow sites with a clean class system, a CMS your marketing team can actually use, and interactions that serve the content. When Webflow stops being the right tool, we say so and show you what comes next.
You own the code and IP Weekly demos Reply within one business day
OlDevs is a full-stack technology studio in Vancouver, British Columbia that designs and builds Webflow sites for organisations whose marketing teams need to publish without filing a ticket.Our Webflow work covers visual builds on a disciplined class system, CMS collections modelled around real content, interactions used sparingly, forms and integrations, localisation, and the SEO and publishing settings that decide how a site actually performs. We also handle migrations onto Webflow from older platforms, and migrations off Webflow when a project outgrows what the platform can do. Every engagement ends with a written handbook and a training session so your team can edit the site safely.
Key facts
Webflow platform expertise
We build in the Webflow Designer with a documented naming convention, often Finsweet's Client-First, so styles stay predictable. Components, variables and a real type and spacing scale keep the site consistent as it grows.
We design Collections around how your content actually behaves, not around one page layout. Reference and multi-reference fields, filtered Collection Lists and sensible field names give editors a CMS they can extend without breaking the design.
Webflow interactions are easy to overuse. We animate to guide attention and explain state, keep motion off the critical rendering path, respect reduced motion preferences, and test on mid-range phones rather than a fast laptop.
Native Webflow forms handle most enquiries, and we connect the rest through webhooks, the Webflow Data API or an integration platform into your CRM, help desk or booking tool. Where volume or logic outgrows the built-in form, we say so early.
We set page titles, descriptions, canonical behaviour, sitemap and redirect rules inside Webflow rather than bolting them on later, and we build multi-language sites with Webflow Localization where that is the right fit for your content.
We migrate sites onto Webflow from WordPress and older builders, and off Webflow to custom code when a project outgrows it. Either way you get a content audit, a redirect map, a written handbook and a training session for your marketing team.
Process
Discovery and content audit
We inventory what exists, what performs and what should not survive the move, then agree the sitemap, the content model and what a good outcome looks like.
Structure and design
Wireframes first, then design of the key templates with real content. Type scale, spacing, colour and component behaviour are agreed before anything is built.
Build in Webflow
Components, Collections, templates and interactions, with a working demo every week so you see the site progressing instead of reading a status report.
Integrate, test and launch
Forms, CRM and analytics wiring, accessibility and performance checks, redirects and SEO settings, then a scheduled publish with someone watching it land.
Handover, training and care
A recorded training session, a written handbook, editor roles set correctly, and a named contact for the questions that always arrive in month two.
How we work
We move into Webflow early rather than polishing static mockups forever. Seeing real type, real content and real breakpoints in the Designer surfaces problems while they are still cheap to fix.
Every project gets a naming convention and a style guide page inside the site itself. Anyone who opens the project six months from now can see how it was built without guessing.
We map Collections, fields and relationships before laying out a single section. Getting the model right first is what stops a site needing a rebuild the moment a second content type appears.
Image formats, font loading, video handling and third-party scripts are decided up front. Webflow will happily let you publish a slow page, so the discipline has to come from the build.
We build to WCAG 2.2 AA: real heading order, visible focus states, alt text fields in the CMS, colour contrast that survives the brand palette, and a keyboard path through every interaction.
If a requirement will not fit Webflow cleanly, you hear it in the first week with the options and trade-offs written down. Nobody enjoys discovering a hard limit two weeks before launch.
Who it's for
Marketing and communications teams inside larger organisations who need a site they can update themselves, with roles, governance and brand consistency that survive staff changes.
Member bodies and public sector teams with accessibility obligations, bilingual English and French requirements, and content that many contributors touch. We build to WCAG 2.2 AA as standard.
Multi-location brands that need one Webflow project driving consistent location pages from the CMS, so head office controls the template and every location stays on brand.
Founders who need a credible site quickly and want to change the message weekly without a developer in the loop. We build so the site moves as fast as your positioning does.
2014
Studio founded in Vancouver
1 week
Between working demos
1 business day
Reply to every enquiry
FAQ
It suits marketing sites, campaign sites and content-led sites where a small team publishes often and design quality matters. It is a weaker fit when you need complex user accounts, heavy transactional workflows or deep integration with internal systems. We tell you which side of that line you sit on before any build starts.
Server-side logic, complex relational data and long-running integrations are the usual walls. Webflow's automation and logic features have changed over time, so current at the time of writing we route anything past straightforward form handling to an external service or to custom code. We structure the site so that boundary is easy to cross later.
That is the point of a good Webflow build. We name Collections and fields in plain language, keep structural elements out of reach of editors, set the right roles, and run a recorded training session. You also get a written handbook covering publishing, images, redirects and the changes worth sending back to us instead of attempting alone.
Yes. We audit the existing content, map it to Webflow Collections, move the assets, rebuild the templates and produce a redirect map so rankings and inbound links survive the move. Where a plugin did something Webflow cannot, we find a replacement or build it, and we tell you what that costs in time before you commit.
It happens, and it is not a failure. We migrate sites off Webflow to custom front ends and headless setups, keeping the content, the URLs and the design language intact. Because we are a full-stack studio, the same accountable team that ran your Webflow site can build the application layer that replaces it.
Yes. We build bilingual English and French sites, using Webflow Localization where it fits and a structured alternative where it does not. Localisation is more than translated strings, so we plan URL structure, hreflang, date and number formats, and who owns each language before the build begins.
Send us the site you have now, the pages you need and any deadline you are working to. We reply to every enquiry within one business day, walk the current site with you on a video call in your time zone, then send a written scope. Once the build starts you see a working demo every week. Request a quote to begin.
Let’s connect
Tell us what you’re building. We’ll reply within one business day with next steps and a tailored quote — no obligation.