Docs

Getting started

index365 ships two tracks under one brand. Track 1 is product plans: a free monthly homepage audit, then paid plans for whole-site audits, monitoring, and team workspaces. Track 2 is high-touch services: web and app builds, custom software, SEO/GEO, and security audits for mid-market and enterprise teams.

Which track is right for me?

If you want a fast read on a public site, start with the free AI-Readiness homepage audit. Paid plans unlock whole-site coverage, Marketing Signal, Website Security, and monitoring where included.

If you have a strategic problem (revenue stalled, AI features not yet shipped, headless rebuild stuck), the right move is a Track 2 engagement. Start with the apply form so we can scope and price together.

What happens after you apply

  1. Within one business day we read your apply form submission and reply personally.
  2. If we have an obvious fit, we schedule a 30-minute call to scope the engagement.
  3. Within five business days of that call you have a written proposal with a fixed-fee or retainer structure.
  4. Once you accept, kickoff is typically within two weeks. For urgent engagements we move faster.

Track 1 account flow

Create an account, add your site, and run the monthly homepage audit from the dashboard. The free plan includes one AI-Readiness homepage result each month. Paid plans unlock the full site, the other audit products, team seats, and monitoring as the plan allows.

Product workflow

  1. Add your domain and confirm you are authorized to audit the public site.
  2. Run the free homepage audit or use a paid plan for smart-sampled templates that represent the whole site.
  3. Review findings by severity, product area, affected URL, and recommended fix.
  4. Export the report for your team, ticket backlog, client update, or implementation partner.

Human and agent workflows

Every result is intended to have two interfaces: a human-readable dashboard and an agent-readable contract. Humans review scope, priority, billing, reports, monitoring, and team accountability. Agents consume stable run IDs, affected URLs, severity, evidence, recommendations, and status changes.

Today, the dashboard and report exports are the control surface. The connector layer will wrap the same projects, runs, findings, reports, and monitoring events through API, CLI, MCP, webhooks, and plugins as those surfaces launch.

Where to next

  • Pricing covers both tracks side by side
  • FAQ answers the recurring questions about refunds, timelines, and what we do not do
  • Browse the marketing site to see the live solution and industry pages