We want an AI feature in the product but both engineers are on the core roadmap.
The AI feature, from prototype to production, in your codebase: an evaluation set, cost and latency budgets, fallback behaviour, and monitoring so you can tell when it degrades.
The published price applies when discovery confirms the work fits the scope and requirements below. Materially different or additional work is quoted separately.
Delivery timeline and milestones
Prototype in staging with an evaluation set built from your real data
Quality target hit, cost and latency inside budget, and failure modes handled
Behind a feature flag in production for internal testing
Live for users, with monitoring and a cost dashboard
Handover and documentation for changing prompts and models without us
What we need from you
- Repository access
- Representative sample data
- One engineer for a weekly review
- An agreed definition of ‘good enough’ before work starts
Payment and scope
€8,850 to start after the €150 discovery credit. The final invoice is €9,000.
Work outside this published package, third-party subscription and usage fees, and ongoing support are excluded unless separately agreed.
Common questions
The AI feature, from prototype to production, in your codebase: an evaluation set, cost and latency budgets, fallback behaviour, and monitoring so you can tell when it degrades. It is delivered against dated milestones, ending with handover and documentation for changing prompts and models without us.
It is delivered in 4 weeks for a fixed €18,000, excluding VAT. Payment splits in two: €8,850 to start after the €150 discovery credit, and €9,000 on delivery. The milestones above show what ships and when.
To keep the 4 weeks timeline, we need Repository access, representative sample data, one engineer for a weekly review, and an agreed definition of ‘good enough’ before work starts. Access and a decision-maker are what keep the build moving; without them, delivery dates slip.
That is what the €150 discovery session confirms. We check the systems, data, and integrations this build touches before committing. If it fits the published scope, the price holds. If your setup needs materially different work, we scope and price that separately rather than absorb it mid-build.
Anything outside the scope above, plus third-party subscription and usage fees and ongoing support, unless separately agreed. If discovery shows the work is materially different from this published build, it is quoted separately. You will know before we start, not halfway through.