122 commits, 0 signups, here’s what shipped

The problem

Construction project managers spend 6–12 hours per quarter performing retrieval-tax searches in Procore — looking up the latest revision of a drawing, status of an RFI, which sub is on the COI-missing list. Field teams stop using Procore because every lookup costs 60–90 seconds of clicking. The information is there; the friction is the UI.

The product

Forward answers the same lookups by text. PM texts “status on RFI 142” from the trailer; bot replies in 8–15 seconds with the answer + a source citation:

You: status on rfi 142

Forward: RFI 142 — Cable tray clearance conflict
  Status:    Open, pending substitution review
  Submitted: 4/29/2026 by Mike Sandoval (electrical sub)
  Assigned:  Owner-rep (Mark Stein, KFA)
  Due:       5/16/2026
  Last activity: 5/8 — substitution request attached.

  Source: Procore RFI 142, sub-request log.

How it works under the hood

• Claude Sonnet 4.6 tool-use over a 70-tool catalog (Procore read + Autodesk drawing search + OneDrive doc retrieval + field calculations + spec section lookup + cost-code translation, etc.)
• Prompt caching on the system prompt + tool catalog (90%+ cache hit rate after the first message)
• Project-disambiguation resolver runs before any read — texts to a dedicated project line route to one project; texts to the shared line use a phone-number-based tenant lookup to disambiguate which project “RFI 142” references
• Write-through-PM-approval-queue pattern: any mutation (RFI reply, daily log entry, photo upload, change-order draft) goes through a draft state. PM approves with one tap before it hits Procore.
• Every response cites its sources inline (“from RFI 142 + sheet A-401 rev 4”) so the PM can verify

Stack

• FastAPI on Render (Python 3.12)
• Postgres 18 + Redis on Render
• Next.js 15 marketing site + Next.js 15 dashboard on Vercel
• SendBlue for SMS/iMessage
• Anthropic Claude Sonnet 4.6 for the agent loop
• WorkOS SSO for the dashboard
• Stripe Connect for billing

The honest distribution story

I shipped 122 commits of marketing infrastructure in a 2-day autonomous run with Claude Code. 11 persona landing pages, 12 competitor comparisons, 29 use-case pages, 38 free calculators, 1 gated PDF lead-magnet, an automated press-pitch sender. Net new signups: zero.

Diagnosis is upstream of conversion. The funnel works end-to-end — I verified the SMS demo answers correctly, the email form posts to /leads, attribution captures the UTM source. The problem is that no one has visited the site. Vertical SaaS for construction PMs is hard to reach via Twitter/HN/Reddit because the audience reads trade publications and texts foremen, not browses ProductHunt.

This page is the first move in the next phase: actually reaching the audience. If you’re a commercial GC PM, superintendent, or operations leader, the demo line above is live now. Try any query you’d ask a PM and you’ll see the answer back in seconds.

What I’d value feedback on

• The product: what query would I have to answer for you to recommend this to a colleague?
• The distribution: if you’ve sold to an audience that doesn’t live on the internet, what actually worked at this stage?
• The architecture: happy to deep-dive on tool-use catalog design, the approval queue, source citation, or the Procore integration.

Drop your email above for early access or any of the above conversations. Or just text the demo line — that’s the fastest way to see what this actually does.