| |

Frameworks vs One-Offs

I’ve battled for a long time now with the idea of building a framework around which I can then quickly build-out future projects one after the other. It sounds great in principle, although it does take time to get that basic framework right.

By “framework”, I mean something that takes care of user management, billing, permissions, outgoing webhooks, incoming API capability, etc. And also something that makes it easy to have a core component to take care of all that stuff, whilst also layering-in the project-specific things on top. Potentially the framework could also include smaller components that can be quickly configured for the specific project, for example a basic CRUD (create-read-update-delete) table and associated pages.

I have started one of these, and got most of the way there, including integration with Stripe. Then Chargebee, when I realised Stripe didn’t do taxes properly. Then Paddle when I realised Chargebee calculated taxes but didn’t pay them.

And now I’ve gone full-circle back to the one tool that takes care of that stuff, and more : Outseta.

The more I use it for my next project (Padsync) the more I appreciate how much Outseta takes care of. So much pain has gone away.

Padsync is an “eat my own dogfood” project. I love Outseta, but I want payments via Paddle so that the messy taxes are taken care of. The alternative is (as I live in post-Brexit UK) to register for VAT in each EU country, even if I only have one customer in that country. Plus anywhere else in the big wide world outside the EU.

That’s a big nope from me. I’m in the SAAS business, not the tax paperwork business.

So now I’ve got a much simpler framework that does the integration with Outseta, adds authentication check into the appropriate pages, and allows easy updates for app-specific code.

I wish I’d thought of that a long, long time ago.

Similar Posts