Good Fit Qualifier

Honest answers

Whether this is for you, before you spend an hour finding out

We would rather lose the call early than lose it in month three. Here is the shape of practice Sirius suits, and the shape it does not.

A good fit if

These are the practices where the product earns its place in the first fortnight.

  • You run between one and twenty clinical rooms
  • Scheduling, records, and billing are three systems today
  • Somebody spends their morning reconciling those three
  • You want a named engineer rather than an account manager
  • You are willing to move one clinic first and judge from that

Probably not if

We will say so on the first call rather than sell into the gap.

  • You need inpatient or ward management
  • Your rota is built around shift patterns rather than appointments
  • You require an on-premise deployment
  • Procurement needs a five-year fixed contract
  • You want the product bent to match your current process exactly

What if we are close to the second list?

Tell us which line and we will give you a straight yes or no on the call. Twice a year that answer is yes and we build the thing; more often it is no and we say so.

Do you ever turn practices away?

Four times last year. Two needed inpatient management, one wanted on-premise, and one was three weeks from a merger and should not have been changing systems at all.

Will you tell us if we should stay where we are?

Yes. If the reconciliation problem you have is a process problem rather than a software problem, replacing the software will not fix it and we will explain why.

Not sure which list you are on?

Ask before you book
About this block

Good Fit QualifierFREE

A qualifying FAQ that sets a checked good-fit column against a crossed not-for-you column, then answers the three questions that follow from them on two-column hairline rows.

Faq88: Good Fit Qualifier

A qualifying FAQ that sets a checked good-fit column against a crossed not-for-you column, then answers the three questions that follow from them on two-column hairline rows.

Free block

This block is free. No license or account is required: install it with the CLI and use it in unlimited projects.

Installation

Radix flavor

bash
npx shadcn add "https://ui.beste.co/r/faq88"

Base UI flavor

bash
npx shadcn add "https://ui.beste.co/r-base/faq88"

This installs the block to components/beste/block/faq88.tsx plus the badge23 and button21 components it uses for the eyebrow and the closing action.

Quick start

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

tsx
import { Faq88, faq88Demo } from "@/components/beste/block/faq88";

export default function FaqPage() {
  return <Faq88 {...faq88Demo} />;
}

Then replace the demo with your own props. Written out, a trimmed setup looks like this:

tsx
import { Faq88 } from "@/components/beste/block/faq88";

export default function FaqPage() {
  return (
    <Faq88
      badge={{ label: "Honest answers" }}
      heading="Whether this is for you, before you spend an hour finding out"
      description="We would rather lose the call early than lose it in month three."
      fit={{
        title: "A good fit if",
        description: "The practices where the product earns its place in the first fortnight.",
        items: [
          "You run between one and twenty clinical rooms",
          "Scheduling, records, and billing are three systems today",
        ],
      }}
      notFit={{
        title: "Probably not if",
        description: "We will say so on the first call rather than sell into the gap.",
        items: ["You need inpatient or ward management", "You require an on-premise deployment"],
      }}
      items={[
        {
          question: "What if we are close to the second list?",
          answer: "Tell us which line and we will give you a straight yes or no on the call.",
        },
      ]}
      closingLabel="Not sure which list you are on?"
      button={{ label: "Ask before you book", href: "/contact" }}
    />
  );
}

Props

PropTypeDefaultDescription
badge{ label: string }Eyebrow above the hairline rule, rendered through Badge23
headingstringSection heading in the left column of the header
descriptionstringSupporting paragraph, right-aligned from md up
fitFitColumnThe good-fit column, checked and accent-bordered
notFitFitColumnThe not-for-you column, crossed and plain
itemsFaqItem[][]Follow-up questions on hairline rows
closingLabelstringPrompt beside the closing action
button{ label: string; href: string }Outline closing action
classNamestringExtra classes for the outer section
ts
type ActionLink = {
  label: string;
  href: string;
};

type FitColumn = {
  title: string;
  description: string;
  items: string[];
};

type FaqItem = {
  question: string;
  answer: string;
};

Behavior notes

  • The two columns are separate named props rather than an array, so each side has a fixed meaning. The positive column is always first and always accent-bordered, and the negative one always uses the plain border on a muted surface.
  • Icons follow from position, not from a flag on the item: the good-fit column gets Check in the accent, the other gets X in muted. Both are aria-hidden, since the column heading already frames the list.
  • Either column can be omitted and the other still renders in its own grid track, so a one-sided version is possible without editing the block.
  • List rows carry border-t with no closing rule, so both lists stay open at the bottom and the card's own padding closes them instead.
  • Cards are flex flex-col, so a pair with different amounts of copy still fills the row evenly.
  • The follow-up rows are a 1fr to 1.6fr split from md, giving the answer more width than the question, and stack below md.
  • Question rows render as h3, keeping the section a real outline under the h2.

More FAQ blocks

View all FAQ
PRO

faq90

Security Questionnaire Answers

A procurement FAQ grouping security controls into hairline rows that pair each question with a tone-coded yes, partial, or not-yet chip and the detail behind it, closing on a security pack request.

PRO

faq70

Two-Column FAQ

FAQ accordion split into two independent columns.

PRO

faq81

Grouped FAQ Columns

FAQ split into two labelled groups, each an independent accordion of ruled questions, so a long list stays scannable by topic; closed by a response-time note beside an outline pill CTA.

FREE

faq80

Two Column Answer Grid

An always-open FAQ laid out as a two-column grid of numbered, hairline-separated question and answer entries, closing with a soft support panel that pairs a short prompt with two actions.

PRO

faq94

First Call Questions

A split FAQ: a sticky column with an eyebrow, a serif heading that settles in word by word, an intro and a pill action, beside a ruled accordion whose serif questions open to calm, plain answers.

PRO

faq9

Three Column Grid

Q&A pairs arranged in a responsive grid layout. Ideal for displaying concise answers in a scannable, multi-column format.