Skip to content
New guide: how to scope an AI project before you build

How we work

How a project runs

Technology projects usually go wrong between scope, delivery and ownership. We put each of those in writing early, so problems show up as scope questions rather than surprise invoices.

The three stages

Discover, build and operate.

Each stage has a defined scope, a deliverable and a price. The next stage starts after the previous one is accepted. No stage is open-ended by default.

01

1-2 weeks

Discover and scope

A short, written assessment of the data, the process and the decisions that cannot be deferred. You leave knowing the next step and its price.

  • Current-state audit and risk list
  • Data and integration map
  • Scoped stage plan with acceptance criteria
  • Fixed price for the first stage

02

Milestones

Build and ship

Weekly demos run from a test environment. Each milestone ends with something you can click, test and hand to your team.

  • Typed implementation in mainstream languages
  • Evaluation tests and features behind flags
  • Automated tests and CI/CD
  • Architecture decision records as we go

03

Optional

Operate and sustain

Launch ends with a handover. Upgrades, monitoring and incident response continue on a cadence you choose.

  • Dependency and security patch cadence
  • Monitoring and alert thresholds
  • Performance and cost review
  • Monthly roadmap hour

Cadence

What the week looks like.

We keep status updates in writing. Each engagement has one written thread, a weekly demo you can attend, and a decision log that everyone on the project can read.

Weekly

A demo from staging and a short written note: what shipped, what is next, what is blocked.

You and the accountable engineer

Per milestone

We go through the acceptance criteria together. A milestone closes only when they are met.

Product owner and engineering lead

When scope moves

A written change note with the cost and its effect on the plan. Estimates do not change without a note.

Whoever owns the budget

At handover

A walkthrough of repositories, environments, runbooks and the decision log. Recorded if useful.

Your engineering team

Ownership

Handover starts before launch

Handover is a set of decisions made during the build: repositories, accounts, runbooks and a decision log. The aim is that your team can run the platform without the original author.

  • Repositories in your organisation, with your access controls and CI.
  • Cloud and third-party accounts owned by you from the first environment.
  • Architecture decision records that explain the trade-offs behind each choice.
  • Runbooks for deploys, rollbacks, integrations and alerts.
  • A recorded walkthrough for your team, plus a written index of where everything lives.

Questions

The practical ones

How does the first engagement usually start?

With a fixed-price discovery. It takes one to two weeks and produces a written assessment, a scoped plan and a price for the first build stage. You can stop there and keep the documents.

Who is on the project?

One accountable engineer from PRISIUM™, working with your product and platform people. For narrow specialist work we may bring in a second person, but that is agreed in the scope up front.

How do you price build work?

We price build work by milestone, with acceptance criteria and a price for each one. We do not bill hourly against an open ceiling. If the scope changes, the change is priced before it is built.

What do we need to provide?

Access to the current systems, someone who can make product and data decisions, and a named person to accept deliverables. That is usually enough to start. We find out the rest as we go.

What happens after launch?

Launch comes with a handover. After that, some teams run the platform in-house and others keep ongoing support for upgrades, monitoring and incident response. Neither option is a condition of launch.

Can you work with our in-house engineers?

Yes, and it often works best. We pair on the difficult parts, write down the decisions and make sure your team can change the system without us.

Next step

Start with a discovery conversation.

It ends with a recommendation and a price for the first stage. It does not end with a proposal for the whole year.

Prefer email? Write what you are working on and we will reply.

Send a note

By sending this, you agree that we may reply to your enquiry. See our privacy policy.