8
7 Comments

Time to start over

It's safe to say that this idea has been validated now. We have 1000 customers and $42k MRR. When we started we wanted to be the best website builder for churches. We used WordPress to get up and running quickly and put a ton of effort into custom functionality. Basically, you can't install a plugin and rebuild what we have currently done.

I went down the route of building a headless option for WordPress using React for a custom Admin Interface. It worked great but at the end of the day, it was still hacking WordPress to get it to do what we wanted.

A month ago, I decided to start fresh and give myself two weeks to build something custom. I focused on Authentication, Stripe Subscriptions, and a simple UI. It worked great! So well, that I can't imagine not using this moving forward.

Today, I forked my repo and started Version 2 of Version 2.

Wish me luck!

, Founder of Icon for The Church Co
The Church Co
on November 3, 2020
  1. 1

    very cool. keep going. churches need this.

  2. 1

    Are you moving away from WordPress completely, then?

    1. 1

      Yes. After I ran a test on a new system, the benefits we so clear. We aren't really using Wordpress now for anything more than Auth and a dashboard so moving away gives us more freedom to do more than websites.

      1. 1

        I'm curious, what did you move to instead of Wordpress? I'm new to the CMS space and there are so many

        1. 2

          It's completely custom. I'm using Node/React/Postgres to build a CMS from scratch.

          1. 1

            Nice! I've been contemplating that as well, looking at the CMS landscape it's either Wordpress/Drupal, newer but not quite as robust tools, or paid tools. Do you think you'd do this custom build without the 4+ years of exp with a CMS under your belt?

            1. 2

              If I had already had a custom CMS starting point to use, I would have used that. At the time, I was using Wordpress for most all the work I was doing. It let me move quickly and still write custom code. I'm glad I started this way. Now that we have enough customers and revenue we can afford to build the product I really want and that will let us run for the next 10 years.

Trending on Indie Hackers
Why Indie Founders Fail: The Uncomfortable Truths Beyond "Build in Public" User Avatar 123 comments I built a tool that turns CSV exports into shareable dashboards User Avatar 94 comments $0 to $10K MRR in 12 Months: 3 Things That Actually Moved the Needle for My Design Agency User Avatar 74 comments The “Open → Do → Close” rule changed how I build tools User Avatar 65 comments I got tired of "opaque" flight pricing →built anonymous group demand →1,000+ users User Avatar 45 comments A tweet about my AI dev tool hit 250K views. I didn't even have a product yet. User Avatar 42 comments