Ongoing AI Advisory

Keep making sound AI decisions as the work changes.

Bring the vendor proposal, workflow change, or question that needs a second read. I'll help you decide what needs attention and what can wait.

Book a 30-minute call See a sample decision log

Free introductory conversation.

The facts

Monthly: fixed retainer, paid in advance
2 sessions: 60 minutes each, per month
2 reviews: of materials, up to 20 pages total
2 days: business-day response target

Plus up to two hours of asynchronous work each month. Month to month. No initial minimum. Cancel before the next billing period.

Use this when

A martech vendor proposal, AI feature, workflow change, data question, or implementation decision is moving faster than your team can evaluate it.
A claim needs an independent second read before anyone commits.
Decisions are being made without a record of the evidence behind them.
You want a fractional AI advisor: a standing second opinion without adding headcount or a retainer you can't exit.

You leave with

A decision log entry for every question — question, evidence, decision, owner, revisit date — plus written comments on the materials reviewed. The log is yours.

Month one is intentionally designed to establish enough context that later advice is specific to your systems, constraints, and decision rights, rather than generic AI commentary.

A request, and what comes back

Every question gets a written entry you can find later.

The decision log is the running record: what was asked, what the evidence showed, what was decided, who owns it, and when to look again.

Decision log · Entry 14 · ThursdayIllustrative. Not a client record.

What people bring

Decisions that benefit from a second read.

You keep the decision and the operational ownership. I help you see what the evidence supports.

A vendor proposal

What it assumes about your data, what it leaves out, and which questions to ask before signing.

A workflow someone wants to change

Whether the change removes a review step that was doing real work, and what to watch after.

A pilot that's drifting

Usage is down or output quality slipped. Is it the tool, the data, or the habit? What to check first.

A build request from another team

Is it ready to build, or does it need a design step first? What the quote should include.

A question from leadership

“Why aren’t we using AI for this?”, or the newsletter your CEO forwarded with one line: “Thoughts?” Answered with what would have to be true first, in language you can send back as it is.

Something you built with me

Operating questions, small changes, and whether a new request is a tweak or a new scope.

Each month

A defined amount of attention.

Capacity is stated so you can plan around it. Unused capacity doesn't roll over. Substantial technical execution is scoped separately.

Monthly capacity
Included	Each month	How it's used
Working sessions	2 × 60 min	Scheduled or on demand. Bring the decision; we work it through and log it.
Material reviews	2, ≤20 pages	Proposals, specs, plans. Written comments and a log entry back.
Asynchronous work	Up to 2 hours	Email questions, a quick look at an export, a short written recommendation.
Response target	2 business days	Monday to Friday, US Eastern, excluding communicated closures. A response starts the conversation; resolution depends on the question. This isn't incident coverage.

Working sessions
Each month2 × 60 min
How it's usedScheduled or on demand. Bring the decision; we work it through and log it.
Material reviews
Each month2, ≤20 pages
How it's usedProposals, specs, plans. Written comments and a log entry back.
Asynchronous work
Each monthUp to 2 hours
How it's usedEmail questions, a quick look at an export, a short written recommendation.
Response target
Each month2 business days
How it's usedMonday to Friday, US Eastern, excluding communicated closures. A response starts the conversation; resolution depends on the question. This isn't incident coverage.

Getting started

No Diagnostic required.

Advisory can follow any service, or begin on its own. New clients start with a context review so the first log entry is about your situation, not general advice.

If we've worked together

We start in month one with what you already have: the findings brief, the map, or the build. The first session is the first decision. This is where most long-term client relationships end up, because the context is already there.

If we haven't

A scoped context review fits inside the first month's allowance for most teams: one session and one material review to understand your systems, tools, and who decides what. If your situation needs more than that, I'll quote a separate onboarding rather than eat the month.

In their words

“I'm so grateful to have the pleasure of working with and learning from Allison. Beyond her technical strengths, she brings passion, curiosity, and a genuine joy to every interaction. She is someone I look up to as a female in a male-driven industry.”

Excerpts from 2025-2026 company award submissions

Allison on a call at her desk, notebook open.

Before you book

Common questions.

Anything not covered here, bring to the call.

Is there a minimum term?

No. Month to month, paid in advance. Cancel any time before the next billing period and that's the last month.

What if something breaks and we need you today?

Advisory isn't incident coverage. The two-business-day target is for a response, not a fix. If you need operational support for something I built, we scope that separately.

Can you do the work, not just advise on it?

Small things, within the two async hours. Anything substantial is a Sprint or a Build, quoted separately, so Advisory stays about decisions.

Who owns the decision log?

You do. It lives in your tools and stays with you if we stop working together.

Bring the decision that's sitting in your inbox. We'll work out whether a standing second read is what you need.

Free introductory conversation. No preparation required.

Book a 30-minute call Compare all services