Useful ideas for running better systems.
I write about websites, automation, digital self-reliance, and practical technical decisions so you can save time, spend less badly, and run your business with more clarity.
I’m James, the founder and face of Let's Figure It Out.
I’m James. Most of my work sits at the intersection of websites, automation, operations, and the awkward space where business owners know something is inefficient but do not yet have a clear path forward.
The point of this site is not to impress you with tools. It is to help you understand what is possible, what is worth doing, and what is probably wasting your time or money.
I’m the person you see most directly through the writing and experiments, but Let's Figure It Out is built around a broader idea: useful content, practical technical thinking, and hands-on help for businesses that want better systems.
Some posts are about better websites. Some are about automation, tooling, and digital independence. Some are about experiments that go well, and some are about the tradeoffs you only understand after trying something for real.
The aim is to make technical ideas easier to use in real business situations.
Clearer decisions, fewer wasted hours, and a better sense of what to do next.
A lot of people are paying for subscriptions they do not need, tolerating slow manual processes, or being sold technical solutions without any real explanation of the tradeoffs.
The writing here is meant to help you spot leverage sooner, ask better questions, and make stronger decisions without needing to become deeply technical yourself.
The ideas here are closely tied to real implementation work, so the writing stays grounded in changes that can actually be made, not just interesting theory.
Curiosity first. Hype last.
I like trying new tools, but novelty is not the point. The point is whether something genuinely saves time, lowers cost, improves reliability, or opens a better way of working.
- Articles about websites, automation, digital self-reliance, and operational improvement.
- Experiments with tools and systems, including what worked and what did not.
- Practical explanations for people running a business, not trying to become engineers.
- Business owners who know their operations could run better.
- People who are open to new technology but want the tradeoffs explained clearly.
- Anyone who would rather build useful systems than keep paying for avoidable friction.
Get new articles straight to your inbox.
The main ideas land on the site first. The newsletter is the easiest way to keep up with new writing and the occasional extra worth sending on.