solo stack
← All work

Case study

live

Every bride in one place, from the first appointment to the day she collects.

RingUps runs the front and the back of a bridal boutique. Who is in which fitting room, what has been ordered in for a named bride, what she has paid, and what the new Saturday hire needs to know before she touches a gown. It replaced a booking tool, several spreadsheets and a drawer of handwritten cards.

Retail and appointments · built for a bridal boutique · live and in daily use

One record

Her appointments, her order, her payments and her fittings, all against one name.

Six stages

From the deposit going in to the day she walks out with the gown.

Three rooms

One column each, to the minute, so two people cannot take the last slot.

The problem, in her words

Four places, and the bride was in all of them.

Nothing here was a software problem to begin with. It was four honest systems, each of them fine on its own, none of them able to answer a question that crossed between them.

The calendar knew she was coming in. It did not know what she had bought.

Bookings in one tool, orders in a spreadsheet, and nothing joining the two.

I only found out a gown had never been ordered because the bride rang to ask.

A deposit taken in March, a purchase order nobody raised, and a wedding in June.

Her deposit went in the till and that month looked brilliant. The gown cost me in July.

Money taken counted as money earned, so the good months were not real months.

Every fitting note was on a card in a drawer, in whoever happened to write it.

Alteration notes that only made sense to the person who wrote them.

What that actually cost

The typing was the small part. The real cost was that one person held the whole thing in her head, so nobody else could cover a Saturday properly, and a mistake only ever surfaced when a bride phoned to ask about it.

[ 01 ]  The day

A Monday, one column per fitting room.

This is the screen the shop opens at nine. A two hour bridal appointment looks like two hours, not like one line in a list, so nobody books a fitting into a gap that was never really there.

ringups — appointments

Monday, 14 September 2026Juniper & Ash Bridal, Okotoks

Mon

14

11

Tue

15

7

Wed

16

9

Thu

17

12

Fri

18

14

Sat

19

16

Sun

20

All appointments9Booked1Completed1Cancelled
09:0010:0011:0012:0013:0014:0015:0016:0017:0018:0019:00
Ivory Room

Amara Reyes

Bridal consultation · DK

Priya Anand

Second look · DK

Hana Ito

Bridal consultation · SR

Now

Meghan Doyle

Bridal consultation · SR

Blush Room

Jasleen Sandhu

First fitting · BK

Rosa Delgado

Final fitting · BK

Team meeting

Blocked ·

Naomi Okpik

Collection · DK

Alterations 1

Simone Tremblay

Alterations fitting · EN

Farah Haddad

Alterations fitting · EN

Bev Kowalchuk

Alterations fitting · EN

Cancelled appointments hold no room, so the slot can be resold. Every name invented.

Two people cannot take the last slot

The system itself refuses the second one. It is not a matter of somebody noticing in time.

A cancellation frees the room

A cancelled appointment holds nothing, so a Saturday morning can be sold again the same day.

Blocked time stays blocked

A team meeting or a mirror being replaced is not a bookable gap. It shows as what it is.

Every name, figure and date on these screens is invented. The layout is exactly what the software does.

What we built

One record per bride, and everything hangs off it.

A bridal sale is not one transaction. It is an appointment, then a decision, then a deposit, then an order placed with a designer on the other side of the world, then a gown that turns up months later, then three fittings, then a day that cannot move.

Each of those steps used to live somewhere different. Now they are written against the bride, in the order they happened, with a name and a time on each one. Whoever is standing at the counter can answer the question she is actually asking, without going to find the owner.

One order, start to finish

She books

Written up in the room

Deposit taken

money you owe

Ordered from the designer

The gown arrives

Fittings

She collects

now it is a sale

The day

Bookings, fittings and collections, by room and by person, drawn to the minute.

What is in the shop

Gowns, samples and accessories, and what is on order for a named bride.

The money

Deposits, instalments and the balance, held against her order rather than a loose receipt.

The training

Short courses your staff work through on a phone, with proof that they passed.

[ 02 ]  The order

Where her gown is, and taking the balance on the same screen.

Every bride asks the same question, and answering it used to take two people and a phone call to a supplier. The rail across the top of this screen is the answer, in one look.

ringups — order OR-2026-0418

Priya AnandEvent date 19 Jun 2027 · sold by Dale Nakamura, 2 Mar 2026
  1. The order is written

    2 Mar 2026, sold by Dale Nakamura

  2. Contract signed

    2 Mar 2026

  3. Deposit taken

    $1,500.00 on 2 Mar 2026

    Held as money owed until collection.

  4. Ordered from the designer

    PO LW-4471, 14 Mar 2026

  5. You are here

    The gown arrives

    1 of 2 received, 28 Jul 2026

  6. Fittings

    0 of 3 booked

  7. Balance settled

    $2,500.00 of $4,467.75 paid

  8. She takes it home

    The held deposit becomes revenue on this day

ItemSupplierDetailAmount
Gown — style 7412Lindenwood AtelierSize 10 · Ivory · Special order3,450.00
Cathedral veil — 108 inLindenwood AtelierIvory · Cut to length385.00
Alterations — package BIn houseThree fittings included420.00

Subtotal 4,255.00

GST 5% 212.75

Total 4,467.75

Payments

DateKindMethodAmountTaken by
2 Mar 2026DepositVisa ····44171,500.00Dale Nakamura
14 Jun 2026Instalmente-transfer1,000.00Bev Kowalchuk

Paid $2,500.00 · Balance $1,967.75

$1,500.00 deposit held as money owed until collection.

Take payment

$1,967.75

CardCashe-transferStore credit

Card number

MM / YY

CVC

Send a payment link instead

The card form sits inside the page. The number never reaches the shop's own system.

Countersigned — D. Nakamura, 2 Mar 2026

Full name

Priya Anand

Title

Customer

Priya Anand

Typing a name records the date, the time and the address it was signed from. The printed page and the emailed copy are worked out once, from the same wording.

Print the agreement
An invented order. The deposit is held as money owed, and only becomes a sale on the day she collects.

The board that does the chasing

An order nobody placed does not go quiet.

Six columns, from a bride placing an order to the day she collects. The dates run backwards from the day she actually needs the gown, so an order that was never placed turns up here a fortnight after the deposit, rather than a fortnight before the wedding.

ringups — special orders

4 lines need attention. Brides whose date has passed are hidden — 3 hidden.
Bride placed order2

Sold, but not ready to move

Meghan Doyle · style 6120, size 8

Lindenwood Atelier · wedding 14 Aug 2027

Deposit unpaid

Okpik wedding party · style 3308 ×4

Marchmont Bridal · wedding 22 May 2027

Measurements missing for 2

Ready to be placed3

Deposit paid, details complete

Hana Ito · style 7412, size 6

Lindenwood Atelier · wedding 10 Apr 2027

Place now — 16 days since deposit

Simone Tremblay · style 2255, size 12

Ashgrove Gowns · wedding 27 Mar 2027

Rush

Farah Haddad · style 8801, size 14

Marchmont Bridal · wedding 4 Sep 2027

Order confirmed2

Designer confirmed, with a number and a date

Jasleen Sandhu · style 4470, size 10

PO AG-2287 · expected 30 Nov 2026

Rosa Delgado · style 1190, size 8

PO LW-4468 · expected 15 Oct 2026

Waiting on arrival3

In production or shipping

Priya Anand · style 7412, size 10

Expected 26 Sep 2026

Bev Kowalchuk · style 5533, size 16

Expected 2 Oct 2026

At risk — wedding in 7 weeks

Amara Reyes · style 9007, size 4

Expected 18 Dec 2026

Arrived2

In store, on this list only

Naomi Okpik · style 3308, size 10

Arrived 21 Jul 2026

Pickup overdue — 19 days in store

Novak wedding party · style 6641 ×2

Arrived 4 Aug 2026

Picked up1

Collected recently

Poitras wedding party · style 2210 ×3

Collected 6 Aug 2026

Deadlines worked backwards from the date she actually needs it. An order nobody placed does not go quiet — it turns up on this board.

The rule that earns its keep

If two bridesmaids need fabric from the same batch, it stops you placing half the order. Nobody has to remember that, because the software refuses it at the point of ordering. It can be overridden with a deliberate tick, and it never happens by accident.

Every name, figure and date on these screens is invented. The layout is exactly what the software does.

The detail that changed the accounts

Money you have taken is not money you have earned.

A deposit sits as money you owe until the day the bride walks out with the gown. On that day, and not before, it counts as a sale. That sounds like a technicality right up until the first time a brilliant March turns out to have been paid for by gowns you had not bought yet.

A good month is a real month

March stops looking brilliant on the strength of gowns you have not bought yet.

Your bookkeeper stops guessing

The figures come out in the shape an accountant already recognises, with no unpicking.

Nothing is edited behind you

A correction is a new line with a name and a time against it, never a quiet overwrite.

[ 03 ]  The people

The person on the floor on Saturday is not the person who knows.

A boutique loses more money to that gap than to almost anything else. So the same software teaches, and keeps the proof that it did.

training — handling a special order

Course progress38%

A gown that arrives wrong is only cheap to fix in the first hour it is in the building. Everything on this page is done before it goes on the rail.

Check the style number on the bag against the purchase order before you cut the tape.

Dye lot

Two gowns in the same wedding party must come from the same dye lot. If they do not, stop and flag it before either is altered.

Style number

Damage on arrival

  • Style number matches the purchase order
  • Size matches the purchase order
  • Colour and dye lot recorded
  • Photographed in the bag
  • Bride emailed the same day

If anything on this list fails, do not hang it. Leave it bagged and tell the manager the same day.

Nothing is marked complete until the quiz is passed, and the record is written by the system rather than claimed by the learner.
  • They pick up where they stopped, on a phone, between appointments
  • Nothing counts as finished until the quiz is passed
  • The record is written by the system, not claimed by the learner

Every name, figure and date on these screens is invented. The layout is exactly what the software does.

What it proves

It is not really about bridal.

Take the gowns out and this is a shape a great many businesses have. You book people in for time. You order things in for one named customer. And you take money months before you deliver anything.

A salon

Chairs and colour rooms instead of fitting rooms.

A shade ordered in for one client, needed on the day of her wedding.

A clinic

Treatment rooms, and a therapist who can only be in one of them.

An insole or a brace made to measure, with a lab in the middle.

A tattoo studio

Booths and artists, booked in half days.

A deposit held against a day that cannot be resold at short notice.

A furniture or flooring shop

The measure, then the fitting, with two vans and four crews.

A sofa in a fabric that is nine weeks out, sold to a named customer.

A kitchen showroom

Design appointments that run two hours and cannot be squeezed.

Doors and worktops on separate lead times that have to land together.

An optician

Eye tests, then fittings, then collections.

Lenses made to a prescription, with a customer waiting on them.

What it does not do

  • It does not send text messages. Nothing has ever been sent from it and no account is set up for one.
  • A purchase order prints, or saves as a file. Somebody still sends it to the designer.
  • The time clock records hours and deliberately does no pay maths. Payroll stays where it is.

If your business has the same shape

Whatever we build for you, you own it.

A first call is thirty minutes and costs nothing. You tell us the part of the week that is worst, and we tell you honestly whether this is worth building or whether you should buy something off a shelf.

It is yours from the first day

It sits in accounts in your business name, not in ours, so it keeps running whether or not we do.

Anyone can pick it up

It is built with ordinary, widely used tools, and written down in plain language for that reason.

There is nothing to pay to leave

No exit fee, no notice period on the build, and a full copy of your own information comes with you.