Pulseboard Template: SaaS Landing With a Live Dashboard

Pulseboard Template: SaaS Landing With a Live Dashboard

Pulseboard is the product analytics starter in Zugo's gallery of 25 templates. It pairs a full SaaS landing page (funnels, retention, cohorts, pricing, FAQ) with a demo dashboard that recomputes its cards and chart when you switch the date range. Cloning it is free, and each change afterward is a chat request costing 3 credits.

The dashboard is what makes this template useful and also what makes it easy to misread, so the first thing worth settling is where the numbers come from.

What does the Pulseboard template ship with?

Two halves that share a visual language: a marketing site aimed at product teams, and a signed in workspace that looks like the tool being sold.

The landing page is a good study in objection handling. The FAQ does not sell, it answers the five things a skeptical engineer actually asks, and the how it works section shows code rather than describing it. Both patterns transfer to any technical product you are selling.

The dashboard sidebar is split into analyze and monitor, which is a sensible information architecture to inherit. The overview screen carries the pieces most product dashboards need: comparison against the previous period, a trend chart, and a table of top events filtered by platform.

Is the dashboard showing real data?

No, and this is the line to be clear about before you show it to anyone. Nothing is being tracked. There is no snippet collecting events, no backend, and no storage. The range switch recomputes the cards and redraws the chart in the browser from generated values, which is why it feels responsive and why the numbers change when you click.

The sign in screen says as much in small print: it is a demo, and no credentials are stored. Nothing behind it is protected, and reloading resets the workspace.

That does not make the dashboard worthless. As a design reference, an investor demo, or the front end of something you are about to build properly, it is a strong starting point that would take a designer days to produce. It is simply not an analytics product.

If you want real numbers about real visitors on a site you built with Zugo, that is a different and much simpler job: connect Google Analytics, which is one of the built in connectors, and read the data in its own interface. The setup is covered in how to connect analytics.

If you want the dashboard itself to display your own data, that means a database behind it, which is the Supabase connector plus a series of edits describing what to store and how to summarize it. It is achievable and it is a project, not a prompt.

Who should start from Pulseboard?

Anyone selling a technical product to technical buyers. The structure fits developer tools, API businesses, monitoring services, data platforms, and internal tools being pitched to a leadership team. The combination of an argued landing page and a plausible product view is exactly what a pitch needs.

It also fits founders validating demand before writing software. Publish the page, describe the product honestly as coming soon, collect signups, and find out whether anyone wants it. That is a legitimate use of a template, provided the page does not claim the product already works.

It fits badly if you need a real dashboard for real data on day one. In that case the template's marketing half is dead weight, and you are better off describing the dashboard you need from scratch, which the how to build a SaaS dashboard with AI guide walks through. The full map of what else is in the gallery is in the Zugo templates guide.

Which claims must come out before launch?

More than in any other template in the gallery, because this one sells trust. The page carries a security certification claim, a data residency claim, a GDPR readiness statement, an uptime figure, a bundle size benchmark, a median time to first result, an event volume included for free, and a row of customer logos. Every one of them is demo copy.

Compliance claims are the dangerous category. Saying you hold a certification you do not hold is not an exaggeration in marketing copy, it is a false statement to a buyer, and enterprise procurement will ask for the report. Delete those lines unless you can produce the document.

The pricing section needs the same treatment. Three tiers with feature lists look convincing, and they describe a product nobody has built. Replace them with your real prices or remove the section until you have prices.

Ask for the cleanup in one explicit edit that names the items: certification and compliance lines, the uptime number, the performance benchmark, the customer logos, the FAQ answers that reference storage and data handling, and the pricing figures. Naming them individually is what makes the result checkable.

How do you adapt Pulseboard to your product?

Meaning first, styling last, and decide the dashboard's fate early because it drives everything else.

1. Rename the product and rewrite the promise. One edit covers the name across both halves, the tab title and the footer.
2. Replace the three features with what your product actually does, keeping the pattern of a claim plus a small visual per feature.
3. Rewrite the three steps so the code snippets match your real integration, or remove the snippets if there is no code involved.
4. Fix pricing and the FAQ, or cut both until you have honest answers.
5. Decide on the dashboard: keep it as a labeled demo, remove it, or commit to wiring real data behind it.
6. Publish and check on a phone. The project gets an address like yourname.zugo.run, with a custom domain on top on paid plans.

Write each request so it can be judged done. "Make the hero punchier" and "replace the hero headline with this exact sentence and shorten the subheading to one line" cost the same 3 credits, and only one of them has a right answer.

What does adapting it cost?

Cloning is free, so the meter starts with your first edit. A landing page rewritten with honest copy is usually four or five edits, and a dashboard rebuilt around real data is a longer conversation.

Free gives you 5 credits, Pro is $25 a month for 200 credits, and Business is $99 a month for 800 credits. Two hundred credits is roughly 16 multi page platforms, 33 builds or 66 edits, so the marketing rewrite is cheap and the real cost sits in whatever you decide to build behind the dashboard.

Every build is opened in a sandbox first, and a version that fails to load is not delivered. A simple change comes back in about a minute, and a larger multi page rebuild takes a few minutes.

What can Pulseboard not do?

It does not collect anything. No autocapture, no events, no sessions. The snippet on the page is illustrative copy, and pasting it anywhere does nothing.

A real analytics product is not one prompt away. Ingesting events at volume, storing them, and querying them fast is genuine backend engineering. Zugo can build the interface and, with Supabase, a modest data layer behind it. It will not build a scalable event pipeline because you asked nicely.

Zugo does not replace a development team on a complex product. A landing page, a validated demo and a small internal dashboard are all comfortably in range. Past that point you want engineers, and the GitHub export exists so the project can leave with you.

The sensible first move costs nothing. Open the gallery at zugo.dev, clone Pulseboard, strip the claims you cannot back, and see whether what remains is a page you would actually send to a customer.