// What we do

Three products. One companion.

Working AI on three time horizons — a day, a quarter, and a month — with a maker programme alongside. Sold at fixed scope on the Microsoft 365, Power Platform, and Azure AI Foundry stack. EU AI Act, ISO/IEC 42001, and NIST AI Risk Management Framework baked in, not charged separately.

3 picks · 90 days · 1 named owner

KveikjaSpark Day

One day, on-site at your office. The morning is a strategy session with the C-suite: score candidate use cases, pick the two or three that should ship in the next ninety days, name an owner per pick. The afternoon is a live build with the executive team and four to six operating leaders: an Alvio principal builds two or three reference prototypes in your Microsoft 365 tenant — Copilot Studio agents, Power Platform apps, Azure AI Foundry components — alongside the named owners. Each prototype clears a thirty-minute risk and controls review before it leaves the room.

By the close of the day, your team has reference prototypes they can study, a one-page 90-day plan signed in the room, and named owners ready to start.

Duration
8 hours, on a single day, on-site
Format
Fixed scope
Next step
Sprettur-Coach (default) or Sprettur-Deliver (exception)

12 weeks fixed · 1 capability shipped · 30 employees trained

SpretturSprint

Twelve calendar weeks to put one production AI capability live in your tenant. Policy drafted, ratified, and communicated alongside the build. Thirty employees trained at three levels — executive, manager, frontline — meeting EU AI Act Article 4 in one motion. KPI baseline before go-live; written measurement report at week sixteen.

Default

Sprettur-Coach — customer-led ship

Your named owners build the production capability; the Alvio principal coaches. A weekly working session reviews progress, unblocks decisions, and gates the controls. Your people own the code, the deployment, the operation. This is the engagement Alvio is built to run.

Premium — exception

Sprettur-Deliver — Alvio-led ship

Same twelve weeks, same scope, same controls memo. The difference: an Alvio principal as engagement lead with two senior practitioners embedded with your team. Alvio writes the code, configures the platform, runs the deployment, signs the handover. Sold when you ask for it.

Duration
12 calendar weeks, fixed scope
Format
Coach (default) or Deliver (premium)
Next step
Áfram-Steer to keep the rhythm and the controls in place

1 fractional CAIO · 4 quarterly reviews · 24h incident clock

ÁframOnward

A monthly partnership, six-month minimum. A named Alvio principal acts as virtual Chief AI Officer. Quarterly executive reviews cover regulatory horizon scanning across the EU AI Act, ISO/IEC 42001, NIST, and the Microsoft AI roadmap. An independent AI risk audit lands annually. A 24-hour engagement clock covers material AI incidents.

Default

Áfram-Steer — advisory retainer

A fractional CAIO at 0.15–0.25 FTE. The principal attends your executive team and audit committee on AI matters. Steer does not ship capabilities — your team continues to ship, Alvio steers. The natural follow-on for customers who chose Sprettur-Coach and want to keep the rhythm of named-owner shipping.

Premium

Áfram-Build — advisory + delivery pod

Same advisory base, plus a small Alvio delivery pod that ships one new governed AI capability every month. Sold when your internal team is not yet ready or the cadence requirement is too aggressive for a coached pace.

Duration
Monthly rolling, six-month minimum, evergreen
Format
Steer (default) or Build (premium)
Next step
Annual renewal, or transition to an internal CAIO with handover from Alvio

5 first makers · 1 maker community · 6 weeks fixed

SmiðjaForge — companion

Microsoft has been making the low-code / no-code promise — Power Apps, Power Automate, Power Platform — for the better part of a decade. The promise was always real; adoption was always disappointing because the people who knew which workflow they wanted to automate did not have the technical confidence to ship it. AI coding assistants close that gap. The promise is finally workable. The job now is to capture the value with controls, not as shadow IT.

Smiðja is the operating playbook that does that. Sanctioned tooling, light governance gates, named maker roles, training at three levels, a community model. Smiðja does not turn your employees into software publishers. It gives the people who already know what their workflow needs a framework to ship what they always could have built and never did. Smiðja is what makes Sprettur-Coach possible.

Duration
4–6 weeks, fixed fee
Format
Standalone, companion to Sprettur, or foundation of an Áfram retainer
Next step
Sprettur-Coach, with the first cohort of makers in place

What's next? Book a Kveikja.

Eight hours, on-site. Two or three working AI prototypes in your tenant by the time we leave.

Book a Kveikja