Skip to content

Home, figured out.

Helps homeowners turn a project idea into a brief and compares contractors against public permit and licence records.
At a glanceswept Oct 14, 2026

≈ 142visits/mo

Use not read yet · estimate, read Oct 14, 2026

  • Home, figured out.142
  • #1 Jotform1.7M
For
Homeowners planning a home project who need to find and vet a contractor.
Used for
  • Shortlist contractors for a home project
  • Check a roofing quote against public records
  • Prepare questions to ask contractors before calling them
Worth knowingcomputed from what we read · each with its source
How a program reaches itfound, not claimed · read Oct 18, 2026
  • MCP serverfyi.contractors/contractorsverified in the MCP registry
  • Stateanswers, 8 toolschecked 2026-10-18
  • Address to connectcontractors.fyi/mcp

MCP server details →

This card as JSON, for your agent →

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.

Alternatives in Productivityby use, among tools still maintained

Figure and bar: visits/mo, estimate · year: online since

Compare Home, figured out. with

Pick up to two.

All 10 alternatives to Home, figured out. →

All Productivity tools →

Not it? Say what you need

beta

Three tools from the Atlas for the job you describe, each with what fits and what does not.

From people who use itnot part of the reading

No notes yet. What do you use Home, figured out. for?

Sign in to leave a note
Questions this page answers
  • What is Home, figured out.?

    Helps homeowners turn a project idea into a brief and compares contractors against public permit and licence records. It is listed in the Atlas under Productivity.

  • Who is Home, figured out. for?

    Homeowners planning a home project who need to find and vet a contractor.

  • What are alternatives to Home, figured out.?

    In Productivity, by use: Corpus, ODEI, Domus, BuildSignal, Plant Guide, YAPL.

How we read a tool

No votes, no reviews, no vendor claims. Every week a crawler reads each tool's own site and a few public registries, and the words on the card are bands over what it read.

  • Use: visits to the site (estimated), installs from npm and PyPI, presence in Chrome's usage report.
  • Activity: the newest release on GitHub, npm or PyPI; the newest dated page on the site; open roles on a public jobs board.
  • Price: the vendor's own pricing page, read with the date. A figure is printed only when it is on that page.
  • The line and the use cases are written by us from the homepage, one tool at a time, and refused when they repeat the vendor's marketing.

How AI assistants read each site — the reading vendors ask us about — is on each tool's own visibility page.

How we read every tool → · By INITE Atlas Desk