I’m testing a simpler path from HTML to a shareable page

As a web developer, I really like the idea of keeping this focused instead of turning it into another full website builder. The HTML/ZIP upload and instant publishing flow sounds especially useful for quick projects

You asked where new users get stuck, so here's one from ten minutes ago.

Your post says payment is intentionally disabled, and the landing says "Free beta, no payment required". Then the nav has Pricing, and Pricing has three plans with real numbers on them, plus a points currency I had to stop and work out. Three lines sat next to each other: "5 points per day", "50-point wallet", "1 point = one page online for one day". I couldn't tell if that means five new pages a day, fifty pages total, or one page kept up for fifty days.

So I never reached the sign-up to first-publish flow you actually asked about. I stalled one step earlier, on what this would cost me, and the answer was there twice in two different shapes.

To your actual question. The thing I'd want to know is what it costs to leave a page up and then forget about it, because that is the real behaviour with a side project. Nobody comes back to manage a wallet.

And a trade, if you want it. I spend 30 minutes on SaveKit properly, sign-up through first publish, the part you asked about, and you spend 30 on my entry page. Not opinions, a task. I'd hand you something like "find out what this costs and how long it takes", then shut up and watch where you stall. You'd do the same to me. Mine is a five-question quiz page for a product I sell. It's the part I already suspect is broken. 92% of people who land there never click a single question, and the numbers can't tell me whether they left or just sat there.

No hard feelings if it's not your thing, and no follow-up from me.

Love the signup → HTML/ZIP preview → live URL path — that mid-step is usually where people bounce. One useful metric set: time-to-first-shareable-URL, and preview→publish drop-off. If you offer 3–4 one-click starter templates (portfolio, changelog, waitlist, docs), you might shrink that gap without turning SaveKit into a full site builder.

the first publish flow is probably where i’d spend the next week too. i’d make the first success possible with a tiny preset or example someone can publish in one click, then let them replace it with their own html. a blank canvas is a lot of work before they know the value. i’d also watch whether people ask for expiry controls before publishing or only after they’ve shared something.

The sign-up → first publish path is the right place to focus. I’d track time-to-first-shareable-URL and where people drop between preview and publish; an example gallery of 3–4 page types (portfolio, changelog, one-page waitlist, docs) could make the blank-state decision easier without adding much UI. Which page type are early testers trying first?

Congrats on shipping SaveKit — the focused “paste HTML → shareable URL” flow feels useful for founders who want to validate an idea quickly without setting up an entire site.

I’m testing a small tool that reviews public landing pages for clarity/conversion blockers, using evidence from the page. I’d love to include savekit.net in a free beta review; in return, I’d only ask for 10 minutes of honest feedback on whether the diagnosis is useful. Interested?