What's Next for CodedShapes
A Paid Tier for Scripts, Templates, and Tools
When I first started CodedShapes, I wanted to write about the stories, the lessons, and the mindset behind computational design. I kept it light on the technical stuff because I thought the principles mattered more than the tools and they apply to everyone, regardless of what software or tool you use.
But over time, I noticed that a lot of you wanted the technical stuff too. And I wanted to make the technical stuff too (we never shy away from the technical). You’d reply asking how I actually built something, or what script I used, or whether I had a template you could start with.
So I started making those things, courses, scripts, guides. But I kept them separate. I didn’t want to turn CodedShapes into a tutorial blog, so I barely mentioned them here. The course went on one site. Scripository went on another.
While that made sense, most people didn’t even know they existed.
So, this year, I kept asking myself: what’s the simplest way to bring all of this together without losing what makes CodedShapes valuable in the first place?
Well, I think I found the answer. That is to bring it all here, but keep it optional.
The paid tier of CodedShapes.
Okay, I know what you’re thinking.
Let me just say that I am not putting my articles behind a paywall nor am I going to start. I find a lot of value sharing and writing my experience for free. So you’ll still hear from me weekly.
The paid tier is where I’m putting everything you can actually use in your work.
Right now, that means my full course on applying computational design to your work, plus a Notion template for tracking the value your scripts deliver (something I wish I had when I started).
But over the next few months, I’ll be adding all the scripts people have been asking me for, the ones I reference in articles or use in my own projects, plus more templates, guides, and resources as I build them.
This is for you if:
You’ve been reading CodedShapes and thinking “I should actually try this in my own work” but you’re not sure where to start. Or you’re already doing computational design and you just want the actual script or template without having to rebuild it from scratch.
Basically: if you’ve ever read something here and wished you had the files to go with it, that’s what the paid tier is for.
You don’t have to subscribe for long
Now, let me guess what you’re thinking again.
It’s just another subscription.
I get it. There are too many out there already. I feel it too. I am currently on the verge of cancelling my Disney Plus account but they keep coming with new shows to watch.
But the way I think about it: it’s an ever-growing set of useful resources that you get access to for the same monthly fee. Which means, you can come back in a year’s time and the resources might have doubled but the monthly fee might still be the same.
You can always subscribe for just a month, and then cancel it. Use that month to get the most out of it and be on your way. No hard feelings at all. If you plan it well, you can actually use that whole month to get a lot of resources out.
Then, in a few more months time, when the paid stuff has grown and there’s something interesting again, sign up for another month, and repeat the cycle.
I’m not going paid because I want to trap people. I just want to offer practical solutions for people that need them and to bring everything that I create under one roof, so that it’s less confusing for everyone.
The weekly articles aren’t changing
I just want to stress this again.
The free newsletter isn’t going anywhere. I’ll still be here every week writing about computational design. That’s not changing.
The paid tier is for people who want the actual files. The scripts. The templates. The things you can bring into your workflow and use.
This is the simplest version of what I’ve been trying to do for years. Help people work better by sharing what I’ve built. All under one name and no more having to cobble together all these random systems.
If you have questions, about what’s included or whether it’s right for you, or anything really, just reply to this email.
Again, thanks for being a member (paid or not), I appreciate you taking the time to read what I create.
I just want to thank you again for being here.
Consider signing up to CodedShapes and I’ll send you a free guide on computational design as a thank you.



