How IDMA works, step by step

Sign up with an email address, then create a project. The first thing the form asks is what the workspace is for: SEO and content, or a voice assistant. Most people want the first — one workspace for one site or brand, with its own chat thread, its own connected tools and its own schedules. Agencies keep one per client so nothing bleeds across accounts. The choice is made once and can't be changed later, because it decides which surfaces the project has.

A voice assistant project skips most of what follows: there is no site to crawl, so no first analysis runs, and no connectors or automations to set up. You go straight to describing how the phone should be answered. It does not answer calls yet — what that means is on the homepage. The remaining steps below describe the SEO path.

The form asks for your domain, business name, field of work, who you're writing for, the language and location you're targeting, and a few seed keywords. None of it is a preference: it's the context every agent reads before it does anything, and it's the difference between a content brief that sounds like your business and one that sounds like a template. You can leave parts blank and fill them in later, and the form tells you what each gap will cost you.

Then the work starts on its own. IDMA searches your field of work and each seed keyword separately to find who ranks above you, crawls your site for technical problems, and reads your published content — before you've asked for anything. The project opens when that finishes, usually in a few minutes.

Nothing is waiting in your inbox or your thread when it does. The chat starts empty, the way it always did — but the manager has already read both audits, so the first question you ask is answered from real findings about your site instead of starting a job and making you wait.

Describe the goal in plain language. Your manager agent reads it, answers from what it already knows about the project, and runs a specialist only when the answer needs new work. There's no agent picker to get wrong, and no dashboard to learn.

If you already know who you want, a slash command skips the routing step — /analyzer goes straight to the Technical SEO Analyzer, /writer to the Content Writer. Long jobs return a “working” message immediately and stream their results in, so nothing freezes while a crawl runs.

Results arrive as structured cards in the project thread — a title, what ran, the findings, and the actions you can take. Scheduled runs land in the same place as things you asked for, so there's no second inbox to check.

The thread is the history. Ask “what changed since last month?” and your manager reads the earlier runs on that project rather than starting from nothing.