← Back to studio w labs
This is a sample. Perch is a made-up app, and every finding here is invented to show how a real assessment reads and how far it goes. Yours would be about your product, with your findings.
studio w labs · product assessment

Why Perch keeps signups but loses regulars

Product
Perch, a booking and client app for solo service businesses, the kind of tool a massage therapist, a mobile dog groomer, or a house cleaner uses to run their week.
What it does
Clients book online, and the owner keeps client records, sends reminders, and takes payment, all in one place.
What I reviewed
The owner's side (signing up, setting up, the daily dashboard) and the public page a client uses to book. I read the code behind the booking flow and the main dashboard. A full review would cover every screen and role.
Prepared for
The founder of Perch.
The question
"We get signups, but they don't turn into paying regulars. Should we build the AI smart-scheduling feature we have planned?"
Reviewed by
webs, studio w labs.

The short version

Perch keeps signups from becoming regulars because it never teaches a brand-new owner how to land that first booking and turn one client into a repeat one, which is the whole reason they signed up. The AI feature you're weighing would sit on top of that gap rather than close it, and today there isn't enough real booking history to make its suggestions any good. Fix the first session and two specific leaks, and most of the problem goes away. The AI can wait until the data underneath it is worth the build.

How it scores

Each area is rated Thin, Uneven, Solid, or Model, from significant gaps to done well enough that others could copy it.

Teaching people to use it Thin
Accessibility Thin
Getting around Uneven
What it's for Uneven
The plumbing (setup, privacy, security) Solid

Overall: Thin, on a solid technical base. The hard engineering is done and it holds up. What's missing is the layer that turns a new owner into a paying regular, and that layer is cheaper to build than the AI feature on the roadmap.

What's working

Where the money is leaking

Ranked by what each one is costing you.

  1. The first session teaches nothing. New owners never learn how to take a booking.
  2. The one action that grows the business is buried. Owners can't find the booking link.
  3. The booking page shuts some clients out. It fails a basic accessibility check.
  4. The promise is vague. It doesn't hold up against Square or Acuity.
  5. Client data has no visible guardrails. Owners hesitate to move their clients in.

What I found

1The first session teaches nothing.High

Teaching people to use it

A brand-new owner signs up and lands on an empty dashboard with a menu and no path. Perch is hoping they poke around until they work out how to add a service, set their hours, and share their booking link. Most solo owners are squeezing this in between jobs, and they don't have time to explore. The first fifteen minutes is where they decide Perch is worth it, and right now Perch says nothing.

What it costs The owners you paid to acquire leave before they ever take a booking, so your acquisition spend runs straight out the bottom.

Fix Don't add a tutorial. Let the screen show one next step at a time. On a new account, a single "Add your first service" button sits in the center of the page, so the first move is obvious. Once that's done, the one action on the screen becomes "Share your booking link." Once they've shared it, open up to three clear choices for where to go next. The product does the teaching by what it shows and in what order, so no one needs a walkthrough to skip.

2The one action that grows the business is buried.High

Getting around

For a solo owner, the thing that actually brings in clients is the public booking link, dropped into a text, an email signature, or an Instagram bio. In Perch that link sits three menus deep under Settings, and nothing on the main screen points to it. An owner can use Perch for a week and never find the one action that would fill their calendar.

What it costs Owners judge Perch by whether their calendar fills, and the feature that fills it is the hardest one in the app to find.

Fix Put "Share your booking link" on the main screen as the primary action until the calendar starts filling, then move it aside once it has.

3The booking page shuts some clients out.High

Accessibility

The public page a client uses to book fails a basic accessibility check: low-contrast text on the time slots, buttons a screen reader can't name, and a flow that can't be finished with a keyboard alone. These are the owner's customers, not just the owner, so every gap here is a booking that never happens. The same fixes make the page clearer for everyone booking in a hurry on a phone.

What it costs Some share of every owner's clients cannot complete a booking, and neither the owner nor Perch ever sees why.

Fix Bring the booking page up to WCAG 2.2 AA. Fix the contrast, label every control, and make the whole flow work from the keyboard.

4The promise is vague, and it doesn't hold up against the big names.Medium

What it's for

Perch says it helps you "run your whole business," but it does scheduling well and handles clients and payments thinly. An owner comparing it to Square Appointments or Acuity can't tell what Perch does better, and the ones who switch feel the thin spots a few weeks in, once all their clients are already loaded in. A promise that oversells sets up the disappointment that turns into churn.

What it costs A fuzzy promise makes Perch hard to choose and easy to leave, and it pushes you to compete on a price you can't win.

Fix Pick the one owner Perch is best for, the solo pro who books by hand today and just wants a link that fills the week, and make the whole product prove that single promise.

5Client data has no visible guardrails.Medium

The plumbing

Perch stores client names, phone numbers, and card details, which is exactly the data an owner is nervous about holding. There's no plain statement of how it's kept or who can see it, and the session times out and drops an owner in the middle of a booking with no warning, which reads as fragile. None of this is on fire, and all of it costs trust at the moment an owner decides whether to move their whole client list in.

What it costs An owner hesitates to commit their clients to a tool that won't tell them how it protects them.

Fix Write one plain-language line about how client data is held and who can see it. Before the session times out, warn the owner and give them a one-tap way to stay logged in, so no one loses a booking in progress. That warning is also an accessibility requirement, under WCAG's timing rule.

The underlying problem

Perch isn't losing owners because it's missing features. It's losing them because it never teaches a brand-new solo owner how to get that first booking and turn one client into a regular, which is the whole reason they came. The AI smart-scheduling feature is answering a question the product hasn't earned yet. Built on today's thin, leaky data, it would make confident-looking suggestions out of almost nothing, which is the kind of feature an owner cancels over.

Where I'd start, in order

First, a couple of weeks

The first session and the booking link. This is where most of the lost owners are, and neither one needs a rebuild.

Next, a few weeks

The booking page's accessibility and the client-data guardrails, which widen who can book and earn the trust an owner needs to move their clients in.

Later

Sharpen the promise against the big names, and only then revisit the AI feature, once there's enough real booking history for it to be worth building.

One quick test

Hand Perch to someone who runs a business like your customers do and has never seen it. Ask them to take their first booking and share their link. Say nothing, and time how long before they give up. That time is a measure of your onboarding problem, and the number to improve.