Scope in writing, before work starts
Every engagement begins with a written scope, a fixed price and acceptance criteria. If the scope changes, the change is priced and offered, never absorbed and invoiced later.
Prizma is an AI consulting firm built around a simple belief: the gap between what AI can do and what most organizations are actually doing with it is enormous, and closeable.
We have helped organizations in education, research, and enterprise go from idea to working software.
Custom software for organizations that need it to hold up under review.
The stack is deliberately ordinary (Next.js, Supabase, the Anthropic API, Vercel), so any competent developer can maintain what we build. We retain our platforms and methods and license them, which is why each product starts from something proven. Work is priced per delivered product; advisory is billed by the hour, agreed in advance.
We answer non-disclosure and security questionnaires in writing on request, before scoping.
The people who scope your project are the people who build it and support it after launch.
Every engagement begins with a written scope, a fixed price and acceptance criteria. If the scope changes, the change is priced and offered, never absorbed and invoiced later.
A platform that guesses is worse than one that says it does not know. Every figure our systems produce carries its source, and a person approves every consequential step.
A standard stack, documentation at handover, and source-code escrow on request. The organization should be able to keep running what it licensed even if we could not.
If something will not work, or we are not the right firm for it, we say so at scoping, even when it costs us the engagement.
What stays with you, so the product keeps running whatever happens to us.