So the current site looks like it's from 2005 + a twitter feed. Very all over the place with blue links and basically no colour scheme. Given the state of the current website I'm suggesting that my workload be:

  1. Redesign the website pages (a dozen or so simple pages)
  2. create a colour scheme
  3. re-do/completely redesign logos
  4. SEO
  5. hosting + ongoing management
  6. basic file upload facility (unsure if i want to provide a login system to do that)
  7. Potentially keep the twitter feed+ a couple other peripherals depending on the last bits the client wants.
  8. SSL
  9. Addition/linking/creating social media accounts.
  10. events
  11. probably some form of google analytics/tracking/cookie management for understanding user traffic.
  12. mobile friendly

I'm thinking in the region of $1-2k?

Write your answer…

5 answers

I would recommend to get paid by the hour instead of a fixed price. you can always be generous towards your customer and if you're getting super fast you need to up the price to reflect the speed and quality.

It depends on your tax model, every job as freelancer also should contain a buffer so you can eat and live before needing the next one directly after (so you don't have to take contracts because you need to eat for example) as well as healthcare and other points .... do your homework create an excel-sheet get the normalized fee of the market add the taxes, average it out over 12 months ... find out what you would earn if you would be employed compare it add the costs of employment and insurances .... get the delta and then have a look how long you estimate it would take in real net hours add at least 12% up and multiply it with .16% because net != reality

that is how much you should charge. not some random number what it feels like this is business do the calculations so you survive and have financial stability.

it's good that you ask how much you should take or 'what feels normal' but in the end this pure finance math ... you need to do it! or get someone who knows it and let them help you :).

Spot On1
Show all replies

Mark yes it's just a baseline, we would also need different granularities, pension, insurances, investment costs :). I just outlined the bare minimum how to get to a price.

Reply to this…

Hashnode is a friendly and inclusive dev community.
Come jump on the bandwagon!

  • 💬 Ask programming questions without being judged

  • 🧠 Stay in the loop and grow your knowledge

  • 🍕 More than 500K developers share programming wisdom here

  • ❤️ Support the growing dev community!

Create my profile

You have to decide what your rate is as a designer, whether it's hourly or by project.

What's your time worth? And what are you offering the client (in terms of skill and execution)?

Is this website a $1000 website, or could someone in a lower income bracket knock it off for $500? Is your client a high-paying client who's looking for $2000 work, or do they have a budget mindset that creates a cheaper looking $500 aesthetic?

There's lots of variability in the decision, and the value of design and development itself can't truly be encompassed in a proper pricing model. Is it a matter of raw materials and man hours - or is there an third element of creativity that increases the price? Inevitably it's up to you to decide.

Most of what you listed should be out of box stuff, so a grand would/should be the high end assuming the site were to remain static. -- excluding the hosting and on-call management fees which I'd be billing entirely separately.

Though some things, like the SSL, may be unnecessary/wasteful/pointless for them, depends on the topic of the site and what users are doing on it.

The file upload facility is the part that probably the only part that really should up the price to a grand before talking the ongoing fees. That's a spot were screwups can't be tolerated given the gaping security holes that can open if you don't dot all your t's and cross your i's... or, wait, that's not right.

I probably wouldn't charge more than a grand at the start unless I were to create a bespoke CMS under the hood for it -- which I'd be tempted to at LEAST create a "poor man's" system underneath for template management.

But it's hard to ballpark without knowing what the site is, how many separate pages it warrants, what the content is, and who their audience is.

It could be some things, like making it 'prettier' than their plain "2005" look (which is funny, what you describe sounds more like 1995) could in fact negatively impact their traffic. Remember, people visit websites for the content, not the goofy graphics or cutesy scripted behaviors you hang around it.

It's a 12 point list, but way not enough to make a price.

There should be answers (not here) to questions like:

  • exactly how many pages and subpages are we talking about?
  • is it just standard interface? Or sliders, accordeons, cards, etc.?
  • what do forms do? How many? Send mail? Store?
  • what app logic?
  • etc. etc.

i would recommend you create user stories for each requirement. then break those into smaller tasks and then estimate the effort based on the singular smaller tasks. i would guess that estimate you came up with doesn't even cover half of it. i mean you could agree on a price and then with the logo design you could have 30 changes one after the other because they are fussy clients.

you need to set out the client expectations and what you will offer for the price so both parties are clear on the agreement and what each of you are getting from it.

are you covering the costs of hosting? what about the SSL? are you providing a simple cheap SSL or an EV SSL?

SEO? wow. ok where do you start? onsite? W3C compliance? HTML5 valid? Rich text snippets? web Schema? etc etc...

File upload? to where? local server? a VM? or a cloud host such as amazon or google? are you paying the costs of the accounts?

hosting + management? how many hours management? 24/7 service?

seriously.. have a rethink..

Show all replies

Yes, in its most basic form but does the SSL come with warranty? Nope.

If you are serious about web security I would advise anyone to go down the EV SSL route.

Reply to this…