UX design listed as a separate line item on the quote — what is this, is it really necessary?

Ask the agency directly: "Will you provide a clickable wireframe prototype for us to approve before moving on to visual design?" If they start hemming and hawing, have that 45,000 TL line item removed from the quote immediately.

Correction: I misremembered the figure, it was a bit lower.

We went through a similar process on our wholesale website last year. We paid an extra 30,000 TL for the UX line item; they cut the 8 mandatory fields in the quote form down to 4 steps and simplified the filters. Our monthly B2B quote requests went from around 40 to over 70 in the first two months.

A lot of agencies out there just customize off-the-shelf templates and throw that buzzword in to pad the invoice. Are they really going to run user tests or interview a purchasing manager from the packaging industry? Highly doubt it. Most of them just sketch a couple of diagrams and call it a day.

you have every right to be skeptical because its an area ripe for abuse... think of it this way: UI is the storefront window, and UX is the aisle layout. even if the window looks amazing, if you walk out because you cant find the packaging you need on the shelves, that store wont make a dime but tbh thats really all it comes down to.

the other two agencies quoting a single lump sum will probably just code a ready-made template straight away. tbh the one breaking out ux is at least claiming they'll think through the site's logic but make sure the exact deliverables are written into the contract.

To see if they actually earn that money, ask for three specific deliverables: 1) A user journey map, 2) A category and filter hierarchy schema, 3) Monochromatic prototype testing. If they won't commit to these in writing, you're just paying for a fancy label.

I've been managing digital projects for years; a site with poor visuals but a seamless flow will always make sales. On the flip side, a site that looks stunning but drives people crazy when searching for a product is doomed. Cut down on the visual fluff if you must, but never compromise on information architecture.

This thread is archived.

The discussion got scattered let me summarize. When making decisions, write down the worst-case scenario too not just the best.

I'm also curious if anyone does it differently.

I think differently. If it's your first time, start small; scaling comes later.

Proven by experience.

Yes, that's exactly how it is with what is ux design. Processes without records never improve, because you don't know what to fix.

Good luck with that.

i agree and I'd like to emphasize that then every "we'll look at it later" in a meeting means unbilled work.

good luck with that.

I've been down this road, let me tell you. Any unwritten clause becomes a point of disagreement later, as both sides remember it differently.

Hasty decisions become decisions you have to fix six months later. That's all, sorry if I went on too long.

The discussion got scattered, let me summarize. Don't hesitate to ask; those who don't ask always pay more.

People defend habits, not processes. Resistance comes from there. Good luck with that.

I was thinking the same thing. Every "we'll look at it later" in a meeting means unbilled work.

Code without setup documentation isn't yours even if you have it.

Correct.

I'm curious too. When making a decision, first look at what data you have on hand.

If you have questions, write them; I'll answer as best I can.

I felt relieved reading this answer, so it's not just me. Hasty decisions become decisions you have to fix six months later.

The biggest time-waster for us was not knowing who had the final say. Good luck with that.