FAQ
Straight answers, before you ask.
The questions that come up in most scoping conversations. If yours isn't here, ask directly.
Who do you work with?
Executives, functional leaders, and corporate teams who want to use tools like ChatGPT, Claude, and Codex responsibly and productively. Engagements range from a single leadership briefing to multi-month adoption programs across teams.
Do you work inside our environment, or yours?
Yours. Training, configuration, and custom builds all happen inside your approved workspaces and accounts, under your admin controls and policies. Custom GPTs are created in your workspace. Nothing is built or stored in ours.
What do you explicitly not do?
Custom API development, production software integrations, legal advice, and cybersecurity audits. This practice stays in enablement and adoption; for engineering and specialist domains we work alongside your internal teams and qualified vendors.
Virtual or onsite: which should we choose?
Most configuration, training, and coaching works well virtually at $500 per hour. Onsite ($1,000 per hour) tends to suit leadership briefings, board sessions, and intensive multi-day team training. Many clients combine the two: onsite to launch, virtual to sustain.
How does the optional remote assistance work?
For virtual engagements, sessions may use Chrome Remote Desktop, with the participant's permission and subject to company policy, to handle approved downloads, settings, and one-time configuration. The reason is billable time: this happens live while we're speaking, so your hours aren't spent narrating setup steps that aren't beneficial for you to understand. Unless you want to learn them, in which case we go through every step together.
The participant stays present the entire time, personally handles all passwords and authentication, and can end access at any moment. It's optional, and plenty of engagements never use it.
How do you handle confidential information?
Work happens in your environment under your policies, and responsible data handling practices are part of what we teach. Mutual NDAs are welcome. Please don't send confidential or sensitive information through the website contact form; a general description of what you're exploring is enough to start.
How does an engagement start?
With a short scoping conversation, at no charge. From there you'll get a proposed plan with format (virtual, onsite, or both), estimated hours, and the applicable rate. Work proceeds hourly or against a prepaid block, whichever suits.
Which tools do you cover?
Engagements most often involve ChatGPT (including custom GPTs and workspace configuration), Claude (including Claude Cowork and Claude in Chrome), and Codex, because that's where most teams start. The practice isn't tied to any of them. If your organization has standardized on a different model or platform, the work adapts: the methods behind configuration, instruction design, workflow templates, and verification carry across tools.
Do we need licenses before we start?
You purchase and administer your own subscriptions so billing, data, and control stay with you. Plan selection and workspace setup guidance is part of the configuration work if you haven't chosen yet.
Is this strategy consulting or hands-on training?
Both, deliberately. Executive briefings give leadership an accurate picture and a decision framework; working sessions configure tools, build assets, and train teams on real work. The combination is the point: understanding first, then knowing what to do.
Still have a question?
Send it over. Replies typically within two business days.
Ready to make AI genuinely useful?
Start with a short scoping conversation. No charge, no deck, no pressure. Just a clear read on where AI can help your team and what it would take.
Replies typically within two business days.