Skip to article
Notes for wedding creatives

Founder story

I Built the Wedding CRM I Actually Wanted to Use

Read the story
A filmmaker adjusting a camera on a tripod before a wedding ceremony
For the business behindthe beautiful work.

Who built Bower?

Bower was built by Clifton, a wedding filmmaker who has run Retrosound Films with his wife since 2018. He built it because every CRM he tried felt like more software than the job of booking a wedding actually needs.

That's the short version. Here's the longer one, in my own words.

I'm not the most organized person. That's a strange thing to admit on the About page of a CRM, but it's the whole reason this one exists.

HoneyBook was always a little extra for us

We used HoneyBook at Retrosound. Nothing was broken. It just always felt like overkill: more pages, more buttons, and more setup than I needed to send a couple a contract and an invoice.

Plenty of studios love it, and if you're a systems person who enjoys configuring every step, it might be the right fit. I'm not that person. I wanted to reply to an inquiry, get the contract signed, and get back to editing.

The moment that stuck with me came from the other side of the booking. More than once, a wedding planner emailed asking me to just send them a PDF of the contract so they didn't have to deal with HoneyBook.

When the people you work with are building workarounds to avoid your software, the software isn't helping anybody.

Read the full comparison: Bower vs. HoneyBook

I shopped around before I built anything

I didn't start out wanting to build software. I started out wanting to switch.

Dubsado was the obvious next stop, and it's powerful. But getting oriented felt complicated enough that the onboarding could have used its own onboarding. 17hats looked closer to what I wanted, but the price didn't make sense for how simply I work.

So I kept running into the same problem from different directions. Every option was built for someone more organized than me, or someone willing to pay more for features they'd never touch.

HoneyBook alternatives for wedding photographers

So I built the one I'd actually use

One day I decided to stop shopping and build the CRM I would use myself, before I ever thought about anyone else using it.

Before weddings, I spent years building websites, and I lived by one rule the whole time: keep it simple, stupid. Every feature on a page had to earn its spot. That rule came straight over to Bower.

In practice, it looks like this. An inquiry comes in and becomes a Project. The conversation, the wedding details, the contract, and the money all live in that one place, so I never have to rebuild a client record or go hunting for the last email.

The planner gets a link to view the contract. The couple gets their own links to sign. If a parent is paying the retainer, they get the invoice. Nobody has to create an account or remember a password.

If a feature doesn't make booking a wedding easier, it doesn't go in.

See how Bower works

What a coffee shop taught me about weddings

I also owned a coffee shop for a while. That's where I learned what it actually means to serve people well.

When there's a line out the door, nobody cares how clever your espresso program is. They care that you got their order right, fast, and made it feel easy. The good stuff happens behind the counter. The customer just gets their coffee.

Weddings turned out to work the same way. Couples remember how easy you were to book. Planners remember which vendors made their week harder. A couple shouldn't need a tutorial to sign a contract, and a planner shouldn't have to email you for a PDF.

Bower is built to keep the complicated parts on your side of the counter.

Why I'm putting Bower out there

I know how this can look. A wedding vendor launches software, and it's fair to wonder whether he's looking for a way off his feet and onto his peers' credit cards.

That's not how this started. Bower helped me first. It made my own booking simpler, and somewhere along the way I realized I couldn't be the only vendor who felt like HoneyBook was more than they needed.

If it helps other photographers and videographers book with less friction, great. And when vendors have an easier time, couples and planners do too. A cleaner booking is a better first impression for everyone involved, long before anyone sees a single frame of your work.

It's also why founding access is $19 a month for the first 100 studios, and that rate stays as long as your membership does. The first people who trust this thing shouldn't pay for that trust later.

Frequently asked questions

Who makes Bower?

Bower was built by Clifton, a wedding filmmaker who has run Retrosound Films with his wife since 2018. He built it for his own studio first, after HoneyBook, Dubsado, and 17hats all felt like more than he needed.

Is Bower made by a wedding photographer or videographer?

A videographer, but it's built for both. Photographers and videographers book weddings the same way: inquiry, contract, retainer, questionnaire, and a lot of follow-up in between.

Why is Bower simpler than HoneyBook or Dubsado?

Because it was built by someone who didn't want to configure his CRM. Bower keeps each wedding in one Project and sends clients private links with no account to create. HoneyBook and Dubsado offer more customization today, so if that's what you want, they're worth a look.

Is Bower a HoneyBook alternative?

Yes. It's a good fit if you mainly need to reply to inquiries, send contracts and invoices, and keep wedding details straight without extra setup.

Try Bower free for 14 days. No credit card, and you can test it with the contract you already send.

Make room for the good stuff

More weddings.
Less busywork.

Bring your own contract. Try your next booking.
See how Bower fits the way you work.

Try Bower free for 14 days No credit card. No client accounts.