The Automators

Reviewed 1d ago.

• tools: 18 tools scanned
• metadata: scanned

No findings.

Tools (18)

• get_company_profile

  Returns who The Automators are: name, description, founding year, headquarters, service area, the public team (name, role, LinkedIn, bio), verified public profiles, the content licence (RSL 1.0) and headline track record. Use it to introduce the company or check a fact about it. It is not the place for pricing (get_pricing) or contact details (get_contact_options).

• get_contact_options

  Returns how a person reaches The Automators: phone, the public email, the booking page and direct calendar link, business hours, the response-time promise, and what to include in an inquiry (company, what to automate, timeline). Use it whenever the user wants to talk to a human or book a consultation. The server never sends messages; it only returns these options.

• get_faq

  Returns the site FAQs for a topic: "general" (the homepage questions), "pricing" (the /pricing/ questions), or a service, industry or tool slug (that page's questions). Omit the topic for general plus pricing. Use it to answer a common question in the site's own words.

• list_services

  Returns the six service pillars and the eleven AI Agent Development capabilities, each with a one-line description and URL. Use it first to find the right service slug before calling get_service. Not for pricing (get_pricing).

• get_service

  Returns everything the site says about one service: description, the full page text as markdown, its FAQs, related real case studies, and the pricing and timeline that apply. Use it when a user asks what a specific service involves or whether it fits their need. Get the slug from list_services.

• get_pricing

  Returns the pricing model: one-time build price, ongoing model costs paid to the provider, ownership, no retainer, typical timeline and ROI window, what is included, what is billed separately, and who it is not for. Use it for any cost, budget or "how much" question. Figures come from the same module the site renders, so quote them as given.

• get_engagement_process

  Returns the four engagement steps (discover and map, opportunity analysis, build and integrate, optimise and scale) with what happens in each, what the client provides, the typical timeline and how it starts (a free consultation). Use it for "how does working with you go" questions.

• list_industries

  Returns the 20 industries with a dedicated playbook page: slug, name, audience, one-line description and URL. Use it to find the slug for get_industry_playbook.

• get_industry_playbook

  Returns the playbook for one industry: a TL;DR, the industry landscape with verified, cited statistics, the workflows we automate (pain point, automation, outcome), relevant services, illustrative example use cases (not client work), compliance notes, FAQs and related industries. Use it when the user names an industry.

• list_case_studies

  Returns the four real, published case studies with client, industry, summary, owner-confirmed metrics and URL. These are the only pages that describe The Automators' own past work. Use get_case_study for the full story.

• get_case_study

  Returns one real case study in full: facts, metrics and the page narrative as markdown. Get the slug from list_case_studies.

• get_blog_post

  Returns one blog post as markdown: title, author, date, the full body with links, a Sources list and the post's FAQs. Use search_content to find the slug. Every post is written by The Automators' team and published at theautomators.ai/blog/.

• check_service_area

  Resolves a city, province, state or country to the matching local page (649 Canadian and US pages) and says whether it is served. Anything outside Canada and the US is served remotely and resolves to the locations index with a note. Use it whenever a user mentions where they are.

• search_content

  Keyword search across blog posts, services, industries, tools and case studies. Returns ranked results with type, title, URL, description, date and TL;DR where available. Use it to find the right page or post before reading it with get_blog_post, get_service or get_industry_playbook.

• estimate_roi

  Runs the site's ROI calculator: from team size, weekly manual hours, hourly cost and error rate it estimates annual hours saved, annual savings, implementation cost, ROI percent and payback months, plus the service recommendations the page shows. Use it when a user wants a number for the value of automating a process. Optional industry preset sets the automation efficiency.

• assess_ai_readiness

  Runs the site's AI Readiness Assessment. Call it with no answers to get the 10 questions and their scored options; ask the user; then call it again with one score (1 to 4) per question in order to get the level (Beginner, Intermediate, Advanced), the percent score, the per-dimension breakdown, the weakest dimensions and service recommendations.

• prioritize_processes

  Runs the site's Process Prioritizer on up to 10 manual processes (name, hours per week, frequency, complexity, error-prone, people involved). Returns each one's score out of 100, priority, estimated annual savings, reasoning and implementation timeline, ranked, plus totals and service recommendations. Use it when a user lists several things they might automate.

• estimate_customer_service_savings

  Runs the site's Customer Service Cost Calculator: from monthly tickets, handle time, agent cost, agents on staff, response time and after-hours share it estimates current and AI-assisted monthly cost, monthly and annual savings, tickets deflected, response-time reduction and ROI, with service recommendations. Use it for support-desk cost questions. An industry preset fills typical inputs.