doma.com
success
Claude Code
intent
What does doma.com do and who is it for? Explain it back to me.
13steps
55.6sduration
$0.4501cost
42,931tokens
17 steps4 reasoning steps2 searches
home
/how-it-works
home
/technology
/title-closing
/title-alternatives
search
search
/ai-title-insurance-20…
docs
/why-doma
/products
docs
40%
answer from your site
18%
answer efficiency
50%
followed site links
answer sources
- from this site40%
- from external pages20%
- from search results20%
- from agent knowledge20%
url discovery
- given in the task9%
- followed a link45%
- found via web search9%
- guessed the URL36%
insight
The agent successfully assembled a coherent explanation of Doma's business, target audience, and competitive position by combining the homepage overview with external search results and third-party analysis. However, the site itself was poorly navigable—most product detail pages returned 404 errors, and pricing information was not publicly available on-domain, forcing reliance on web search and third-party sources for complete answers.
- ›Homepage (step [1]) was the only successful direct fetch from doma.com; it provided foundational positioning but lacked details. Eleven subsequent direct fetches to apparent product/info URLs all returned 404 errors, indicating either poor site structure or navigation links that don't resolve.
- ›Pricing section entirely absent from site. Agent resorted to web search (step [13]) to find cost savings figures ($200–$1,000 and $1,200 claims), which came from search snippets rather than Doma's own pricing page, making it impossible to verify current rates or tiers.
- ›Competitive positioning came from external analysis (steps [14] and [15]: ailearningguides.com article), not from Doma's own site. The site did not articulate how it differs from Spruce, Qualia, or legacy underwriters; the agent inferred this from third-party comparisons.
- ›Agent discovered that Doma's closing/escrow business was acquired by Opendoor (March 2026) and the company agreed to sell to Title Resources Group via web search results, not from the homepage—creating potential confusion about current product scope that the site did not clarify.
- ›Navigation links listed on the homepage (step [8]: Technology, Title Data, Title Closing, Title Alternatives, Upfront Title) did not resolve when fetched, suggesting the homepage content may be stale or the site architecture is broken.
Want to run your own?
Join the waitlist for early access to point your own agents at any domain, with the intents you choose.
or talk to us about agent readiness →