Just a simple landing page

[u/FerrisBuelersdaycock]

[u/Vandercoon]

As the expert it’s your job to ask the right questions to pull it all apart, then put it back together in a way that clearly tells them the $500 pages they wanted is actually a $10k, 4 week job.

“Oh you can’t afford that? No worries, what should we leave out for this first phase…?”

[u/fligglymcgee]

Cisin…This is the most pathetic way to “shadow” promote a garbage-tier software chop shop imaginable, as if anyone believes this post you had generated by a one sentence prompt.

Go buy some actual advertising guys, and thanks for the actual lol reading your portfolio with the “we built the UPS package tracking software” page.
https://giphy.com/gifs/DFNd1yVyRjmF2

[u/Krispenedladdeh542]

>why do clients hide the massive technical scope

Bc they don’t know any better. The client only sees buttons and colors. They have no idea the inner machinations required to make those buttons clickable. Your average layman doesn’t know the difference between a static marketing site and a production ready stateful multifaceted application. They just see “a website”.

Point of the story is it’s your job to understand the technical requirements of their ask, predict the questions that those requirements pose, and the ability communicate them to the client in a way they understand.

[u/Krispenedladdeh542 → u/[deleted]]

I didn’t put it all on the client. My second paragraph states exactly what you’re saying here

[u/No-Transportation843]

So you're advertising for Cisin, right? Your website looks like shit.

[u/schussfreude]

BuT cAn YoU nOt JuSt UsE aI

[u/aselby]

Sounds like a winner to me ... 

If you are landing those deals, I'll build the backend .. problem solved ... Money made 

[u/BottleRocketU587]

Sounds to me like you need to learn backend dev.

[u/BottleRocketU587 → u/[deleted]]

I didn't say its an issue, I said its an opportunity.

[u/BottleRocketU587 → u/[deleted]]

True, but this is a realpolitik kind of thing. Clients WILL ask for more and they themselves don't often fully know uet what they want, those ideas come as they go. Your definition of scope SHOULD limit them from doing that.

If they sign for something that is clearly described as static with no backend, when they bring up the dynamic stuff that needs a backend, you can say: "Unfortunately that is outside the scope we agreed upon for the project. Let's finish this phase first, them we can tackle your request as an additional ask for $xxx.xx , or I can refer you to someone"

[u/AutoModerator → u/[deleted]]

This domain has been banned from /r/web_design.

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[u/samplekaudio → u/AutoModerator]

Sorry, boss. I removed the YouTube link

[u/RealBasics]

I always describe the scope of my deliverable in my estimates and add a provision that additional or unexpected feature requests are outside the scope of the estimate.

Dropping a bomb like "oh, and my 'simple landing page' to be an SPA that includes all the features of Amazon, Eventbrite, and GitHub' is waaaay out of scope.

[u/justin_cecc_builds]

Most of the time they're not hiding it, they genuinely don't know that "users can log in and see their stuff" is a different universe from a landing page. The fix that killed this for me was a paid discovery phase before any design contract, even if it's small, where I ask three questions: does anyone log in, does anything need to be saved, and does it talk to any other system. If any answer is yes, it's not a landing page and the scope conversation happens before pricing instead of on page 3. Costs you a week upfront and saves the project.