Questions, answered straight
The things teams ask before they start.
No hedging. If something here does not answer it, the discovery call will.
Engagement & pricing
Most teams ask the same three things first: how it is priced, how fast they see something real, and what happens if it stalls.
How do you price an engagement?
Every engagement is scoped in the discovery call, then quoted as a fixed milestone with a fixed price. You see the scope and the number for the first system before any work begins. We work in milestones you approve before you pay, so you are never funding open-ended hours.
Do we pay a large retainer up front?
No. We bill per milestone, and you approve each one before it is invoiced. The first milestone is small on purpose: prove the lift on one workflow, then decide whether to expand.
What does a first engagement cost?
It depends entirely on the workflow and your systems, which is exactly what the discovery call is for. We will not quote a number we cannot stand behind. You will leave the first call with a clear scope and a fixed price for the first system.
Ownership & risk
Before signing, teams want to know who owns the work, what happens if it does not pan out, and whether they are stuck with us afterward.
What if it doesn't work?
You approve the result against a number you set before we build, so working is defined up front, not argued after. If a milestone does not clear the bar, you do not pay for it. We would rather kill a system early than ship one that does not earn its place.
Do we own what you build?
Yes. The systems we build are yours, running in your environment, on your accounts. You are not renting access to a black box, and you are not locked into us to keep it running.
Will we need an in-house AI team to maintain it?
No. We hand over plain documentation, and the system runs in tools your team already operates. Where you want ongoing tuning, we can stay on. Where you do not, you keep it and move on.
Timeline & fit
Not every workflow is worth automating, and not yet. Here is how we think about timing and whether your work is a fit at all.
How long until we see something real?
Weeks, not quarters. The first system is deliberately scoped to reach your real workflow fast, because a system in production teaches us more than a longer plan on paper. Timelines vary with the workflow and your systems.
Is our work a fit for this?
If a chunk of your week is repetitive, rule heavy, and high volume, it usually is. The discovery call is a free read on exactly that: we score your workflows and tell you honestly where it pays off first, or whether it does not yet.
Why not just use ChatGPT, or build it ourselves?
A chat tool answers one prompt at a time. We build a system that owns a workflow end to end, in your tools, measured against your number. Plenty of teams start by trying it themselves; we tend to come in when the gap between a demo and something that runs every day, reliably, becomes the hard part.
Data & security
Real work means real access. Here is how we treat your data and your security requirements.
Is our data safe?
We work through the same access a teammate would have, scoped to the systems the work touches and nothing more. We are glad to work under your NDA and your security requirements.
Where does our data go?
It stays in your environment wherever the workflow allows. We design around your data handling rules, not the other way around, and we will walk your security team through exactly how a system touches your data before anything ships.
Still deciding? Bring the question to the call.
Thirty minutes, no pitch. We will give you a straight read on whether this fits and where it would pay off first.