None of these are design problems. They are decisions nobody made, about who the site is for, what it has to prove, and who is allowed to change it. That is where I start.
You ship faster than the website can describe. The product moved on, the positioning moved on, and the site still explains the old one. You need pages your marketing team can change without waiting for a sprint.
See how I workInvestments, units and listings have a structure, and the site has to match it instead of forcing everything into one template. Plus enquiry paths that reach the right person rather than a shared inbox.
See how I workYou have the design and the client relationship. You need someone who turns Figma into a production Webflow build on schedule, works to your standards, and stays out of the client conversation unless you want him in it.
See how I workFour projects, and what each one had to solve.
AdspaceSaaS / marketplaceYouTube influencer marketing platform connecting brands with a network of 40,000+ creators. The site had to explain the model to two different audiences at once and route each of them to an enquiry.
REMAX BelizeReal estateReal estate site with a listings CMS. Listings had to be publishable without a developer, and the investment content had to work for buyers outside the country.
RecognizedB2B / expert brandAuthority platform for coaches and consultants. The site had to sell credibility, so proof and a clear path to contact mattered more than a feature list.
FreddiePullenPersonal brandSite for a founder, podcaster and speaker. One person, three different reasons to get in touch, each needing its own path.Who the site is for, what it has to prove, and what is failing now.
Pages, hierarchy and messaging, before a single screen is designed.
Layouts, type and interaction in Figma, tested against real content.
A responsive Webflow build with components and a CMS shaped around your content.
Redirects, analytics, forms and metadata checked before the site goes live.
Changes after launch, based on what visitors actually do.
An existing site that no longer matches the company, rebuilt without losing the search traffic you already have.
Positioning, structure, design and build from scratch.
Campaign pages that continue the promise that brought the visitor, instead of diluting it.
Your design, built properly and on schedule.
Built in Webflow, with components and a CMS your team can maintain.
Ongoing changes without a retainer you cannot justify.
It depends on how many page types there are, how much content already exists, and what has to integrate. A redesign on an existing structure costs less than a new site that also needs positioning and content work. Tell me what you have and you get a number, not a range.
Most projects run from a few weeks to a couple of months. The variable is rarely the build, it is how quickly content, images and approvals come back. You get a date once we agree the scope and who approves what.
Yes. Every project is designed in Figma first and approved there before anything is built.
Yes, Webflow is the default, because it gives your team a CMS they can use without a developer. If a project genuinely needs something else, I will say so.
Yes, and it is most of what I do. A redesign includes a URL and content plan so the traffic you already have survives the move.
Yes. That means an inventory of what exists, a redirect map, a CMS that matches your content, and checks after launch.
Yes. Content changes, new sections and fixes after launch, without a retainer you cannot justify.
Yes. Some clients bring a finished design, some bring a brand and no site, some bring a team that needs an extra pair of hands. All three work.
Yes. Agencies usually bring a Figma file and a deadline. I build it, keep to your standards, and stay out of the client conversation unless you want me in it.
