Engagement

Terms you can hold us to.

Projects are quoted individually based on scope, complexity, and timeline — but every engagement carries the same four commitments, in writing.

Reviewing work together at a laptopDirect, from first call to launch
01

The four commitments

These aren't marketing lines — they're the working terms of every Prizm proposal.

01

Fixed scope

The proposal defines exactly what will be delivered. If the scope changes, the quote changes with your sign-off — never silently. You will never open an invoice and find a surprise.

02

Clear milestones

Work is broken into reviewable stages with a delivery target for each. You see progress as it happens, not at the end — and every stage is something you can actually inspect.

03

Full source ownership

Everything we build is yours — code, documentation, and infrastructure configuration. You can maintain it with any engineer, including not us. No license fees, ever.

04

Direct line

No account managers or hand-offs. You communicate directly with the engineer building your system, from first call to launch — which is also why communication stays fast and precise.

02

How pricing works

Every project is quoted individually — a landing page and a document-processing pipeline are different animals. The discovery conversation is free, and you'll have a firm, fixed quote in writing before any build work starts.

Discovery sessionFree — always
Focused automationsTypically a few weeks
Full platforms & applicationsLonger, milestone-scheduled
Ongoing maintenanceAvailable, never required
Planning documents and a firm quoteFixed quote, in writing
03

Common questions

What does a project cost?

Every project is quoted individually based on scope, complexity, and timeline. The discovery conversation is free, and you'll have a firm, fixed quote in writing before any build work starts.

How long does a build take?

Focused automations typically land in a few weeks; full platforms and applications run longer. Your proposal includes a milestone schedule with a delivery target for each stage, so the timeline is agreed before we start — not discovered at the end.

Who actually does the work?

The engineer you talk to on the first call is the engineer who builds your system. Nothing is outsourced or handed off, which is also why communication stays fast and precise.

Do we need to be "AI-ready" first?

No. Messy spreadsheets, inconsistent processes, and scattered tools are the normal starting point — untangling that is part of the work. If your situation genuinely isn't a fit for automation yet, we'll tell you that in discovery instead of selling you a project.

What happens after launch?

You receive documentation, training for your team, and the complete source code — you own it outright. Ongoing maintenance is available but never required; the system is built so any competent engineer can take it over.

How is our data handled?

Client project data is governed by our service agreement, kept within the systems you approve, and never used for anything beyond your engagement. NDAs are welcome — many clients start there.

Same terms. Your project.

Tell us what's eating your team's hours. We'll reply within one business day with an honest read on whether it's worth building.

Start a project