For business owners · Personal AI Audit & Implementation Roadmap

Before you buy another AI tool, find out where AI belongs in your business.

I study how your business actually runs: the tools, the handoffs, the enquiries, the admin that lands on your desk. Then I rank where AI is worth it, where it isn’t, and what to build first.

You get a written plan you can act on: a ranked shortlist, a build-ready specification for the first system, the tools and running costs written down, and a 90-day order of work. Every document is editable and yours.

See a sample roadmap

$970 USD · one-time · one business · delivered 7–10 business days after your complete intake arrives. Nothing is charged on the call.

  1. A map of how your business runs today
  2. Your AI opportunities, ranked
  3. The tools, connections and running costs
  4. A build-ready specification for the first system
  5. Your 90-day implementation roadmap
  6. A walkthrough with me, and the editable files
Enquiry assistant · pilot specFictional sample
Trigger
A valid website enquiry
Output
Summary and reply draft in a review queue
Review
A person approves every draft before it is sent
Go-live
Both tests pass on the replay first
The six audit documents, with an excerpt of the fictional pilot spec on top.

Who this is for

You run a business. You know AI could help. You don’t know where to start, and you don’t want to guess with your money.

This is for you

  • You already have customers, tools and a way of working, and you want AI inside it, not a new business model.
  • Enquiries wait for replies, follow-ups depend on someone remembering, or the same admin gets done by hand every week.
  • You’ve tried a few AI tools and nothing stuck, or you’ve been pitched an automation and couldn’t judge if it was the right one.
  • You want a plan you can hand to a builder, not a slide deck about “the future of AI”.
  • You’d rather know what not to automate before you pay anyone to build.

Not yet

If you’re starting from zero with no customers yet, take the free AI Business Build Week on the LAUNCH track instead.

And if you already know exactly what you want built, skip the audit: book the call and I’ll quote the build directly.

Starting from zero? The free LAUNCH track

Why start with a plan

The expensive mistakes I’ve seen came from the choice, not the code.

When I ran a team of 12 developers, the costly problems were rarely bad code. They were the wrong thing built first. AI makes that mistake cheaper to make and easier to repeat: a tool bought because a competitor uses it, an automation that sends the wrong message to a real customer, a chatbot with nobody checking what it says.

The audit puts the decision before the build. I look at where work and enquiries actually slip in your business, score each candidate on value, feasibility and risk, and only then specify what to build. Often the best first step is not the flashiest one.

  1. Map
  2. Rank
  3. Specify
  4. Build

Build comes after the audit, with whoever you choose.

Where I look

  • Where enquiries wait, and how long nobody can tell
  • Which follow-ups depend on someone’s memory
  • Which weekly admin is the same steps every time
  • Where your information lives in five places and nobody trusts any of them
  • Where AI should never act without a human checkpoint

These are the places I look. What I find in your business, and what it’s worth to you, is what the audit is for. I don’t promise hours saved or revenue.

What you get

Six documents. Each one answers a question you’d otherwise pay to guess.

Every document is editable and yours. Build it with me, with your own team or with another developer.

  1. A map of how your business runs today

    Your main tools, processes and handoffs on one page, including the tasks that quietly eat your week. You’ll see your business the way a builder needs to see it.

    Lets you brief any builder from one document instead of re-explaining your setup on every call.

    See it in the sample
  2. Your AI opportunities, ranked

    A shortlist of where AI could help, ranked by value, feasibility and risk. Up to three priority workflows get a deeper assessment: why they matter, what they depend on and what needs testing before anyone builds.

    Lets you say no to the ideas that look good and aren’t, with reasons on paper.

    See it in the sample
  3. The tools, connections and running costs

    Which models and tools I’d use, what connects to what, what access is needed, and the monthly running-cost assumptions, written down so you can check them rather than discover them on an invoice.

    Lets you keep what already works, and know the cost before you commit.

    See it in the sample
  4. A build-ready specification for the first system

    For the first implementation: what triggers it, what goes in, what comes out, where a person reviews it, who is responsible and the checks it must pass before it goes live. Specific enough for a developer to start on day one.

    Lets you get comparable quotes, or hand it straight to your own team.

    See it in the sample
  5. Your 90-day implementation roadmap

    What to do first, what can wait and in what order, with estimated effort for each step and the decisions you’ll need to make along the way.

    Lets you move one step at a time instead of starting everything at once.

    See it in the sample
  6. A walkthrough with me, and the editable files

    A 45-minute walkthrough with me, plus one round of corrections after you’ve read the documents. I take you through the recommendations live, answer your questions and hand over every working document in an editable format. Nothing is locked in a format only I can use.

    Lets you own the plan. Build it with me, your team or anyone else.

    See it in the sample

Includes up to $200 of AI research and technical validation where it’s needed, such as testing a model on your real enquiry types. It’s part of the $970, not an extra charge, and not credits handed over to you.

Sample roadmap · fictional business

Here’s what the documents look like.

An excerpt from a sample I wrote for a fictional business, Harbor Learning & Coaching: a coaching company on WordPress with LearnDash and BuddyBoss, where one admin assistant answers every enquiry by hand. The business, its numbers and its tools are invented to show the format. Your audit is written about your business.

Enquiry handling today

Fictional sample

The setup map

  1. Website enquiry arrives
  2. Assistant looks up program details
  3. Writes a reply
  4. Owner checks difficult cases
  5. Sends and updates the tracker

Ranked shortlist

Fictional sample
  1. Enquiry handling Frequent, clear start and end, testable without replacing the website
  2. Onboarding administration Useful once program information is clear
  3. Progress summaries Valuable for coaches; impact on retention untested

How the shortlist was scored

Fictional sample

Each candidate gets three scores from 1 to 5. Value: how often it happens and what a slip costs. Feasibility: clear inputs, a clear start and end, and past examples to test on. Risk: what happens if it’s wrong in front of a customer.

Fictional scoring of three AI opportunities, 1 to 5
OpportunityValueFeasibilityRiskDecision
Enquiry handling442First: pilot as drafts a person approves
Onboarding administration321Second: write the program facts down first
Progress summaries434Third: only with a coach approving each summary
  • Risk is a gate, not a multiplier. A high value score never buys its way past risk: anything rated risk 4 or 5 gets a named human checkpoint in the spec, whatever else it scores.
  • Feasibility 2 or lower means fix the inputs before building anything. Here that’s the program facts, which the enquiry pilot needs anyway.
  • On a tie, the option that’s cheaper to switch off goes first.

Stack decision

Fictional sample
Keep
WordPress, LearnDash, BuddyBoss
Test first
Clearer program facts and reply templates
Assumption
$150/month incremental tools allowance, replaced by vendor quotes in a real audit

Sequence · the 90-day roadmap

Fictional sample
  1. Days 1–10Understand and prioritise
  2. Days 11–30Simplify, then test
  3. Days 31–60Measure and put it to work
  4. Days 61–90Decide what comes next
Enquiry assistant · pilot specFictional sample
Trigger     A valid website enquiry
Inputs      The enquiry + approved program facts
Output      Summary and reply draft in a review queue
Review      Harbor's admin (a person) approves every draft before it is sent
Owner       Harbor's admin; owner handles flagged cases
Acceptance  Missing facts are flagged; nothing sends automatically
Test 1      20 past enquiries replayed; 0 drafts state a price or date
            not in the program facts
Test 2      Every refund, complaint or health question in the replay
            is flagged to the owner, never drafted as a reply
Go-live     Both tests pass on the replay before a live enquiry is drafted

What Harbor keeps

Fictional sample
  • Setup map and opportunity assessment
  • Cost and capacity assumptions
  • First-implementation specification
  • 90-day roadmap, editable, usable with any builder

Harbor Learning & Coaching does not exist. Notice what the top-ranked idea is: not a chatbot that talks to customers on its own, but a draft a person approves. That’s usually where I start.

How it works

Five steps. You always know what’s next and what I need from you.

  1. Step 1: A free 15-minute call

    You tell me what you sell and where work or leads slip. I come prepared and tell you straight which of four answers fits: do it yourself with my free tools, the audit, a direct build proposal if your brief is already clear, or that we’re not a fit.

    You do
    book a time and write two lines about your business.
    You get
    an honest answer, with no obligation.
  2. Step 2: Scope and kickoff

    If the audit is the right step, I send a short written scope: the business, the goals, the workflows in focus, what I’ll need from you and a provisional start date. Once you’ve agreed and paid, I send the intake: a short questionnaire and a list of what to share. The day your complete intake arrives, I confirm the delivery date in writing: 7–10 business days later.

    You do
    agree the scope, pay, and send the intake.
    You get
    a provisional start date in the scope, then the delivery date in writing the day your complete intake arrives.
  3. Step 3: I study your business

    I work through your answers, your tool list and a 60-minute discovery session (live screen-share, or recorded if time zones don’t allow) on how a typical enquiry, order or week runs. I ask follow-up questions in writing so nothing depends on memory.

    You do
    the 60-minute discovery session and answers to my questions.
    You get
    no busywork; I only ask for what the plan needs.
  4. Step 4: I rank, test and specify

    I score every opportunity, assess up to three in depth, and where it’s useful I test a model or tool on real examples you’ve approved for that purpose. Then I write the specification for the first build and the 90-day order of work.

    You do
    nothing, unless I need a decision.
    You get
    findings tested where it matters, not just opinions.
  5. Step 5: Walkthrough and handover

    We go through the plan together in a 45-minute walkthrough. I explain every recommendation and what I’d do first, answer your questions, and hand over the editable files. Delivery is on the date I confirmed in writing when your complete intake arrived. After you’ve read the documents, you get one round of corrections.

    You do
    show up with questions, then send your corrections in one list.
    You get
    the full set of documents, yours to keep.

Steps 3 to 5 take 7–10 business days from the day your complete intake arrives.

How I work

I plan your business the way I build my own products.

Labgenz is my AI lab. I run it alone, with AI as my team, and I hold it to the standards I used with a team of 12 developers. The same habits go into your audit.

  • Decision before build. Nothing gets specified until it has been ranked against the alternatives.
  • Risk is a gate, not a multiplier. A high-value idea with a high risk score doesn’t get averaged through. It gets a human checkpoint or it waits.
  • Human checkpoints by default. Every system I specify says where a person approves before anything reaches a customer.
  • Measured, not eyeballed. Where something can be tested, I test it against real examples before I recommend it.
  • Written handovers. Every decision, assumption and open question is written down, so you or any builder can pick up exactly where I stopped.
  • One change at a time. The roadmap moves in small, reversible steps, and each one is shown before it replaces what works.

Proposed: Misclo phone screen: a late meeting leads the AI companion to propose a shorter home workout and a quicker dinner, waiting for the user’s OK. Accepted: The same Misclo screen after the change is accepted, with an Undo link.

Misclo · scripted sample on staging · in development
Side view of Theo overlaid on its reference in red and cyan on a measurement grid, used to check proportions.
Theo · measured against the reference, not eyeballed

Misclo is my own fitness app, in development with launch set for 1 January 2027. Each version is shown on staging before it replaces the last, with the previous one kept as rollback. Theo, my 3D character, is a Tripo AI mesh I rigged and animated in Blender with AI-written tools, checked against reference images in same-height overlays. See the builds in my lab

Animated artwork of Aymane at his desk, smiling at the camera.My animated double (AI-generated)
Aymane Hitmi · Labgenz

Who does the audit

Me. Not a junior, not a template, not a chatbot.

  • 45+digital projects I’ve managed
  • 12developers I led as a team
  • 4+years as CTO, formerly, at a US marketing agency
  • 2software products I’ve built and shipped

I’ve sat on both sides of this: the person deciding what to build, and the person responsible when it breaks. I use AI throughout the audit to research, analyse and draft, and I read, check and sign off every recommendation myself. The calls are with me.

On Instagram you may meet an AI version of me. It’s always labelled as AI. The audit, the calls and the walkthrough are me. What’s AI and what’s me

What the $970 doesn’t include

The audit is the plan. Building it is a separate decision.

If you want the first system built, I’ll quote it separately after the walkthrough, against the spec you already own. You’re under no obligation to use me.

Included

  • One business studied
  • A ranked shortlist of AI opportunities
  • An in-depth look at up to three priority workflows
  • The tool and running-cost assumptions
  • A build-ready specification for the first system
  • A 90-day roadmap
  • A 45-minute walkthrough with me and one round of corrections
  • Up to $200 of AI research and technical validation, inside the price

Not included

  • Building or configuring the systems in the roadmap
  • Third-party subscriptions, model usage or software licences
  • Ongoing support or maintenance after the walkthrough
  • More than one business, or more than three workflows assessed in depth
  • Testing every vendor integration end to end. I test what changes the recommendation, and the spec lists what still needs testing
  • Legal, tax, financial or compliance advice. Where a step needs one of those, the roadmap says so
  • Any promise of hours saved, leads won or revenue. The audit tells you where AI is worth trying and how to test it

After the audit

Three ways forward. All of them start from the same spec.

  1. Yourself

    Build it yourself or with your team

    The spec and roadmap are written for that.

  2. Another builder

    Hand it to another developer

    They get the same documents I’d work from.

  3. Me

    Have me build it

    I quote against your spec, and you see each step before it replaces the last.

If you’d like me to build, these are my starting prices.

Your exact quote follows the spec. Starting prices are the same on every page. Websites, platforms and content builds have their own pages: websites, platforms, content.

See the automation systems I build
Starting prices for automation builds
What I’d buildStarting at
Automation · Single SystemFrom $850
Automation · AI Agent / AssistantFrom $1,500
Automation · Ops Bundle (3 systems)From $2,300

Not ready to spend $970?

Start with the free version of step one.

The Ops Map is the method I use at the start of every audit: map how your business runs, then score the top opportunities by value, feasibility and risk. It’s free, ungated and comes with the prompt and the sheet. If you do it yourself and bring it to the call, we start further ahead.

The free tool gives you the map and a ranked list. The audit adds my assessment, tests where they matter, the build spec, the costs and the 90-day order of work.

MAPOPERATE · Day 1Ops Map + AI Opportunity Scorecard

Questions

What people ask before they book.

What exactly does $970 buy?

One business studied, a ranked shortlist of AI opportunities, an in-depth look at up to three priority workflows, the tool and running-cost assumptions, a build-ready specification for the first system, a 90-day roadmap, a 45-minute walkthrough with me and one round of corrections after you’ve read the documents. It’s a plan, not a built system.

How long does it take?

7–10 business days from the day your complete intake arrives. The written scope gives you a provisional start date before you pay, and I confirm the delivery date in writing the day the complete intake arrives.

How much of my time does it need?

The 15-minute call, the intake questionnaire, a 60-minute discovery session on how your business runs, a few written follow-up answers, the 45-minute walkthrough and one list of corrections.

What access do you need to my tools?

As little as possible. Most audits work from screenshots, exports and a screen-share. Where a tool offers view-only or guest access, that’s what I ask for. Never send me passwords by email or chat. If I need access, add me as a guest or view-only user under my own email, and remove me after the walkthrough.

Do you use AI on my business information?

Yes, for research, analysis and drafting. Before we start I name the AI tools and their data settings. Your information goes only to those tools and nowhere else, and you can mark anything off-limits. How I handle what you share.

Can I take the roadmap to another developer?

Yes. You get editable documents written so any competent builder, including your own team, can start from them. The spec lists the access, dependencies and decisions needed to begin.

Will you try to sell me a build at the end?

I’ll tell you what I’d do first and, if you ask, what it would cost with me. You’ll have a spec you can take anywhere, so the choice stays yours.

Can you work with the tools I already use?

That’s the starting point. The audit maps what you already pay for, and the plan keeps what works. Where something needs replacing, I say why, and what it costs.

What if AI isn’t the answer for my problem?

Then the audit says so. Sometimes the best first step is a clearer process or a simple template, not a model. A plan that tells you not to build something is still a plan worth having.

Do you guarantee results?

No. I don’t promise hours saved, leads or revenue, and you should be wary of anyone who does before they’ve seen your business. What I do guarantee is the scope: every document in the list above, delivered on the date I confirm in writing when your complete intake arrives.

I don’t have a business yet. Is this for me?

Not yet. Start with the free AI Business Build Week on the LAUNCH track, or the free tools in my library. The audit is for businesses that already run.

Next step

Fifteen minutes to find out whether the audit is the right first move.

Tell me what you sell and where work or leads slip. I’ll come prepared, and you’ll leave the call knowing which of four answers fits: the free tools, the audit, a direct build, or not a fit.

Prefer email? contact@labgenz.com

$970 USD · one-time · one business. Nothing is charged on the call.