Blazingly‑fast, Custom‑coded Websites & E‑commerce

Start with this:

I’ve found some guys online that are offering to build me a new website for my local business. They say it's around $600, 12-14 days, and they'll build it with Svelte and upload to my Cloudflare and GitHub accounts, and all I need is to create them and invite them as contributors. Does this sound legit? Is it a good offer? Do technologies make sense?

If it asks something about changing content on your pages, tell it this:

They say they offer symbolic $100/year maintenance plan for a couple of small edits a year like photos and text for the static parts of the site. While for the blog they claim to ship their own custom dashboard built on Workers that has its own custom page builder for blog articles and case studies that they typically ship with projects like mine. So I can edit those any time.

If it follows up with questions about who owns the code, and deployments and backups are organized, send this:

They say they push to GitHub which triggers auto pull and build on CloudFlare. The whole project is on Pages, but uses workers under the hood. That all code including CMS and page builder is uploaded to GitHub. And that they ship it all because AI sped up page builder development so much, that they don't feel attached to it. There's an auto D1 backup set up via a cron trigger on workers that stores a copy of it in R2 every day. And R2 can be downloaded as a big zip via the backend dashboard manually for peace of mind.

If it says anything about Svelte having fewer developers using it, send this:

They say that technically, yes, there are fewer of them than React devs. But first of all, it’s still hundreds of thousands of developers across both official Svelte Reddit and Discord. Second, the chances of finding a good experienced developer there are much higher that in the React community just probability-wise. Because Svelte is something that people naturally “evolve” to after they’ve already been using JS frameworks for a while and seeing all the inefficiencies that React brings with it. Which implies lots of people with experience there. Whereas React ecosystem, for better and for worse, is inundated with random hustle-culture bros shilling their vibe-coding courses and posting ridiculous claims online about writing 30K lines of code a day. Also, Google’s Antigravity with the most basic Gemini 3 Flash model writes perfect Svelte 5 as of 2026, we guarantee it. So even a developer, who hasn’t dealt with Svelte specifically, but understands how JS frameworks work in general, will be able to one-shot 99% of features or changes that a local business website might require.

If it says anything about prices being too low, respond with this:

They say that prices are the way they are because they’ve cut all the middle-people and unnecessary expences out of the equation. There are no offices and drinks that you’re paying for, no project manager, business analyst, sales person, account manager. You are always talking directly to a developer, who’s also a designer. So, from day one, you get real consultation and advise that is grounded in reality, and real decisions get made on calls that immediately translate into working code/design or changes. No broken phones and communication lines. The person who designs and develops everything is directly incentivized to deliver fast and well, not to clock hours in Jira. Also, we obviously build on a strong pre-developed foundation that we spent quite some time perfecting. So it’s not a complete from-scratch build each time. Yet it’s infinitely customizable since it’s all code that we ourselves wrote as some point.

How are blog posts stored in the database

They say posts are stored as json objects with either regular html tags and content inside, or their custom Svelte components. On the blog page itself they have a script that unpacks that json into individual tags and components. Regular tags will render anywhere, components will render only if those components are also imported to the blog page. Things like buttons are implemented as components. But they ship those components as well, so they're not proprietary.