How do we get started?+
Send a paragraph describing the problem via the form on this page or by email. I reply within one business day with either a scope-call invite or a referral if it isn't a fit.
What does a typical engagement look like?+
A 30-minute scope call, a fixed-scope proposal with milestones and price, then weekly Loom updates and demos during the build. Every engagement ends with docs, a runbook, and a training session.
How do you price?+
Every engagement fits one of three shapes: Sprint (1–3 weeks, fixed-scope), Build (3–8 weeks, fixed-price per milestone), or Retainer (monthly, ongoing). Exact numbers come out of a 30-minute scope call so the price actually matches your problem.
How fast can you start?+
Small engagements (1–2 weeks of work) typically start within 5 business days. Larger builds go through a 2–3 week scoping phase first.
Do you work with our existing team and codebase?+
Yes — I ship PRs into your repo, pair with your engineers, and follow your review process. I can also run standalone if you don't have an in-house team yet.
Which industries do you work with?+
SaaS, fintech, e-commerce, legaltech, healthcare, media, and agencies. If your problem shape is 'we have data or workflows that a human shouldn't be doing', I can probably help.
How do you handle data privacy and security?+
Data stays in your environment where possible. Secrets live in a managed vault, every workflow is audit-logged, and PII redaction is on by default for LLM steps. I'm happy to sign an NDA before the scope call.
How do you ensure AI features actually work in production?+
Every AI engagement includes a golden dataset, eval suite, and a CI gate before any prompt or model change ships. That's how we catch regressions before your users do.
Do you offer ongoing support after launch?+
Yes — optional monthly retainers cover monitoring, on-call for critical workflows, and iterative improvements as your process evolves.
What if we're not sure which service we need?+
That's what the scope call is for. Describe the outcome you want, and I'll tell you honestly whether it's an automation problem, a data problem, or an AI-product problem — and what the right first step looks like.