Webflow Agency Retainer Long-term Retainer.

The agency needed someone who could turn client requests into working Webflow builds, not just design files. I started there as a graphics designer, but the work kept growing into harder territory: membership logic, CMS architecture, third-party integrations, codebases that needed cleaning up. That’s where I came in.

The agency needed a partner who could pick up scope across active client projects without constant hand-holding: Webflow development, Memberstack architecture, CMS consulting, API integration support. Tasks came through Asana. Quick questions through Slack. Design passed through Figma before anything got built, hours tracked in Hubstaff.

A learning platform that needed membership logic. One client wanted to launch a full learning app, courses, lessons, news, a user dashboard, but needed content to unlock based on each user’s membership plan. Memberstack and Webflow’s CMS don’t talk to each other by default. I built the connection between them, so users only saw what their plan allowed, and added lesson progress tracking so people could see exactly where they left off.

A recruitment site that needed its job board synced. Another client already ran their listings through idibu but wanted those jobs to show up on their Webflow site automatically, no manual re-entry, nothing falling out of sync. I worked directly with idibu’s team, using their API and Postman, to build that connection.

An agency that had outgrown its own naming system. With 15+ sites and different builders working across them, class names had gotten inconsistent and hard to hand off. The agency needed one standard everyone could work from. I introduced Client-First as that standard and went back through existing sites to bring them in line.

Everyday builds that needed a steady hand. Beyond the bigger technical work, the agency needed someone who could just handle the day-to-day without it piling up: layout fixes, reusable components, nav and footer polish. That fell to me too.

That relationship held up long enough to grow into 15 to 20+ client sites.

Agencies don’t just need someone to execute a spec. They need someone who can take a half-formed problem, “we need our CMS to do this” or “we need this system to talk to that one,” and turn it into something that works. That’s the role I played here.

If your agency is building in Webflow and needs a technical partner who can take that kind of problem off your plate, I’d love to connect.