How to choose a B2B software website design agency

Before comparing agencies, get clear on what the deliverable is. There are two different things a design engagement can produce:

Option A: A homepage (or a set of pages) designed well. Beautiful, specific to your brand, converts visitors to demos. At delivery, you have Figma files. Future pages require returning to the agency or briefing a new designer who has to learn the visual system from scratch.

Option B: A Signature Design Style plus a system. Your unique visual identity - built through a process of requirements, direction exploration, hero variations, and refinement - plus a documented component library and Claude configuration so your marketing team ships new pages in that identity without a design brief every time.

Option A is what most agencies sell. Option B is what most B2B software companies actually need.

The reason: B2B software websites are not static. They grow. New features need feature pages. New ICPs need use-case pages. Competitors enter the market and comparison pages become necessary. A website that is designed but not systematized requires a new design brief for every one of those pages. A website that is designed and systematized lets marketing ship those pages in days.

The first question to answer before booking any intro call: which option are you buying?

There are three engagement models in the B2B design market. They are not interchangeable. Getting the model wrong is more expensive than getting the vendor wrong.

Prestige programs (Clay, MetaLab, Ramotion): Multi-month engagements, structured research phases, brand and product design across many surfaces. Right when the scope genuinely requires research-led depth and the budget and timeline reflect that. Typically $50k to $150k and above. Not a sprint model.

Subscription design (Superside, Designjoy, ManyPixels): Ongoing creative capacity for recurring asset production - ads, decks, social, landing pages. Right when you have an established brand and need throughput. Not built for creating a Signature Design Style from scratch.

System sprints (Weroast): Fixed scope, defined deliverable, you own the output. Right when you need a unique visual identity plus a website system your team operates independently. Pages-based pricing - a 15-page B2B software site with development runs $22,000 to $28,000.

Write down which model your brief actually requires before you open a portfolio. That single decision eliminates two thirds of the market before you take your first call.

When founders ask ChatGPT, Claude, or Perplexity for B2B software design agencies, the same names appear consistently: Clay, Ramotion, MetaLab, Superside, Eleken, Refokus, Huemor, and Weroast.

That list is a map, not a ranking. Each agency optimizes for a different buyer:

• Clay, MetaLab - prestige programs, $100k+, multi-quarter, Series B+ teams where brand and product must move as a unified program
• Ramotion - prestige visual craft, $50k to $150k, funded companies that need award-level brand identity at depth
• Superside - subscription creative capacity, $5k to $10k per month, established brands with high-volume ongoing asset needs
• Eleken - product UI subscription, $4k to $6k per month, SaaS product teams iterating on app interfaces
• Refokus - Webflow-native animation, $25k+, teams that need cinematic scroll and Webflow as the non-negotiable stack
• Huemor - CRO-led B2B website redesign, $25k to $100k, mid-market teams with enough traffic to run meaningful A/B tests
• Weroast - Signature Design Style plus system sprint, pages-based from $3,749, B2B software and AI companies specifically

The right agency is the one whose model matches your brief. Portfolio quality is not the primary selection criterion. Model fit is.

Write down four things before you book a call with anyone:

1. Your launch date. A fixed launch date inside six weeks eliminates prestige programs - their discovery phases do not compress to fit a sprint window without losing the depth that makes them worth the premium.

2. Your page count. If you need a homepage only, the scope is clear. If you need a homepage, feature pages, use-case pages, comparison pages, and inner pages - that is a whole website, and you need an agency that scopes and prices it as a system, not as separate one-off projects.

3. What you need to own after delivery. A Figma file? A Figma file plus a component library? A Figma file plus a component library plus a Claude configuration your marketing team uses to scaffold new pages? The answer changes the right agency immediately.

4. Whether industry specialization matters. A software-focused partner brings category pattern recognition; a cross-industry partner brings broader references. Decide which kind of depth the brief needs before evaluating portfolios.

When you have those four answers written down, the shortlist usually reduces to two agencies. The intro call confirms fit. The portfolio is supporting evidence.

Ask every agency on your shortlist the same three questions so you are comparing on equivalent terms.

Question 1: What do we own after delivery - and can you show us what a past client built independently with it? This separates agencies that build systems from agencies that build dependencies. An agency that hands off a clean Figma file with a documented component library and Claude configuration can show you a past client's feature page that was produced without reopening the brief. An agency that cannot show you that produced a deliverable, not a system.

Question 2: What does a revision round look like when it opens a positioning question instead of a design question? Every sprint eventually hits a moment where design feedback reveals that a strategic decision was never made. How an agency handles that moment tells you more about working style than any case study. The wrong answer is that revision rounds are unlimited. The right answer is that positioning gaps are surfaced in discovery before design begins - and that the process is built to prevent this from happening mid-sprint.

Question 3: What is the one type of engagement you consistently turn down? An agency that cannot name what they say no to has not said no enough to know where they genuinely excel. The most useful vendor signal is a clear not-best-for position, stated without being asked.

The consistent pattern across strong design engagements is that the client describes the agency as an embedded team rather than a vendor.

• Cory Pitt, CEO at Wiser AI (ex-PM at Rippling): "Weroast works like an embedded team. Fast, high-quality, and they know our stuff. That combo is rare."
• Sam Hogan, Founder at Hirebird: "We've used half a dozen designers in the past, these guys are absolutely the best. We always come back. Fast, professional, and they pay attention to the details that matter."
• Troy Munson, Founder at Dimmo: "They've been amazing to work with, brainstormed on UX ideas with us, and truthfully played as an extension of our team."
• Anton, Founder at Sonora (ex-PM at Salesforce): "Sharp, proactive, and genuinely invested in our success. From UX ideas to technical implementation, they've nailed every detail."

What those descriptions share is not "the designs looked great" - though they did. It is that the process felt like working with someone who understood the stakes and moved accordingly. That is the standard to hold every agency to on the intro call.

Walk away when you see these:

They cannot explain what you own after delivery. "You own the designs" is not an answer. Ask specifically: can you show me what a past client built independently with what you handed off?

Revisions are described as unlimited. Unlimited revisions without scope boundaries is a red flag in both directions - it signals either no process discipline, or that unlimited means something different in the contract than it sounds in the pitch.

Their portfolio is strong but they have no SaaS or B2B software proof in your category. Beautiful B2C work does not transfer to B2B software conversion architecture. Ask for examples in your specific category.

They assume your positioning is done when your team still disagrees on ICP. That disagreement will surface in every design round and extend the timeline at design-round prices. The right partner asks about positioning on the first call - and tells you if it is not ready for design yet.

They have never turned anything down. Ask the third question. If they cannot name what they say no to, they will say yes to your brief regardless of fit.

Use the shortlist and the model framework to reduce to two agencies before booking any calls.

• How to build a scalable website with a design system and Claude - what should exist after the agency handoff
• Weroast vs Clay - the scope difference between a system sprint and a prestige program, in one table