Will the sprint produce working software?
Not normally. Lightweight technical exploration may support a decision, but the deliverable is the decision package and roadmap—not production software.
Service 01 / Strategy sprint
Choose the right AI opportunity before committing to a build.
A focused two-week engagement for organizations deciding where AI can create practical value. You leave with a prioritized opportunity, feasibility assessment, risk register, architecture recommendation and 90-day delivery roadmap.
Engagement at a glance
- Best for
- Teams deciding where AI deserves investment
- Typical format
- Two weeks · 5–10 working days
- Primary outcome
- A clear investment decision and 90-day roadmap
- Starting point
- Ideas, pressure to act or an early prototype
01 / DETAIL
When this is the right starting point
Your organization has promising ideas, pressure to use AI or an early prototype, but no clear decision about what deserves investment. The sprint compares practical value, feasibility and risk before a larger commitment.
02 / DETAIL
Questions the sprint answers
The work turns a broad ambition into decisions that leaders and delivery teams can act on.
- Which problem is valuable and sufficiently focused?
- Which users, data sources and systems are involved?
- Should the company build, buy, integrate or postpone?
- Where are human review, permissions or specialist advice required?
- How will success be measured?
- What implementation sequence is realistic?
03 / DETAIL
What is included
A focused assessment of the opportunity, the current workflow and the decisions required to move forward.
- Up to three stakeholder interviews
- Current-workflow assessment
- Prioritization of up to three use cases
- Data and integration readiness review
- Preliminary technical risk screening
- Baseline and success-metric definition
- Architecture recommendation
- Build-versus-buy analysis
- Cost and provider considerations
- 90-day roadmap
- Executive readout
04 / DETAIL
What you receive
A concise decision package covering the prioritized opportunity, feasibility, risks, recommended architecture and delivery sequence. The recommendation may be to proceed, revise, buy, postpone or stop—and explains why.
05 / DETAIL
Client participation
The sprint needs access to the people and information required to test assumptions rather than relying on generic recommendations.
- Executive or accountable sponsor
- Access to relevant process owners
- Representative workflow and system information
- Timely feedback on assumptions
- Agreement on the result to be improved
06 / DETAIL
Timeline
Approximately two calendar weeks or 5–10 working days, depending on stakeholder availability and the number of opportunities being compared.
07 / DETAIL
Not included
The sprint is a decision engagement, not an implementation project or formal assurance exercise.
- Production implementation
- Formal legal advice
- Comprehensive data-protection impact assessment
- Penetration testing
- Unlimited workshops
08 / DETAIL
Frequently asked questions
What to expect before and after the sprint.
Do we have to hire Norrelium for the build?
No. The recommendation and roadmap are designed to support an internal team, another supplier or a follow-on Norrelium engagement.
What happens after the sprint?
You choose whether to proceed, revise, buy, postpone or stop. If a build is justified, the roadmap defines the first practical delivery phase.
Next step
Is this the right engagement?
Share the current situation, desired result and constraints. Norrelium will confirm whether this engagement is the right starting point.