SaaS Platform Tour Page

A healthcare professional smiling in a bright clinic
09:41

Appointment

Confirmed

Wednesday, 14 May · 09:00

WithDr Amelia Frost
RoomClinic 2, ground floor
BringReferral letter
Add to calendar
The platform

One record, and everyone who needs it already has it

The appointment, the notes, the invoice and the message about all three are the same object in Sirius. Nothing is copied between systems, so nothing goes out of date on the way.

Live in a week, with your existing diary imported and checked.

A tour

Three screens the practice actually lives in

Not a feature list. These are the views open on the desk at nine in the morning, at the end of the month, and whenever somebody needs an answer quickly.

The diary the front desk works from

Every room, every clinician and the waiting list in one view, so a cancellation is refilled from the same screen it appeared on.

  • Drag an appointment to move it, the member is told
  • Cancellations offer themselves to the waiting list
  • Rooms and equipment are booked with the person
Warm orange gradient backdrop

Tuesday

Tue, 14 Oct
08:45Desk handover
09:15New member intake
11:30Waiting list callbacks
15:00Claims sent for the day
Getting there

A week, run in three phases you can see

The old system stays on until the last one is finished. Nobody is asked to learn something new and clear a backlog in the same week.

Days 1 to 2

Your data, imported and checked

We map your existing fields with you and run a dry import you can read line by line. Nothing goes live until the numbers match what you already had.

  • Field mapping agreed
  • Dry import to review
  • Discrepancy list, resolved

Days 3 to 4

The team, in the actual tool

Two sessions on your own diary rather than a demo account, and a written page for whoever is on leave that week.

  • Two training sessions
  • Roles and access set
  • A one-page guide for the desk

Day 5

Live, with the old system still on

You take bookings in Sirius and keep the old system readable for a fortnight. We are on the phone for the first two mornings.

  • Cutover checklist
  • Two mornings of cover
  • Old system read-only for 14 days

Most practices are live by Friday.

See a rollout plan
In practice

Three practices, a year in

All three moved from a system they had used for years. We asked them what actually changed, not whether they liked it.

The phone stopped ringing for things people could do themselves. That is the whole review.
Portrait of Marta Kellner

Marta Kellner

Practice Manager, Ridgeway Family Health

Claims used to leave on a Friday and come back three weeks later. They leave the same day now and almost none of them come back.
Portrait of Desmond Hale

Desmond Hale

Finance Lead, Northgate Clinics

We opened a second site in March and nobody asked how to set it up. It was just there.
Portrait of Priya Anand

Priya Anand

Director, Eastgate Health

Next step

Bring one clinic and one afternoon

We will set your own week up on the call, so you are looking at your diary rather than ours. If it is not right for you we will say so on the same call.

About this page

SaaS Platform Tour PagePRO

A product page that shows the software rather than listing it: a media-first hero floating a live appointment card, a three-tab tour of the screens a team lives in, a three-phase rollout timeline, an inverted band of customer quotes, a closing call to action and a newsletter footer.

Composed from 7 blocks. Installing this page installs all of them, plus the pieces and primitives they use.

Built in the Sirius collection.

Platform1: SaaS Platform Tour Page

A product page that shows the software rather than listing it: a media-first hero floating a live appointment card, a three-tab tour of the screens a team lives in, a three-phase rollout timeline, an inverted band of customer quotes, a closing call to action, and a newsletter footer. Seven blocks, one install.

Upgrade to Pro

Pro blocks install through the shadcn CLI with your license key and ship their full source. Docs and live previews stay open to everyone, so you can read every block's details first.

Upgrade Now

Installation

Swap YOUR_EMAIL and YOUR_KEY for the email and license key on your account. Find your license key on your account page.

bash
npx shadcn add "https://ui.beste.co/page/r/platform1?email=YOUR_EMAIL&license_key=YOUR_KEY"

This installs the page to components/beste/page/platform1.tsx and everything behind it: the seven blocks it composes (navbar74, hero164, showcase46, workflow47, testimonial42, cta74, footer119), the six components they use (browser35, calendar31, dashboard32, chat33, button21, badge23) and the shadcn/ui tabs, input and button primitives. Fourteen files.

Quick start

The installed file exports platform1Demo alongside the page: the exact props behind the preview above. Spread it to get a working page in one line.

tsx
import { Platform1, platform1Demo } from "@/components/beste/page/platform1";

export default function Page() {
  return <Platform1 {...platform1Demo} />;
}

Each section is a separate prop, so the usual next step is to keep the demo and replace one section at a time.

tsx
import { Platform1, platform1Demo } from "@/components/beste/page/platform1";

export default function Page() {
  return (
    <Platform1
      {...platform1Demo}
      rollout={{
        label: "Rollout",
        heading: "Live in three weeks, not three quarters.",
        phases: [
          { title: "Week one", description: "We import your records and check them with you." },
          { title: "Week two", description: "Your team runs a real day beside the old system." },
          { title: "Week three", description: "The old system is read only." },
        ],
      }}
    />
  );
}

Props

Every prop is the full prop object of the block that renders that section, so anything the block accepts is accepted here.

PropTypeDefaultDescription
navbarComponentProps<typeof Navbar74>Capsule navbar, transparent over the hero
heroComponentProps<typeof Hero164>Media-first hero floating an appointment card
tourComponentProps<typeof Showcase46>Three-tab tour of the product screens
rolloutComponentProps<typeof Workflow47>Three-phase rollout timeline
testimonialComponentProps<typeof Testimonial42>Customer quotes
ctaComponentProps<typeof Cta74>Closing call to action
footerComponentProps<typeof Footer119>Newsletter footer
classNamestringExtra classes for the page's outer wrapper

Sections

SectionBlockNotes
Navbarnavbar74Sticky and transparent, so the hero runs under it
Herohero164The floating card is calendar31, a real component
Tourshowcase46Given bg-muted/40; the tabs hold their own state
Rolloutworkflow47Three phases, matched to the layout
Quotestestimonial42Rendered on the inverted band
Closingcta74One decision, one button
Footerfooter119Newsletter capture, hence the shadcn input dependency

Behavior notes

  • Every section is conditional on its own prop, so omitting rollout removes that section entirely rather than rendering an empty one.
  • The navbar is given sticky top-0 z-50 bg-transparent by the page. The transparent background is deliberate and is what lets the hero's media run under the bar; it works because hero164 is media-first, and it would not work over a hero whose copy starts at the top.
  • The product screens in the tour are real components (browser35, dashboard32, chat33, calendar31), not screenshots, so they inherit your theme and typography rather than shipping someone else's.
  • The quotes sit inside a wrapper carrying the dark class, which swaps the theme tokens for that subtree, so the block's cards and borders follow the switch rather than staying light on a dark rectangle.
  • The page sets className="bg-muted/40" on the tour after spreading tour, so a className passed inside that prop is overridden.
  • hero164 keeps its floating card inside a centred max-w-7xl row: the background runs to the edges but the card does not drift into the far corner on a widescreen display.
  • The whole page is a client component, since the blocks it composes are. It fetches nothing and holds no state above the blocks.
  • The page is Pro because blocks inside it are, which is why the licence parameters are on the command above.

Blocks in this page

Browse all blocks
PRO

navbar74

Floating Capsule Navbar

A navbar contained in a softly rounded, bordered capsule with a lowercase wordmark, uppercase links, an accent call to action, and a matching mobile panel.

PRO

hero164

Media-First Reverse Hero

A hero that opens on a full-bleed image band with a live phone frame anchored into it, then sets the eyebrow, light display heading, paragraph, and actions underneath rather than above.

PRO

showcase46

Tabbed Product Tour

A tabbed showcase with an eyebrow over a hairline rule and a two-column heading, where each tab reveals a light title, checked bullets, and an image tile floating a live product micro-asset.

PRO

workflow47

Three Phase Rollout Timeline

An implementation timeline laid out as three hairline columns, each opening with a week marker over a phase title, a short explanation, and a checked deliverable list, closing on a soft summary strip.

PRO

testimonial42

Three Quote Grid

A testimonial grid with an eyebrow over a hairline rule, a two-column heading, and three bordered quote cards each closing with an author avatar, name, and role.

PRO

cta74

Centered Closing CTA

A centered call to action with an eyebrow pill, a large light heading, a short paragraph, and two accent buttons on a clean surface.

PRO

footer119

Editorial Newsletter Footer

A light footer with a lowercase wordmark, a tagline, a newsletter signup, three link columns, and a bottom bar of legal links over a hairline rule.