What does consultance.ai build?

Production AI engines: agents, voice, vision, RAG, workflow automation, and predictive models — designed, deployed, and maintained end-to-end.

Who is consultance.ai for?

Real estate firms, property management companies, and operations-heavy businesses worldwide. Active clients across Dubai, London, Toronto, and Pakistan.

How long from idea to deployed engine?

Proof of concept in 1–2 weeks on your real data. Production engine deployed in weeks 3–6. Self-healing systems and team training included.

How does pricing work?

30-minute discovery call is free. Written audit follows in 1–3 days. Build is project-priced; ongoing partnership is a flat retainer with unlimited servicing.

Do you transfer code and IP?

Yes. Code and IP transfer at every milestone. No subcontractors, no offshore handoffs — direct line to the engineers building.

What stack do you build on?

OpenAI, Anthropic Claude, Vercel, Supabase, Next.js, React, Tailwind, Stripe, Linear, and GitHub — production-grade tools the team trusts.

Marketing automationCuratedMedium

SEO + GEO Claude skill

Fire your SEO team. One command runs a full audit in four minutes. Does what Ahrefs, Semrush, and $5k/month agencies charge for.

operator summary

Who this is for

Best for founders, agencies, and operators that want Ahrefs and Semrush style output without the monthly seat fee.

where consultance.ai fits

We would wire this into a weekly cron, route the PDF and blog plan into Notion and Slack, and add a review gate before any auto-published content goes live.

install path

Setup steps

Install the Claude Code skill from the GitHub repository with one command.

Add DataForSEO API credentials in the skill config (free trial credit is enough to test).

Run /seo-audit yourdomain.com and inspect the generated PDF report.

Connect the blog skill only after a human reviews the first round of recommended titles.

where it breaks

Before you connect live data

• Run dummy data first. Real client data is not a test bed.
• API keys never go in a public repo. Use env vars and a secrets manager.
• Add logging, access control, monitoring, and a rollback path before launch.
• Read the license. Forking a repo without checking is how lawsuits start.

license note

Credit the original author

Check the repository license and DataForSEO terms before running audits on client domains.

We list this as a guide, not as our build, unless we are actively maintaining a fork.

Claude setup prompt

Paste this into Claude. It will install it for you.

Open Claude or Claude Code. Paste the prompt below. It will ask you a few setup questions, then walk you through every step adapted to your machine.

You are helping me install and run **SEO + GEO Claude skill** on my machine.

Repo / link: https://github.com/aaron-he-zhu/seo-geo-claude-skills
Category: Marketing automation
What it does: Fire your SEO team. One command runs a full audit in four minutes. Does what Ahrefs, Semrush, and $5k/month agencies charge for.
Difficulty: Medium

Setup steps from the public guide:
1. Install the Claude Code skill from the GitHub repository with one command.
2. Add DataForSEO API credentials in the skill config (free trial credit is enough to test).
3. Run /seo-audit yourdomain.com and inspect the generated PDF report.
4. Connect the blog skill only after a human reviews the first round of recommended titles.

Before writing or running anything, ask me these in ONE batch and wait for my reply:

1. What operating system am I on? (macOS / Windows / Linux)
2. Do I already have Docker installed and running?
3. Do I have Git installed?
4. Do I have Node or Python installed, and what versions?
5. Which model provider keys do I have available right now? (Anthropic, OpenAI, Gemini, OpenRouter, none)
6. Where do I want this installed on disk?
7. Is this just to test locally, or am I planning to connect it to live business data soon?
8. Anything sensitive (real client data, payment access, mailbox access) it should NOT touch on this machine?

After I answer, walk me through each setup step adapted to my environment. Stop after each step, show me the command, and wait for me to confirm it ran before moving on. If a step fails, diagnose the actual error before suggesting the next move. Do not connect this to live business data until I explicitly say go.

implementation path

Want it wired into your business instead of your laptop?

A repo on your machine is a starting point. The work that pays back is connecting it to the CRM, inbox, payments, and team processes you already run. That is the part we ship.

Book a discovery call Back to the library