Product designer & AI builder for B2B SaaS teams

I work best with founders, product teams, and growth teams facing a clear product or conversion challenge.

That could mean improving onboarding, fixing a confusing user flow, redesigning a core product experience, creating a design system, strengthening a landing page, or giving structure to an early-stage product.

The best fit is a team that can share its goals, customer insight, constraints, and feedback - and is ready to act on a clear design direction.

I help SaaS teams make products and marketing experiences clearer, easier to use, and more consistent.

It depends on the engagement. Projects may cover:

• Onboarding, activation, and core user flows.
• UX/UI design for web or mobile products.
• Design systems and reusable interface patterns.
• Landing-page messaging, structure, UX, and conversion.
• Interaction and motion direction.
• Product or website structure.
• High-fidelity design and prototyping.
• Implementation guidance.
• Website or landing-page design and development when included in scope.

Each engagement is shaped around the problem you want to solve and the result you want to reach.

It depends on the project, but you’ll usually get a combination of strategy, design, prototypes, and clear direction for what happens next.

That may include:

• User flows and journeys.
• High-fidelity product designs.
• Interactive or coded prototypes.
• Landing-page designs.
• Design systems and reusable components.
• UX recommendations.
• Clear reasoning behind important design decisions.
• Documentation and implementation guidance.
• Developer-ready designs and handoff.
• A clearer roadmap for what should be improved next.

The work goes beyond handing over design files. You should come away understanding why certain decisions were made, what problems we were trying to solve, and how your team can continue building on the work afterwards.

I start by understanding the problem before designing the interface.

We look at the business goal, user needs, current experience, available evidence, constraints, and what a successful project needs to achieve.

From there, I break the work into clear phases and explain the thinking behind major design decisions. Feedback is tied back to the goals of the project, which helps stakeholders evaluate the work from a product perspective rather than personal taste.

You get direct senior involvement from strategy through final design.

SaaS Designer is a one-person studio led by Brendan (myself).

You’ll work directly with me throughout the project, all the way from understanding the problem and shaping the direction through to producing the final designs.

There is no handoff from a sales team to a separate delivery team.

If a project calls for development or specialist support, that will be outlined clearly in the scope so you know who is involved and what they are responsible for.

This is a direct consulting relationship built around a defined problem, outcome, scope, and set of project phases.

Agencies can be a great fit when you need a larger team, multiple disciplines, or a lot of production capacity.

That said, it’s worth understanding who will actually be doing the work before you sign on.

Some agencies are built around a model where senior people handle sales, strategy, or client communication, while much of the day-to-day design work is completed by more junior team members. That isn’t necessarily a bad thing, but it can be very different from working directly with the person you originally spoke with.

I’m not the loudest person in the room, and I’m not interested in being performative for the sake of looking busy. I do my best work in environments that value clear thinking, thoughtful collaboration, and strong execution over constant meetings and unnecessary process.

My approach is built around quiet confidence and reliability. I listen carefully, ask the right questions, work through problems without ego, and follow through on what I say I’ll deliver.

I’m comfortable working independently, but I collaborate closely when it matters. I prefer focused communication, clear expectations, and giving people the space to do good work.

Yes. I’d consider myself pretty AI-native at this point.

I keep up with the latest AI design and development workflows and regularly use tools like Claude Code, Codex, and other AI tools as part of my own process.

In fact, most prototypes I build these days aren’t just static Figma screens. When it makes sense, I’ll build clickable, coded prototypes so we can test ideas in something that feels much closer to the real product.

I’m also not afraid to get into the code, work with an existing codebase, or push changes to GitHub. I’ve vibe-coded more than 10 of my own private apps, so I’m comfortable working somewhere between design, prototyping, and development when a project calls for it.

That doesn’t mean I use AI just for the sake of using AI. I’ll use whatever approach helps us understand the problem, explore ideas faster, and get closer to something your team can actually build.

As part of working together, I’m also happy to bring your team up to speed on some of the newer AI design and development workflows I’m using and look at where they might genuinely be useful inside your own company.

I can lead the strategy and design process from an early starting point, but I will need access to the knowledge your team already has.

That may include:

• Your business goal and definition of success.
• Product context and customer insight.
• Existing research, feedback, reviews, support questions, or call recordings.
• Access to the current product, website, analytics, or related materials.
• A clear decision-maker.
• Relevant stakeholder input.
• Timely feedback and approvals.
• Technical constraints from product or engineering.
• Content, messaging, or subject-matter input.

You do not need to arrive with a finished plan. I can help turn the information you have into a clear project direction.

Figma is still my main design tool, especially for interface design, design systems, prototyping, collaboration, and handoff.

But my workflow has become much broader than Figma.

Depending on the project, I’ll also use tools like Claude Code, Codex, GitHub, and other AI-assisted design and development tools to explore ideas, build prototypes, and get closer to the real product earlier in the process.

These days, a prototype doesn’t always need to be a clickable Figma file. Sometimes it makes more sense to build the actual interaction in code so we can experience it properly.

I care much more about using the right tool for the problem than forcing every project through the exact same design process. The tool itself is secondary to the quality of the thinking, decisions, and final experience.

Yes. Website or landing-page design and development can be part of an engagement when it fits the project.

Before work begins, the scope will define the platform, page count, content responsibilities, integrations, technical needs, level of customization, and any post-launch support.

For landing pages, I can also work on positioning, messaging, page structure, customer objections, proof, calls to action, and conversion flow.

Timing depends on the scope, number of flows or pages, stakeholder availability, feedback speed, and development needs.

Before the project begins, you will receive a phased timeline with clear milestones and responsibilities.

That timeline assumes feedback, content, and approvals arrive at the agreed points. Scope changes or delays may affect the schedule, and any changes will be communicated clearly.

Pricing depends on the scope, complexity, value of the work, and the level of support the project needs.

After the initial conversations, I will recommend a scope that fits the objective and explain the investment attached to it.

If the full project sits outside your available budget, we can reduce the scope or split the work into phases rather than cutting the parts needed to make the project useful.

No designer can responsibly guarantee a specific business outcome from design work alone.

Results can also depend on implementation quality, traffic, product-market fit, pricing, sales, customer support, and how the team acts on the work.

What I can do is define clear goals, agree on success criteria, make responsibilities clear, and design the project around measurable improvements.

I would rather set realistic expectations and evaluate the work against agreed evidence than promise a result no designer controls alone.

Send a short description of your product, the problem you want to solve, your timing, and any useful context through the contact form.

From there, we will book a short video call to talk through the project and see if the fit is right.

If it is, the next stage is a deeper strategy conversation followed by a recommended scope, timeline, and plan.