There are a number of ways you could go with this:

Cost+: Close to what you are suggesting: Calculate your hourly cost, add a profit. Then define your projects with your client, and estimate number of hours of work. That would be your price - like craftspeople do it. The pro for this approach is, that you let your own cost determine your price, which is very inside-out making it easier for you to justify your hourly pay. But the con is, that your customers will challenge your estimate, and you will spend a lot of time quantifying projects. But if you don't know yet how much time each project will take, this could be a way to start off. Benchmark against market price, though or find the price sensitivity of your customers.

Create products: When you have more knowledge of clients needs and time used for development, you could package your development into products and charge for that. Small - Medium - Large with a development price for each. You could do it as a one-off, or you could integrate it with a maintenance model - see next.

SaaS-model: You could integrate your site development with maintenance, provide SEO and similar service. That would make it very convenient for your customers, and create an ongoing cash flow for you as a subscription fee. Either as a fixed monthly fee or as part of the cash flow through the website, if you want to share risk and upside.

But no matter what you do, make sure you know the delivery of your competitors. Where are you unique in your delivery? What do your competitors charge? Unless you deliver something truly unique, you have to be within the same price range.

I hope some of this could work for you. If you want to discuss your pricing possibilities further, feel free to mail me or set up a call.

Best regards

Kenneth Wolstrup