FAQ
Questions people usually ask first.
How engagements work, what they cost, how your data is handled, and what you'll own at the end. If your question isn't here, ask me directly.
Working together
What kinds of businesses do you work with?
Everything from small businesses and founders to enterprise teams. The common thread is a real workflow where AI can save time, recover revenue, or improve customer experience, and a team that wants to own what gets built.
How does an engagement usually start?
With a short intro call to understand your goals and constraints. From there, most work follows three stages: an AI opportunity assessment to pick the right first project, a pilot on one workflow with real users, and a reliability review to make sure it holds up in production. You can start at whichever stage fits.
Do you work remotely?
Yes. I work remote-first with overlap across North American and European time zones, and I'm happy to join your existing tools for chat, tickets, and documentation.
Can you work alongside our existing engineering team?
Yes, and that's often the best setup. I can lead the AI work, pair with your engineers, and leave behind documentation, evaluations, and runbooks so your team can maintain and extend the system confidently.
Pricing & timelines
How much does it cost?
It depends on scope. Assessments and reliability reviews are usually quoted as a fixed fee, pilots and implementation are scoped per milestone, and ongoing support can run as a monthly retainer. After the intro call you'll get a written proposal with a clear price before any work begins.
How long until we see something working?
The aim is to put a working slice in front of real users early, then harden it with evaluations, monitoring, and guardrails. Exact timelines depend on data access and integrations, and are agreed in the proposal.
What if the pilot shows AI isn't the right fit?
That's a valid outcome. Every pilot has success criteria agreed upfront, so a clear 'not yet' is a decision backed by evidence, made before you spend more.
Data, security & governance
How do you handle our data?
Your data is used only for your project, with the least access needed to do the work. I prefer working inside your own cloud accounts and tools, and I'm happy to sign an NDA or follow your security and vendor-onboarding process.
Will our data be used to train AI models?
Not by me. Systems are configured with providers and settings that don't use your data for model training wherever those options exist, and the choices are documented so you can review them.
How do you keep AI systems safe and compliant?
Through clear permissions, human approval for high-impact actions, audit trails for what the system did and why, and evaluations that catch failures before users do. Governance is designed in from the start rather than added at the end.
Technical
Which AI models and tools do you use?
Whatever fits the problem, budget, and your constraints. That usually means leading commercial models or open-weight models, retrieval over your own data, and integrations with your CRM, helpdesk, or internal systems, all measured against agreed quality, latency, and cost targets.
Who owns the code and the system at the end?
You do. Code, prompts, evaluation sets, and documentation are delivered into your accounts and repositories, so there's no lock-in to me.
Do you offer support after launch?
Yes. Options range from a handoff period with your team to an ongoing retainer for monitoring, improvements, and new workflows.