About

What This Place Is

I Could Probably Do That is a research site for people who look at a product, a quote, or a subscription and think: I could probably do that myself.

Sometimes you can. Sometimes you shouldn't. Sometimes you can, but not yet. This site exists to help you figure out which one you're looking at.

Every project gets the same treatment: real cost breakdowns, honest time estimates, skill assessments, and a direct comparison between doing it yourself and buying the solution. I score each project across six criteria and show my work — not because I think I've built the perfect framework, but because a transparent framework is more useful than someone's gut feeling.

Content Types

🔧

DIY Build

I did the project myself, documented the process, and have real numbers to back it up.

🛒

I Bought It

I evaluated the DIY route, decided buying made more sense, and explain why honestly.

📦

Product Review

Deep evaluation of a market-ready product, tested with real-world use — not just an unboxing.

💭

Thoughts

Shorter posts on process, philosophy, project updates, and the occasional reflection.

Who's Writing This

I'm Logan. I work a full-time job, I have a kid, and I have a compulsive need to understand how things work before I spend money on them.

I've 3D printed things I probably should have bought, bought things I probably should have built, and learned something from every bad call in both directions.

I'm not a professional tradesperson, an engineer, or a content creator by training. I'm a person who researches things too thoroughly and figured I might as well make that useful to someone else.

I've started and abandoned enough side projects to know this about myself — I'm better at starting than finishing, and I'm prone to over-researching as a way to avoid actually doing the thing. This site is partly an accountability mechanism. If I'm going to evaluate DIY projects, I have to actually do them.

How AI Fits In

I use AI tools — primarily Claude by Anthropic — extensively in my research, writing, and site development. I'd rather you know that upfront than discover it later and feel misled.

The Workflow

I pick the project. The idea, the question, the "I could probably do that" moment — that's mine. It comes from real life.

I research with AI. Claude helps me pull apart technical specs, compare products, find studies, calculate costs, and pressure-test my assumptions. Think research partner, not ghostwriter.

I build (or buy) the thing. This is the part AI can't do. I'm the one with the drill, the 3D printer, the soldering iron, or the credit card.

I write it up, AI helps me edit. The voice is mine. The experience is mine. The conclusions are mine. AI helps me organize and communicate faster.

For the full story on why I'm being transparent about this, read Building Online Content with AI: An Honest Take.

What This Isn't

This isn't a "top 10 best widgets" site built to collect affiliate clicks. I do use affiliate links — there's a disclosure at the bottom of every post that includes them — but the scores and recommendations exist independently of whether a product has an affiliate program. If the best option doesn't have a link, I'll still tell you to buy it.

This also isn't a site where every project ends with "and you should totally DIY this!" Sometimes the answer is buy it, hire someone, or wait until you have the right skills. That honesty is the whole point.

What I Commit To

▸ Affiliate relationships never influence scores or recommendations.

▸ If I haven't used it, tested it, or built it — I'll tell you.

▸ "I Bought It" posts exist because honest frameworks don't always say DIY.

▸ AI use is disclosed. Always.

Get In Touch

Questions, feedback, or a project you think deserves the ICPDT treatment?

[email protected]