Blocks
6 blocks for a pre-seed startup page
A pre-seed page has to prove the problem exists and that somebody is solving it. Six categories, the order between proof and waitlist, the investor logo faults and the real catalogue counts.
Key points
- With no product, pricing turns into a waitlist.
- Seventy-four logo blocks, nearly all built for SVG.
- The newsletter collects consent, not only addresses.
A pre-seed page has to prove the problem exists and that somebody is solving it, not that the product is ready. The catalogue indexes 51 hero blocks, 74 logo, 53 feature, 41 pricing, 6 newsletter and 45 footer, read on 2026-11-01: six categories for a pre-seed page.
The numbers are per-category counts, measured the same day on the public pages. The logo category with 74 blocks is the richest of the six, and the riskiest: a strip of wrong logos on a pre-seed page shows more than a weak title.
What the page has to do
Whoever looks at a pre-seed startup wants three things within a minute: which problem it solves, why now, and who is behind it. The page answers with a concrete title, a visible demo or prototype and team names with what they did before. Promises about the future are allowed only when kept apart from what exists today.
- A verifiable problem, with the cost it carries today for those who face it.
- A declared stage: prototype, private beta or waiting list.
- Team names and background, not “a team of experts”.
- A way to be contacted again, with date and frequency.
The order of the blocks
| Section | Role on the page | Blocks available |
|---|---|---|
| hero | name the problem and its audience | 51 |
| logo | show who already believes | 74 |
| feature | explain what the product does today | 53 |
| pricing | build a waiting list | 41 |
| newsletter | keep contact without promises | 6 |
| footer | give team, address and contacts | 45 |
Hero, logo, feature, pricing, newsletter, footer. Logos sit high because on a pre-seed page they replace the customers you do not have: investors, accelerators or technology partners. Pricing is the block to rethink, not to skip: without a product it becomes a waiting list with access tiers, and the newsletter collects whoever wants to know when.
The blocks to start from
The tables list block, registry, files and category. The 4-file logo is a static strip: no animation, no CMS loading, so logos go in by hand and get updated by hand. The 2-file pricing holds three columns, which on a waiting list is already too many: two are enough, with and without early access.
Hero blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Hero 01 - Agency Hero Section | Shadcn Space | 8 | hero |
| Hero 02 - Real Estate Hero Section | Shadcn Space | 6 | hero |
Logo blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Logo Cloud 15 | Shadcn UI Blocks | 4 | logo |
| Logo Cloud 01 | Shadcn Space | 3 | logo |
Feature blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Feature 01 - Feature with Testimonials | Shadcn Space | 3 | feature |
| Feature 02 - Three Columns Feature with Icons | Shadcn Space | 3 | feature |
Pricing blocks
| Block | Registry | File | Category |
|---|---|---|---|
| Pricing 01 - Startup Pricing Plans | Shadcn Space | 2 | pricing |
| Pricing 02 - Scalable Pricing Table | Shadcn Space | 2 | pricing |
What breaks in production
The first fault is the logo strip: files arrive as PNG with different backgrounds and the grid looks like a collage, or an investor logo is used without permission and must be removed fast. The second is the waiting list confirming without saving, and the third is pricing promising a monthly figure for a product that does not exist.
- PNG logos with different backgrounds: the strip looks like a collage.
- A logo used without permission: urgent removal.
- A form confirming without storing the address.
- A monthly price on an unavailable product.
curl "https://ui.eneawork.it/api/blocks/category/logo?limit=5"The response lists five logo strips with source and files: read it to see which load from data and which have names written into the markup. On a pre-seed page the difference matters, because logos change every time a new investor joins.
A limit to declare
The 74 logo blocks assume monochrome SVG marks: with raster files, mixed transparent backgrounds and free proportions the grid breaks and gets normalised by hand. No catalogue block handles the consent a waiting list requires, and that stays legal work before technical work.
In the catalogue: logo strip, components and all blocks. The guides: measured heroes, copy-paste or headless and UI library weight.
Frequently asked questions
What replaces pricing when the product does not exist?
A two-tier waiting list, with the date you will share news and what signing up delivers. The price grid gets reused with new headings, but the copy must say nothing is being bought: otherwise the first confirmation email is already a problem.
Which logos can a pre-seed page show?
Only authorised ones: investors, accelerators and partners who agreed in writing. A logo lifted from a fund site without permission is a legal risk, and on a freshly published page it is also the first thing somebody reports.
Does a pre-seed site need a team section?
Yes, but with names and one line of background each. Whoever evaluates an early-stage startup invests in people, and a stock photo in place of the founder strips credibility from everything else on the page.
Newsletter or contact form?
Newsletter, with double opt-in and one line stating how many emails per month. A contact form on a pre-seed page collects few questions and many job requests; the newsletter measures real interest, which is the number that matters at this stage.
How do I update logos without touching code?
With an array in a data file and a component that reads it, or a CMS when the person updating is not technical. The catalogue block keeps names in the markup: refactor it once, and later an update is one data line.