How to Design a Customers Page When You Have Ten Customers

How do you design a customers page when you only have ten customers?

Design it around depth instead of volume. With ten customers, you cannot win on a wall of logos, so show fewer customers in more detail: who they are, what problem they had, what changed, and a quote in their own words. Group them by use case so a visitor finds someone like themselves within seconds.

Early B2B companies often skip the customers page entirely, or they build one modeled on a company with thousands of customers. The result is a grid with ten logos, a lot of white space, and a headline about being trusted by industry leaders. Visitors notice the gap between the claim and the evidence.

Ten customers is not a weakness to hide. It is a different design problem. A small customer base can produce a more convincing page than a large one, because each story can carry real detail. Here is how I would structure it on a Webflow site.

What is a customers page for at this stage?

At this stage, a customers page answers one buyer question: has anyone like me used this and been glad they did? It is not there to impress with scale. It is there to reduce the risk a buyer feels when choosing a young vendor, by showing specific, believable evidence from people in a similar situation.

That framing changes every design decision. A large company's customers page signals popularity. A small company's page has to signal fit and honesty. The buyer is not asking how many customers you have. They are asking whether you understood a problem like theirs and fixed it.

It also changes who visits the page. Early on, the customers page gets traffic from late-stage buyers checking you out after a demo, and from AI answer engines looking for evidence about what your product does. Both reward concrete detail over volume.

Should you show logos at all?

Yes, but not as the main event. A small row of logos near the top tells visitors that real companies use you. Then move quickly to the stories. Ten logos in a large grid draws attention to the number. Ten logos in a tight row, followed by detailed stories, draws attention to the people.

Only show logos you have permission to use. That sounds obvious, but early-stage teams often add a logo because a customer said something nice on a call. A logo is a public endorsement. Get written approval, and keep a record of it in your CRM or a shared document, so you know which logos are safe if anyone asks.

I wrote about why logos alone do little in why customer logos are not proof for B2B software. On a small customers page, the logo row is a doorway. The stories are the room.

How should you structure each customer story?

Use the same short structure for every story: who the customer is, the problem they had before, what they tried, what changed after working with you, and a direct quote. Keep each story scannable, with the customer's name, role, and company at the top, and the most concrete outcome in the first two lines.

Consistency matters more than length. When every story follows the same pattern, a visitor can compare them quickly and find the one closest to their own situation. Inconsistent formats force people to read every word to understand what each story is about, and most will not.

The outcome should be specific but honest. If the customer has shared a number they are comfortable publishing, use it with their approval. If not, describe the change in plain terms, such as "the team stopped copying leads between tools by hand." A plain, true outcome is more convincing than a vague claim of improved efficiency.

How do you group ten customers so visitors find themselves?

Group by the reader's situation, not by your product features. Common groupings are use case, company size, or industry. With ten customers, two or three groups is enough. Label each group in the words a buyer would use, so a visitor can scan the page and jump straight to the stories that look like their own problem.

Pick the grouping your buyers already use to describe themselves. If prospects introduce themselves as a "five-person sales team," group by team size. If they lead with industry, group by industry. Your sales calls are the best source for this. Listen to the first sentence prospects use when they explain who they are.

On Webflow, I would build the stories as a CMS collection with a reference or option field for the group. That lets the page filter or section stories by group without manual layout work, and it makes adding the eleventh customer a five-minute task instead of a redesign.

What should you do when a customer will not be named?

Tell their story anyway, with their permission and without identifying details. Describe the company by type and size, use the person's role instead of their name, and keep the problem and outcome specific. An anonymous story with real detail is more useful than a named story with none, as long as you are clear that the customer is anonymized.

Do not invent details to make an anonymous story feel more real. If the customer did not share a metric, do not add one. If you are unsure whether a detail could identify them, leave it out. The value of the story comes from being true, and an anonymous story is already asking the reader to trust you a little more.

I covered this in more depth in how to write a customer story when the customer cannot be named. On the page itself, mark these stories clearly so nobody feels misled when they cannot find the company.

What design details make a small customers page feel credible?

Real photos, real names, specific roles, and quotes that sound like a person talking rather than marketing copy. Avoid stock images, generic headlines, and superlatives. Use a clean layout with enough space for each story to breathe, and keep the visual weight on the people and their words, not on decoration.

Quotes do a lot of work here. A good quote is short, specific, and slightly informal. "We stopped losing demo requests over the weekend" beats "an amazing partner that transformed our business." If a customer's real words are better than your summary, lead with their words.

Dates help too. A small note showing when a story was published or last updated tells visitors the relationship is current. A customers page full of stories with no dates can make a young company look older and quieter than it is.

Where should calls to action go on the page?

Put one clear call to action after each group of stories, and one at the end of the page. The action should match the visitor's stage. Someone reading customer stories is often close to a decision, so a direct "talk to us about a similar setup" link works better than a generic newsletter signup.

Keep calls to action specific to the story group when you can. If the stories above are about small sales teams, the button can say something like "see how this would work for your sales team." That small change connects the evidence the visitor just read to the next step you want them to take.

Avoid pop-ups and interruptions on this page. Visitors here are doing careful reading. An interruption at that moment feels like pressure, and pressure on a page meant to build trust works against you.

How should the page change as you add customers?

Let it grow from depth to breadth. At ten customers, every story gets full detail. At thirty, the strongest stories stay detailed and the rest move to shorter cards. At a hundred, you can add a logo wall and filters, but keep a few deep stories at the top, because in my view detail persuades in a way volume cannot.

Build for that growth from the start. A CMS-driven layout, consistent story fields, and a grouping field make each stage a content change rather than a redesign. The worst outcome is a hand-built page that someone has to rebuild every time a new customer agrees to a story.

Review the page every quarter. Check that each story is still accurate, that quoted people still work at the company, and that every logo is still approved. A customers page with an outdated quote from someone who left the company months ago undermines the trust the page was built to create.

What should you do next?

List your ten customers, mark which ones have approved logos and stories, and pick two or three groups based on how buyers describe themselves. Write each story in the same short structure, with a real quote and an honest outcome. Then build it as a CMS collection so the page can grow without a redesign.

I design and build B2B websites on Webflow, including pages like this that have to earn trust with limited proof. If you want help structuring a customers page for an early-stage product, reach out at pravinkumar.co and let's chat.