Why We Don't Have a 'Services' Page
How one word choice in the nav bar filters thousands of visitors before they even click.
Gaffy
Founder & Product Lead
8 min read
When the design team first sent over the Dartstudio wireframes, there was one thing I asked to change before I’d even looked at the rest of the layout.
In the header nav, the third item from the left read Services.
“Please change it,” I said.
“Change it to what?”
“Don’t know yet. Just not that.”
Sounds trivial. One word in a nav bar. But the discussion that followed, which ran for two weeks, was one of the most important ones we had while building this studio.
What one word carries
Every word has weight. Most of that weight is invisible. Readers don’t notice they’re reading word X and not word Y, but their reaction to the page is already shaped by that choice before they have time to think.
“Services” is a word that communicates one thing very clearly: we exist to serve, you exist to buy. That’s a transactional contract. Simple. Clean. No ambiguity about who’s paying and who’s receiving briefs.
There’s a class of business where that contract is exactly right. If you run an agency that sells production capacity, you give me a brief, I give you a deliverable, then “Services” is an honest and accurate word choice. Nothing wrong with that.
What goes wrong is when the word gets used for relationships that aren’t transactional. When it’s used by a studio that actually wants partnerships. When it’s used by a senior consultant who’ll reject your brief if they think your brief is wrong. When it’s used by a team that’ll push back on your decisions and sometimes decline unhealthy projects.
When “Services” is used for relationships like that, it lies. And a small lie in the nav bar grows into bigger misalignment at the sales call. Then at kickoff. Then at delivery.
A two-week discussion
Back to the wireframe.
After I said “not Services,” the design team asked what the alternative was. Several showed up on the whiteboard:
Work With Us. Decent, but feels like a recruitment page. There’s also ambiguity: “work with us” could mean “be employed by us” or “collaborate with us.” Pass.
Engagements. Too formal. Feels like a law firm. Pass.
Partnerships. Close to what we wanted, but already overused in tech. Every startup claims “partnership” for things that are actually transactional. Pass.
Solutions. I’m not going to explain why this one’s a pass. You already know.
What We Do. Too vague. Reader has to click to find out what.
Offerings. Sounds like a café. Pass.
How We Help. Friendly, but again communicates a helper-helpee dynamic. Pass.
We were stuck for days. Every option felt wrong in a different way. Until one of our partners floated a word none of us had thought of:
Collaborate.
We paused.
“That’s a verb, not a noun.”
Yes.
“It’s not standard in a nav bar.”
Yes.
“It communicates two directions.”
Yes.
Picked.
What the word does
I’m not going to write that we’ve been running A/B tests for six months and seen a conversion lift of X percent. We haven’t reached that point, and even if we had, numbers from one studio are too small to be useful as data for anyone else.
What I can write is this: before we built Dartstudio, most partners on this team spent over a decade on the other side of the sales conversation. As engineers or architects pulled into meetings after the agency or vendor had already signed the contract. We saw the same pattern over and over: clients showing up with expectations shaped by vendor signaling, and when those expectations didn’t match the reality of the engagement, the drama that followed was always the same.
Clients who came in through a door labeled Services arrived with briefs and asked for quotes. That’s not wrong. They read the signaling accurately. But when that vendor was actually a consultant who’d reject the brief because the brief was hiding a deeper problem, the first meeting became a mismatch. The client felt over-promised. The vendor felt under-appreciated. Nothing was wrong; the signaling was just lying from the start.
What we hope Collaborate does, and this is our hypothesis, not a conclusion, is attract a different conversation. The visitor who clicks an unfamiliar word is a visitor evaluating who Dartstudio is, not scanning for the cheapest vendor. They might arrive with a business problem asking for a discussion, not with a finished brief asking for a quote.
Is the hypothesis right? We’ll know in a few years. What we’re sure of now is this: old signaling will attract old conversations, with the friction we’ve already lived through in our previous careers. Changing the signaling is the cheapest way to avoid that friction. And if the hypothesis is wrong, the cost of changing one word in the nav bar is far smaller than the cost of running five-year engagements with clients whose expectations never matched.
A word in the nav bar isn’t a guarantee. But it’s the first hypothesis we bring into every conversation.
The broader implication
I’m not writing this to argue that every studio should swap “Services” for “Collaborate.” That’s missing the point.
What I’m arguing: the words in your navigation bar are the first filter prospects read, and they read it before they read anything else on the page.
Almost every business spends serious time writing copy for the hero section, value proposition, feature descriptions, testimonials. But the nav bar, which 100% of visitors see before 100% of the other content, usually gets filled with the default template: About, Services, Pricing, Blog, Contact.
That default communicates one thing to prospects: this business is standardized, just like thousands of other businesses with the same nav bar.
For some businesses, that’s the right message. For SaaS that wants to look reliable and familiar, following the template is reasonable. Their buyers want predictability.
But for a small studio, for a senior consultant, for a premium service business, for a founder whose positioning is different, following the template communicates that your positioning isn’t actually different. You claim boutique, but your nav bar matches a 200-person agency. Your claim contradicts your UI.
Some questions worth asking yourself:
Does every word in your nav bar accurately describe how you want to be treated? Or is there a word or two you picked because “that’s what other websites do”?
If you changed one word in your nav bar, which one would most shift prospect expectations? The answer usually points to the biggest mismatch between your positioning and your presentation.
Are you comfortable with the kind of inquiry your nav bar attracts? If you get a lot of inquiries with wrong expectations, your nav bar is probably inviting those expectations. Even when your hero section is trying to communicate the opposite.
A small note on cost
Swapping “Services” for “Collaborate” wasn’t free. We paid for it.
First cost: SEO. Nobody types “collaborate with a tech studio” into Google. People type “software development services” or “jasa pengembangan software.” If we wanted search traffic, we either had to compromise or get traffic from elsewhere.
We chose both. The URL path is still /collaborate, but the page title and meta description use more searchable language. The internal content uses keywords matched to search intent. We lose a little organic search. Not all of it.
Second cost: education time. Some prospects who called via referral were confused by the term. “So are you guys an agency or a consultancy?” We had to explain. That’s a small friction we added to the sales process.
But that small friction also works as a filter. Prospects who can’t sit through a paragraph of explanation usually can’t sit through long architecture discussions either. They want a vendor who quotes prices fast. That’s not us.
Every branding choice has a cost. The point isn’t to avoid cost. The point is to make sure the cost you’re paying leads to the filter you want.
Closing
I started writing this article thinking it was a story about one word. The more I wrote, the clearer it became this isn’t about a word. It’s about honesty between branding and operations.
If you run a studio that wants partnerships, but your nav bar communicates service vendor, where’s the honesty? Prospects reading your nav bar calibrate their expectations against it, and when they show up with wrong expectations, you either spend the engagement correcting them, or you give up and become the service vendor you claimed you weren’t.
I suspect many studios frustrated by “clients who don’t appreciate our expertise” are actually frustrated by clients reacting very accurately to their own signaling. If you signal service vendor at the nav bar, don’t be surprised when you get treated like one at the sales call.
The fix isn’t complicated. But it’s also not comfortable, because it forces you to pick an unfamiliar word, one that’s harder to explain, one that’ll lower inquiry volume before raising its quality.
That’s a trade-off that only makes sense if you’re sure about your positioning. If you’re not sure, if you still want the option to take every project that comes in, keep “Services” in the nav bar. That’s an honest word for a business that wants to stay flexible.
But don’t claim partnership while signaling transactional. Pick one. And let your UI match.