Rules, not a model

Tool Finder

Say what you want to build. The finder matches keywords against the tools already on the card, then seats the highest score in each relevant role. It does not call a model, and a paid placement cannot move a pick.

Building on a budget? See what's free right now on the Free-Tier Tracker

Internal tool

Matched “an internal tool for the ops team” to Internal tool. Each seat is the top published score for that role.

Odds-onCoder
Claude Code
Top coder score on the card. Multi-file edits from the terminal.
Tool page
86
Odds-onApp builder
Lovable
Top app builder score on the card. A first web app from a description.
Tool page
82
Odds-onAutomation
n8n
Top automation score on the card. Technical teams automating their own stack.
Tool page
80
RoughieDatabase
Notion
Top database score on the card. Teams whose notes and docs are already in Notion.
Tool page
74

Starter prompt

Build an internal tool for an ops team of five. They need a list of open requests, a status field, an owner, and a notes box. Sign-in can be a shared password for v1. Do not add a public marketing page. Describe the list view, the detail view, and how a request moves from new to done.

Template

Team:
Request fields:
Statuses:
Who can edit:
What v1 leaves out:

Rules, not a model

Tool Finder

Reading the card…

Rules, not a model

Tool Finder

Building on a budget? See what's free right now on the Free-Tier Tracker

Internal tool

Matched “an internal tool for the ops team” to Internal tool. Each seat is the top published score for that role.

Odds-onCoder
Claude Code
Top coder score on the card. Multi-file edits from the terminal.
Tool page
86
Odds-onApp builder
Lovable
Top app builder score on the card. A first web app from a description.
Tool page
82
Odds-onAutomation
n8n
Top automation score on the card. Technical teams automating their own stack.
Tool page
80
RoughieDatabase
Notion
Top database score on the card. Teams whose notes and docs are already in Notion.
Tool page
74

Starter prompt

Build an internal tool for an ops team of five. They need a list of open requests, a status field, an owner, and a notes box. Sign-in can be a shared password for v1. Do not add a public marketing page. Describe the list view, the detail view, and how a request moves from new to done.

Template

Team:
Request fields:
Statuses:
Who can edit:
What v1 leaves out: