# Handhold

> Handhold is an agent-led inbound platform. We accompany prospects and customers across discovery, qualification, demo, and onboarding with personalised AI agents — not just a single "Book a Demo" replacement, and not a chatbot or canned product tour.

## What we do

- Inbound Q&A: agents answer prospect questions in real time using your knowledge base
- Personalised demos: agents run discovery and tailor the demo per visitor, 24/7
- Onboarding: agents guide new customers from sign-up through activation

## Product

- [Handhold homepage](https://handhold.io/): Product overview, positioning, primary CTAs.

## Writing

- [Blog index](https://handhold.io/blog): writing on agent-led inbound, demo design, B2B SaaS GTM.
- [How Parim cut bad-fit demos by 60% with an AI demo agent](https://handhold.io/blog/parim-case-study): Parim's sales reps were spending hours on demos with prospects who were never a fit, and inbound arriving after hours never reached them. Here's how an AI demo agent changed that. Markdown source: https://handhold.io/blog/parim-case-study.md
- [Your buyers are qualifying you inside ChatGPT before they ever book a demo](https://handhold.io/blog/buyers-qualify-you-in-chatgpt): In 2026, B2B buyers shortlist software inside ChatGPT, Claude, and Perplexity before visiting a single website. Here's what that means for your inbound funnel, and how to stay visible at the exact moment buyers decide who to consider. Markdown source: https://handhold.io/blog/buyers-qualify-you-in-chatgpt.md
- [Why Use AI Demo Agents for Your Inbound (2026 Guide)](https://handhold.io/blog/why-use-ai-demo-agents): AI demo agents run discovery and deliver personalised demos 24/7, so prospects get answers instantly and sales teams focus on closing. Here is what they actually do, what problems they solve, and when to use one. Markdown source: https://handhold.io/blog/why-use-ai-demo-agents.md
- [Hiring an SDR vs deploying an AI demo agent - the honest comparison](https://handhold.io/blog/sdr-vs-ai-demo-agent): Hiring an SDR to handle inbound demos is one of the most expensive decisions B2B SaaS companies make. Here's the math, and what most teams are choosing instead. Markdown source: https://handhold.io/blog/sdr-vs-ai-demo-agent.md

## Legal

- [Privacy policy](https://handhold.io/privacy-policy)
- [Terms of use](https://handhold.io/terms-of-use)
- [Cookie policy](https://handhold.io/cookie-policy)
- [Data processing addendum](https://handhold.io/data-processing-addendum)
- [Subprocessors](https://handhold.io/subprocessors)
- [Responsible disclosure policy](https://handhold.io/responsible-disclosure-policy)

## Notes for agents

- Every blog post on handhold.io has a raw-MDX alternate at `/blog/<slug>.md` (served as `text/markdown`). The body is the MDX source — YAML frontmatter plus markdown plus the occasional JSX component (`<Figure>`, `<FAQ>`, etc.). Most LLMs handle this well; if you need pure markdown, strip JSX tags. The HTML response also advertises the alternate via `<link rel="alternate" type="text/markdown">`.
- Structured data: every page emits JSON-LD (Organization + WebSite + founder Person nodes at the site root; BlogPosting + Person + BreadcrumbList on each blog post) referenced by stable `@id` values.
- Sitemap: https://handhold.io/sitemap.xml
- robots.txt: https://handhold.io/robots.txt — explicitly allows GPTBot, ClaudeBot, anthropic-ai, ChatGPT-User, OAI-SearchBot, PerplexityBot, Google-Extended, Applebot, Applebot-Extended.