The engagement that ships the roadmap.
The AI Solution Roadmap prioritises what to build. The Implementation engagement is where we build it — deployment, cutover, knowledge transfer, and a documented project scope so your team runs the system without us in the room. Built from the workbook and the roadmap together, not from a fresh discovery. No SaaS subscription, no recurring license, no obligation.
Pre-req
Roadmap artifact
Engagement
Scoped per build
You leave with
A live system, run by your team
Request your implementation quote
We will reply within five business days with a scoped, line-item quote.
Stage 04 · Implementation · fixed-scope engagement with a line-item quote.
The quote is built from your AI Solution Roadmap — start there if you have not run the roadmap engagement yet.
What you receive
The engagement, in four pillars.
- 01
Deployment
The live wiring — integrations, infrastructure, and runtime. We build the system in your environment, connect it to the systems you already operate, and stand it up where the team will run it. No SaaS subscription, no recurring license, no obligation.
- 02
Cutover
The handover from the old flow to the new — sequenced, with a rollback envelope. We schedule the cutover against your operating calendar, run it alongside your team, and leave a written rollback plan in case the timing has to slide.
- 03
Knowledge transfer
Recorded walkthroughs, runbooks, and the team's first three runs alongside us. By the end of the engagement your team can operate the system without us in the room — that is the test we run the project against.
- 04
Project scope
A documented envelope — line-item ceiling, what is in, what is explicitly out. Anything outside the line items is a written change order with a price tag, not a surprise on the invoice.
Questions? Email werkbench@polsia.app.
Frequently asked
Before you hand over the roadmap.
- 01
Do I need the AI Solution Roadmap first?
Yes — the quote is built from the roadmap artifact, not from a fresh discovery. The roadmap gives us the ranked opportunities, the execution plans, and the data inputs we wire against. Without it we would be redoing the same discovery work the roadmap already paid for. If you have not done the roadmap yet, start there.
- 02
What does knowledge transfer actually look like?
Two recorded walkthroughs — one for the operator, one for the reviewer — written runbooks for the day-to-day and the failure modes, and the team's first three real runs alongside us. After those three runs the system is theirs and the support window begins.
- 03
How is the project scope set, and what changes it?
The scope is a line-item ceiling drafted from the roadmap execution plan and confirmed before kickoff. Anything outside those line items is a written change order with a price tag — not a mid-engagement surprise. The roadmap's "DIY steps" are typically performed by your team in parallel and do not affect the Werkbench scope.
- 04
What happens after go-live?
A defined support window tied to the engagement scope — typically two weeks for an SMB build, longer for larger cuts. After the window closes your team runs it. If you want a longer support relationship, that is its own scoped conversation; it is not a subscription and we do not roll it into the implementation fee.