What does the consultation cost?

$500 for 90 minutes, including preparation before the call and a written summary afterwards.

How is this different from a discovery call?

A discovery call is free and exists to work out whether a training or deployment engagement makes sense for you. It's a sales conversation. The consultation is a service: you bring a specific question and we solve it, whether or not there's any further work. If you want to explore working together, book the discovery call instead.

Will you try to sell me something?

No. It's a paid engagement, so the call is spent on your question. If the answer turns out to be work we do, we'll say so once and leave it there.

Who should be on the call?

Whoever owns the decision, plus anyone who'd have to implement it. Two to four people works best. More than that and it becomes a presentation rather than a working session.

What if we need more than 90 minutes?

Most questions fit. If yours clearly won't, say so when you book and we'll tell you honestly whether a consultation is the right format or whether you need a proper engagement.

Can the fee go toward a larger engagement?

Yes. If you go on to book a deployment sprint or on-site training within 60 days, the consultation fee comes off the first invoice.

Paid consultation90 minutes · $500

Bring a real question. Leave with a plan.

Ninety minutes with a Deployment Labs engineer on whatever you're actually stuck on: AI sprawl across your team, a rollout you want to get right first time, or what compliance really requires in your industry. It's a service, not a sales call.

Book a consultation Or book a free discovery call

Exploring whether to work with us on training or deployment? The discovery call is free and is the right starting point.

The 90 minutesPrepared before · Written up after

Before

We read your brief

Sent when you book.

0 min

Context

No background time. We read your brief first.

Working session

Your question, on the table, with an engineer.

Decisions

Sequence, tools, owners.

Written summary

In your inbox within 24 hours.

Before
We read your brief
Sent when you book.
0 min
Context
No background time. We read your brief first.
10
Working session
Your question, on the table, with an engineer.
70
Decisions
Sequence, tools, owners.
90
Written summary
In your inbox within 24 hours.

Which one do you need?

Two ways to talk to us. Pick by what you need, not by price.

Discovery call · Free · 30 minutes

Are we a fit?

A sales conversation, and we say so. It exists to work out whether a training or deployment engagement makes sense for you.

For exploring training, a sprint, or a retainer
We scope your team, tools and use cases
You leave with a proposal if it makes sense
No cost, no obligation

Book a discovery call

This page

Consultation · $500 · 90 minutes

Your question, answered.

A service, not a funnel step. You bring one decision with real consequences and we solve it, whether or not there is any further work.

For a specific decision you own
We read your brief before the call
A working session with an engineer, not a pitch
Written summary within 24 hours
Fee credited toward any engagement within 60 days

Book a consultation

What people bring

Four conversations we have most often.

You don't need to fit one of these. They're here to show the altitude: a specific decision with real consequences, not a general briefing on AI.

Your team is running wild with AI

People are using whatever they found, in whatever way they invented, with no shared standard. You want it wrangled into something coherent before it becomes a liability, without killing the momentum that got you here.

Usually routes toAI governance

You're about to give everyone access

Licences are approved and you get one chance to do the rollout properly. What to standardise on, who gets access first, what to have in place before day one, and what actually drives adoption past the first fortnight.

Usually routes to2-day training

You need to know what compliance requires

You handle regulated data and the honest answer to "can we use this?" is nobody's sure. What HIPAA, GDPR, SOC 2 or FINRA actually require of AI use in your workflows, and where the real exposure sits.

Usually routes toAI governance

You want a second opinion on a plan

You've got a roadmap, a vendor proposal or a build-versus-buy decision, and you want someone who does this weekly to tell you where it breaks.

Usually routes toDeployment sprint

What's included

Ninety minutes, prepared for. Then it's written down.

We read your situation before the call so none of the time goes on background. Within a day you have a document like the one on the right.

90 minutes with a Deployment Labs engineer, not a salesperson
Review of your situation sent in advance, so we start with context
A written summary afterwards with what we discussed and what to do next
Specific tool, platform and sequencing recommendations for your case
Straight answers, including "you don't need us for this"

Who you'll talk to

Freeman LaFleur

Co-founder · Chief Deployment Engineer

Runs the technical side of every engagement: platform setup, Claude Code and Codex onboarding, and the skills, automations and internal tools a team leaves with. Writes the Claude Code hub.

Meet the team

Consultation summary

Sent within 24h

Rollout plan for a 40-person agency

Example

Situation: ChatGPT Team licences for six months. Three heavy users, a Slack channel of prompts, no shared standard. Legal has asked what client data is allowed in.
Recommendation: Standardise on ChatGPT Team for the whole company now and add Claude Code for the four engineers. Don't move to Enterprise until weekly seat usage passes half.
Sequence: 01Usage policy this week. Thirty minutes with the generator, then a named owner.
02Role prompt library, owned by ops, living in the workspace people already open.
03Client-brief drafting as the first shared workflow. High volume, low risk, visible.
Tools: ChatGPT TeamClaude CodeCustom GPTsUsage policy generator
Next 30 days: Owner named. Two workflows live. A review step defined for anything client-facing. We check in once at day 30, no charge.

Book · $500

Pick a time that works.

You'll get a short form after booking asking what you want to cover. The more specific you are, the more useful the ninety minutes will be.

Fee credit

Book a deployment sprint or on-site training within 60 days and the $500 comes off your first invoice.

Prefer email? hello@deploymentlabs.ai

Questions

Before you book

Ninety minutes, one decision

Bring the question. We'll bring the plan.

If you already know you want to explore a bigger engagement, take the free discovery call instead. Either way, you talk to an engineer.

Book a consultation Book a free discovery call