Skip to content

Customer Experience

Why This Exists

This document defines the customer experience Algosure must create.

Algosure is not tender software. Algosure is the world's first AI Digital Procurement Company. It gives each customer a Digital Procurement Company made up of Digital Professionals, Practices, Business Capabilities, SOPs, Organizational Memory, AI reasoning, executable workflows, and continuous learning.

The product experience should feel like leading a procurement company, not using software.

Owner

The owner is the Chief Product Officer and Enterprise Architect.

The owner is accountable for ensuring the customer experience reflects the Blueprint and does not collapse into disconnected feature interaction.

Business Value

The customer experience creates business value by making Algosure understandable, trusted, and operationally useful. It helps customers lead procurement work with visibility, structure, accountability, and confidence.

Experience Thesis

Customers are not users. Customers are CEOs of their Digital Procurement Company.

This means the primary experience is leadership:

  • Seeing what the Digital Procurement Company is working on.
  • Understanding priorities and risk.
  • Receiving executive briefings.
  • Approving critical actions.
  • Coordinating Digital Professionals.
  • Monitoring Practice performance.
  • Learning from outcomes.

Digital Procurement Headquarters

The customer enters their Digital Procurement Headquarters.

The headquarters is the organizing experience for the Digital Procurement Company. It should make the system feel like a professional enterprise environment where procurement work is led, coordinated, executed, and improved.

Headquarters area Customer experience
Executive Office The customer receives briefings, approvals, priorities, and executive workflow support.
Board Room The customer reviews strategic decisions, risks, performance, and portfolio direction.
War Room The customer leads urgent or high-value opportunities through focused coordination.
Proposal Studio The customer oversees bid response creation, review, and submission readiness.
Compliance Centre The customer sees compliance status, risks, evidence, and required action.
Marketplace The customer manages supplier context, sourcing intelligence, and supplier relationships.
Academy The customer develops procurement capability and captures learning.
Intelligence Centre The customer reviews opportunity intelligence, analytics, KPIs, and insight.

Leadership Journey

flowchart LR
    Enter[Enter Headquarters]
    Briefing[Review Executive Briefing]
    Prioritize[Set Priorities]
    Coordinate[Coordinate Digital Professionals]
    Approve[Approve Decisions]
    Execute[Monitor Execution]
    Learn[Review Outcomes and Learning]

    Enter --> Briefing
    Briefing --> Prioritize
    Prioritize --> Coordinate
    Coordinate --> Approve
    Approve --> Execute
    Execute --> Learn
    Learn --> Briefing

Executive Briefing Experience

The Executive Briefing should be a central customer experience pattern.

It should answer:

  • What changed since the last briefing?
  • Which opportunities require attention?
  • Which approvals are pending?
  • Which risks are emerging?
  • Which Digital Professionals need direction?
  • Which workflows are blocked?
  • Which KPIs changed?
  • What does Ari recommend?
  • What must the customer decide?

Board Room Experience

The Board Room is for strategic oversight.

It should support:

  • Opportunity portfolio review.
  • Major bid decisions.
  • Compliance and risk governance.
  • Performance review.
  • Investment and funding discussion.
  • Supplier strategy.
  • Learning and capability progress.

The Board Room should make procurement leadership visible and structured.

War Room Experience

The War Room is for focused execution.

It should support:

  • High-priority bids.
  • Deadline-driven coordination.
  • Cross-Practice escalations.
  • Compliance resolution.
  • Proposal readiness.
  • Executive intervention.

The War Room should reduce fragmentation during critical procurement work.

Proposal Studio Experience

The Proposal Studio is the working environment for bid responses.

It should make bid work coordinated across:

  • Atlas for bid management.
  • Orion for business analysis.
  • Lex for compliance.
  • Nova for intelligence.
  • Ava for approvals.
  • Ari for executive coordination.

Compliance Centre Experience

The Compliance Centre should help the customer trust the work.

It should show:

  • Eligibility checks.
  • Submission requirements.
  • Evidence.
  • Risks.
  • Interpretations.
  • Guardrails.
  • Approval requirements.

Lex leads this experience.

Intelligence Centre Experience

The Intelligence Centre should help the customer understand procurement context.

It should show:

  • Opportunity intelligence.
  • Market signals.
  • KPI trends.
  • Business performance.
  • Bid outcomes.
  • Supplier insight.
  • Learning loops.

Nova and Pulse lead major parts of this experience.

Customer Trust Requirements

The customer experience must provide:

Requirement Why it matters
Clear ownership Customers know who or what is accountable.
Clear evidence Customers understand the basis for recommendations.
Clear decisions Customers know what needs approval.
Clear workflow state Customers know where work stands.
Clear memory Customers know what the company has learned.
Clear guardrails Customers know where AI can act and where humans decide.

Scope

This document defines the customer experience at the Blueprint level. It does not define UI layouts, visual design, interaction details, or implementation architecture.