01
Built in development
rabR
For clients
Ask for a cut with your service, day, area and price. Compare offers, then book.
Good cuts. Local connections.
Under development · Calgary first · Android first, then iPhone
The apps
Purpose-built apps keep each side of the marketplace focused.
01
Built in development
For clients
Ask for a cut with your service, day, area and price. Compare offers, then book.
02
Built in development
For barbers
Find requests, send clear offers, manage appointments, and build a profile you own.
03
Planned
For barbershops
A dedicated app for barbershops is planned.
How it works
rabR starts with what a client needs. A barber responds with clear terms. The client decides what to accept.
A service the client is looking for.
A barber considers the request
A response the client can compare.
The client accepts one offer
The agreed service and terms, kept together.
Both sides can view the booking
Built in development
Accepting one offer closes the request and declines the other open offers. Declining one offer keeps the request open.
For clients
Keep the service, timing and price together so each proposal is easy to compare.
Built in development
Choose the service, preferred day and time of day. Add your area, exact address and proposed price in CAD. Your address stays separate from the area barbers browse.
Compare the barber, date, time, price, duration and short note. An offer can suggest a different day or price. Accept or decline.
Acceptance creates one appointment. The service, agreed time, price, duration and address stay together for you and the barber.
For barbers
Review local requests, make clear offers and manage the appointments that follow.
Built in development
Go Online enables request browsing on your phone. Choose a date to see open requests and their service, time preference, area and proposed price.
Propose a date, time, one CAD price and a service duration. Add a short note if needed. You can have one open offer on each request.
When a client accepts, the agreed details appear in an appointment. Either person can cancel before the start. From the start time, the booked barber can mark it complete.
Note / 01
It controls browsing on your phone, not a public availability calendar. Going offline hides requests and pending offers from your view, but a client can still accept an offer you sent. Appointments remain accessible. The app does not check for new requests in the background.
Built in development · server
Being connected and tested · app screens
Every barber applies and is reviewed by rabR’s founder before they can see requests or send offers.
Built in development · server
Being connected and tested · app screens
Add a short bio, services with a price and time each, and languages. Stats come only from completed rabR appointments. Profiles have no outside links or contact details.
Trust by design
Built in development · server
Being connected and tested · app screens
Every barber applies. rabR’s founder reviews each one before they can browse requests or send offers.
Built in development
Browsing uses a server-side approximate pin within a roughly 1 km × 1 km cell. The app does not use phone GPS.
Built in development
Only clients of completed appointments can rate. Every rating counts. Ratings appear after the week ends.
Built in development
Profiles carry no outside links or contact details, so no one is sent to another app.
Where Claude fits
We're adding Claude, an AI model made by Anthropic, behind the scenes. It never talks with clients, and it never makes the final call about a person.
Planned
Before a barber's bio goes live, our own rules check it first. Then Claude double-checks it for hidden phone numbers, links and unsafe words.
Planned
Claude will summarise each barber application so our founder can review it faster. The founder still decides every time.
The price map
The map puts area and price in context without placing an exact address on the map.
Being connected and tested
Open requests appear as pins labelled with the client’s proposed price. A pin opens the request details. Overlapping pins group together for a closer look.
Planned
The planned view shows a client’s own open requests and offers. It is not a directory of every barber or other clients’ requests.
The server keeps a randomly placed point inside the selected area’s roughly 1 km × 1 km cell. It stays fixed. The exact address is withheld while barbers browse and send offers, then shared with the booked barber in the appointment.
The map does not use phone GPS or turn addresses into map points.
Built in development · server-side approximate pins
Progress
Android is first, with Calgary as the initial focus. Development work is not the same as a finished release.
Built in development
Sign-in, client requests, barber offers, appointments, star-and-tag reviews, the barber’s device-only Go Online mode, and server-side approximate map pins.
Founder approval and barber profiles with bio, services, languages and earned stats are built on the server.
Being connected and tested
Client area selection, the barber map with development data, approval and profile screens, and the request-to-appointment journey on Android phones.
Planned
The client map, direct booking and payments.
No real money moves in the app today.
About
rabR is being built in Calgary, Alberta, by founder Karanveer Singh. We're starting with one city and getting the basics right: fair offers, approved barbers and clear rules.
Contact