Clay / FenceQuote / quote-throughput

Do not let plausible strategy mutate into unsupported sales claims.

A claim ledger separating sourced facts, vendor claims, hypotheses, caveats, and claims to avoid.

Working thesisEvidence-linkedPilot gates
Use with care
Working assumptions require contractor proof.

Market numbers are directional; vendor claims need attribution; quote-throughput, pricing, managed-desk, ROI, and performance claims require contractor artifacts before they should shape external positioning.

Before claims

Claim boundaries

Do not overclaim

Performance claims need proof

Do not claim booked-job lift, close-rate improvement, speed-to-lead ROI, or quote accuracy until pilots produce contractor-specific evidence.

Estimate caveat

Preliminary means non-binding

Satellite/map outputs are screening aids only. Slope, access, utilities, HOA rules, property lines, permits, demolition, soil, and site conditions can materially change price.

Managed-work caveat

Customer contact needs legal rails

Any homeowner-facing follow-up or quote-desk work needs consent, privacy/TCPA handling, apparent-authority limits, approved scripts, and contractor review gates.

Claim discipline

Evidence taxonomy

Sourced fact

Can be used if citation and scope are explicit.

Vendor claim

Directional only; attribute and avoid neutral-proof language.

Hypothesis

Requires contractor artifacts, pilots, or paid/data-sharing commitment.

Unsafe claim

Do not use externally until validated; may create legal or trust risk.

Sourced fact

Usable with citation

Directly supported by public source or the existing local strategy context.

Vendor claim

Use carefully

Useful directional signal, but must be attributed and not treated as neutral proof.

Hypothesis

Must validate

Strategic assumption that sounds plausible but requires contractor evidence.

Unsafe claim

Do not sell this yet

Overstated, unverified, or likely to distort the source.

Ledger

Verified vs hypothesis

Sourced

Verified / source-grounded

  • Existing FenceQuote strategy already frames two real business paths: self-serve widget/SaaS and setup-assisted or managed quote-throughput service (local draft: /Users/michaeltran/projects/hermes-private-lab-site/docs/research/clay-fencequote-two-paths.md).
  • US fence construction is large and fragmented in public IBISWorld data: estimated $20.4B revenue in 2026, 315k+ businesses, high/increasing competition, no company above 5% share (; ).
  • Fence projects have enough economic value to support ROI logic if FenceQuote can influence even a small number of additional jobs. HomeAdvisor reports a $3,266 national average and $1,859–$4,828 typical range ().
  • Fence-specific software already exists across estimating, CRM, drawing, map measurement, website instant-estimate, and follow-up workflows (; ; ; ; ).
  • Horizontal home-service/FSM platforms already include quotes, scheduling, invoicing, payments, customer communication, follow-up, price books, financing, and AI/customer-service features (; ; ; ).
  • Remote property measurement is proven in adjacent contractor workflows, especially roofing/exteriors and landscaping: EagleView, Roofr, Hover, Nearmap, SatQuote, and RealGreen all sell measurement/estimate speed as a core benefit (; ; ; ; ; ).
  • Speed-to-lead has credible general web-lead research behind it, but not fencing-specific proof. The InsideSales/MIT Lead Response Management report found the odds of contacting a lead in 5 minutes vs 30 minutes drop 100x, and qualifying a lead in 5 minutes vs 30 minutes drops 21x (). HBR/HBS published the related “Short Life of Online Sales Leads” article/citation (; ).
  • Google Local Services Ads generate phone/message leads, and Google states that regularly failing to answer calls or respond to messages may affect ad ranking (;co=GENIE.CountryCode%3DUS).
Validate

Still hypothesis

  • Fence contractors lose enough revenue from slow response, delayed quoting, or weak follow-up to pay for FenceQuote.
  • Contractors trust satellite/map-assisted preliminary fence measurements enough to use them before a site visit.
  • Homeowners want an instant or near-instant preliminary fence quote rather than simply a fast callback.
  • A contractor’s price book can be captured in a repeatable setup workflow without becoming custom consulting every time.
  • Contractor approval gates can happen quickly enough to preserve the speed advantage.
  • FenceQuote can integrate or coexist with the contractor’s current stack instead of forcing a rip-and-replace.
  • Clay can reach enough fence contractors cheaply and credibly to validate sales motion before the brand gets locked.
  • Managed quote-throughput can produce enough incremental jobs or saved admin labor to support a $1k–$3k/month service package.
Caution

Weak/vendor-biased evidence

  • Competitor performance claims are mostly self-reported marketing claims. Treat claims like “20% more jobs,” “2.5x faster,” “44% revenue growth,” and “21x more conversion” as directional until corroborated by customer interviews or independent data (; ; ; ).
  • Market-size reports vary by scope: IBISWorld’s US Fence Construction category is contractor/install-focused, while Mordor/Coherent global fencing reports include materials, regions, and applications. Use them for directional tailwinds, not exact TAM precision (; ; ).
  • Lead-response studies are not fence-specific. The strongest source is general web-lead/contact research; home-service agency blogs are useful for context but not definitive proof for fencing (; ).
Claim ledger

Candidate claims for final research pack

Likely safe if verified
  • Homeowners usually compare multiple contractor bids before choosing.
  • A meaningful share of homeowners expect same-day or on-the-spot quotes.
  • Digital quotes are preferred by many homeowners.
  • Speed-to-lead is a well-supported general lead-conversion factor, though not fence-specific.
  • Major FSM competitors already bundle quoting, CRM, follow-up, scheduling, booking, and AI/call answering.
  • Pure estimating/invoicing apps have low monthly price anchors; managed implementation/service can support higher pricing.
  • Fencing is a large enough U.S. market to justify a focused beachhead, but public market-size figures vary by definition.
Unsafe until further validation
  • “Fence contractors lose X% of leads because they quote too slowly.”
  • “FenceQuote will increase close rate by Y%.”
  • “Most fence contractors lack CRM/software.”
  • “The average fence contractor will pay $N/month.”
  • “Fully automated quote follow-up can run without human approval.”
  • “The market is $20.5B” unless carefully labeled as IBISWorld’s Fence Construction market-size estimate, not FenceQuote’s obtainable market.
Verification

Source and verification requirements

Preferred source types:

  • Primary/company materials for competitors and pricing.
  • Industry reports from credible orgs where accessible.
  • Public filings or investor materials for field-service/lead-gen companies when relevant.
  • Contractor forums/reviews/interviews as qualitative signal, not quantitative proof.
  • Government/BLS/Census/NAICS data for contractor counts, wages, establishment sizes, etc.
  • Academic/industry research on speed-to-lead, sales follow-up, and home-services buying behavior.
  • Public review sites and case studies only with careful caveats.

Weak source types:

  • SEO blogs with unsourced statistics.
  • Vendor claims without methodology.
  • AI-generated summaries.
  • X/Twitter posts, unless used only as discovery leads or practitioner anecdotes.

A separate verification pass should check the draft evidence pack and claim ledger for:

  • Link validity
  • URL resolves or archived/source alternative is provided.
  • Access date recorded.
  • Source relevance
  • Source actually discusses the cited claim.
  • Source context is not distorted.
  • Number accuracy
  • Number in draft matches source exactly.
  • Units, geography, year, sample, and methodology are preserved.
  • Claim strength
  • Source supports the claim directly, indirectly, weakly, or not at all.
  • Weak/vendor/promotional claims are labeled.
  • Recommendation integrity
  • Strategic recommendations do not overreach beyond evidence.
  • Hypotheses are not presented as facts.

Verifier output schema:

```markdown

Before anything is shown to Clay as research-backed:

  • Build a claim ledger with IDs.
  • For every numeric claim, record:
  • exact wording in draft;
  • source URL;
  • exact excerpt copied from source;
  • accessed date;
  • source type;
  • support level: direct / indirect / weak / unsupported;
  • caveat.
  • Run a separate verifier pass over the ledger.
  • Verifier checks:
  • links resolve;
  • quoted excerpt exists on source page/PDF;
  • draft wording does not overstate the source;
  • units/geography/year/sample are preserved;
  • vendor claims are labeled as vendor claims.
  • Any unsupported claims are removed, reworded as hypotheses, or moved to “needs validation.”