What kind of prototypes can you build in a sprint?+
Typical sprints build a customer or employee assistant over your documents, an agent that completes a workflow step, a brand-voice content model, or document extraction. The use case must be narrow enough to evaluate in 4 weeks. We confirm feasibility in the first scoping call.
How do you handle hallucinations?+
We agree an evaluation set of real examples in week 1 and measure the prototype against it, including how often it invents answers. We then add guardrails, source citations and human review where errors are costly. The accuracy and hallucination report is a named deliverable, not a promise of zero errors.
Where does our data go?+
The prototype runs in your cloud tenant or an EU region we agree on. Your data is not used to train public models, access is limited to the named team, and a data processing agreement covers the work. The security and data flow note documents every flow.
Who owns the prototype?+
You do. Code, prompts, evaluation sets and documentation are handed over at the end of the sprint, so you can continue with us, with your internal team or with another partner.
Do we have to build with Grapefruit after the sprint?+
No. The sprint ends in a go/no-go recommendation and there is no obligation to continue. If the answer is go, the production estimate is detailed enough for your procurement to compare offers.
What drives the cost of a prototype sprint?+
The sprint has a fixed scope agreed before we start. What moves the fee is the number of data sources and integrations, how sensitive the data is, and whether the prototype must run on-premises. We confirm scope and fee after a 30-minute call.