Let’s get this out of the way:
I’m agnostic.
Before you @ me, let me clarify — I’m talking about tools, tech, and platforms.
Website builder? Agnostic.
Project management software? Agnostic.
Data visualization tools? Agnostic.
NFT blockchain? Crypto wallet? Agnostic.
Sales platforms? Marketing stacks? Social media tools? Agnostic.
Accounting systems? Banking tools? Trading platforms? Payment platforms? Agnostic.
LLMs? Text, image, video, or voice generation tools?
You guessed it — Agnostic.
I say agnostic because neutral sounds milquetoast — like I don’t care.
And that’s not it.
🧭 Why I’m Agnostic
Why am I platform agnostic? Because I’ve seen the evolution up close—and change is the only constant.
When I was graduating college, software came on CDs. You picked a lane, got certified, and if you stuck with it, you could build a career around one system. Programs had long lifecycles. Companies operated in silos. If you learned Microsoft Project, Oracle, or QuickBooks early, you were set.
Cannibalization was something you worried about—but self-cannibalization? Never.
Back then, no one talked about disrupting their own roadmap or sunsetting a flagship product. You built your moat and defended it. The cycle was slow, and the hierarchy was clear.
But things changed—and I’m glad they did.
I’ve spent years working in tech, especially in fast-moving spaces like social, mobile, healthcare, blockchain, Web3, and AI. The pace forces you to adapt, and that’s a good thing. I love that we have virtual infrastructure and SaaS models now. I don’t miss sourcing physical servers, racking them, or troubleshooting hardware issues.
I’d rather spend my time solving core problems than patching drivers or hoping that the last backup is clean and recent.
So when it comes to systems, platforms, or tools—I stay open.
Not because I’m undecided. Because I want what fits the problem, not what worked five years ago.
🛠️ Tool Bias vs. Tool Fit
I’ve been on both sides of the RFP and RFQ process. I’ve pitched and procured, scoped and sold. And the moments that always make me cringe are when someone confidently pitches their preference—not because it’s the right fit, but because it’s the only thing they know.
Bias masquerading as expertise.
Sometimes that works out. The preferred tool might be the right one. Other times, it’s just inertia. Or worse—it’s someone trying to sell a decision that was already made, regardless of what the problem actually calls for.
I’m not here to knock confidence. But I’ve learned to stay flexible. I try to listen, read the room, and ask better questions in real time:
What’s the goal?
What’s working?
What needs to scale?
Is the cost worth it?
How can I help?
Then I do the mental calculus: what solution fits best for this—not last year, not another client, not a certification I earned a decade ago.
🤝 Agnostic Doesn’t Mean Unprepared
When people ask, “Do you have experience with [insert platform]? What tools do you use?” — I get it.
It’s a good question — it just tends to elicit the wrong response.
Short answer? Yes.
Long answer? Yes, I’ve used it — or something close. And if I haven’t, I’ll learn it quickly.
But what they’re really asking is usually one of two things:
- Have you used our tool before?
- Can you operate without being babysat?
The problem is, a direct answer often isn’t enough.
And saying “I’m platform agnostic” can sound like a non-answer.
So I usually respond like this:
“I’m familiar with project management tools like Jira, Asana, Trello, Airtable, Notion, Basecamp.
I’ve used and implemented several. There are also a lot of newer platforms like WorkOpti and Luma doing cool things.
Do you have a preferred setup, or would I be helping decide if I’m brought onboard?”
That turns the conversation from “Can you keep up?”
To “Want me to lead?”
🚀 I Can Learn It. Fast.
One of the hardest things to convey in an interview or call is that I’ve spent years building, selecting, implementing, supporting, and training people on systems — often when it was a duct-taped mess of early tools with a CLI for a CMS.
Back then, everything was clunky by design.
Today, if your product isn’t intuitive, it won’t scale.
So when someone asks if I’ve used their exact tool, I’m honest. If I haven’t, I’ll say so. But I also know that modern systems are built to be adopted quickly. And I’ve done it—over and over again.
I know how to reverse-engineer workflows.
I know how to spot the bottlenecks and where the adoption friction will hit.
And I know how to learn fast—so I can lead without needing weeks of ramp-up.
🧠 Know What You’re Good At
Sure, I’ve studied and learned to program over the years — and I can poke around a codebase, maybe troubleshoot a config file or two. But if you need someone writing production-ready code, that’s not where I bring the most value — and I’ll never pretend otherwise.
Mostly, it helps me speak dev.
But if you need someone to manage the product, run the roadmap, bridge teams, analyze data, manage payroll, figure out how to scale, start a company, plan a product launch, build a marketing or social strategy, or turn a sketch into a sprint — I’m in the right seat.
Need someone to work on a specific PM platform, or some internal Frankenstein setup? I’ll make it thrive.
I was managing timelines and complex workflows in Microsoft Project back when we still burned CDs.
Website builders? Omnichannel stores and point-of-sale platforms? Same story.
I cut my teeth hand-coding HTML and CSS, then watched the web evolve — through Dreamweaver, early WordPress, and into today’s drag-and-drop tools.
So yes, I can use whatever platform you prefer. Or help you choose one that actually fits the job.
Need to plan out socials, reels, or TikToks?
Build a Discord?
Produce a Medium series or launch a Substack?
Spin up a Notion hub or structure a GitBook?
Web3? NFTs? Smart contracts? Blockchain?
Develop an AI-integrated workflow? Make it agentic? Add an AI surface layer?
I’ve done it — or something close enough that I can adapt fast.
🔄 Flexible by Design
Being agnostic doesn’t mean I don’t have preferences. It means I don’t let them override the needs of the project.
Sure, I have go-to tools I love, platforms I trust, and workflows that feel seamless—but I don’t mistake familiar for best, or feel the need to change what’s already working just to make it easier for me.
If there’s a better fit for the situation, I’ll learn it, use it, and get results—without losing momentum.
🎯 Agnostic ≠ Indifferent
Being agnostic doesn’t mean I don’t care. It doesn’t mean I’m vague. And it definitely doesn’t mean I’m unprepared.
It means I’ve seen enough cycles, platforms, and pivots to know that loyalty to a tool is not the same as loyalty to the outcome.
I’d rather focus on solving a core problem than obsess over the tool.
That’s why I stay flexible.
That’s why I stay curious.
That’s why I stay agnostic.
