When you search for a B2B SaaS website design agency, you get two kinds of results. Some agencies show you what they made. Others tell you what they believe. Neither answers the question you are really asking. That question is: will this team make the site say what we sell, to the people who buy it? And can you check their work before you pay? This post is a checklist for that question. We are a studio that does this work, and we would like to be judged by the same list.
We work with founder-led software companies in India and the US. So the second half of this post covers how the two markets differ in price and process. The first half applies everywhere. It covers six signals to look for, five red flags, and the questions that show whether a team will own the work or only take orders.
Six things to look for
1. They start with the sentence, not the moodboard
The best predictor of a good outcome is what the agency does in week one. Some agencies start with a moodboard, a style exploration or "three creative directions". A moodboard is a collage of colors, fonts and reference sites. If that is the first deliverable, the agency has skipped positioning. Positioning is the short statement of who you sell to, what you sell, and why it is better. Without it, the new design will only decorate what the current site already says. A good agency delivers a written line first. That line names your buyer, your category and the change you make for them. Once that line exists, the team can test every design choice against it.
Ask directly: "What do you deliver before any design starts?" You want an answer that mentions the sentence, the buyer, and the proof. Proof means customer names, numbers and case studies. We wrote about why this order matters in positioning before pixels. The short version is that a good layout makes a clear message clearer. A layout cannot create a message that is not there.
2. Their portfolio is live sites, not mockups
Every agency has a portfolio. Look closely at what is in it. Dribbble shots, Behance case studies and Figma frames are pictures of sites. They prove the agency can draw. A live site on the client's own domain proves more. It proves the agency can ship. It proves the client accepted the work. And it proves the design survived a real content team adding real pages.
Open three of their live sites on your phone. Read the homepage copy on each one. Ask yourself whether it is specific to that client's buyer, or whether you could swap it between the three sites. Then run one of them through our scorecard. If the agency's own showcase work scores weak on the sentence and the proof, expect your site to score the same.
3. One team owns copy, design and build
The most common failure in SaaS website projects is the handoff. A copywriter writes the words without seeing the layout. A designer lays out the page without owning the words. A developer builds it without either of them in the room. The result is a page made of three people's compromises. The fix is a structural one. The people who write the sentence should be present when the hero is designed and when it is built. The hero is the first screen of the homepage.
Ask who writes the copy. If the answer is "you do" or "we can recommend a copywriter", the agency does not own the message. That message is the most important part of the site. Ask who builds the site. An agency that hands you a design file and a list of development partners is selling half a project.
4. Real product screenshots, not an illustration system
A SaaS buyer wants to see the product. Many agencies propose a custom illustration system instead. An illustration system is a set of drawn graphics used in place of product screens. Agencies like them because they look distinctive and photograph well in a portfolio. They also avoid the hard work of making a dashboard look good. The result is a homepage full of floating gradient cards that tells the buyer nothing about the product.
Look for agencies whose SaaS work shows the actual product in the first two screens, cropped and captioned. We did this when we rebuilt Pickcel's site. The solutions and integrations pages used real screens, so buyers could evaluate the product before the sales call. After launch, procurement teams stopped asking the same questions on every deal.
5. They have a plan for after launch
The project should continue past launch day. The real test is the first month of inquiries. Ask what happens in the 90 days after the site goes live. The answer should include four things:
- Analytics wired to a conversion event. A conversion event is a tracked action, like a form submit.
- A source field on the contact form, so you know where each inquiry came from.
- A review of which pages inquiries start on.
- A round of copy fixes based on what the data shows.
An agency that ends at "handover and training" is selling a static page. Measurement is what turns the site into a system that improves over time. Most agencies leave this part to "your marketing team". In a founder-led company, that usually means nobody.
6. The process fits your calendar, not theirs
For a founder-led company, the practical question is time. Some agencies run on weekly two-hour workshops and live design reviews. That process will stall the first time a fundraise or a sales quarter gets in the way. Look for a process that is asynchronous by default. Asynchronous means the work moves forward without everyone being in the same meeting. That means written deliverables you can review at night. It means a preview URL that updates as work happens. It means decisions recorded in a document. Calls are reserved for the three or four moments that need them.
This matters twice as much across time zones. An Indian studio working with a US founder, or the reverse, should be able to say exactly when the overlap window is. They should also say what happens outside it. If they cannot, the project will only move when both sides happen to be awake.
Five red flags
- A portfolio of Figma files. These are pictures of sites, not finished sites. Ask for three live URLs and open them.
- "Copy is the client's responsibility." This means the agency does not own the message. You will get a good-looking page that says what your old page said.
- A retainer before a scope. A retainer is a fixed monthly fee. Monthly fees with no defined deliverable pay for the agency's idle staff. A website is a project with an end. Pay for the project.
- An illustration system instead of your product. If their SaaS case studies show no product screens, yours will not have any either.
- No numbers in their case studies. "Increased brand perception" is not a result. Look for inquiry counts, changes in sales-cycle length, conversion rates, or at least a named client who will take a reference call.
Agency, freelancer or studio
The word "agency" covers three very different kinds of team. Which one you need depends on where your problem is.
| Freelancer | Large agency | Small studio | |
|---|---|---|---|
| Best when | You already have positioning and copy and need someone to build | You need a brand system across many surfaces and have a team to manage it | Positioning is the problem and you want one team to own message, design and build |
| Owns the copy? | Rarely | Sometimes, through a separate copy team | Yes, it is the first deliverable |
| Ships the build? | Depends on the person | Usually, through a dev team | Yes, the same people |
| After launch | Ends at handover | Retainer | 60 to 90 days of measurement, then handover |
| Price shape | Lowest, billed per page or per hour | Highest, a retainer plus a project fee | Middle, a fixed scope over 6 to 10 weeks |
| Risk | One person is a single point of failure, and there is no strategy | Account layers, so the people who pitched are not the people who build | Capacity, since the good ones take only a few clients a quarter |
Most founder-led SaaS companies between seed and Series B fit the third column. The sentence has never been written. The product has outgrown the site. And there is nobody inside the company to manage a large agency. Our SaaS website design engagements are built for that position. That is also the bias of this post.
US and India: what actually differs
We work in both markets. The criteria above do not change between them. What changes is the price and the working rhythm.
Price is the first difference. A senior US studio doing positioning plus build charges mid five figures to low six figures in dollars for a homepage-led site. A senior Indian studio doing the same scope charges roughly a quarter to a half of that. In rupees, that is the high single-digit lakhs to the low tens of lakhs. One lakh is 100,000 rupees. The gap is real. But it only holds if the writing is at the same level. A cheaper site that says nothing does not save you money. Below both sits the template-and-freelancer band. That band is right when the positioning already exists and wrong when it does not.
Rhythm is the second difference. US agencies tend to run on meetings. Indian studios that sell to the US tend to run on documents, because they have to. For a founder with a day job or a sales quarter, the second style is easier to live with. Ask any agency, in either market, to describe a week of the project without a single live call. If they cannot, expect the calendar to slow the project down.
The third difference is how proof reads to the buyer. A site built for US buyers needs proof a US buyer recognizes. That means named customers, numbers with context, and case studies they can click. An Indian agency that has only built for Indian buyers may not have the instinct for this. Check their US-facing work specifically. The same applies in reverse for a US agency building for the Indian market. Buyer vocabulary and price signals differ there.
Four things do not differ. Whether the first deliverable is a sentence. Whether the case studies have numbers. Whether the same people write, design and build. Whether anyone looks at the site after launch. Hire on those four, in either country.
The questions to ask on the first call
- What do you deliver before any design starts?
- Show me three live sites you built. Who wrote the copy on them?
- Who on your team will write, design and build ours? Are they the people on this call?
- What happens in the 90 days after launch?
- What is your process for a founder who can give you two hours a week?
- Which of your case studies has a number in it, and can I speak to that client?
- What would you change first on our current homepage?
The last question matters most. A team that has read your site before the call, and can name its weakest point, will own the message. A team that answers "we would need to do a discovery phase" is going to charge you for reading your homepage.
Before you brief anyone
Run your own homepage through the scorecard. It takes a minute. It tells you which of the five points is weak: the sentence, the buyer, the proof, the path or the measurement. Then hire for that point. If the sentence scores weak, an agency whose first deliverable is a moodboard will not fix it, however good the portfolio looks. If the sentence is strong and the proof is weak, you may not need a redesign at all. You may need a case-study writer and a developer instead.
If you want a second opinion before spending anything, book the teardown. It is a recorded walkthrough of your page against the same five points. We rewrite the sentence and re-order the page. It costs ₹20,000 or $249, and we credit that amount if you go on to work with us. If you want the full argument for how a B2B homepage should be built, section by section, read the guide. Read that first and you will brief any agency better, including this one.