These are the systems behind our own sales, publishing, knowledge, and public tools—evidence of the operating standard we can apply inside another company.
Inside our own website enquiry workflow
A useful conversation becomes a service enquiry when the visitor chooses it
FollowAI connects the assistant, a check of service interest, contact permission, and a handoff to Sales OS and the team. Explore the boundary with two example conversations.
Fictional data · no live submissions
The visitor’s own words
“Please have your team build a support agent for our shop, using our FAQ and a human handoff. We want to discuss scope and pricing.”
A page visit or a greeting does not establish a project. The conversation starts with what the person actually wants.
This walkthrough explains the implemented flow using fictional data. Its controls do not create leads or send messages.
The operating workspace behind FollowAI sales, with companies, contacts, pipeline, tasks, offers, research, and follow-up connected to the same record.
Nine working screens across pipeline, discovery, offers, tasks, and reporting
Company discovery and enrichment from public sources and the company website
Website enquiries arrive through a controlled public intake endpoint
Private because it contains real commercial data
Private workspace / 02
Site OS
The publishing and SEO workspace behind FollowAI Knowledge—from real search demand to review, indexing, and performance monitoring.
Idea queue, article queue, SEO view, service pages, and health checks
Search Console data informs the editorial queue
A factual review gate remains before publication
Private because it contains real commercial data
Public / 03
Knowledge system
A structured public content system with human review before publication and pages people and search engines can navigate.
Five practical sections across tools, automations, solutions, guides, and services
Real HTML pages rather than a client-only content shell