Five AI workflows I set up in under an hour
The difference between AI that saves you time and AI that creates busywork is usually just one decision: where you put the input. Here are five setups that work.
ReadIdeas, how-tos, opinions, and useful things. Take what's helpful, leave what isn't.
The difference between AI that saves you time and AI that creates busywork is usually just one decision: where you put the input. Here are five setups that work.
ReadThe technical setup takes a day. Getting a team to actually use it takes three months. Here's the gap nobody talks about.
ReadMost AI tools were built for English first. Building VoxVox forced me to question everything I thought I knew about language models and who they're for.
ReadHonest assessment after a year of consulting: some tools earned a permanent spot in my workflow. Most didn't. Here's the list.
ReadWe spent three sessions debugging a tool that worked fine. The real problem was a team that didn't trust the output. What happened next.
ReadMost prompts fail not because the AI isn't capable, but because the human didn't give it enough context. Here's a framework I use with every client.
ReadWorking in CDMX means navigating tools built for English-first markets, payment systems that don't work here, and clients with very different risk tolerance. A field report.
ReadA film about indigenous women in Hidalgo. Not my industry. Not my background. Here's why I got involved, and what it's taught me about building for communities.
ReadBoth are capable. The differences matter depending on what you're trying to do. An honest assessment without affiliate links or vendor relationships.
ReadOne year in. Here's what worked, what didn't, what I charged (and what I should have charged), and what I'd tell myself starting over.
ReadGet Sparks in your inbox. New pieces every few weeks, no spam, easy to unsubscribe.