Menu
← Sample assessment library

SAMPLE — Fictional business

This is illustrative Velnariq output based on a fictional organisation. It is not an assessment of a real company and should not be treated as professional, legal, security or financial advice.

SAMPLE — Fictional business

Sample Technology Opportunity Assessment

Retail & Multi-site Business

Northbridge Home & Living Ltd

Growing UK retail company with stores and an online channel

Evidence statuses stay visible throughout.

1. Executive summary

  • Northbridge Home & Living Ltd is a fictional UK retailer operating several stores plus an online sales channel.
  • Owner-provided evidence points to inconsistent site connectivity, mixed reliance on older on-premises systems, fragmented customer-contact channels and manual weekly reporting.
  • Priority opportunities focus on validating multi-site connectivity performance, clarifying recovery expectations for critical store and online services, consolidating customer-contact visibility, and establishing evidence-led security discovery — without treating unverified weaknesses as confirmed vulnerabilities.

2. Business context

  • Fictional Companies House-style record: private limited company trading as a home and living retailer.
  • Public website evidence (illustrative): store locator for multiple UK locations and an ecommerce catalogue.
  • Owner-provided context: growing store estate, hybrid head-office/store operations, and increasing dependence on online order fulfilment.

Owner challenges and goals:

  • Store teams report intermittent connectivity that interrupts till and inventory lookups at peak times. (Owner-provided)
  • Head office still relies on an older server for some stock and pricing tools. (Owner-provided)
  • Customer contacts arrive by phone, email, web form and marketplace messages with limited shared visibility. (Owner-provided)
  • Weekly trading packs are assembled manually from several systems. (Owner-provided)
  • Goals: more reliable store operations, clearer recovery expectations, better customer-response consistency, and validated security priorities.

2b. Guided problem discovery (illustrative)

Shows how Velnariq keeps customer statements, observations, potential problems, impact, unknowns and validation needs distinct. Status remains hypothesis until evidence supports a stronger claim.

Business goals

  • Improve operations
  • Improve reporting and visibility
  • Improve reliability

Customer statement

We use lots of spreadsheets to build the weekly trading pack.

Observation

Weekly trading packs are assembled manually from several systems (owner-provided).

Potential problem

Manual / fragmented reporting workflow across store and online channels.

Possible business impact

  • Employee time
  • Decision-making
  • Operational efficiency

Primary / related capabilities

Primary: Data & Intelligence → Reporting

  • Related: Operations → Workflow
  • Related: Finance → Financial reporting

Illustrative capability coverage

  • Operations: Potential concern
  • Data & Intelligence: Potential concern
  • Customer Service & Experience: Observation
  • People & HR: Not assessed
  • Procurement: Not assessed

Not assessed means insufficient evidence in this sample — not a healthy score.

Technology requirement

Order and trading information should move between store, online and reporting processes without repeated manual consolidation.

Solution capability: Data integration / reporting — potential fit (not a product recommendation).

Why this? Because the owner reports manual weekly packs. Evidence is owner-provided. Error rate remains unknown. Validate source systems before choosing any platform.

Unknown / validation

  • Unknown: Source systems of record
  • Unknown: Time spent assembling packs
  • Unknown: Error rate in manual consolidation
  • Validate: Confirm reporting owners and systems involved
  • Validate: Understand volume and frequency of trading packs
  • Validate: Establish whether integration or reporting tooling is already available

3. Evidence considered

Public evidenceBusiness

Company website lists multiple UK store locations and an online shop.

Owner-providedConnectivity

Owner reports inconsistent connectivity between stores and head office during peak trading.

Owner-providedCloud & Infrastructure

Owner reports continued use of an on-premises server for selected stock and pricing tools.

Owner-providedCustomer Experience

Owner reports customer contacts across phone, email, web form and marketplace channels without a single shared view.

Owner-providedData & Analytics

Owner reports manual consolidation of weekly trading reports.

UnknownContinuity

Formal recovery objectives (RTO/RPO) for till, ecommerce and stock systems are not evidenced.

Requires validationCybersecurity

Identity, MFA, endpoint and monitoring controls are not evidenced in the sample pack; no vulnerability assessment was performed.

4. What we know

  • The fictional business operates multi-site retail plus an online channel. (Public evidence / illustrative assumption)
  • Owner evidence indicates connectivity consistency is a live operational concern. (Owner-provided)
  • Owner evidence indicates some critical tools still depend on an on-premises server. (Owner-provided)
  • Customer-contact handling is fragmented across channels. (Owner-provided)
  • Reporting currently depends on manual consolidation. (Owner-provided)

5. What remains unknown / requires validation

  • Measured bandwidth, failover and SD-WAN/MPLS arrangements per site. (Requires validation)
  • Exact hosting topology for ecommerce, till and stock systems. (Requires validation)
  • Documented recovery objectives and tested restore evidence. (Unknown)
  • Current identity, endpoint, email security and monitoring posture. (Requires validation — not confirmed as weak or strong)
  • Ownership and tooling for a unified customer-contact view. (Requires validation)

6. Technology landscape

Solution areas covered in this fictional sample. Use the anchors from public solution cards to jump here.

Connectivity & Networks

Owner evidence indicates inconsistent multi-site connectivity affecting store operations; measured performance and resilience arrangements require validation.

What we know

  • Peak-time store connectivity disruption is reported by the owner.
  • Stores depend on connectivity for till and inventory lookups.

Still unknown / requires validation

  • Circuit design, failover, Wi-Fi quality and remote-access arrangements per site.

Cloud & Infrastructure

Some stock and pricing tools still depend on an older on-premises server; hosting and modernisation options need evidence before any migration recommendation.

What we know

  • Owner confirms continued on-premises dependency for selected tools.

Still unknown / requires validation

  • Full application and hosting inventory, dependencies, and change constraints.

Cybersecurity

Security priorities are framed as discovery needs because current controls were not evidenced. This sample does not assert confirmed vulnerabilities.

What we know

  • Retail operations depend on networked till, stock and customer systems — a stated business dependency.

Still unknown / requires validation

  • Identity, MFA, endpoint, email security, monitoring and incident-response controls. No penetration test or vulnerability scan is included.

Customer Experience & Communications

Customer contacts arrive through multiple channels without a shared operational view, creating repeated effort risk.

What we know

  • Phone, email, web form and marketplace contacts are all in use according to the owner.

Still unknown / requires validation

  • Volumes, response SLAs, CRM usage and ownership of channel consolidation.

Business Continuity & Resilience

Recovery expectations for store and online services are commercially important but not yet evidenced.

What we know

  • Till, ecommerce and stock systems are critical to trading continuity based on owner context.

Still unknown / requires validation

  • Documented RTO/RPO, backup coverage and restore test evidence.

Data & Analytics

Weekly trading packs are assembled manually from several systems, indicating reporting friction.

What we know

  • Manual consolidation of weekly trading reports is owner-confirmed.

Still unknown / requires validation

  • Source systems of record, data quality ownership and reporting platform options.

7–9. Opportunity areas, prioritisation and recommended actions

Your Technology Opportunity Plan

The technology opportunities worth exploring for Northbridge Home & Living Ltd.

Based on fictional owner and public evidence, the highest-value next steps are validating multi-site connectivity performance, clarifying recovery expectations, improving customer-contact visibility, and establishing an evidence-led security discovery plan.

We identified 6 evidence-led opportunities to consider.

My opportunities

What we recommend exploring

NOW

Validate multi-site connectivity performance and resilience

HIGH OPPORTUNITY

Owner evidence indicates peak-time connectivity issues that interrupt store operations. The next step is measurement and architecture validation, not an assumed network replacement.

Indicative complexity

MEDIUM

Suggested priority

NOW

Potential benefit

  • Clearer picture of site-by-site performance
  • Agreed resilience requirements for trading hours
  • Evidence to compare connectivity options
Why we're suggesting this
  • Owner-provided reports of intermittent store connectivity
  • Operational dependency on till and inventory lookups
See today and a potential future

Today

  1. 1Stores experience intermittent disruption during peaks
  2. 2Limited shared visibility of circuit performance across sites

Potential future

  1. 1Measured baselines per site
  2. 2Documented failover expectations
  3. 3Prioritised remediation backlog

What to do next

  1. 1Capture per-site symptoms and business impact windows
  2. 2Inventory current circuits, Wi-Fi and failover
  3. 3Define success criteria before selecting suppliers

NOW

Reduce fragmented customer-contact handling

HIGH OPPORTUNITY

Multiple inbound channels without a shared view create repeated contact risk. Consolidation should follow volume and ownership discovery.

Indicative complexity

MEDIUM

Suggested priority

NOW

Potential benefit

  • Fewer repeated customer contacts
  • Clearer ownership of response
  • Better visibility of open enquiries
Why we're suggesting this
  • Owner-provided channel fragmentation across phone, email, web and marketplace
See today and a potential future

Today

  1. 1Contacts arrive in separate inboxes and tools
  2. 2Store and head-office teams may answer the same customer twice

Potential future

  1. 1Shared queue or CRM view
  2. 2Agreed response ownership
  3. 3Simple reporting on open cases

What to do next

  1. 1Map channel volumes for two trading weeks
  2. 2Confirm accountable owner for customer response
  3. 3Pilot a shared view for the highest-volume channels first

NEXT

Clarify recovery expectations for critical trading services

MEDIUM OPPORTUNITY

Till, ecommerce and stock dependencies are clear from owner context, but RTO/RPO and restore evidence are unknown.

Indicative complexity

REQUIRES SCOPING

Suggested priority

NEXT

Potential benefit

  • Agreed recovery objectives
  • Backup coverage gaps made visible
  • Restore tests scheduled
Why we're suggesting this
  • Owner-stated criticality of till, ecommerce and stock systems
  • No evidenced recovery objectives in the sample pack
See today and a potential future

Today

  1. 1Recovery expectations are informal
  2. 2Restore test evidence is not available in this sample

Potential future

  1. 1Documented RTO/RPO by service
  2. 2Tested restore cadence
  3. 3Clearer continuity ownership

What to do next

  1. 1List critical services and acceptable downtime
  2. 2Confirm current backup coverage
  3. 3Schedule a controlled restore test for the highest-priority system

NEXT

Inventory hosting dependencies before modernisation decisions

MEDIUM OPPORTUNITY

An on-premises server dependency is confirmed by the owner, but wholesale migration is not recommended until the estate and constraints are mapped.

Indicative complexity

HIGH

Suggested priority

NEXT

Potential benefit

  • Complete application/hosting inventory
  • Clear dependency map
  • Evidence-based modernisation options
Why we're suggesting this
  • Owner-provided on-premises server dependency for stock and pricing tools
See today and a potential future

Today

  1. 1Selected tools depend on an older server
  2. 2Hosting topology for other systems is not fully evidenced

Potential future

  1. 1Documented estate map
  2. 2Risk-ranked modernisation candidates
  3. 3Phased options with validation gates

What to do next

  1. 1Inventory applications, hosts and owners
  2. 2Capture change windows and compliance constraints
  3. 3Separate must-stay-on-premises workloads from candidates for change

LATER

Reduce manual weekly trading-pack effort

MEDIUM OPPORTUNITY

Manual consolidation is confirmed. Automation should follow source-of-truth and ownership discovery.

Indicative complexity

MEDIUM

Suggested priority

LATER

Potential benefit

  • Less manual report assembly
  • Consistent KPI definitions
  • Faster trading reviews
Why we're suggesting this
  • Owner-provided manual weekly reporting process
See today and a potential future

Today

  1. 1Staff assemble trading packs from several systems
  2. 2Definitions may differ between extracts

Potential future

  1. 1Agreed KPI definitions
  2. 2Repeatable extract or dashboard
  3. 3Less weekend report assembly

What to do next

  1. 1List source systems and KPI owners
  2. 2Document current pack contents
  3. 3Pilot one automated extract for the highest-effort section

NOW

Establish evidence-led security discovery priorities

REQUIRES MORE INFORMATION

Current controls were not evidenced. Security work should start with discovery of identity, endpoint and monitoring controls — not with unverified vulnerability claims.

Indicative complexity

REQUIRES SCOPING

Suggested priority

NOW

Potential benefit

  • Documented control inventory
  • Prioritised validation backlog
  • Clearer cyber-resilience ownership
Why we're suggesting this
  • Stated business dependency on networked till, stock and customer systems
  • Absence of control evidence in the sample pack
See today and a potential future

Today

  1. 1Control posture is unknown rather than confirmed weak
  2. 2No vulnerability assessment is included in this sample

Potential future

  1. 1Evidence of MFA/identity posture
  2. 2Monitoring and incident-response clarity
  3. 3Validated priority controls

What to do next

  1. 1Confirm identity and MFA arrangements for staff and admin access
  2. 2Inventory endpoint and email security tooling
  3. 3Define incident-response contacts and backup restore ownership

Trust through restraint

Not a priority right now

AI & Automation

No owner evidence in this sample establishes high-volume repetitive processes ready for AI. Revisit after reporting and contact-handling baselines are clearer.

This assessment combines public business information with the information you provide. Recommendations are decision-support and should be reviewed before making significant technology investments.

10–11. Dependencies / risks / questions and NOW / NEXT / LATER action plan

Action Plan

Practical next steps for your opportunities

This plan turns the evidence-led opportunities into validation and sequencing actions. Unknown information remains a discovery task.

NOW

Now

Do these first

NOW

Validate multi-site connectivity performance and resilience

MEDIUM

Why this matters

Store trading depends on reliable connectivity for till and inventory lookups.

What we know

  • 1.Owner reports peak-time disruption
  • 2.Multiple stores plus online channel

What we still need to validate

  • 1.Per-site circuit and failover design
  • 2.Measured latency/packet loss during peaks

Recommended next steps

  • 1.Run a two-week symptom log
  • 2.Inventory WAN/Wi-Fi/failover
  • 3.Agree trading-hour resilience criteria
Dependencies and unresolved questions

Dependencies

  • 1.Site access for measurement
  • 2.ISP/provider inventory

Unresolved questions

  • 1.Which sites are most affected?
  • 2.Is ecommerce fulfilment on the same connectivity path?

NOW

Establish evidence-led security discovery priorities

REQUIRES SCOPING

Why this matters

Networked trading systems create a security priority that requires validation, not assumed weaknesses.

What we know

  • 1.Business depends on networked till, stock and customer systems

What we still need to validate

  • 1.Identity/MFA posture
  • 2.Endpoint and email security tooling
  • 3.Incident-response ownership

Recommended next steps

  • 1.Complete a control inventory interview
  • 2.Confirm admin access paths
  • 3.Document backup restore ownership
Dependencies and unresolved questions

Dependencies

  • 1.IT/security owner availability

Unresolved questions

  • 1.Who owns identity administration today?
  • 2.What monitoring exists, if any?

NOW

Reduce fragmented customer-contact handling

MEDIUM

Why this matters

Fragmented channels increase repeated contact and slow response.

What we know

  • 1.Phone, email, web and marketplace channels are all active

What we still need to validate

  • 1.Two-week channel volumes
  • 2.Current CRM or shared inbox usage

Recommended next steps

  • 1.Map volumes
  • 2.Assign response owner
  • 3.Pilot shared view for top channels
Dependencies and unresolved questions

Dependencies

  • 1.Store and head-office cooperation

Unresolved questions

  • 1.Which channel drives the most rework?

NEXT

Next

Investigate after the immediate priorities

NEXT

Clarify recovery expectations for critical trading services

REQUIRES SCOPING

Why this matters

Without RTO/RPO, continuity investment cannot be prioritised safely.

What we know

  • 1.Till, ecommerce and stock systems are critical to trading

What we still need to validate

  • 1.Backup coverage
  • 2.Last successful restore evidence

Recommended next steps

  • 1.Agree downtime tolerance by service
  • 2.Confirm backup scope
  • 3.Schedule one restore test
Dependencies and unresolved questions

Dependencies

  • 1.Hosting/provider access

Unresolved questions

  • 1.What is acceptable downtime for ecommerce vs till?

NEXT

Inventory hosting dependencies before modernisation decisions

HIGH

Why this matters

On-premises dependency is confirmed, but migration without inventory creates avoidable risk.

What we know

  • 1.Selected stock/pricing tools run on an older server

What we still need to validate

  • 1.Full application inventory
  • 2.Dependency and change constraints

Recommended next steps

  • 1.Build estate map
  • 2.Classify must-stay vs candidates for change
  • 3.Defer migration quotes until inventory exists
Dependencies and unresolved questions

Dependencies

  • 1.Application owners

Unresolved questions

  • 1.Which integrations depend on the on-premises server?

LATER

Later

Revisit as evidence, dependencies or priorities develop

LATER

Reduce manual weekly trading-pack effort

MEDIUM

Why this matters

Manual consolidation consumes management time and introduces inconsistency risk.

What we know

  • 1.Weekly packs are assembled manually from several systems

What we still need to validate

  • 1.KPI definitions
  • 2.Systems of record

Recommended next steps

  • 1.Document pack contents
  • 2.Agree owners
  • 3.Pilot one automated extract
Dependencies and unresolved questions

Dependencies

  • 1.Finance/ops reporting owners

Unresolved questions

  • 1.Which section of the pack takes the most time?

Ready to bring everything together?

Generate a customer report from this same saved evidence context, opportunity plan and action plan. This does not run another AI assessment.

12. Decision-ready summary & final report structure

  • Treat connectivity measurement, customer-contact ownership and security control discovery as immediate priorities.
  • Do not commit to cloud migration or network replacement until inventories and success criteria exist.
  • Keep unknowns visible: recovery objectives and control posture are not yet evidenced.

Final report

Technology Opportunity Assessment

Northbridge Home & Living Ltd

Generated 15/03/2026, 10:00:00

Registration
FICT-88421
Website
https://example-northbridge-home.invalid

1. Executive Summary

Multi-site retail plus online channel is evidenced from public/illustrative website content.

Connectivity, contact fragmentation and manual reporting are owner-confirmed concerns.

Recovery objectives and security controls remain unknown and require validation.

No confirmed security vulnerability is asserted in this sample.

2. Business Priorities

Priorities were not structured in this assessment.

3. Technology Opportunity Map

Validate multi-site connectivity performance and resilience

Owner evidence indicates peak-time connectivity issues that interrupt store operations. The next step is measurement and architecture validation, not an assumed network replacement.

Impact: High impact · Confidence: unknown · Priority: NOW

Reduce fragmented customer-contact handling

Multiple inbound channels without a shared view create repeated contact risk. Consolidation should follow volume and ownership discovery.

Impact: High impact · Confidence: unknown · Priority: NOW

Clarify recovery expectations for critical trading services

Till, ecommerce and stock dependencies are clear from owner context, but RTO/RPO and restore evidence are unknown.

Impact: Medium impact · Confidence: unknown · Priority: NEXT

Inventory hosting dependencies before modernisation decisions

An on-premises server dependency is confirmed by the owner, but wholesale migration is not recommended until the estate and constraints are mapped.

Impact: Medium impact · Confidence: unknown · Priority: NEXT

Reduce manual weekly trading-pack effort

Manual consolidation is confirmed. Automation should follow source-of-truth and ownership discovery.

Impact: Medium impact · Confidence: unknown · Priority: LATER

Establish evidence-led security discovery priorities

Current controls were not evidenced. Security work should start with discovery of identity, endpoint and monitoring controls — not with unverified vulnerability claims.

Impact: Medium impact · Confidence: unknown · Priority: NOW

4. Recommended Solutions

Further discovery

Further discovery required

Evidence is not yet sufficient to recommend a specific product. Catalogue availability alone is not a recommendation.

5. 90-Day Roadmap

NOW

Validate multi-site connectivity performance and resilience

Run a two-week symptom log

Owner to be agreed · Validate during discovery

NOW

Establish evidence-led security discovery priorities

Complete a control inventory interview

Owner to be agreed · Validate during discovery

NOW

Reduce fragmented customer-contact handling

Map volumes

Owner to be agreed · Validate during discovery

NEXT

Clarify recovery expectations for critical trading services

Agree downtime tolerance by service

Owner to be agreed · Validate during discovery

NEXT

Inventory hosting dependencies before modernisation decisions

Build estate map

Owner to be agreed · Validate during discovery

LATER

Reduce manual weekly trading-pack effort

Document pack contents

Owner to be agreed · Validate during discovery

6. Expected Business Outcomes

Outcomes will become clearer as recommendations are validated.

7. Evidence & Assumptions

What we know

  • Multi-site retail plus online channel is evidenced from public/illustrative website content.
  • Connectivity, contact fragmentation and manual reporting are owner-confirmed concerns.
  • Recovery objectives and security controls remain unknown and require validation.
  • No confirmed security vulnerability is asserted in this sample.

  • COMPANY WEBSITE

    2 items

  • OWNER PROVIDED

    5 items

  • AI INFERENCE

    0 items · metadata only

Assumptions & unknowns

  • Illustrative assumption: store locator and ecommerce pages reflect current trading channels.
  • Unknown: measured connectivity performance and failover design.
  • Unknown: formal RTO/RPO and restore test evidence.
  • Requires validation: identity, endpoint, email and monitoring controls.

Limitations

  • SAMPLE — Fictional business. Not professional, legal, security or financial advice.
  • No live customer systems were accessed.
  • No vulnerability scanning or penetration testing was performed.
Technical appendix · evidence reference IDs

r-e2, r-e7, r-e4, r-e6, r-e3, r-e5

SAMPLE — Fictional business

This is illustrative Velnariq output based on a fictional organisation. It is not an assessment of a real company and should not be treated as professional, legal, security or financial advice.

Ready for a personalised assessment?

Your own assessment will use the evidence you provide about your business. Viewing this sample does not create a Stripe charge, consume an assessment allowance or grant entitlement.

Start your assessmentView pricing