A custom podcast link page
The job was small and stable, the custom design mattered to us, and we already had hosting, so building it was worth it and saved us a paid plan. Change the upkeep answer to “nobody” and the quiz says to pay instead.
AI makes it easy to build your own version of the software you pay for. Answer 10 quick questions about one tool and get a straight answer: build it, use open source, or keep paying.
free claude skill
A free Claude skill that asks the same ten questions, plots your answer on the same map, looks up real open-source and paid options for your job, and writes a decision brief you can forward. It can also sort your team's whole stack.
Something went wrong. Please try again.
By subscribing, you agree to receive recurring marketing communications from Tenex at the email you provide. Unsubscribe anytime. See our Terms and Privacy Policy.
free claude skill
If it didn't, download build-vs-buy-check.zip.
To install: upload the .zip in Claude's Skills settings, or unzip it into
~/.claude/skills/ for Claude Code. Then say "should we build or buy" and name the tool.
Answer all 10 to see your result. 10 to go.
Most teams used to buy by default, because building took a team and months. AI coding agents made a working first version cheap, but someone still has to host it, fix it, update it and support the people using it. That ongoing cost is what the quiz weighs.
Make your own version, often with an AI coding agent. It's worth it when you'd use it every day and someone owns the upkeep.
Use a maintained open-source project. Run it yourself, or pay a host to run it for you.
Pay for a service that already does the job, and let them handle reliability, updates and support.
Payoff adds up how much better your version would be, how often you'd use it, and whether it's part of your edge (0–6).
Burden adds up the size of the job, the cost of it breaking, what it connects to, and how sensitive the data is (0–8).
Three answers override both scores. If you haven't checked what exists, check first. If a paid tool or an open-source project already fits, use it. If nobody will maintain it, pay for it, unless it's your edge and you'd use it daily, when building it with a partner fits. The scores show the reasoning so you can argue with it. They don't estimate savings.
Buying from specialized vendors and building partnerships succeeds about 67% of the time. Internal builds succeed about a third as often. MIT NANDA, The GenAI Divide (2025), as reported by Fortune
A working agent demo only takes an afternoon, so it's easy to start building before anyone asks whether you should. Build where the workflow is part of how you compete, keep the first version narrow, and name the owner before launch.
We built this quiz while making an episode about rebuilding apps with AI, then ran our own projects through it.
The job was small and stable, the custom design mattered to us, and we already had hosting, so building it was worth it and saved us a paid plan. Change the upkeep answer to “nobody” and the quiz says to pay instead.
We built one with Codex and an open-source portrait model. It passed our tests, including one that caught a real font-export bug. We haven't finished comparing it with existing tools, so the quiz says to check those first.
PhotoCraft, a community project, handled our editable-text test, but one complex Photoshop file came out visibly different. If you borrow, test it on your own files.
Running a publishing system isn't where we want our time to go. WordPress is open source, but someone still has to host it, update it and keep it secure. For that job, paying for a managed plan wins.
Each guide lists the open-source and paid options for that tool, the traps teams hit, and a build brief you can paste into a coding agent.
One place for the current logo, photos and templates, so people stop pulling old files out of the shared drive.
Every support request gets an owner and a place in the queue, instead of sitting in a shared inbox.
Where the team's tasks and requests live, who owns each one, and what's stuck.
A form comes in, a deal closes, an alert fires, and the follow-up in your other apps happens without anyone retyping it.
By department: Marketing · Sales · Customer support · Operations · Finance · People and HR · Product and engineering · Data and analytics · Design and creative · Legal · IT and security