← Back to the Blog

REGAL PULSE · BLOG

Why I built Regal Pulse

Why I Built Regal Pulse I've spent years running ecommerce websites, and one thing I've learnt is that a website being online doesn't necessarily mean it's working. I was reminded of that rather painfully recently. I'd…

Why I Built Regal Pulse

I've spent years running ecommerce websites, and one thing I've learnt is that a website being online doesn't necessarily mean it's working.

I was reminded of that rather painfully recently.

I'd updated a plugin on one of my ecommerce sites and, somewhere in the process, the add-to-cart functionality stopped working properly.

The website was still online. The homepage loaded. Product pages loaded. Everything looked normal.

Except customers couldn't actually buy anything.

It stayed that way for nearly a day.

And how did I find out?

A customer emailed us.

That's a pretty terrible monitoring system.

The problems you don't know about

That wasn't an isolated incident.

I've had PayPal checkout stop working because a cookie had been incorrectly categorised. Everything worked perfectly if a visitor accepted cookies, but reject them and suddenly they couldn't complete their purchase using PayPal.

I've had forms stop submitting because of broken conditional logic.

I've had forms stop working because CAPTCHA wasn't behaving as expected.

And then there are problems that aren't really technical faults at all.

On the same day I'd been trying to work out what had broken my add-to-cart button, I spoke to one of my ecommerce clients after a big product launch.

There had been plenty of anticipation for the launch, but some of the products went live showing as out of stock.

The website hadn't failed. The server wasn't down. Nothing had crashed.

Inventory had accidentally been assigned to a different SKU.

It was spotted a few hours later and corrected, but those first few hours were some of the most important hours of the launch.

How many people came to buy, saw "Out of stock" and simply left?

We don't know.

And that's exactly the problem.

"Your website is up" isn't enough

I've used uptime monitoring for years, and it's useful.

But I've become increasingly frustrated with the idea that a website can be considered healthy simply because a server responds and a page loads.

Imagine walking into a physical shop.

The lights are on and the front door opens, so technically the shop is open.

But the tills aren't working.

You can't put anything in your basket.

Half the products have the wrong stock status.

And the form at the customer service desk doesn't actually go anywhere.

You probably wouldn't describe that shop as working properly.

Yet online, a traditional uptime monitor could quite happily give you a green tick while all of that is happening.

I wanted something that looked at a website more like a customer does.

The idea that became Regal Pulse

The idea had been sitting somewhere in the back of my mind after that particularly bad day, but the actual concept came together a little later.

It was a Sunday evening and I was watching YouTube videos about UI and UX design.

Then something clicked.

What if I built something that actually followed the customer's journey?

Not just "Does the website respond?"

Can I open the product?

Can I select the options?

Can I add it to my basket?

Can I get through the journey I'm supposed to be able to complete?

And, importantly, if something stops working, can I find out before a customer has to tell me?

That was the original idea behind Regal Pulse.

It started as a customer journey monitor.

It didn't stay that way for very long.

Because websites don't break in isolation

The more I worked on it, the more I realised the same problem exists in lots of different places.

You make a change to improve one part of your website. Did it accidentally affect something else?

Your website is still running, but has something important changed?

Have your Google rankings suddenly dropped?

Is a page that was performing well now behaving differently?

Is there an issue that has been quietly sitting there for days because nobody has happened to stumble across it yet?

There are plenty of tools that can give you individual metrics. What I wanted was something that kept watch over the bigger picture.

And that's what Regal Pulse has gradually become.

The longer-term plan goes further again. Connections with platforms such as WordPress and Shopify should give Regal Pulse more context about what's changing behind the scenes too.

Rather than simply saying "something has changed", I want it to get better and better at answering the much more useful question:

"What changed, what did it affect, and do I actually need to do something about it?"

One less thing to worry about

Most business owners don't want another dashboard to stare at all day.

I certainly don't.

And most don't want to become experts in uptime monitoring, automated testing, SEO tracking or website diagnostics either.

They've got a business to run.

That's really what I want Regal Pulse to solve.

I want to know that somebody - or in this case, something - is keeping an eye on the website when I'm doing something else.

If everything is fine, great. Leave me alone.

If something isn't fine, tell me what happened in language I can understand and help me work out what to do about it.

Because finding out your website has been broken for hours is bad.

Finding out because a customer had to email you is worse.

Why "Regal Pulse"?

Regal has followed me across the businesses and brands I've built over the years, so that part was fairly easy.

"Pulse" felt particularly fitting.

The aim isn't simply to check whether a website is alive.

It's to keep a finger on the pulse of the business behind it - watching the things customers rely on and spotting when something doesn't look right.

Regal Pulse isn't quite ready for its full public launch yet, but it's getting very close.

Over the next few posts, I'll go into some of the individual problems I've encountered over the years and show how I've approached solving them with Regal Pulse.

Not features for the sake of having features.

Problems I've experienced myself, and would rather not experience again.