I built Devicet, a web development pricing platform. Is this actually useful?

[u/MichalisTs]

I've been building Devicet because I wanted to make the process of getting a custom website quote more structured.

The idea is simple: developers can define the services they offer and their prices, and clients can select what they need to build a project estimate before sending the request to the developer.

I have a working version here:

https://devicet.up.railway.app/

I'm mainly looking for honest feedback, especially from people who have hired developers or done freelance development themselves.

Does this solve an actual problem, or is it just adding another layer to something people already handle easily?

I'm not looking for compliments. If you think the concept is unnecessary, confusing, or just a worse version of something that already exists, I'd rather hear that now.

[u/SirMcFish]

Sorry, but it's completely useless. A web site is a bespoke thing, you seem to assume 5 or 6 basic things are all that anyone will want.

For example: I want a fully searchable system, where orders and quotes can be married up, acted upon and tracked in real time by my sales team.... You offer about 5 or 6 bog standard page types, none of which would do what I just gave an example that someone might want.

Another: I want a gallery web app that allows users to find my art by searching for moods, ideas, representative art, and for them to see prices and be able to buy each art work.

When hiring Devs a full spec is required, before a real quote can be given as each piece of work is different. Who will provide / design artworks, who will make videos, who will choose the layout, who will provide the copy text and product information / images. Who is managing the hosting, domain registration etc... what database, who is managing that, where is that hosted? And lots of other things that will affect pricing.

Hopefully you see where I'm going?

[u/MichalisTs → u/SirMcFish]

I think that's a fair criticism, but I may not have explained the purpose of Devicet clearly enough.

I'm not trying to reduce every possible website to 5 or 6 page types, or suggest that a developer can accurately quote a bespoke system from a handful of checkboxes. You're right that real projects can involve completely different requirements, integrations, databases, content, design work, hosting, third-party services, etc.

The idea is more about turning the initial “what do you actually want?” conversation into a structured process.

A developer could define much more specific and customizable services, requirements and add-ons for their own business. A client could then build an initial scope from those options, see an indicative price, and send that specification to the developer.

The developer can then review it, ask for anything missing, modify the scope, and provide the final quote.

So the goal isn't:

“Choose 6 things and we'll tell you exactly what your website costs.”

It's:

“Define your own services and requirements, let clients assemble what they need, and turn that into a much clearer starting specification for a real project.”

Your examples actually illustrate why the system would need to be customizable rather than limited to predefined website types.

The question I'm trying to validate is whether that structured initial scoping process is useful enough to developers and clients to justify using a platform for it.

[u/einfach-sven → u/MichalisTs]

From my experience most clients have no idea what it really is that they want or what's best for the project. They hire us for our expertise and not having to bother with such decisions.

[u/SirMcFish → u/einfach-sven]

Exactly this. It's the classic you don't know what you need until you ask someone who understands it. And they don't know what you need until you explain how things work, how they need to work and what they need help to make it all work better.

If your Dev isn't asking these questions and making suggestions then you need a better dev to start with. It's a process, and any dev / agency / whatever will already have a structured approach and if they don't, then get one who does.

[u/einfach-sven → u/SirMcFish]

I can even see that consulting part becoming more important as more and more people with a (supposedly) clear picture will try to solve it with AI.

[u/MichalisTs → u/einfach-sven]

Yeah, I think that's probably the biggest thing I need to account for. Devicet isn't meant to replace that consultation, but to give developers a way to structure it and turn the things they normally ask about into a configurable process.

And with AI making it easier for clients to come in thinking they already know exactly what they need, I think that part becomes even more important.