Searching for a B2B SaaS website design agency returns two kinds of results: agencies that show you what they made, and agencies that tell you what they believe. Neither answers the question a founder is actually asking, which is "will this team make the site say what we sell, to the people who buy it, and can I check their work?" This post is the checklist for that question, written by a studio that does the work and 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 covers how the two markets differ in price and process. The first half is the same everywhere: six signals to look for, five red flags, and the questions that separate an agency from a vendor.
Six things to look for
1. They start with the sentence, not the moodboard
The single best predictor of a good outcome is what the agency does in week one. If the first deliverable is a moodboard, a style exploration or "three creative directions", the positioning has been skipped and the design will decorate whatever the current site says. If the first deliverable is a written line, the one sentence that names your buyer, your category and the change you make, the rest of the project has something to be right about.
Ask directly: "What do you deliver before any design starts?" The answer you want mentions the sentence, the buyer, and the proof stack. We wrote about why the order matters in positioning before pixels; the short version is that layout amplifies clarity and cannot manufacture it.
2. Their portfolio is live sites, not mockups
Every agency has a portfolio. Look 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 URL on the client's own domain proves the agency can ship, that the client accepted the work, and that it survived contact with a real content team.
Open three of their live sites on your phone. Check whether the copy on the homepage is specific to that client's buyer or could be swapped between the three. Then run one through our scorecard. If an agency's own showcase work scores weak on the sentence and the proof, that is what your site will score.
3. One team owns copy, design and build
The most common failure in SaaS website projects is the handoff. A copywriter writes without seeing the layout, a designer lays out without owning the words, a developer builds without either of them present, and the result is three people's compromises. The fix is structural: the people who write the sentence are in the room when the hero is designed and when it is built.
Ask who writes the copy. "You do" or "we can recommend a copywriter" means the agency does not own the argument, and the argument is the site. Ask who builds. 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. Agencies often propose custom illustration systems because they are distinctive, photograph well in a portfolio and avoid the hard work of making a dashboard look good. The result is a homepage with floating gradient cards that tells the buyer nothing.
Look for agencies whose SaaS work shows the actual product, cropped and captioned, in the first two screens. When we rebuilt Pickcel's surface, the solutions and integrations pages were built to be evaluated before the sales call, with real screens; the effect was that procurement stopped asking the same questions on every deal.
5. They have a plan for after launch
A site is not finished on launch day; it is finished when the first month of inquiries has been read. Ask what happens in the 90 days after the site goes live. The answer should include analytics wired to a conversion event, a source field on the form, a review of which pages inquiries start on, and a round of copy fixes based on what the data shows.
An agency that ends at "handover and training" is selling a brochure. Measurement is what turns the site into a system, and it is the part most agencies leave to "your marketing team", which in a founder-led company means nobody.
6. The process fits your calendar, not theirs
For a founder-led company the practical question is time. A process built on weekly two-hour workshops and live design reviews will stall the first time a fundraise or a sales quarter gets in the way. Look for a process that is asynchronous by default: written deliverables you can review at night, a preview URL that updates, decisions recorded in a document, and calls reserved for the three or four moments that need them.
This matters double across time zones. An Indian studio working with a US founder, or the reverse, should be able to describe exactly when the overlap window is and what happens outside it. If they cannot, the project will run on whoever is awake.
Five red flags
- A portfolio of Figma files. Pictures of sites, not sites. Ask for three live URLs and open them.
- "Copy is the client's responsibility." The agency does not own the argument. You will get a beautiful page that says what your old page said.
- A retainer before a scope. Monthly fees with no defined deliverable are how agencies fund their bench. 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 either.
- No numbers in their case studies. "Increased brand perception" is not a result. Look for inquiry counts, sales-cycle changes, conversion rates, or at minimum a named client who will take a reference call.
Agency, freelancer or studio
The word "agency" covers three very different animals. Which one you need depends on where the problem is.
| Freelancer | Large agency | Small studio | |
|---|---|---|---|
| Best when | Positioning and copy exist; you need execution | You need a brand system across many surfaces and have a team to manage it | Positioning is the problem; you want one team to own argument, 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, same people |
| After launch | Ends at handover | Retainer | 60 to 90 days of measurement, then handover |
| Price shape | Lowest; per page or per hour | Highest; retainer plus project | Middle; fixed scope, 6 to 10 weeks |
| Risk | Single point of failure; no strategy | Account layers; the people who pitched are not the people who build | Capacity; the good ones take a few clients a quarter |
Most founder-led SaaS companies between seed and Series B are in the third column: the sentence has never been written, the product has outgrown the site, and there is nobody internal to manage a large agency. That is the position our SaaS website design engagements are built for, which is also the bias of this post.
US and India: what actually differs
We work in both markets, and the honest answer is that the criteria above do not change. What changes is the price shape and the working rhythm.
Price. 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 the high single-digit to low tens of lakhs. The gap is real, but it only holds if the writing is at the same level; a cheaper site that says nothing is not cheaper. Below both sits the template-and-freelancer band, which is right when the positioning already exists and wrong when it does not.
Rhythm. 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 is a feature. 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 be the bottleneck.
Proof legibility. A site built for US buyers needs proof a US buyer recognizes: named customers, numbers with context, cases 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, where buyer vocabulary and price signals differ.
What does 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, 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 is the one that separates agencies from vendors. A team that has read your site before the call and can name the weakest point is a team that will own the argument. A team that answers "we'd need to do a discovery phase" is going to bill you for reading your homepage.
Before you brief anyone
Run your own homepage through the scorecard. It takes a minute and 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. If the sentence is strong and the proof is weak, you may need a case-study writer and a developer, not a redesign at all.
If you want a second opinion before spending anything, the teardown is a recorded walkthrough of your page against the same five points, with the sentence rewritten and the page re-ordered, for ₹20,000 or $249, credited if you go on to work with us. And if you want to see the full argument for how a B2B homepage should be built, section by section, it is in the guide. Read that first, and you will brief any agency better, including this one.