Question 1

What does a first project cost?

Accepted Answer

A fixed-scope first project is $2,500 – $12,000, quoted once after we understand the workflow. If you would rather build it with us, co-building is $250 / hour with hour packs. Every number is on the pricing block above.

Question 2

How long before something is actually running?

Accepted Answer

Usually one to three weeks from kickoff to a system running on your real work, depending on how many systems it touches. You see something working early, not at the end of a long engagement.

Question 3

Which models do you use?

Accepted Answer

Whichever fits each step. We orchestrate between models rather than betting everything on one vendor, and we run them in your accounts so you are not locked in. If a cheaper model passes the evals, we use the cheaper model.

Question 4

Why do evals matter?

Accepted Answer

Because a system that looks right in a demo and fails on your real edge cases is worse than no system. We build a test set from your own examples and nothing reaches production until it passes.

Question 5

What happens when the model gets it wrong?

Accepted Answer

Risky steps stop for a person: the system proposes and a human approves. Everything is logged, exceptions are surfaced rather than buried, and wrong answers become new test cases so the same mistake is caught next time.

Question 6

Who owns the accounts and the code?

Accepted Answer

You do. Systems are deployed in your infrastructure and your accounts. Handover includes the integration, the evaluations, and the documentation, so nothing depends on us being on retainer.

Question 7

How is our data handled?

Accepted Answer

Your data stays in your accounts. Retrieval runs over your own documents with your permissions respected, and we do not use your data to train models. What leaves the building is what the workflow needs, and nothing else.

Question 8

What does handover mean, concretely?

Accepted Answer

The code and configuration running in your environment, the evaluation set you can re-run after any change, a short runbook for what to watch, and a session with your team so the system outlives the project.