Common questions

A collection of production-grade AI automation systems — lead acquisition, agent orchestration, AI visibility, and voice agents. Each one built and tested in production. The site itself runs the AI Visibility Engine from the catalog.

Five systems: a Lead Acquisition Engine (sources and qualifies prospects daily), an Agent Operations Platform (orchestrates AI agents across routine tasks with a dashboard), an AI Visibility Engine (gets businesses found by AI assistants like ChatGPT and Perplexity), an AI Voice Receptionist (answers and makes calls 24/7), and a Custom Build option for anything outside those four.

We scope what you need, build it on production-grade tools, and hand over source code, documentation, and a walkthrough. Each system is self-contained — no ongoing platform dependency, no monthly fees. Standard tools, full documentation, the source is yours.

Every system is built on open, well-documented tools — n8n for workflows, LangGraph for agent orchestration, Playwright for scraping, Ollama for local LLMs, Supabase for data, and Next.js for interfaces. No proprietary runtimes, no black boxes.

It starts with a conversation about what you need. We scope the system together, build it on production-grade tools, and hand over source code, documentation, and a walkthrough. Each build is self-contained — no ongoing dependency.

AEO (Answer Engine Optimisation) is the practice of structuring a web presence so AI systems — ChatGPT, Perplexity, Claude, Gemini — cite it accurately and can act on it. The AI Visibility Engine in the catalog implements this as a complete system.

Every system uses open, well-documented tools any web developer can read on day one — standard workflow, database, scraping, and AI tooling. Because you receive the source code, a system is genuinely yours to operate and extend. If your team has touched a database and a bit of Node, they can maintain it.

Any repetitive, rule-based operation that eats a business's week. The catalog covers the most common shapes: lead generation (the empty-pipeline problem), agent orchestration (automating routine tasks), voice reception (answering and booking calls), and AI visibility (being found by AI assistants).

WebMCP (Model Context Protocol for the web) lets a site register typed tools that AI agents can discover and call without scraping. When an AI agent visits a WebMCP-ready site, it can invoke tools programmatically — no form filling, no hallucination about what the business offers. Porsync ships WebMCP natively.

This site is the live example — it runs the AI Visibility Engine (Schema.org, llms.txt, WebMCP) and is indexed by every major AI crawler. The /tools page documents every registered WebMCP tool. The /case-studies section walks through systems proven in production.

The AI Visibility Engine includes WebMCP implementation — declarative attributes, robots.txt configuration, and structured data — across any stack. Contact: connect@porsync.com

Adding declarative attributes (toolname, tooldescription, toolaction) to a website's key CTAs, configuring robots.txt to allow AI crawlers, and deploying supporting schema markup. Together these make a site actionable by AI agents in WebMCP-capable browsers.

AEO makes a site citable by AI answer engines — optimizing for being mentioned in AI-generated responses. WebMCP makes a site actionable by AI agents — optimizing for agents being able to book, query, or transact directly on the site. The AI Visibility Engine implements both.

Yes. porsync.com is WebMCP-instrumented. AI agents with WebMCP support can book a consultation and invoke available tools directly on the site without human assistance.